Re: latest rust fails to install
On 25.02.2017 08:19, Kevin Oberman wrote: > On Fri, Feb 24, 2017 at 8:33 AM, tech-lists wrote: >> rust compiles but fails to install. Here's the last couple of pages of >> output, from a machine at FreeBSD 11.0-STABLE #0 r313940 and ports >> r434693. It's like the number after the filename is wrong, so we get >> file not found errors. > > There was a bug opened on this yesterday. Problem seems to be fairly well > understood. Solution... not so much. I ended up installing the package. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217309 Hi! A patch to fix this error is being reviewed: https://reviews.freebsd.org/D9816 Sorry for the breakage. -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/pgpoolAdmin | 3.3.1 | 3.6.0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Facing issue after upgrading Firefox version in Free BSD 9.2 RELEASE not able to launch firefox
Hi , I have upgraded FF version from firefox-esr: 24.3.0_2,1 -> 45.6.0_3,1 in Free BSD 9.2 version using below command in my BSD , "pkg install firefox-esr". After the upgrade I am not able to launch the firefox . When I type firefox below error message is displayed in my terminal , "XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: Shared object "libpixman-1.so.30" not found, required by "libgtk-x11-2.0.so.0" Couldn't load XPCOM. " Please find the below outputs : Output from 'uname -a' : FreeBSD pod1201-client11.ibesa 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Fri Sep 27 03:52:52 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 Output from 'ident /usr/ports/www/firefox/Makefile' : /usr/ports/www/firefox/Makefile: $FreeBSD: head/www/firefox/Makefile 433286 2017-02-04 07:56:59Z jbeich $ Please do let me know what needs to be done for it to work. I am new to BSD as well. Thanks & Regards , Uma ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: New port gitsome
On Sat, Feb 25, 2017 at 09:42:38PM +0100, Olivier Duchateau wrote: > On Sat, 25 Feb 2017 16:48:17 -0300 > "Danilo G. Baio (dbaio)" wrote: > > > On Sat, Feb 25, 2017 at 07:48:05PM +0100, Olivier Duchateau wrote: > > > For py3-* ports, you can look at how audio/py-mutagen and > > > audio/py3-mutagen are build. > > > > > > I don't think, you need to become maintainer of these ports (it's just > > > "copy of"). > > > > > > > Hi Olivier. > > > > I've withdrawn maintainer entry on the new py3-* ports. Patch updated. > > > > And is ok, just one PR for all py3-* ports? > > This question depends of commiter. > > Personally I prefer new patch for each new port. Besides Bugzilla is clever, > you can add an ordered list of dependencies for a given port. > > > > > Regards. > > -- > > Danilo G. Baio (dbaio) > > > -- > olivier But like all py3-* new ports are just a 'copy of' and serves for the same purpose I thought that one patch and one commit will work. I will wait a little longer and if no one agrees with this I will submit one PR for each new py3- port (17). Thank you again. Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: Facing issue after upgrading Firefox version in Free BSD 9.2 RELEASE not able to launch firefox
Uma Somasundaram skrev: > > Hi , > I have upgraded FF version from firefox-esr: 24.3.0_2,1 -> 45.6.0_3,1 in > Free BSD 9.2 version using below command in my BSD , > > "pkg install firefox-esr". > > After the upgrade I am not able to launch the firefox . When I type firefox > below error message is displayed in my terminal , > > > "XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: > Shared object "libpixman-1.so.30" not found, required by > "libgtk-x11-2.0.so.0" > Couldn't load XPCOM. " > > Please find the below outputs : > > Output from 'uname -a' : > > FreeBSD pod1201-client11.ibesa 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: > Fri Sep 27 03:52:52 UTC 2013 > r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC > i386 The FreeBSD version you are running is already EOL: https://lists.freebsd.org/pipermail/freebsd-announce/2016-October/001754.html Upgrade to 10.3 or 11.0 first and then try again. -- Herbert ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Facing issue after upgrading Firefox version in Free BSD 9.2 RELEASE not able to launch firefox
Hi, However your FreeBSD is on EOL (consider migrating to a newer version, at least for the sake of security updates), but I had similar problem on 10.3, I guess the problem is Firefox is updated but some libs that it depends on is not being updated (mine was libdbus, which Firefox needed libdbus-1.so.3 after update, but it was -1.so.2 still). Do a upgrade on your packages/ports, and it'll fix it. -- Best regards, MMokhi. On 2/27/17, Uma Somasundaram wrote: > Hi , > > I have upgraded FF version from firefox-esr: 24.3.0_2,1 -> 45.6.0_3,1 in > Free BSD 9.2 version using below command in my BSD , > > "pkg install firefox-esr". > > After the upgrade I am not able to launch the firefox . When I type firefox > below error message is displayed in my terminal , > > > "XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: > Shared object "libpixman-1.so.30" not found, required by > "libgtk-x11-2.0.so.0" > Couldn't load XPCOM. " > > Please find the below outputs : > > Output from 'uname -a' : > > FreeBSD pod1201-client11.ibesa 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: > Fri Sep 27 03:52:52 UTC 2013 > r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC > i386 > > Output from 'ident /usr/ports/www/firefox/Makefile' : > > /usr/ports/www/firefox/Makefile: > $FreeBSD: head/www/firefox/Makefile 433286 2017-02-04 07:56:59Z jbeich > $ > > Please do let me know what needs to be done for it to work. I am new to BSD > as well. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
How to create a port only for specific FreeBSD releases
Hi to all, I'm trying to make a port which installs only a couple of simple scripts (thus NO_BUILD, NO_ARCH, and void MASTER_SITES and DISTFILES...). Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd like to know if there is a way to prevent the port from installing on older FreeBSD releases. In the Porter's Handbook I found this paragraph, but it seems regarding only ported app's source code: https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html TIA Andrew ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to create a port only for specific FreeBSD releases
On 2017/02/27 14:37, Andrew Hotlab wrote:
> Hi to all, I'm trying to make a port which installs only a couple of
> simple scripts (thus NO_BUILD, NO_ARCH, and void MASTER_SITES and
> DISTFILES...).
>
> Since these scripts are designed to run on FreeBSD 10.0 and newer,
> I'd like to know if there is a way to prevent the port from installing on
> older FreeBSD releases. In the Porter's Handbook I found this paragraph,
> but it seems regarding only ported app's source code:
>
> https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
Well, given that the earliest supported version in ports is now
10.3-RELEASE, this problem appears to have fixed itself for your purposes.
In general, you can test against ${OSVERSION} in your port's Makefile to
detect what OS version the port is being built on, and mark the port as
broken where the OS version is not suitable.
Note however that binary packages are built on the oldest supported
version of the major branch, so by marking the port broken for the OSV,
you will prevent binary packages being available for that entire major
branch. It's best to apply this sort of brokenness determination at the
level of the major version number, rather than anything finer grained.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
[SOLVED] How to create a port only for specific FreeBSD releases
> From: Andrew Hotlab
> Sent: Monday, February 27, 2017 3:37 PM
> To: freebsd-ports@freebsd.org
> Subject: How to create a port only for specific FreeBSD releases
> Hi to all, I'm trying to make a port which installs only a couple of simple
> scripts
> (thus NO_BUILD, NO_ARCH, and void MASTER_SITES and DISTFILES...).
>
> Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd like to
> know if there is a way to prevent the port from installing on older FreeBSD
> releases. In the Porter's Handbook I found this paragraph, but it seems
> regarding
> only ported app's source code:
> https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
Sorry, just found by myself. I included these lines before the do-install
section:
.include
.if ${OSVERSION} < 1000100
IGNORE= runs only on FreeBSD 10.0 and newer
.endif
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
> On 27 Feb, 2017, at 9:07, Andrew Hotlab wrote:
>
>> From: Andrew Hotlab
>> Sent: Monday, February 27, 2017 3:37 PM
>> To: freebsd-ports@freebsd.org
>> Subject: How to create a port only for specific FreeBSD releases
>
>> Hi to all, I'm trying to make a port which installs only a couple of simple
>> scripts
>> (thus NO_BUILD, NO_ARCH, and void MASTER_SITES and DISTFILES...).
>>
>> Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd like
>> to
>> know if there is a way to prevent the port from installing on older FreeBSD
>> releases. In the Porter's Handbook I found this paragraph, but it seems
>> regarding
>> only ported app's source code:
>> https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
>
>
> Sorry, just found by myself. I included these lines before the do-install
> section:
>
> .include
> .if ${OSVERSION} < 1000100
> IGNORE= runs only on FreeBSD 10.0 and newer
> .endif
It's really not needed at all. Nothing below 10.3 is supported, and the ports
system will complain already. Please don't include that block in your port.
# Adam
--
Adam Weinberger
ad...@adamw.org
https://www.adamw.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
Andrew Hotlab wrote:
From: Andrew Hotlab
Sent: Monday, February 27, 2017 3:37 PM
To: freebsd-ports@freebsd.org
Subject: How to create a port only for specific FreeBSD releases
Hi to all, I'm trying to make a port which installs only a couple of simple
scripts
(thus NO_BUILD, NO_ARCH, and void MASTER_SITES and DISTFILES...).
Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd like to
know if there is a way to prevent the port from installing on older FreeBSD
releases. In the Porter's Handbook I found this paragraph, but it seems
regarding
only ported app's source code:
https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
Sorry, just found by myself. I included these lines before the do-install
section:
.include
.if ${OSVERSION} < 1000100
IGNORE= runs only on FreeBSD 10.0 and newer
.endif
IGNORE_FreeBSD_9= This version only for FreeBSD 10+
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
Adam Weinberger wrote:
On 27 Feb, 2017, at 9:07, Andrew Hotlab wrote:
From: Andrew Hotlab
Sent: Monday, February 27, 2017 3:37 PM
To: freebsd-ports@freebsd.org
Subject: How to create a port only for specific FreeBSD releases
Hi to all, I'm trying to make a port which installs only a couple of simple
scripts
(thus NO_BUILD, NO_ARCH, and void MASTER_SITES and DISTFILES...).
Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd like to
know if there is a way to prevent the port from installing on older FreeBSD
releases. In the Porter's Handbook I found this paragraph, but it seems
regarding
only ported app's source code:
https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
Sorry, just found by myself. I included these lines before the do-install
section:
.include
.if ${OSVERSION} < 1000100
IGNORE= runs only on FreeBSD 10.0 and newer
.endif
It's really not needed at all. Nothing below 10.3 is supported, and the ports
system will complain already. Please don't include that block in your port.
# Adam
Thats not true. I have port version just for 9.x and even today I still
see the source file the port fetches still being downloaded.
It has
IGNORE_FreeBSD_10= and IGNORE_FreeBSD_11= in it's Makefile.
Best you have IGNORE_FreeBSD_9= in your Makefile to be sure you get
what you want.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
> From: Adam Weinberger
>
> Sent: Monday, February 27, 2017 5:30 PM
> To: Andrew Hotlab
> Cc: freebsd-ports@freebsd.org
> Subject: Re: [SOLVED] How to create a port only for specific FreeBSD releases
>
>> On 27 Feb, 2017, at 9:07, Andrew Hotlab wrote:
>>
>>> From: Andrew Hotlab
>>> Sent: Monday, February 27, 2017 3:37 PM
>>> To: freebsd-ports@freebsd.org
>>> Subject: How to create a port only for specific FreeBSD releases
>>>
>>> Hi to all, I'm trying to make a port which installs only a couple of simple
>>> scripts
>>> (thus NO_BUILD, NO_ARCH, and void MASTER_SITES and DISTFILES...).
>>>
>>> Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd like
>>> to
>>> know if there is a way to prevent the port from installing on older FreeBSD
>>> releases. In the Porter's Handbook I found this paragraph, but it seems
>>> regarding
>>> only ported app's source code:
>>> https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
>>
>>
>> Sorry, just found by myself. I included these lines before the do-install
>> section:
>>
>> .include
>> .if ${OSVERSION} < 1000100
>> IGNORE= runs only on FreeBSD 10.0 and newer
>> .endif
>
> It's really not needed at all. Nothing below 10.3 is supported, and the ports
> system
> will complain already. Please don't include that block in your port.
>
> # Adam
Thank you Adam, I wrote my previous post before reading Matthew's reply.
I removed that check from my port.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
> From: Ernie Luzar
> Sent: Monday, February 27, 2017 5:43 PM
> To: Adam Weinberger
> Cc: Andrew Hotlab; freebsd-ports@freebsd.org
> Subject: Re: [SOLVED] How to create a port only for specific FreeBSD releases
>
Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd
like to
know if there is a way to prevent the port from installing on older FreeBSD
releases. In the Porter's Handbook I found this paragraph, but it seems
regarding
only ported app's source code:
https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
>>>
>>> Sorry, just found by myself. I included these lines before the do-install
>>> section:
>>>
>>> .include
>>> .if ${OSVERSION} < 1000100
>>> IGNORE= runs only on FreeBSD 10.0 and newer
>>> .endif
>>
>> It's really not needed at all. Nothing below 10.3 is supported, and the
>> ports system will
>> complain already. Please don't include that block in your port.
>>
>> # Adam
>>
>>
> Thats not true. I have port version just for 9.x and even today I still
> see the source file the port fetches still being downloaded.
>
> It has
> IGNORE_FreeBSD_10= and IGNORE_FreeBSD_11= in it's Makefile.
> Best you have IGNORE_FreeBSD_9= in your Makefile to be sure you get
> what you want.
Actually, it seems that Matthew and Adam are right, but I'm not able to
understand if
it's a warn or a block action:
https://svnweb.freebsd.org/ports?view=revision&revision=431746
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
> On 27 Feb, 2017, at 10:00, Andrew Hotlab wrote:
>
>> From: Ernie Luzar
>> Sent: Monday, February 27, 2017 5:43 PM
>> To: Adam Weinberger
>> Cc: Andrew Hotlab; freebsd-ports@freebsd.org
>> Subject: Re: [SOLVED] How to create a port only for specific FreeBSD releases
>>
> Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd
> like to
> know if there is a way to prevent the port from installing on older
> FreeBSD
> releases. In the Porter's Handbook I found this paragraph, but it seems
> regarding
> only ported app's source code:
> https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
Sorry, just found by myself. I included these lines before the do-install
section:
.include
.if ${OSVERSION} < 1000100
IGNORE= runs only on FreeBSD 10.0 and newer
.endif
>>>
>>> It's really not needed at all. Nothing below 10.3 is supported, and the
>>> ports system will
>>> complain already. Please don't include that block in your port.
>>>
>>> # Adam
>>>
>>>
>> Thats not true. I have port version just for 9.x and even today I still
>> see the source file the port fetches still being downloaded.
>>
>> It has
>> IGNORE_FreeBSD_10= and IGNORE_FreeBSD_11= in it's Makefile.
>> Best you have IGNORE_FreeBSD_9= in your Makefile to be sure you get
>> what you want.
>
> Actually, it seems that Matthew and Adam are right, but I'm not able to
> understand if
> it's a warn or a block action:
> https://svnweb.freebsd.org/ports?view=revision&revision=431746
It's a block, but it's overridable.
# Adam
--
Adam Weinberger
ad...@adamw.org
https://www.adamw.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
> From: Adam Weinberger
> Sent: Monday, February 27, 2017 6:05 PM
> To: Andrew Hotlab
> Cc: Ernie Luzar; freebsd-ports@freebsd.org
> Subject: Re: [SOLVED] How to create a port only for specific FreeBSD releases
>
>> On 27 Feb, 2017, at 10:00, Andrew Hotlab wrote:
>>
>>> From: Ernie Luzar
>>> Sent: Monday, February 27, 2017 5:43 PM
>>> To: Adam Weinberger
>>> Cc: Andrew Hotlab; freebsd-ports@freebsd.org
>>> Subject: Re: [SOLVED] How to create a port only for specific FreeBSD
>>> releases
>>>
>> Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd
>> like to
>> know if there is a way to prevent the port from installing on older
>> FreeBSD
>> releases. In the Porter's Handbook I found this paragraph, but it seems
>> regarding
>> only ported app's source code:
>>
>> https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
>
> Sorry, just found by myself. I included these lines before the do-install
> section:
>
> .include
> .if ${OSVERSION} < 1000100
> IGNORE= runs only on FreeBSD 10.0 and newer
> .endif
It's really not needed at all. Nothing below 10.3 is supported, and the
ports system will
complain already. Please don't include that block in your port.
# Adam
>>> Thats not true. I have port version just for 9.x and even today I still
>>> see the source file the port fetches still being downloaded.
>>>
>>> It has
>>> IGNORE_FreeBSD_10= and IGNORE_FreeBSD_11= in it's Makefile.
>>> Best you have IGNORE_FreeBSD_9= in your Makefile to be sure you get
>>> what you want.
>>
>> Actually, it seems that Matthew and Adam are right, but I'm not able to
>> understand if
>> it's a warn or a block action:
>> https://svnweb.freebsd.org/ports?view=revision&revision=431746
>
> It's a block, but it's overridable.
>
Ok, I guess the better way is to let bsd.port.mk do the job for me! :)
Thanks to all you guys!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required
It seems Kodi requires GLIBCXX_3.4.11 /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/ports/multimedia/kodi/work/xbmc-c327c53/tools/depends/native/JsonSchemaBuilder/bin/JsonSchemaBuilder not found I can't find anything in ports or packages which might install GLIBCXX_3.4.11 Anyone got any pointers for me? Or is it broken? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Change system configuration files with port install
Hi to all, I'm working to build a simple port which, after copying a couple of
scripts under ${PREFIX}, leaves to the user the task to set a few variables in
/boot/loader.conf and /etc/rc.conf.
I was wondering if there is a method and (first and foremost) if it's a sane
idea, to make the port apply changes to these system configuration files.
At this time, I output with pkg-message the instructions to change these files.
Thanks.
Andrew
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required
On Monday 27 February 2017 18:54:56 you wrote: > Hi Dave, > > You must deinstall misc/compat9x before install multimedia/kodi. > > When the kodi installation is complete, you can install compat9x port again. Yes, that fixed it. Thanks! I was almost at the solution myself when your email arrived. I was being a bit blind in terms of the relevant file being in the compat hierarchy and had just noticed that. I'd not quite got to the point of thinking of or trying a deinstall of compat9x though. I was just about to try a reinstall of compat9x Doing a pgk delete of compat9x showed only archivers/rar as a dependency. Sadly, I need rar installed so need compat9 too. Both reinstalled safely after the Kodi build/install though. Thanks again. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] How to create a port only for specific FreeBSD releases
On Mon, 27 Feb 2017 10:05:01 -0700 Adam Weinberger wrote
> > On 27 Feb, 2017, at 10:00, Andrew Hotlab wrote:
> >
> >> From: Ernie Luzar
> >> Sent: Monday, February 27, 2017 5:43 PM
> >> To: Adam Weinberger
> >> Cc: Andrew Hotlab; freebsd-ports@freebsd.org
> >> Subject: Re: [SOLVED] How to create a port only for specific FreeBSD
> >> releases
> > Since these scripts are designed to run on FreeBSD 10.0 and newer, I'd
> > like to know if there is a way to prevent the port from installing on
> > older FreeBSD releases. In the Porter's Handbook I found this
> > paragraph, but it seems regarding only ported app's source code:
> >
> >
https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.html
>
> Sorry, just found by myself. I included these lines before the
> do-install section:
> .include
> .if ${OSVERSION} < 1000100
> IGNORE= runs only on FreeBSD 10.0 and newer
> .endif
> >>>
> >>> It's really not needed at all. Nothing below 10.3 is supported, and the
> >>> ports system will complain already. Please don't include that block in
> >>> your port.
> >>> # Adam
> >>>
> >>>
> >> Thats not true. I have port version just for 9.x and even today I still
> >> see the source file the port fetches still being downloaded.
> >>
> >> It has
> >> IGNORE_FreeBSD_10= and IGNORE_FreeBSD_11= in it's Makefile.
> >> Best you have IGNORE_FreeBSD_9= in your Makefile to be sure you get
> >> what you want.
> >
> > Actually, it seems that Matthew and Adam are right, but I'm not able to
> > understand if it's a warn or a block action:
> > https://svnweb.freebsd.org/ports?view=revision&revision=431746
>
> It's a block, but it's overridable.
A big thanks, for not making it /terminal/!
>
> # Adam
>
--chris
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Change system configuration files with port install
On Mon, 27 Feb 2017 19:44:05 + Andrew Hotlab
wrote
> Hi to all, I'm working to build a simple port which, after copying a couple
> of scripts under ${PREFIX}, leaves to the user the task to set a few
> variables in /boot/loader.conf and /etc/rc.conf.
>
>
> I was wondering if there is a method and (first and foremost) if it's a sane
> idea, to make the port apply changes to these system configuration files.
>
>
> At this time, I output with pkg-message the instructions to change these
> files.
>
>
> Thanks.
>
>
> Andrew
Aside from possibly adding filename.sample(s) with example entries.
You've already made the right choice. :-)
--Chris
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required
On Monday 27 February 2017 21:25:08 you wrote: > > Enviar: lunes 27 de febrero de 2017 a las 21:12 > > De: Dave > > Para: freebsd-ports@freebsd.org > > CC: "Carlos Jacobo Puga Medina" > > Asunto: Re: Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version > > GLIBCXX_3.4.11 required > > > > On Monday 27 February 2017 18:54:56 you wrote: > > > Hi Dave, > > > > > > You must deinstall misc/compat9x before install multimedia/kodi. > > > > > > When the kodi installation is complete, you can install compat9x port > > > again. > > > > Yes, that fixed it. Thanks! > > > > I was almost at the solution myself when your email arrived. > > > > I was being a bit blind in terms of the relevant file being in > > the compat hierarchy and had just noticed that. I'd not quite > > got to the point of thinking of or trying a deinstall of compat9x > > though. I was just about to try a reinstall of compat9x > > > > Doing a pgk delete of compat9x showed only archivers/rar as > > a dependency. Sadly, I need rar installed so need compat9 too. > > > > Both reinstalled safely after the Kodi build/install though. > > > > Thanks again. > > > > Unfortunately, build conflicts are not recorded in the resulting package. > > % cd /usr/ports/multimedia/kodi && make -V CONFLICTS_BUILD > compat9x > > misc/compat9x is listed in CONFLICTS_BUILD [0]. So it's a good idea to > manually check the Makefile. > > [0] > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/conflicts.html Thanks Carlos, I wasn't aware of that. Added to my "fix it" armoury :-) (Copied into ports@ list for completeness of solution) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: seamonkey port compiling error
thanks! I end up just installing the package through 'pkg' instead of building through port. afterwards it works fine. -Original Message- From: Dimitry Andric To: Erdos New Cc: freebsd-ports Sent: Sun, Feb 26, 2017 2:06 pm Subject: Re: seamonkey port compiling error On 26 Feb 2017, at 19:55, Erdos New via freebsd-ports wrote: > > i tried to install 'seamonkey' to my freebsd10.1 32-bit system. however, > encountered errors: > root@oblivion:/usr/ports/www/seamonkey # make install > > > install seamonky: > llvm[6]: Compiling IndexBody.cpp for Release build (PIC) > llvm[6]: Compiling IndexDecl.cpp for Release build (PIC) > llvm[6]: Compiling IndexTypeSourceInfo.cpp for Release build (PIC) > llvm[6]: Compiling Indexing.cpp for Release build (PIC) > llvm[6]: Compiling IndexingContext.cpp for Release build (PIC) > llvm[6]: Linking Release Shared Library libclang.so > llvm[6]: Building Release Archive Library libclang.a > gmake[6]: Leaving directory > '/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/tools/libclang' > gmake[6]: Entering directory > '/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/tools/c-index-test' > llvm[6]: Compiling c-index-test.c for Release build > llvm[6]: Linking Release executable c-index-test (without symbols) > /usr/ports/lang/clang36/work/llvm-3.6.2.src/Release/lib/libLLVM-3.6.so: > undefined reference to `futimens@FBSD_1.4' Most likely, you installed a binary package for devel/llvm36. Binary packages are now built on FreeBSD 10.3, the most recent supported version for ports, and this version has introduced a new syscall which your system does not have. The simplest solution is probably to delete the llvm36 port, and rebuild it on your 10.1 system. Then try to rebuild the Seamonkey port and its dependent ports again. Though it would be easiest if you upgraded the system to 10.3. :) -Dimitry ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ graphics/blender| 2.78b | 2.78c +-+ lang/groovy | 2.4.8 | 2.4.9 +-+ multimedia/obs-studio | 17.0.2 | 18.0.0 +-+ net-mgmt/mk-livestatus | 1.2.8p15| 1.2.8p17 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
