net/samba-libsmbclient SAMBA_PORT= -> SAMBA_PORT?=
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Timur, Could you please change the SAMBA_PORT= directive in samba-libsmbclient to SAMBA_PORT?= samba34 so it can be overridden by make.conf or command line ? There is probably some bad magic that will happen on a machine with samba35 installed and libsmbclient34 and I would like to stay as close as I can to using the same version of samba that's installed and making the above corrections would still allow for the current functionality to be kept while allowing an override. Specifically I would like to stay away from having to edit anything in the ports structure Makefiles as those changes would not be static across port snaps. Thanks in advance. - -- jhell -BEGIN PGP SIGNATURE- Comment: THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND Comment: ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE Comment: IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE Comment: ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE Comment: FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL Comment: DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS Comment: OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) Comment: HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT Comment: LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY Comment: OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF Comment: SUCH DAMAGE. iQEcBAEBAgAGBQJNbIg9AAoJEJBXh4mJ2FR+M1kH/iVXErTNcK9G8ZYydTst2ihD 7sCAl6yhjfRlO7NIzdOMBbisfe8yY4yM6v1npFqHuFfF29GbfFR7CJ3ElGswlI0p Vx5iyStsDzpXr/aT4T0Tc9KyRdm+ZCLd+mIhuhL82l8JoEkhw6u8tlZ4mkVBE+Hx 5dHphmUizqeXEyjqs9e0YCcgR5M15hOHmD8gBwH4xLXgMLeIC3+zJd8vkd52S7yk ShEdqhJQmaTnOxbZYPXihVfJtaPxFjCsfBgi4zBs3mnBstv4izNAS1nhRIfAYXXP SLcgPZje1A3m5KPUQfWiwNwY0/YtPpvpRWlQ2uxHmmPdGbShj+miSLzWAtznOeA= =ypF4 -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"
Re: SIGBUS running `gpg-agent --daemon`
On 2/28/2011 8:00 PM, Yuri Pankov wrote: Hi, Guys, I'm getting the same SIGBUS when running `gpg-agent --daemon` as you discussed on cvs-ports@ list. I'm not sure about the fix, so I have created the entry in gnupg bugtracker: https://bugs.g10code.com/gnupg/issue1320 Thanks, hopefully they can help you better. I've tested it now on 9-current and 8.1-RELEASE and can't make it fail. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go 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: multiple definition of `__i686.get_pc_thunk.bx'
Stephen Montgomery-Smith wrote: b. f. wrote: On Sun 27 Feb 2011 at 12:24:06 PST Stephen Montgomery-Smith wrote: I am the maintainer of the port vis5d+. I just got this email (copied below) saying that vis5d+ isn't building right now. The issue seems to be that some reference to __i686.get_pc_thunk.bx is included twice at some point. This variable seems to be part of an object file crtbeginS.o that is created by gcc or gcc45, in what seem to me to be very mysterious conditions. I am rather sure that the issue has nothing to do with vis5d+, but rather is something to do with either gcc45, or libtools, neither of which I understand. Does anyone out there have any idea of what the problem is, or how it can be solved? From a relatively cursory examination, this appears to be a flaw in the USE_FORTRAN=yes stanza. This will bring in gcc45 as a dependency but doesn't appear to be setting CXX to g++45 though it does do CC=gcc45. Possibly the same for LD, though I haven't checked that. As is clear from bsd.gcc.mk, in almost every case now in use, USE_FORTRAN sets _USE_GCC, which sets CC, CPP, and CXX to the proper values. Also, it sets USE_BINUTILS where appropriate, which sets LD, etc. The problem is rather with libtool, particularly in the link mode, where it may not respect the choice of compiler and toolchain. This problem has been remarked, for two years or more, in the mailing lists and forums, when people discuss the use of compilers other than the base system compiler. With the recent updates, it is more obtrusive, and several ports that were building successfully with default settings are now broken. This needs to be fixed, and it would be better to fix libtool than to add a bunch of ad-hoc fixes to individual ports. b. I agree. libtool is the real culprit. When you run it as libtool -mode=link g++45 stuff and stuff libtool uses c++ instead of g++45. OK, this problem was more subtle than I originally thought. The error I pointed out doesn't occur consistently, but it does occur in the context of building vis5d+. But I have a patch that definitely fixes libtool enough for me. What do you guys think? This perhaps doesn't fix all the problems, but maybe it can act as a model to fix them all. --- configure.bak 2010-09-22 14:44:17.0 + +++ configure 2011-03-01 04:23:35.0 + @@ -27526,7 +27526,9 @@ old_archive_cmds=$lt_old_archive_cmds # A language specific compiler. -CC=$lt_compiler +if test -z "\$CC"; then \\ + CC=$lt_compiler +fi # Is the compiler the GNU compiler? with_gcc=$GCC @@ -27872,7 +27874,11 @@ old_archive_cmds=$lt_old_archive_cmds_CXX # A language specific compiler. -CC=$lt_compiler_CXX +if test -z "\$CXX"; then \\ + CC=$lt_compiler_CXX +else + CC=\$CXX +fi # Is the compiler the GNU compiler? with_gcc=$GCC_CXX ___ 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"
SIGBUS running `gpg-agent --daemon`
Hi, Guys, I'm getting the same SIGBUS when running `gpg-agent --daemon` as you discussed on cvs-ports@ list. I'm not sure about the fix, so I have created the entry in gnupg bugtracker: https://bugs.g10code.com/gnupg/issue1320 JFYI, Yuri ___ 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: xz
On Mon, Feb 28, 2011 at 04:31:27PM -0600, ajtiM wrote: > Than If I run: > portmaster -e xz-5.0.0 > ===>>> Warning: Ports with dependencies on xz-5.0.0: > k9copy-2.3.4_4 > kde4-4.5.5_1 > kdebase-4.5.5 > kdenetwork-4.5.5_2 > kdesdk-4.5.5_1 > kdeutils-4.5.5_2 > kdevelop-4.1.0_2 > kdevelop-pg-qt-0.9.0 > kmplayer-kde4-0.11.2b,3 > konq-plugins-4.4.0 > kuickshow-0.9.1.4.4.0_1 > kwebkitpart-0.9.6.b1_1 > rpm2cpio-1.3_1 > > ===>>> Delete this dependency data? y/n [n] > > ...and what I don't know is do I need to press yes or no, please? Tell it yes. Press y. Portmaster should do the right thing for you. -- Scott LambertKC5MLE Unix SysAdmin lamb...@lambertfam.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: xz
Thank you. BTW: this problem exist more than one year. Sent from my HTC Inspire™ 4G on AT&T - Reply message - From: "Rene Ladan" To: "ajtiM" Cc: Subject: xz Date: Mon, Feb 28, 2011 16:46 Op 28-02-2011 23:31, ajtiM schreef: > Hi! > > Today I tried to run portmaster -ad on FreeBSD 8.2 and I got: > portmaster -ad > ===>>> Gathering distinfo list for installed ports > > ===>>> Starting check of installed ports for available updates > ===>>> Launching child to update xz-5.0.0 to xz-5.0.1 > > ===>>> Port directory: /usr/ports/archivers/xz > > ===>>> This port is marked IGNORE > ===>>> is already in the base system > > ===>>> If you are sure you can build it, remove the >IGNORE line in the Makefile and try again. > > ===>>> Update for xz-5.0.0 failed > ===>>> Aborting update > > Than If I run: > portmaster -e xz-5.0.0 > ===>>> Warning: Ports with dependencies on xz-5.0.0: > k9copy-2.3.4_4 > kde4-4.5.5_1 > kdebase-4.5.5 > kdenetwork-4.5.5_2 > kdesdk-4.5.5_1 > kdeutils-4.5.5_2 > kdevelop-4.1.0_2 > kdevelop-pg-qt-0.9.0 > kmplayer-kde4-0.11.2b,3 > konq-plugins-4.4.0 > kuickshow-0.9.1.4.4.0_1 > kwebkitpart-0.9.6.b1_1 > rpm2cpio-1.3_1 > > ===>>> Delete this dependency data? y/n [n] > > ...and what I don't know is do I need to press yes or no, please? > > xz is really in the base system on 8.2 (and 8.1) as /usr/bin/xz, so the port dependencies are wrong. It should be safe to delete the xz-5.0.0 port, and make a symlink from /usr/local/bin/xz to /usr/bin/xz as a temporary workaround to fool the dependent ports. Regards, René -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.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: xz
Op 28-02-2011 23:31, ajtiM schreef: > Hi! > > Today I tried to run portmaster -ad on FreeBSD 8.2 and I got: > portmaster -ad > ===>>> Gathering distinfo list for installed ports > > ===>>> Starting check of installed ports for available updates > ===>>> Launching child to update xz-5.0.0 to xz-5.0.1 > > ===>>> Port directory: /usr/ports/archivers/xz > > ===>>> This port is marked IGNORE > ===>>> is already in the base system > > ===>>> If you are sure you can build it, remove the >IGNORE line in the Makefile and try again. > > ===>>> Update for xz-5.0.0 failed > ===>>> Aborting update > > Than If I run: > portmaster -e xz-5.0.0 > ===>>> Warning: Ports with dependencies on xz-5.0.0: > k9copy-2.3.4_4 > kde4-4.5.5_1 > kdebase-4.5.5 > kdenetwork-4.5.5_2 > kdesdk-4.5.5_1 > kdeutils-4.5.5_2 > kdevelop-4.1.0_2 > kdevelop-pg-qt-0.9.0 > kmplayer-kde4-0.11.2b,3 > konq-plugins-4.4.0 > kuickshow-0.9.1.4.4.0_1 > kwebkitpart-0.9.6.b1_1 > rpm2cpio-1.3_1 > > ===>>> Delete this dependency data? y/n [n] > > ...and what I don't know is do I need to press yes or no, please? > > xz is really in the base system on 8.2 (and 8.1) as /usr/bin/xz, so the port dependencies are wrong. It should be safe to delete the xz-5.0.0 port, and make a symlink from /usr/local/bin/xz to /usr/bin/xz as a temporary workaround to fool the dependent ports. Regards, René -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.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"
xz
Hi! Today I tried to run portmaster -ad on FreeBSD 8.2 and I got: portmaster -ad ===>>> Gathering distinfo list for installed ports ===>>> Starting check of installed ports for available updates ===>>> Launching child to update xz-5.0.0 to xz-5.0.1 ===>>> Port directory: /usr/ports/archivers/xz ===>>> This port is marked IGNORE ===>>> is already in the base system ===>>> If you are sure you can build it, remove the IGNORE line in the Makefile and try again. ===>>> Update for xz-5.0.0 failed ===>>> Aborting update Than If I run: portmaster -e xz-5.0.0 ===>>> Warning: Ports with dependencies on xz-5.0.0: k9copy-2.3.4_4 kde4-4.5.5_1 kdebase-4.5.5 kdenetwork-4.5.5_2 kdesdk-4.5.5_1 kdeutils-4.5.5_2 kdevelop-4.1.0_2 kdevelop-pg-qt-0.9.0 kmplayer-kde4-0.11.2b,3 konq-plugins-4.4.0 kuickshow-0.9.1.4.4.0_1 kwebkitpart-0.9.6.b1_1 rpm2cpio-1.3_1 ===>>> Delete this dependency data? y/n [n] ...and what I don't know is do I need to press yes or no, please? Mitja http://jpgmag.com/people/lumiwa ___ 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: pr 155131
On Mon, Feb 28, 2011 at 04:26:12PM -0500, Dean Freeman wrote: > the distinfo portion of my udiff should be removed from the patch i supplied > earlier for the DAQ port. Apparently the tarball got garbled slightly on > Sourceforge earlier and that's why the file size was off. We re-uploaded > and the file size and sha256 hash are back to being normal. Just to be clear, the patch at [1] is the one you wish to be applied? If so I do want to bring to your attention that a BUILD_DEPENDS addition does not warrant a PORTREVISION bump as it doesn't affect the package or is a feature that requires people to rebuild. I'll go ahead and work on getting this in the tree shortly... -- WXS [1]: http://www.freebsd.org/cgi/query-pr.cgi?prp=155131-3-diff&n=/patch-3.diff ___ 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: xf86-video-ati 6.14.0 crashes System
On 2011-Feb-27 20:50:03 +, Christian Weisgerber wrote: >Also reported by me for the ATI Radeon RV370 X300 SE and somebody >else for a differently branded card with the same chip. Breaks my ATI Technologies Inc RV380 [Radeon X600 (PCIE)] as well. I have discovered that disabling DRI or acceleration makes it work (though that's not really a solution). But I guess it wouldn't be an "upgrade" from the X.org Consortium without some arbitrary and unnecessary regression. With Option "Log" "sync", the tail end of the X.org log looks like: (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xe7ffe000 0x1fff (II) RADEON(0): MC_AGP_LOCATION : 0xffc0 (==) RADEON(0): Backing store disabled (II) RADEON(0): [DRI] installation complete >As a workaround, install the version 6.13 driver. A separate port >has been created for it. > ># portupgrade -o x11-drivers/xf86-video-ati613 xf86-video-ati This works for me as long as DynamicPM is left disabled. Enabling it also causes a hard lockup. -- Peter Jeremy pgpKGcDgaMqQU.pgp Description: PGP signature
pr 155131
the distinfo portion of my udiff should be removed from the patch i supplied earlier for the DAQ port. Apparently the tarball got garbled slightly on Sourceforge earlier and that's why the file size was off. We re-uploaded and the file size and sha256 hash are back to being normal. -- Dean Freeman Research Analyst, Sourcefire VRT ___ 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: multiple definition of `__i686.get_pc_thunk.bx'
b. f. wrote:
On Sun 27 Feb 2011 at 12:24:06 PST Stephen Montgomery-Smith wrote:
I am the maintainer of the port vis5d+. I just got this email (copied below)
saying that vis5d+ isn't building right now.
The issue seems to be that some reference to __i686.get_pc_thunk.bx is included
twice at some point. This variable seems to be part of an object file
crtbeginS.o that is created by gcc or gcc45, in what seem to me to be very
mysterious conditions. I am rather sure that the issue has nothing to do with
vis5d+, but rather is something to do with either gcc45, or libtools, neither
of which I understand.
Does anyone out there have any idea of what the problem is, or how it can be
solved?
From a relatively cursory examination, this appears to be a flaw in the
USE_FORTRAN=yes stanza. This will bring in gcc45 as a dependency but doesn't
appear to be setting CXX to g++45 though it does do CC=gcc45. Possibly the
same for LD, though I haven't checked that.
As is clear from bsd.gcc.mk, in almost every case now in use,
USE_FORTRAN sets _USE_GCC, which sets CC, CPP, and CXX to the proper
values. Also, it sets USE_BINUTILS where appropriate, which sets LD,
etc. The problem is rather with libtool, particularly in the link
mode, where it may not respect the choice of compiler and toolchain.
This problem has been remarked, for two years or more, in the mailing
lists and forums, when people discuss the use of compilers other than
the base system compiler. With the recent updates, it is more
obtrusive, and several ports that were building successfully with
default settings are now broken. This needs to be fixed, and it would
be better to fix libtool than to add a bunch of ad-hoc fixes to
individual ports.
b.
I agree. libtool is the real culprit. When you run it as
libtool -mode=link g++45 stuff and stuff
libtool uses c++ instead of g++45. I think it would be a relatively
easy fix to make to libtool. I will even have a go at it myself if
no-one else takes the baton, but I think it would be far easier for
someone who knows libtool to do it.
By the way, my proposed bandaid fix is this:
ln -s /usr/local/bin/gcc45 ${WRKDIR}/cc
ln -s /usr/local/bin/g++45 ${WRKDIR}/c++
MAKE_ENV += PATH=${WRKDIR}:$$PATH
which could be put into bsd.gcc.mk. But it really is a very bad hack.
___
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: multiple definition of `__i686.get_pc_thunk.bx'
> > On Sun 27 Feb 2011 at 12:24:06 PST Stephen Montgomery-Smith wrote: > >> I am the maintainer of the port vis5d+. I just got this email (copied > >> below) saying that vis5d+ isn't building right now. > >> > >> The issue seems to be that some reference to __i686.get_pc_thunk.bx is > >> included twice at some point. This variable seems to be part of an object > >> file crtbeginS.o that is created by gcc or gcc45, in what seem to me to be > >> very mysterious conditions. I am rather sure that the issue has nothing > >> to do with vis5d+, but rather is something to do with either gcc45, or > >> libtools, neither of which I understand. > >> > >> Does anyone out there have any idea of what the problem is, or how it can > >> be solved? > >> > > From a relatively cursory examination, this appears to be a flaw in the > USE_FORTRAN=yes stanza. This will bring in gcc45 as a dependency but doesn't > appear to be setting CXX to g++45 though it does do CC=gcc45. Possibly the > same for LD, though I haven't checked that. As is clear from bsd.gcc.mk, in almost every case now in use, USE_FORTRAN sets _USE_GCC, which sets CC, CPP, and CXX to the proper values. Also, it sets USE_BINUTILS where appropriate, which sets LD, etc. The problem is rather with libtool, particularly in the link mode, where it may not respect the choice of compiler and toolchain. This problem has been remarked, for two years or more, in the mailing lists and forums, when people discuss the use of compilers other than the base system compiler. With the recent updates, it is more obtrusive, and several ports that were building successfully with default settings are now broken. This needs to be fixed, and it would be better to fix libtool than to add a bunch of ad-hoc fixes to individual ports. b. ___ 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: pdnsd leaking udp sockets
Marius Nünnerich writes: > On Sun, Feb 20, 2011 at 21:34, Ashish SHUKLA wrote: >> Hi Marius, >> >> Marius Nünnerich writes: >> >> [...] >> >>> Ok, I applied the patch and reinstalled the port. I will leave it >>> running for a few days and report back. So far it's looking good. >>> Thank you very much! :) >> > OK, I had it running for a while now with your fix. It's not leaking anymore. > There is still one close() missing before a return in that same function. Yes, you're right. I've updated the original diff[1] in case someone like to try it. I'll commit it in a day or two. >> I talked to Paul (the upstream author of pdnsd), and he suggested running >> dns/pdnsd with following command-line (requires devel/valgrind port): >> >> % valgrind --tool=memcheck --leak-check=yes --track-fds==yes pdnsd --nodaemon > I'll try this too if I can find the time, but so far it doesn't seem > to leak memory. Cool. References: [1] http://people.freebsd.org/~ashish/diffs/pdnsd-sockets-leak.diff Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! pgpMAxlw4FcuQ.pgp Description: PGP signature
Re: pdnsd leaking udp sockets
On Sun, Feb 20, 2011 at 21:34, Ashish SHUKLA wrote: > Hi Marius, > > Marius Nünnerich writes: > > [...] > >> Ok, I applied the patch and reinstalled the port. I will leave it >> running for a few days and report back. So far it's looking good. >> Thank you very much! :) > OK, I had it running for a while now with your fix. It's not leaking anymore. There is still one close() missing before a return in that same function. > I talked to Paul (the upstream author of pdnsd), and he suggested running > dns/pdnsd with following command-line (requires devel/valgrind port): > > % valgrind --tool=memcheck --leak-check=yes --track-fds==yes pdnsd --nodaemon I'll try this too if I can find the time, but so far it doesn't seem to leak memory. ___ 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"
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description f ports/155115devel/doxygen: dependancy loop o ports/155111Create new megaglest port o ports/155105Port science/vis5d+ does not build. o ports/155101[UPDATE] devel/upp: Version 3211 o ports/155093[patch] net-mgmt/nfdump: update to 1.6.3p1 o ports/155092Update port: textproc/ocaml-csv o ports/155070NEW PORT: games/CastleVox - new fast strategy board ga o ports/155064New port: devel/stringtemplate, a java lib for text fo o ports/155063Port update: devel/antlrworks o ports/155062Port update: devel/antlr o ports/155038Update port: www/gallery3 fix update translations o ports/155035[maintainer] net/openmq: update to 4.5.b.29 o ports/155020[patch] net/ss5 upgrade to 3.8.5 f ports/155015Update math/clp to version 12.1 o ports/155014New port: security/create-cert: Create self-signed cli f ports/155001[PATCH] deskutils/libgcal: upstream crash bugfix o ports/154995[NEW PORT] audio/umurmur: Minimalistic Murmur (Mumble f ports/154973[PATCH] security/ike: fix plist when QTGUI=off, respec o ports/154942net/scribe: rc.d/thrift starts no matter what the rc.c o ports/154902[patch] Port devel/libedit: added libedit.pc for gnome o ports/154867new port: net-mgmt/glpi-plugins-fusioninventory-server o ports/154829[PATCH] devel/arduino: Eliminate references to legacy f ports/154819[REPOCOPY] misc/krecipes -> misc/krecipes-kde4 o ports/154793Fix broken ports: korean/unzip f ports/154743[PATCH] games/odamex v0.5.1 o ports/154730security/openssh-portable is 5.2 f ports/154719[PATCH] net/netdude update to 0.5.1 (incl. libnetdude o ports/154711security/heimdal: kadmin: hdb_open: hdb_open failed in o ports/154700[REPOCOPY] change name of japanese/asterisk-sounds to f ports/154682net/iaxmodem: add rc script for running more than 1 ia f ports/154657net/rsplib needs update to latest upstream version 2.7 f ports/154558math/linux-SHA-1_collision_search_graz : deprecate o ports/154555[PATCH] x11-wm/sawfish update to 1.7.1 et al. o ports/154551New port: java/jdownloader - Download manager for host o ports/154548textproc/pootle: Pootle's rc.d script don't take into o ports/154530[PATCH] graphics/libvisual04: Fix path conflict & take o ports/154519[PATCH] net/beacon: update to 1.4 o ports/154453Rewritten port: audio/teamspeak_server f ports/154431[patch] ports/Tools/scripts: python scripts use bad sh o ports/154401New port: www/jetty7 - newer fork by Eclipse/Codehaus f ports/154311[PATCH] devel/py-asn1: update to 0.0.12a [feature safe o ports/154285[NEW PORT] java/netty: Java NIO client server framewor o ports/154254[patch] asmail imap login broken with gmail at al. o ports/154202New port: security/scannedonly - A Samba VFS virus sca f ports/154194net/freeswitch: update portversion and remove portrevi o ports/154167update devel/geany to 0.20 o ports/154044[PATCH] update x11-toolkits/open-motif to latest versi o ports/154031New port: audio/shoutcast2: SHOUTcast Distributed Netw o ports/153926New port net/freeswitch-snapshot o ports/153810[PATCH] Fix usb_interrupt_read() in devel/libusb for f o ports/153773net/rabbitmq: reads configuration from /etc instead of f ports/153733[patch] emulators/visualboyadvance-m: problem with joy o ports/153715net/freeradius: FreeRADIUS exiting with Signal 11 on F f ports/153697ports java/jboss5 build failed f ports/153688[MAINTAINER] net-mgmt/zabbix-server: update to 1.8.4 f ports/153645Update ports: emulators/mame update to v0.141 o ports/153625[bsd.port.mk] Pass CPPFLAGS to MAKE_ENV and CONFIGURE_ f ports/153622[patch] sysutils/jfbterm: improve TERMCAP option f ports/153612Update devel/arm-elf-binutils to version 2.17 f ports/153607Update devel/djgpp-binutils to version 2.17 o ports/153601New port: security/msktutil Active Directory keytab ma o ports/153503Patch to add PostgreSQL health check to net/haproxy o ports/153473[patch] mail/couri
Re: multiple definition of `__i686.get_pc_thunk.bx'
on 28/02/2011 00:41 Stephen Montgomery-Smith said the following: > Stephen Montgomery-Smith wrote: >> I am the maintainer of the port vis5d+. I just got this email (copied >> below) saying that vis5d+ isn't building right now. > > The problem seems to be with libtool. If I run a command like: > > libtool -mode=link g++45 stuff stuff > > then libtool does NOT use g++45, but it uses c++ instead. If I hand edit > /usr/local/bin/libtool and replace c++ by g++45, this fixes the problem I > describe below. It looks like libtool (foolishly?) records whatever CC/CXX is set when libtool itself is built. -- 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"
