Date: Sat, 1 Jun 2002 23:36:49 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Dan Nelson <dnelson@allantgroup.com>, <freebsd-current@FreeBSD.ORG> Subject: Re: Undefined symbol "SYS_uuidgen"? Message-ID: <20020601233628.G2522-100000@mail1.hub.org> In-Reply-To: <3CF97F78.7D8308D2@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Cool, just did a reinstall of the include files and things appear to be working "much better now" ... thanks :) On Sat, 1 Jun 2002, Terry Lambert wrote: > Dan Nelson wrote: > > In the last episode (Jun 01), Marc G. Fournier said: > > > Performed a 'make buildworld' successfully, but as soon as I tried the > > > 'installworld', when its trying to do the install of libc.so.5, it gives > > > an error to the effect of: > > > > > > /usr/libexec/ld-elf.so.1: /usr/lib/libc.so.5: Undefined symbol "SYS_uuidgen" > > > > Sounds like your kernel and userland are out of synch. Try installing > > a new kernel, and rerunning installworld. You may need to build the > > kernel on another machine if you can't roll back your libc. It's > > always a good idea to back up libc before a world build :) > > "Undefined symbol", not "Undefined system call". > > Sounds more like the sys "include" files were not installed before > the libc was built, since there's a silly script that translates > /usr/include/sys/syscall.h to stubs. > > Another possibility is that the Makefile's in the /usr/src/lib/libc > hierarchy need updating. > > Generally, I'd expect the libc.so version number to bump before > seeing this problem, anyway. 8-(. Looks like someone failed to > bump a version number. > > -- Terry > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020601233628.G2522-100000>