Re: Undefined symbol SYS_uuidgen?
On Sat, Jun 01, 2002 at 10:28:36PM -0300, Marc G. Fournier wrote: 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 Make sure your /sys sources are up to date. You have SYS_uuidgen as an undefined symbol, which means that syscalls.master and derived headers do not contain the new syscall. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Undefined symbol SYS_uuidgen?
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 :) I've tried to search google, and the list archives on freebsd.org, as well as re-scan through UPDATING, and can't find any references to it ;( Help? Since I'm in a state whre I can't get hte network up, is there a file I can edit to fix this? You should be able to use the network in single-user mode; ifconfig and route are statically linked. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Undefined symbol SYS_uuidgen?
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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Undefined symbol SYS_uuidgen?
In the last episode (Jun 01), Terry Lambert said: 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. Yes, that's it. I remember having the same problem with the addition of lchflags last month. Maybe the buildworld should do a make includes into the build tree and use those when building libc? (wouldn't have helped me, as I very rarely build world, but rebuild libraries and bins manually if I need a new feature) 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. You only bump the version when an ABI changes or a function disappears, afaik. We promise backwards compatibility, not forwards. And I don't think we want to bump versions on -current anyway; 4.* has libc.so.4, 5.0-RELEASE will have .so.5. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Undefined symbol SYS_uuidgen?
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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Undefined symbol SYS_uuidgen?
Dan Nelson wrote: You only bump the version when an ABI changes or a function disappears, afaik. We promise backwards compatibility, not forwards. And I don't think we want to bump versions on -current anyway; 4.* has libc.so.4, 5.0-RELEASE will have .so.5. If it's already been bumped for 5.x, I stand corrected: keeping in sync with a release-in-progress where the number has already been bumped is an exercise for the student. 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
