Re: security/ipsec-tools files/patch8-utmp.diff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Jan 25, 2012 at 12:13:01AM -0500, Jason Hellenthal thus spake: > >The subject listed port attempts to apply the patch via its $CWD but if $CWD >is not in not within the $MASTERDIR then the patch fails to apply. Please >adjust the following... > >.if ${OSVERSION} < 97 >EXTRA_PATCHES=files/patch8-utmp.diff >.endif > >To: > >.if ${OSVERSION} < 97 >EXTRA_PATCHES=${MASTERDIR}/files/patch8-utmp.diff >.endif > >Or: > >.if ${OSVERSION} < 97 >EXTRA_PATCHES=${.CURDIR}/files/patch8-utmp.diff >.endif > > >Thanks > >-- >;s =; Thanks. Committed! - -jgh - -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBAgAGBQJPH52jAAoJECBZmmNBUNPcjlkIAIHZ+SOfrBB9QQcgzjDkTKuB VQgpWKirFfU9vQJUp7OGGwxQm6/0swQwNQOitMYMK4DCLC+F7FSf05FYqvYU5HvW CWaMkm/Dc2zYVXgHcT3CN1GYK+gB0lRbxPtsZTW7nkWhw6dMdMzJeQb5LRjYMQvd 9Rh6clzM0DlAqSL3GV30kuxXBZw97kCUnDnQgCfPaq+df8QVVXFCYCxy1qlIFBF1 kVHqTCzhkQwlsV24yHVMiI3aPdNJMN4MfVR1Gi379KzWMeKC3fH0EpjKl0rFels8 IzP5PLRsJrXv8yWux4Uw5h6pLRNs4kZEZ74xaWT7jNVEW+Z1IwN4ZEHjUrTqgro= =XA5N -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/ipsec-tools files/patch8-utmp.diff
The subject listed port attempts to apply the patch via its $CWD but if $CWD is not in not within the $MASTERDIR then the patch fails to apply. Please adjust the following... .if ${OSVERSION} < 97 EXTRA_PATCHES=files/patch8-utmp.diff .endif To: .if ${OSVERSION} < 97 EXTRA_PATCHES=${MASTERDIR}/files/patch8-utmp.diff .endif Or: .if ${OSVERSION} < 97 EXTRA_PATCHES=${.CURDIR}/files/patch8-utmp.diff .endif Thanks -- ;s =; pgpc7xhLW8dc8.pgp Description: PGP signature
Re: Request port removal: sysutils/syscp
Thank you, sir! :) On 01/24/2012 01:27 PM, Chris Rees wrote: > Hi Justin, > > On 24 January 2012 17:58, Janketh Jay wrote: >> Hi Team, >> >>I'm the maintainer of the sysutils/syscp port which has been long >> ditched and replaced with sysutils/froxlor. Can someone please remove >> sysutils/syscp from the ports tree as it is old and potentially dangerous? > Done. Thanks! > > Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On 24 January 2012 20:31, Doug Barton wrote: > On 01/24/2012 06:19, Conrad J. Sabatier wrote: >> ===>>> Gathering dependency list for lang/gcc46 from ports >> ===>>> Launching child to update gcc-4.4.7.2008 to >> gcc-4.4.7.20120117 >> lang/gcc46 >> gcc-4.4.7.2008 >> >> (What is the preceding line -- with the ">>" -- and the similar one >> below, supposed to be indicating exactly? If it means what I think it >> does, then it seems as if portmaster is misinterpreting the intention >> of the "-o" option) > > No, it means that the ports framework is seeing 4.4 as a dependency of > 4.6 for some reason. I've seen that happen in the past when non-base gcc > was in use, but have never had anyone track down the cause > authoritatively. Obviously make.conf is a suspect, but I'm assuming you > already looked there. Often happens when people stick USE_something into make.conf :) (don't do that) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On 01/24/2012 13:18, Conrad J. Sabatier wrote: > Yes, using origin designators in both places worked. Is this an > unwritten requirement in the case of the -o option? No, usually it works with the package name as the second argument (or even a glob pattern as long as it resolves to a unique package name). Like I said, the way that the ports framework handles gcc seems to do things that confuse portmaster. I'm not saying that it's doing anything wrong, it's just different. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On Tue, 24 Jan 2012 12:31:54 -0800 Doug Barton wrote: > On 01/24/2012 06:19, Conrad J. Sabatier wrote: > > ===>>> Gathering dependency list for lang/gcc46 from ports > > ===>>> Launching child to update gcc-4.4.7.2008 to > > gcc-4.4.7.20120117 > > lang/gcc46 >> gcc-4.4.7.2008 > > > > (What is the preceding line -- with the ">>" -- and the similar one > > below, supposed to be indicating exactly? If it means what I think > > it does, then it seems as if portmaster is misinterpreting the > > intention of the "-o" option) > > No, it means that the ports framework is seeing 4.4 as a dependency of > 4.6 for some reason. I've seen that happen in the past when non-base > gcc was in use, but have never had anyone track down the cause > authoritatively. Obviously make.conf is a suspect, but I'm assuming > you already looked there. > > What you probably have to do is pkg_delete -f 4.4, then do the same > portmaster -o command but with 'lang/gcc44' as the second argument. Yes, using origin designators in both places worked. Is this an unwritten requirement in the case of the -o option? Anyway, moving merrily along... :-) Thanks! -- Conrad J. Sabatier conr...@cox.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On 01/24/2012 06:19, Conrad J. Sabatier wrote: > ===>>> Gathering dependency list for lang/gcc46 from ports > ===>>> Launching child to update gcc-4.4.7.2008 to > gcc-4.4.7.20120117 > lang/gcc46 >> gcc-4.4.7.2008 > > (What is the preceding line -- with the ">>" -- and the similar one > below, supposed to be indicating exactly? If it means what I think it > does, then it seems as if portmaster is misinterpreting the intention > of the "-o" option) No, it means that the ports framework is seeing 4.4 as a dependency of 4.6 for some reason. I've seen that happen in the past when non-base gcc was in use, but have never had anyone track down the cause authoritatively. Obviously make.conf is a suspect, but I'm assuming you already looked there. What you probably have to do is pkg_delete -f 4.4, then do the same portmaster -o command but with 'lang/gcc44' as the second argument. hth, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Request port removal: sysutils/syscp
Hi Justin, On 24 January 2012 17:58, Janketh Jay wrote: > Hi Team, > > I'm the maintainer of the sysutils/syscp port which has been long > ditched and replaced with sysutils/froxlor. Can someone please remove > sysutils/syscp from the ports tree as it is old and potentially dangerous? Done. Thanks! Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/16440: commit references a PR
The following reply was made to PR ports/16440; it has been noted by GNATS. From: dfil...@freebsd.org (dfilter service) To: bug-follo...@freebsd.org Cc: Subject: Re: ports/16440: commit references a PR Date: Tue, 24 Jan 2012 19:15:26 + (UTC) scheidell2012-01-24 19:15:15 UTC FreeBSD ports repository Modified files: audio/shoutcast Makefile distinfo pkg-plist audio/shoutcast/files pkg-message.in shoutcast.in Log: - Update to 2.0.0.29. - Bump from beta (build 14) to release (build 29) - Resolve oddities surrounding PLIST_SUB and SUB_LIST (thanks Michael and Gabor) - Update pkg-plist to reflect updated documentation - Support creation of both sc_serv.log and sc_w3c.log on startup PR: ports/16440 Approved by:gabor (mentor) Revision ChangesPath 1.22 +11 -10ports/audio/shoutcast/Makefile 1.9 +2 -2 ports/audio/shoutcast/distinfo 1.4 +1 -1 ports/audio/shoutcast/files/pkg-message.in 1.3 +15 -12ports/audio/shoutcast/files/shoutcast.in 1.4 +3 -1 ports/audio/shoutcast/pkg-plist ___ cvs-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_add -r kde - binary doesn't exist
Raphael Kubo da Costa wrote: > Redirecting the mail to po...@freebsd.org -- the KDE on FreeBSD team > does not maintain KDE3 anymore, so you have better chances of success > here :) > > _ writes: > >> Hi, >> >> Just wanted to inform you that I tried to install kde3 as a binary the >> other day. >> >> Running both: >> >> # pkg_add -r kde >> >> and >> >> # pkg_add -r kde3 >> >> gives me an error message, saying that it doesn't exist on the FreeBSD ftp >> server. >> >> I don't wanna install it from the ports, since this takes forever! >> >> Could somebody upload it again? I think, I found some KDE Binaries here: ftp://ftp7.de.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/ Not the META-packages, but some kde stuff (3 and 4). export these variables in your /etc/profile: PACKAGESITE=ftp://ftp7.de.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/ PKG_SITES=ftp://ftp7.de.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/ export PACKAGESITE PKG_SITES Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Request port removal: sysutils/syscp
Hi Team, I'm the maintainer of the sysutils/syscp port which has been long ditched and replaced with sysutils/froxlor. Can someone please remove sysutils/syscp from the ports tree as it is old and potentially dangerous? Regards, Janky Jay, III ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On Tue, 24 Jan 2012 08:57:14 -0800 Kevin Oberman wrote: > On Tue, Jan 24, 2012 at 7:14 AM, Conrad J. Sabatier > wrote: > > On Tue, 24 Jan 2012 09:21:05 -0500 > > Michael Scheidell wrote: > >> > >> On 1/24/12 9:19 AM, Conrad J. Sabatier wrote: > >> > # portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 > >> > > >> what happens with: > >> > >> # portmaster -CK -o lang/gcc46 lang/gcc44 > >> > >> ? > > > > Well, since gcc44 is no longer installed, I just tried: > > > > portmaster -o lang/gcc47 lang/gcc46 > > > > And the actions that started were much more along the lines of what > > I was expecting. The build of gcc47 is currently underway as I > > write this. > > > > So, it seems it's not a good idea to "mix and match" port origins > > with port names in the case of this particular option. Could this > > be considered a "bug"? It certainly seems to at least qualify as a > > "quirk", I would say. :-) > > > > -- > > Conrad J. Sabatier > > conr...@cox.net > > I wanted to note is that you installed lang/gcc46, the development > version of the compiler. It gets updated very frequently and you may > want this, but it is probably better for most people to install > lang/gcc which is the stable version of gcc-4.6. It gets updated only > when a new gcc-4.6 version is released, so it does not get updated > nearly so often. Posts that depend on USE_FORTRAN or USE_GCC=4.6+ will > both be happy with lang/gcc, though they will pull in the development > version if no gcc-4.6 is installed. Yes, I do recall now a lot of talk about 4.6 being subject to frequent change. Slipped my mind there for a bit. :-) I think I will back off to the other version. I mainly was interested in getting up to the minimum version needed to truly support my AMD Phenom 9550 processor (-march=amdfam10) the same way Clang does. Thanks for that info. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On Tue, Jan 24, 2012 at 7:14 AM, Conrad J. Sabatier wrote: > On Tue, 24 Jan 2012 09:21:05 -0500 > Michael Scheidell wrote: >> >> On 1/24/12 9:19 AM, Conrad J. Sabatier wrote: >> > # portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 >> > >> what happens with: >> >> # portmaster -CK -o lang/gcc46 lang/gcc44 >> >> ? > > Well, since gcc44 is no longer installed, I just tried: > > portmaster -o lang/gcc47 lang/gcc46 > > And the actions that started were much more along the lines of what I > was expecting. The build of gcc47 is currently underway as I write > this. > > So, it seems it's not a good idea to "mix and match" port origins with > port names in the case of this particular option. Could this be > considered a "bug"? It certainly seems to at least qualify as a > "quirk", I would say. :-) > > -- > Conrad J. Sabatier > conr...@cox.net I wanted to note is that you installed lang/gcc46, the development version of the compiler. It gets updated very frequently and you may want this, but it is probably better for most people to install lang/gcc which is the stable version of gcc-4.6. It gets updated only when a new gcc-4.6 version is released, so it does not get updated nearly so often. Posts that depend on USE_FORTRAN or USE_GCC=4.6+ will both be happy with lang/gcc, though they will pull in the development version if no gcc-4.6 is installed. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_add -r kde - binary doesn't exist
On 1/24/12 10:39 AM, Raphael Kubo da Costa wrote: Redirecting the mail to po...@freebsd.org -- the KDE on FreeBSD team does not maintain KDE3 anymore, so you have better chances of success here :) _ writes: Hi, Just wanted to inform you that I tried to install kde3 as a binary the other day. maybe someone here has it in a tinderbox somewhere. what OS version, mach do you need? (output from uname -a) or, maybe someone with a tinderbox would compile it for you for beer credits. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 >*| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_add -r kde - binary doesn't exist
Redirecting the mail to po...@freebsd.org -- the KDE on FreeBSD team does not maintain KDE3 anymore, so you have better chances of success here :) _ writes: > Hi, > > Just wanted to inform you that I tried to install kde3 as a binary the > other day. > > Running both: > > # pkg_add -r kde > > and > > # pkg_add -r kde3 > > gives me an error message, saying that it doesn't exist on the FreeBSD ftp > server. > > I don't wanna install it from the ports, since this takes forever! > > Could somebody upload it again? > > Regards ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On Tue, 24 Jan 2012 09:21:05 -0500 Michael Scheidell wrote: > > On 1/24/12 9:19 AM, Conrad J. Sabatier wrote: > > # portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 > > > what happens with: > > # portmaster -CK -o lang/gcc46 lang/gcc44 > > ? Well, since gcc44 is no longer installed, I just tried: portmaster -o lang/gcc47 lang/gcc46 And the actions that started were much more along the lines of what I was expecting. The build of gcc47 is currently underway as I write this. So, it seems it's not a good idea to "mix and match" port origins with port names in the case of this particular option. Could this be considered a "bug"? It certainly seems to at least qualify as a "quirk", I would say. :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On 1/24/12 9:19 AM, Conrad J. Sabatier wrote: # portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 what happens with: # portmaster -CK -o lang/gcc46 lang/gcc44 ? -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 >*| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
"portmaster -o" behaves a little strangely (IMHO)
The behavior of portmaster with "-o " (as the man page puts it), doesn't seem to be quite what one would expect. While endeavoring to upgrade the already installed lang/gcc44 to lang/gcc46 using the command: portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 (I had already built, but not installed, gcc46, and didn't want any cleaning done before or after, just in case something went wrong) I got some rather unexpected results -- namely that, besides installing gcc46, portmaster wanted to do a normal upgrade of lang/gcc44 within its own directory (from version 4.4.7.2008 to 4.4.7.20120117). Only after adding the "-i" (interactive) option to the command line and answering the prompts did I get the desired operation, a direct upgrade of gcc44 to gcc46. I'm still in the process of acclimating myself to using portmaster, having used portupgrade for years (yes, I know, I'm a little late to the dance), so please bear with me if I'm coming across as a little dense, but... Is this the intended behavior? It strikes me as a little peculiar, portmaster's wanting to perform an entirely unnecessary (and unrequested) operation (the upgrade of the original port within its own directory). It seems to render the automated performance of this type of "third party" upgrade impossible. I'm really not grasping the logic of this arrangement. # portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 ===>>> Port directory: /usr/ports/lang/gcc46 ===>>> Gathering dependency list for lang/gcc46 from ports ===>>> Launching child to update gcc-4.4.7.2008 to gcc-4.4.7.20120117 lang/gcc46 >> gcc-4.4.7.2008 (What is the preceding line -- with the ">>" -- and the similar one below, supposed to be indicating exactly? If it means what I think it does, then it seems as if portmaster is misinterpreting the intention of the "-o" option) ===>>> Port directory: /usr/ports/lang/gcc44 ===>>> Gathering dependency list for lang/gcc44 from ports ===>>> Initial dependency check complete for lang/gcc44 lang/gcc46 >> gcc-4.4.7.2008 ===>>> Continuing initial dependency check for lang/gcc46 ===>>> Initial dependency check complete for lang/gcc46 ===>>> The following actions will be taken if you choose to proceed: Install lang/gcc46 Upgrade gcc-4.4.7.2008 to gcc-4.4.7.20120117 ===>>> Proceed? y/n [y] (answered no here) ===>>> If you would like to upgrade or install some, but not all of the above try adding '-i' to the command line. Sign me "Confused". :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [patch] devel/py-lxml: compile at 10-CURRENT
Hi, Boris! Boris Samorodov wrote on 24.01.2012 12:58: Hi! There is an error while compiling devel/py-lxml at 10-CURRENT: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120114180333/py27-lxml-2.3.2.log I managed to compile the port with the following patch, but I'm sure there is a proper way to do it. Here is the patch: - --- src/lxml/lxml.etree.c.orig 2012-01-24 12:46:24.844235483 +0400 +++ src/lxml/lxml.etree.c 2012-01-24 12:45:28.653235337 +0400 @@ -1,5 +1,7 @@ /* Generated by Cython 0.15.1 on Fri Nov 11 16:39:03 2011 */ +#include + #define PY_SSIZE_T_CLEAN #include "Python.h" #ifndef Py_PYTHON_H - Nice, i'll check it. It's better then patching both py-lxml and libxslt anyway. Btw, did you read this related thread by avg@: http://lists.freebsd.org/pipermail/freebsd-python/2012-January/003825.html May be you have some thoughts about proper way. -- Regards, Ruslan Tinderboxing kills... the drives. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[patch] devel/py-lxml: compile at 10-CURRENT
Hi! There is an error while compiling devel/py-lxml at 10-CURRENT: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120114180333/py27-lxml-2.3.2.log I managed to compile the port with the following patch, but I'm sure there is a proper way to do it. Here is the patch: - --- src/lxml/lxml.etree.c.orig 2012-01-24 12:46:24.844235483 +0400 +++ src/lxml/lxml.etree.c 2012-01-24 12:45:28.653235337 +0400 @@ -1,5 +1,7 @@ /* Generated by Cython 0.15.1 on Fri Nov 11 16:39:03 2011 */ +#include + #define PY_SSIZE_T_CLEAN #include "Python.h" #ifndef Py_PYTHON_H - -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: boost 1.48.0
On Tue, Jan 24, 2012 at 10:05:54AM +0200, Andriy Gapon wrote: > on 23/01/2012 23:25 Baptiste Daroussin said the following: > > I agree this was a fast patching to be able to use it for libreoffice, we > > should for have a closer look at it. > > And, just in case, what I did was put the following line into > tools/build/v2/user-config.jam: > using gcc : 4.6 : g++46 ; > > But this is not flexible enough, it seems. From what I've looked at this is the right solution: modifying user-config.jam, we should just be able to do it a flexible way :) regards, Bapt pgphJ9MNllL7H.pgp Description: PGP signature
Re: databases/mysql55-server and DISABLE_CONFLICTS
Alex Dupre wrote on 24.01.2012 07:55: Marco Steinbach ha scritto: shouldn't I be able to fetch distfiles for conflicting ports, if DISABLE_CONFLICTS is set ? Yes, but in this case you should also set -DNO_IGNORE That did the trick -- thank you. MfG Coco ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: boost 1.48.0
on 23/01/2012 23:25 Baptiste Daroussin said the following: > I agree this was a fast patching to be able to use it for libreoffice, we > should for have a closer look at it. And, just in case, what I did was put the following line into tools/build/v2/user-config.jam: using gcc : 4.6 : g++46 ; But this is not flexible enough, it seems. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: boost 1.48.0
on 23/01/2012 23:25 Baptiste Daroussin said the following: > I agree this was a fast patching to be able to use it for libreoffice, we > should for have a closer look at it. Yeah. BTW, I can confirm that with this version of boost I can now build libreoffice with gcc 4.6. The only change I had to make was in desktop/unx/source/makefile.mk - I had to add this line near the end: APP1STDLIBS+= -lstdc++ -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"