Date: 30 Aug 2005 09:19:01 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Will Maier <willmaier@ml1.net> Cc: freebsd-questions@freebsd.org Subject: Re: Perl 5.8.7 port requires libm.so.4 Message-ID: <443borh8ai.fsf@be-well.ilk.org> In-Reply-To: <20050828155958.GC24820@localhost.localdomain>
index | next in thread | previous in thread | raw e-mail
Will Maier <willmaier@ml1.net> writes: > *- > > I'm running a ~2 days old FreeBSD 5.3-SECURITY install; I'm still getting my > feet wet with FreeBSD. Here's the process I've been using to keep my ports > tree up-to-date: > # portsnap fetch > # portsnap update > # make fetchindex > # portsdb -u > # portupgrade -varRPP > > I've also been reading /u/p/UPDATING before actually running portupgrade; > today I noticed that the Perl 5.8.6->5.8.7 upgrade required running a script > afterwards. I then ran portupgrade, which updated Perl, Ruby and some other > ports. It failed on firefox and gtk20, however, because it couldn't find > libm.so.4. > > I then tried to run perl-after-upgrade, but the Perl interpreter won't run > because it can't find libm.so.4 either. Symlinking /l/libm.so.3 -> > /l/libm.so.4 gets rid of the error, but then the interpreter complains about a > crypt library...symlinking each of the required libs seems a) unlikely to be a > good solution in the end and b) hackish, plus I'm not even sure it *really* > makes the interpreter any happier. > > Have I missed some important step? The OS itself is kept up-to-date using > freebsd-update, although I don't *think* this would affect eg Perl. Sure it will, if it updates you to have a different dynamic library name than the one your programs are linked against. I don't use freebsd-update, but I'd like to point out that libm.so.4 is on FreeBSD 6.x, not 5.x. So you don't seem to be running the base system you think you are.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443borh8ai.fsf>