Re: Unable to build "graphics/gd"
Hallo Jerry, > Thanks for the info. I appreciate it. I don't suppose that there is a > recommended procedure to prevent just such an occurrence again in the > future? Not that it is really all that important. I believe that this > is the first time this has happened to me. This problems are hard to detect. Thanks for reporting. It was related to options not set by default. I have commited a fix now. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [dirk.me...@dinoex.sub.org],[dirk.me...@guug.de],[din...@freebsd.org] http://people.freebsd.org/~dinoex/errorlogs/ ___ 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: Unable to build "graphics/gd"
Greg Lewis wrote: > Marcus von Appen wrote: > > It is a problem with how the FreeBSD upgrade tools work and how > > a port (read: application, library, whatever) manages its own > > build. > > > > Usually a port, in case it links to one of its own components, > > should do that by using the just built component in its build > > directory. Some of them however do not do that but use the > > complete system environment, thus it can happen that they link > > to e.g. an older version of themselves or so, causing anything > > to fail as you just noticed. > > In this case, the port was trying to link against the just built > version of its shared library, it just also tries to link against > some other libraries from other ports and puts -L/usr/local/lib > earlier in the search path than the path to the newly built > libgd.so so the linker picks up libgd.so from /usr/local/lib and > uses that, hence the failure above. I saw the same problem. > > So just a little variant on what you said. Its trying to do the > right thing but just getting the ordering wrong. Might I suggest that one of you file a PR to get the port's library search path fixed, if not already done? To answer the earlier question of how to prevent this sort of problem when installing, I think one way would be to deinstall (making a backup package, to simplify recovery if the new version does not work) before building the new version. ___ 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: Unable to build "graphics/gd"
On Sunday 19 July 2009 11:08:31 am Greg Lewis wrote: > On Sun, Jul 19, 2009 at 02:23:27PM +0200, Marcus von Appen wrote: > > On, Sun Jul 19, 2009, Jerry wrote: > > > On Sun, 19 Jul 2009 13:00:30 +0200 > > > Marcus von Appen wrote: > > > > > > [snip] > > > > > > > Looks like it tries to link against the older version that's still > > > > installed. Try to deinstall gd first, then build and install it > > > > again. > > > > > > Thanks, that fixed it. Strange, but I have not had that problem before. > > > > Just for informational purposes: > > > > It is a problem with how the FreeBSD upgrade tools work and how a port > > (read: application, library, whatever) manages its own build. > > > > Usually a port, in case it links to one of its own components, should do > > that by using the just built component in its build directory. Some of > > them however do not do that but use the complete system environment, > > thus it can happen that they link to e.g. an older version of themselves > > or so, causing anything to fail as you just noticed. > > In this case, the port was trying to link against the just built version > of its shared library, it just also tries to link against some other > libraries from other ports and puts -L/usr/local/lib earlier in the search > path than the path to the newly built libgd.so so the linker picks up > libgd.so from /usr/local/lib and uses that, hence the failure above. I > saw the same problem. > > So just a little variant on what you said. Its trying to do the right > thing but just getting the ordering wrong. I did the recursive pkg_delete as specified in UPDATING and now I have an unworkable KDE. Everything wants to reinstall jpeg-6, which fails because it is already installed. That left me with around 20 modules required by KDE that wouldn't build. When the current portupgrade fails, I will do the PKG_FORCE thing but I shouldn't have to do that. GD not building is just a small piece of the problem. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ 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: Unable to build "graphics/gd"
On Sun, Jul 19, 2009 at 02:23:27PM +0200, Marcus von Appen wrote: > On, Sun Jul 19, 2009, Jerry wrote: > > > On Sun, 19 Jul 2009 13:00:30 +0200 > > Marcus von Appen wrote: > > > > [snip] > > > > > Looks like it tries to link against the older version that's still > > > installed. Try to deinstall gd first, then build and install it again. > > > > Thanks, that fixed it. Strange, but I have not had that problem before. > > Just for informational purposes: > > It is a problem with how the FreeBSD upgrade tools work and how a port > (read: application, library, whatever) manages its own build. > > Usually a port, in case it links to one of its own components, should do > that by using the just built component in its build directory. Some of > them however do not do that but use the complete system environment, > thus it can happen that they link to e.g. an older version of themselves > or so, causing anything to fail as you just noticed. In this case, the port was trying to link against the just built version of its shared library, it just also tries to link against some other libraries from other ports and puts -L/usr/local/lib earlier in the search path than the path to the newly built libgd.so so the linker picks up libgd.so from /usr/local/lib and uses that, hence the failure above. I saw the same problem. So just a little variant on what you said. Its trying to do the right thing but just getting the ordering wrong. -- Greg Lewis Email : gle...@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : gle...@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: Unable to build "graphics/gd"
On Sun, 19 Jul 2009 14:23:27 +0200 Marcus von Appen wrote: > On, Sun Jul 19, 2009, Jerry wrote: > > > On Sun, 19 Jul 2009 13:00:30 +0200 > > Marcus von Appen wrote: > > > > [snip] > > > > > Looks like it tries to link against the older version that's still > > > installed. Try to deinstall gd first, then build and install it > > > again. > > > > Thanks, that fixed it. Strange, but I have not had that problem > > before. > > Just for informational purposes: > > It is a problem with how the FreeBSD upgrade tools work and how a port > (read: application, library, whatever) manages its own build. > > Usually a port, in case it links to one of its own components, should > do that by using the just built component in its build directory. > Some of them however do not do that but use the complete system > environment, thus it can happen that they link to e.g. an older > version of themselves or so, causing anything to fail as you just > noticed. > > Regards > Marcus Thanks for the info. I appreciate it. I don't suppose that there is a recommended procedure to prevent just such an occurrence again in the future? Not that it is really all that important. I believe that this is the first time this has happened to me. -- Jerry ges...@yahoo.com If a can of Alpo costs 38 cents, would it cost $2.50 in Dog Dollars? ___ 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: Unable to build "graphics/gd"
On Sun, 19 Jul 2009 12:58:56 +0200 dirk.me...@dinoex.sub.org (Dirk Meyer) wrote: [snip] > libjpeg.so.9 is obsolete now. pelase use libjpeg.so.10 from jpeg-7. I all ready have the port installed. checking out the '/usr/local/lib' directory, reveals this: lrwxr-xr-x 1 root wheel13B Jul 19 09:01 libjpeg.so@ -> libjpeg.so.10 -rwxr-xr-x 1 root wheel 222K Jul 19 09:01 libjpeg.so.10* I would assume that "gd" is being linked against the correct version. In any case, as I previously posted, deinstalling and reinstalling the 'gd' port fixed the problem; although I am not sure why the problem existed to begin with. -- Jerry ges...@yahoo.com Note to myself: use real bullets next time. ___ 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: Unable to build "graphics/gd"
On, Sun Jul 19, 2009, Jerry wrote: > On Sun, 19 Jul 2009 13:00:30 +0200 > Marcus von Appen wrote: > > [snip] > > > Looks like it tries to link against the older version that's still > > installed. Try to deinstall gd first, then build and install it again. > > Thanks, that fixed it. Strange, but I have not had that problem before. Just for informational purposes: It is a problem with how the FreeBSD upgrade tools work and how a port (read: application, library, whatever) manages its own build. Usually a port, in case it links to one of its own components, should do that by using the just built component in its build directory. Some of them however do not do that but use the complete system environment, thus it can happen that they link to e.g. an older version of themselves or so, causing anything to fail as you just noticed. Regards Marcus pgp0JLNPOmsgo.pgp Description: PGP signature
Re: Unable to build "graphics/gd"
On Sun, 19 Jul 2009 13:00:30 +0200 Marcus von Appen wrote: [snip] > Looks like it tries to link against the older version that's still > installed. Try to deinstall gd first, then build and install it again. Thanks, that fixed it. Strange, but I have not had that problem before. -- Jerry ges...@yahoo.com A general leading the State Department resembles a dragon commanding ducks. New York Times, Jan. 20, 1981 ___ 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: Unable to build "graphics/gd"
Le Sun, 19 Jul 2009 06:39:24 -0400, Jerry a écrit : > I am unable to build the 'graphics/gd' port on FreeBSD-7.2 although I > have updated the posts tree, etc. The build simply stops during the > 'make' phase. A complete copy of the build log is available at this > URL: > > http://pastebin.ca/1499985 There is a problem with libjpeg: /usr/bin/ld: warning: libjpeg.so.9, needed by /usr/local/lib/libgd.so, not found (try using -rpath or -rpath-link) Try to reinstall the port graphics/jpeg 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: Unable to build "graphics/gd"
On, Sun Jul 19, 2009, Jerry wrote: > I am unable to build the 'graphics/gd' port on FreeBSD-7.2 although I > have updated the posts tree, etc. The build simply stops during the > 'make' phase. A complete copy of the build log is available at this URL: > > http://pastebin.ca/1499985 Looks like it tries to link against the older version that's still installed. Try to deinstall gd first, then build and install it again. Regards Marcus pgpiJRGxQvGkH.pgp Description: PGP signature
Unable to build "graphics/gd"
I am unable to build the 'graphics/gd' port on FreeBSD-7.2 although I have updated the posts tree, etc. The build simply stops during the 'make' phase. A complete copy of the build log is available at this URL: http://pastebin.ca/1499985 This is an updated version of the 'gd' port. The previous version build without any problems. -- Jerry ges...@yahoo.com Who goeth a-borrowing goeth a-sorrowing. Thomas Tusser ___ 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"
