Date: Wed, 17 Mar 2010 02:30:18 +0000 From: Pegasus Mc Cleaft <ken@mthelicon.com> To: freebsd-current@freebsd.org Cc: Alexander Best <alexbestms@wwu.de> Subject: Re: build failures after stdlib update Message-ID: <201003170230.18508.ken@mthelicon.com> In-Reply-To: <permail-201003170222481e86ffa800002d04-a_best01@message-id.uni-muenster.de>
index | next in thread | previous in thread | raw e-mail
On Wednesday 17 March 2010 02:22:48 Alexander Best wrote: > so is there no way to fix this? this is what i've tried and still the > problem exists: One thing I am trying (and I have no idea if it will work yet) is seeing if replacing the /usr/lib/libc* archives with a working set from another machine. I am just guessing here, but it looks like the /lib/libc.so.7 that I replaced is only used for dynamic linked executables (and is the reason most of my machine is working after I replaced it). When the tool chain compiles, it does so statically and I believe the archive's it uses are in /usr/lib (and I haven't changed them yet). What I am trying to do is build another 9-current AMD64 in Vbox and when that compile is finished, copy the pieces over to the host machine. I'll let you know if this works. Peghome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003170230.18508.ken>