Date: Tue, 19 Feb 2008 12:54:53 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: lenny@edpausa.com Cc: freebsd-questions@freebsd.org Subject: Re: libc5 on freebsd 6.3 Message-ID: <448x1g3k7m.fsf@be-well.ilk.org> In-Reply-To: <50020.216.254.116.226.1203423985.squirrel@mail.edpausa.com> (lenny@edpausa.com's message of "Tue\, 19 Feb 2008 07\:26\:25 -0500 \(EST\)") References: <51345.216.254.116.226.1203391042.squirrel@mail.edpausa.com> <47BAA996.1000501@FreeBSD.org> <50020.216.254.116.226.1203423985.squirrel@mail.edpausa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
lenny@edpausa.com writes: > Thank you for your response, but it doesn't really help with the situation, > besides the software I'm talking about has been recompiled many time over > since the upgrade. Just to make sure, I recompiled again and it linked to > both libc5 and libc6 right away. That's my issue. Yes, but did you recompile all of the ports libraries that the application links to? Any of *them* could be the problem too. >> lenny@edpausa.com wrote: >>> after several years of relatively trouble free system ( 5 > 6.3 ) and >>> port >>> upgrades, I started having some issues with timesieved daemon of cyrus >>> imap. >>> nothing in the software configuration has changed, but the cyrus port >>> was >>> recently upgraded ( around the same time that the system was upgraded >>> from >>> 6.2 to 6.3 ) >>> >>> the only thing that looks suspicious is the fact that most ( or all ) >>> cyrus binaries are linked to both libc5 and libc6. in fact, after some >>> digging around, I discovered that many other binaries on the system seem >>> be linked to both libraries. I suspect that libc5 is the remnant of 5x >>> installation. >>> >>> What's the safest thing to do ? >>> >>> remove libc5 and link libc5 to libc6 ? >>> >>> rebuild affected software ? ( couldn't find a relevant make.conf option, >>> so what might a flag like that look like ? WITH_LIBC_VER=6 ? >> >> You have to recompile all your installed ports as part of your upgrade >> to a new version of FreeBSD (e.g. 5.x -> 6.x, 6.x -> 7.x, etc). The >> only reason this is necessary is to prevent this kind of problem from >> creeping in as you incrementally rebuild your ports over time. Binaries >> linked to incompatible or inconsistent sets of libraries like two >> different versions of libc will behave unpredictably and may crash. No >> special care needs to be taken when recompiling, just make sure to >> recompile everything (portupgrade -fa or -faPP or similar). >> >> Kris >> >> >> > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448x1g3k7m.fsf>