Re: port questions (why do I find myself fudging symlinks to make stuff work?)
paul beard wrote: On Mar 31, 2004, at 2:29 PM, Charles Swiger wrote: Stop using portupgrade for a moment; do a make deinstall of the expat port (or use pkg_delete -f), do a make clean, and then do a make reinstall. been there, done that, got the bloody knuckles to show for it. [/usr/ports/textproc/expat2]# pkg_info -g /var/db/pkg/expat-1.95.7/ Information for expat-1.95.7: Mismatched Checksums: pkg_info: /usr/local/lib/libexpat.so doesn't exist pkg_info: /usr/local/lib/libexpat.so.5 doesn't exist I think something's broken. You bet: I think you manually deleted files owned by a package. :-) What I suggested should get rid of the broken reference -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
Well, after a lot of different attempts to get past this problem, it seems that expat isn't building all the files it needs to. === Building package for expat-1.95.7 Creating package /usr/ports/packages/All/expat-1.95.7.tgz Registering depends:. Creating gzip'd tar ball in '/usr/ports/packages/All/expat-1.95.7.tgz' tar: lib/libexpat.so.5: Cannot stat: No such file or directory tar: Error exit delayed from previous errors pkg_create: make_dist: tar command failed with code 512 The missing so files are consistent with what I see when I try to build against an upgraded expat installation. The packaged version works just file: the so files are installed and all is well. But portupgrade wants to upgrade expat, and when it does, those missing files make everything else fail. I have no idea how to resolve the issue at the port level: is there a workaround? and I have been pulling from CVS so this shouldn't be an issue of being out of sync, I don't think. ruby is at 1.8.1, per someone else's advice, as well. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 5:20 PM, paul beard wrote: I have no idea how to resolve the issue at the port level: is there a workaround? and I have been pulling from CVS so this shouldn't be an issue of being out of sync, I don't think. Stop using portupgrade for a moment; do a make deinstall of the expat port (or use pkg_delete -f), do a make clean, and then do a make reinstall. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 2:29 PM, Charles Swiger wrote: Stop using portupgrade for a moment; do a make deinstall of the expat port (or use pkg_delete -f), do a make clean, and then do a make reinstall. been there, done that, got the bloody knuckles to show for it. [/usr/ports/textproc/expat2]# pkg_info -g /var/db/pkg/expat-1.95.7/ Information for expat-1.95.7: Mismatched Checksums: pkg_info: /usr/local/lib/libexpat.so doesn't exist pkg_info: /usr/local/lib/libexpat.so.5 doesn't exist I think something's broken. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Wednesday 31 March 2004 02:20 pm, paul beard wrote: Well, after a lot of different attempts to get past this problem, it seems that expat isn't building all the files it needs to. === Building package for expat-1.95.7 Creating package /usr/ports/packages/All/expat-1.95.7.tgz Registering depends:. Creating gzip'd tar ball in '/usr/ports/packages/All/expat-1.95.7.tgz' tar: lib/libexpat.so.5: Cannot stat: No such file or directory tar: Error exit delayed from previous errors pkg_create: make_dist: tar command failed with code 512 The missing so files are consistent with what I see when I try to build against an upgraded expat installation. The packaged version works just file: the so files are installed and all is well. But portupgrade wants to upgrade expat, and when it does, those missing files make everything else fail. I have no idea how to resolve the issue at the port level: is there a workaround? and I have been pulling from CVS so this shouldn't be an issue of being out of sync, I don't think. It is if you didn't rebuild the INDEX and INDEX.db. Kent ruby is at 1.8.1, per someone else's advice, as well. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Wed, Mar 31, 2004 at 02:20:04PM -0800, paul beard wrote: Well, after a lot of different attempts to get past this problem, it seems that expat isn't building all the files it needs to. === Building package for expat-1.95.7 Creating package /usr/ports/packages/All/expat-1.95.7.tgz Registering depends:. Creating gzip'd tar ball in '/usr/ports/packages/All/expat-1.95.7.tgz' tar: lib/libexpat.so.5: Cannot stat: No such file or directory tar: Error exit delayed from previous errors pkg_create: make_dist: tar command failed with code 512 What architecture is this on? Some people have reported problems on amd64 with shared libraries not being created - this appears to be something to do with libtool, but I don't see it on my amd64 box. To work around mysterious port problems you can always just install the packages instead. Kris pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 3:28 PM, Kris Kennaway wrote: What architecture is this on? Some people have reported problems on amd64 with shared libraries not being created - this appears to be something to do with libtool, but I don't see it on my amd64 box. It's on x86, running 4.9. To work around mysterious port problems you can always just install the packages instead. I tried that, but some ports want to rebuild their dependencies and I'm back where I started. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 4:29 PM, Kris Kennaway wrote: You're not doing it right, then :-) Use portupgrade with the -PP switch to force the use of packages. What if there isn't a package for a given port? I wasn't aware there were packages (though I suppose for an ancient release like 4.9 there might be). -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Wed, Mar 31, 2004 at 04:22:22PM -0800, paul beard wrote: On Mar 31, 2004, at 3:28 PM, Kris Kennaway wrote: What architecture is this on? Some people have reported problems on amd64 with shared libraries not being created - this appears to be something to do with libtool, but I don't see it on my amd64 box. It's on x86, running 4.9. To work around mysterious port problems you can always just install the packages instead. I tried that, but some ports want to rebuild their dependencies and I'm back where I started. You're not doing it right, then :-) Use portupgrade with the -PP switch to force the use of packages. Kris pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Wed, Mar 31, 2004 at 04:34:05PM -0800, paul beard wrote: On Mar 31, 2004, at 4:29 PM, Kris Kennaway wrote: You're not doing it right, then :-) Use portupgrade with the -PP switch to force the use of packages. What if there isn't a package for a given port? I wasn't aware there were packages (though I suppose for an ancient release like 4.9 there might be). Well, then you can't use it :) There are certainly up-to-date packages for the basic ports like expat that you're having problems with. Kris pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 5:38 PM, Kris Kennaway wrote: Well, then you can't use it :) There are certainly up-to-date packages for the basic ports like expat that you're having problems with. So here's my problem. I install expat and gettext from packages. Then I install *anything* that depends on those, and they need to be rebuilt. The expat build fails. The gettext fail as a result, and then all the rest do as well. I'm not sure how up to date they are if the ports that depend on them want to rebuild them. Information for expat-1.95.6_1.tgz: Files: /usr/local/man/man1/xmlwf.1.gz /usr/local/bin/xmlwf /usr/local/include/expat.h /usr/local/lib/libexpat.a /usr/local/lib/libexpat.so /usr/local/lib/libexpat.so.4 gettext 0.13.x wants expat.5, so that's not as up to date as it might be. I've dropped a note to the maintainer: perhaps there's something he can point out. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Wed, Mar 31, 2004 at 06:37:44PM -0800, paul beard wrote: On Mar 31, 2004, at 5:38 PM, Kris Kennaway wrote: Well, then you can't use it :) There are certainly up-to-date packages for the basic ports like expat that you're having problems with. So here's my problem. I install expat and gettext from packages. Then I install *anything* that depends on those, and they need to be rebuilt. The expat build fails. The gettext fail as a result, and then all the rest do as well. I'm not sure how up to date they are if the ports that depend on them want to rebuild them. You're installing out of date packages then. The ones on the ftp site are current and provide libexpat.so.5. Kris pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 7:52 PM, Kris Kennaway wrote: You're installing out of date packages then. The ones on the ftp site are current and provide libexpat.so.5. This is what's available for 4.9-RELEASE: [/opt/ports/packages/All]# pkg_info -L expat-1.95.6_1.tgz Information for expat-1.95.6_1.tgz: Files: /usr/local/man/man1/xmlwf.1.gz /usr/local/bin/xmlwf /usr/local/include/expat.h /usr/local/lib/libexpat.a /usr/local/lib/libexpat.so /usr/local/lib/libexpat.so.4 Likewise 5.2-RELEASE: I just pulled that package and checked. The Makefile in my ports tree has this: PORTVERSION=1.95.7. this would/should give me expat.5. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Wed, Mar 31, 2004 at 08:43:34PM -0800, paul beard wrote: On Mar 31, 2004, at 7:52 PM, Kris Kennaway wrote: You're installing out of date packages then. The ones on the ftp site are current and provide libexpat.so.5. This is what's available for 4.9-RELEASE: You want the packages-4-stable directory; RELEASE packages are not updated. See http://www.freebsd.org/ports for more details. Kris pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 31, 2004, at 9:21 PM, Kris Kennaway wrote: You want the packages-4-stable directory; RELEASE packages are not updated. See http://www.freebsd.org/ports for more details. Ah, I see. There was an earlier email to the effect that the packages I needed were under 4.9-RELEASE. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mon, Mar 29, 2004 at 09:21:34PM -0800, paul beard wrote: [ please cc me as I am not on the list] I have been trying to upgrade cups to 1.1.20 and have been running into some problems with libraries not being found (specifically jpeg.9 and tiff.4). After a few different iterations of pkg_add, portupgrade, portinstall, and accompanying pkg_delete, pkg_deinstall, make install, etc., I finally tried symlinking the .so files to the numbered versions that don't seem to exist and all seems to be well. ln -s /usr/local/lib/libjpeg.a /usr/local/lib/libjpeg.so.9 ln -s /usr/local/lib/libtiff.a /usr/local/lib/libtiff.so.4 I hope the above wasn't actually what you did. You should have: % ls -l libjpeg* libtiff* -rw-r--r-- 1 root wheel 157600 Mar 19 15:46 libjpeg.a lrwxr-xr-x 1 root wheel 12 Mar 19 15:46 libjpeg.so@ - libjpeg.so.9 -rwxr-xr-x 1 root wheel 135245 Mar 19 15:46 libjpeg.so.9* -r--r--r-- 1 root wheel 374922 Feb 8 10:05 libtiff.a lrwxr-xr-x 1 root wheel 12 Feb 8 10:05 libtiff.so@ - libtiff.so.4 -r--r--r-- 1 root wheel 322199 Feb 8 10:05 libtiff.so.4 Linking a static library (.a) to a shlib (.so.N) will have undesirable effects. pkgdb doesn't seem to have any problems (I have run it enough times today), cvsup has done its magic a couple of times. That sounds like what I'd expect, since those commands affect some completely different sets of files to the ones that are giving you problems. A more interesting question would be what output do you get from: % pkg_info -g jpeg-\* tiff-\* The symlinks in question should be known to the packaging system: % pkg_info -L jpeg-\* tiff-\* | grep '.so$' /usr/local/lib/libjpeg.so /usr/local/lib/libtiff.so I thought portinstall/upgrade -rR would fix any out-of-date ports and make everything happy? What am I doing wrong to make this libraries not get installed? Yes -- there is certainly something going wrong wrong with the way your system is operating: maybe not with the ports/packages system itself, but something took out those symlinks which should have been there. If you reinstall those two packages you should get all of those files and symlinks recreated correctly for you automatically. However, portupgrade won't necessarily pick up that an installed package has been damaged. The ports system will find that, eg. libjpeg.so.9 is missing (which is the file it specifically checks for when testing if the correct dependencies have been installed), and so assume that the whole graphics/jpeg port hasn't been installed. Then when it goes to install the missing dependency, and finds that it isn't actually missing at all. The general answer to this problem is to force a re-install of the damaged packages: # portupgrade -f graphics/jpeg # portupgrade -f graphics/tiff Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mon, Mar 29, 2004 at 09:21:34PM -0800, paul beard wrote: [ please cc me as I am not on the list] I have been trying to upgrade cups to 1.1.20 and have been running into some problems with libraries not being found (specifically jpeg.9 and tiff.4). After a few different iterations of pkg_add, portupgrade, portinstall, and accompanying pkg_delete, pkg_deinstall, make install, etc., I finally tried symlinking the .so files to the numbered versions that don't seem to exist and all seems to be well. ln -s /usr/local/lib/libjpeg.a /usr/local/lib/libjpeg.so.9 ln -s /usr/local/lib/libtiff.a /usr/local/lib/libtiff.so.4 pkgdb doesn't seem to have any problems (I have run it enough times today), cvsup has done its magic a couple of times. I thought portinstall/upgrade -rR would fix any out-of-date ports and make everything happy? What am I doing wrong to make this libraries not get installed? No idea, you'd have to post some details. Kris pgp0.pgp Description: PGP signature
Re: port questions (why do I find myself fudging symlinks to make stuff work?)
On Mar 30, 2004, at 12:23 AM, Matthew Seaman wrote: A more interesting question would be what output do you get from: % pkg_info -g jpeg-\* tiff-\* [/usr/local/lib]# ls -l libjpeg* libtiff* -rw-r--r-- 1 root wheel 159384 Mar 30 08:04 libjpeg.a -r--r--r-- 1 root wheel 354610 Mar 29 21:11 libtiff.a [/usr/local/lib]# pkg_info -g jpeg-\* tiff-\* Information for jpeg-6b_2: Mismatched Checksums: pkg_info: /usr/local/lib/libjpeg.so doesn't exist pkg_info: /usr/local/lib/libjpeg.so.9 doesn't exist Information for tiff-3.6.1_1: Mismatched Checksums: pkg_info: /usr/local/lib/libtiff.so doesn't exist pkg_info: /usr/local/lib/libtiff.so.4 doesn't exist Hmm, portinstall -f on those two ports seems to get caught in some recursive loop. I'm going thru my entire installed base and redoing it all. Perhaps there's a more clueful way to do it, but unless this will do any harm, it seems the most thorough. I need to explore the docs and get a better understanding of the ports tools: I seem to find this happening again and again. Thanks for the quick and detailed reply. -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
port questions (why do I find myself fudging symlinks to make stuff work?)
[ please cc me as I am not on the list] I have been trying to upgrade cups to 1.1.20 and have been running into some problems with libraries not being found (specifically jpeg.9 and tiff.4). After a few different iterations of pkg_add, portupgrade, portinstall, and accompanying pkg_delete, pkg_deinstall, make install, etc., I finally tried symlinking the .so files to the numbered versions that don't seem to exist and all seems to be well. ln -s /usr/local/lib/libjpeg.a /usr/local/lib/libjpeg.so.9 ln -s /usr/local/lib/libtiff.a /usr/local/lib/libtiff.so.4 pkgdb doesn't seem to have any problems (I have run it enough times today), cvsup has done its magic a couple of times. I thought portinstall/upgrade -rR would fix any out-of-date ports and make everything happy? What am I doing wrong to make this libraries not get installed? -- Paul Beard www.paulbeard.org/ paulbeard [at] mac.com
