Date: Sat, 29 Jun 2002 12:28:00 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Jan Lentfer <Jan.Lentfer@web.de> Cc: freebsd-ports@freebsd.org Subject: Re: Ports collection and FreeBSD-current Message-ID: <20020629122800.A84728@troutmask.apl.washington.edu> In-Reply-To: <1025377586.2820.14.camel@jan-linux.lan>; from Jan.Lentfer@web.de on Sat, Jun 29, 2002 at 09:06:19PM %2B0200 References: <20020629114442.A84248@troutmask.apl.washington.edu> <1025377586.2820.14.camel@jan-linux.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 29, 2002 at 09:06:19PM +0200, Jan Lentfer wrote: > Am Sam, 2002-06-29 um 20.44 schrieb Steve Kargl: > > Something is really broken in the ports collection > > and FreeBSD-current. It seems that any port that > > uses a GNU configure script is broken. A typical failure > > seems to be the generation of a bad config.h file. > > I just run into massive problems with the ports, too. I am running > 4.6-STABLE and I just cvsup'ed my ports. After that almost all ports I > tried refused to build. The problem almost always was: > > /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found > > libc.so.5 is only in 5.0-CURRENT, right? So I can't build most ports > anymore on RELENG_4 and RELENG_4_6? > Yes, libc.so.5 is only in -current. I'm not sure what is the cause of your problems, but you can do the following *HACK* ln -s /usr/lib/libc.so.4 /usr/lib/libc.so.5 ldconfig -R This will allow you to build things, but this is a HACK. You really need to determine why one or more of your binaries is linked against a -current library. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020629122800.A84728>