Hi all, I'm upgrading a FreeBSD amd64 box from 6.2p9 to 7.0p5. After update the sources amd make world with success, I get this error: [...] newfs.lo(.text+0x659): In function `main': : undefined reference to `__mb_sb_limit' newfs_msdos.lo(.text+0x13): In function `mklabel': : undefined reference to `__mb_sb_limit' restore.lo(.text+0xc60): In function `mkentry': : undefined reference to `__mb_sb_limit' restore.lo(.text+0xa6d6): In function `rmthost': : undefined reference to `__mb_sb_limit' sysctl.lo(.text+0xf9f): more undefined references to `__mb_sb_limit' follow tar.lo(.text+0x28f4): In function `read_archive': : undefined reference to `archive_read_support_compression_program' tar.lo(.text+0x3a81): In function `yes': : undefined reference to `__mb_sb_limit' tar.lo(.text+0x432a): In function `safe_fprintf': : undefined reference to `__mb_sb_limit' tar.lo(.text+0x6156): In function `tar_mode_c': : undefined reference to `archive_write_set_compression_program' vi.lo(.text+0x2f80): In function `cut': : undefined reference to `__mb_sb_limit' vi.lo(.text+0x2fb0): In function `cut': : undefined reference to `__mb_sb_limit' vi.lo(.text+0x311e): In function `cut': : undefined reference to `__mb_sb_limit' vi.lo(.text+0x5c29): In function `v_key_name': : undefined reference to `__mb_sb_limit' vi.lo(.text+0x5cf3): In function `v_key_name': : undefined reference to `__mb_sb_limit' vi.lo(.text+0x63b8): more undefined references to `__mb_sb_limit' follow *** Error code 1 Stop in /usr/obj/usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. after try the classical kernel compilation ( cd /usr/src && make -DINSTALL_NODEBUG KERNCONF=MYKERNEL) I've not found any related info in the net. Anyones knows about? Last week I upgraded two others 6.2 amd boxes without problem. PD1. I use the "classical" method over "new" binary method because of my kernel is customized. PD2. I use -DINSTALL_NODEBUG flag because of my / partition is so small and need to preserve the maximum space. -- Thanks, Jordi Espasa Clofent
Jordi Espasa Clofent <jespasac@minibofh.org> writes:> Hi all, > > I'm upgrading a FreeBSD amd64 box from 6.2p9 to 7.0p5. > After update the sources amd make world with success, I get this error: > > [...] > newfs.lo(.text+0x659): In function `main': > : undefined reference to `__mb_sb_limit' > newfs_msdos.lo(.text+0x13): In function `mklabel': > : undefined reference to `__mb_sb_limit' > restore.lo(.text+0xc60): In function `mkentry': > : undefined reference to `__mb_sb_limit' > restore.lo(.text+0xa6d6): In function `rmthost': > : undefined reference to `__mb_sb_limit' > sysctl.lo(.text+0xf9f): more undefined references to `__mb_sb_limit' follow > tar.lo(.text+0x28f4): In function `read_archive': > : undefined reference to `archive_read_support_compression_program' > tar.lo(.text+0x3a81): In function `yes': > : undefined reference to `__mb_sb_limit' > tar.lo(.text+0x432a): In function `safe_fprintf': > : undefined reference to `__mb_sb_limit' > tar.lo(.text+0x6156): In function `tar_mode_c': > : undefined reference to `archive_write_set_compression_program' > vi.lo(.text+0x2f80): In function `cut': > : undefined reference to `__mb_sb_limit' > vi.lo(.text+0x2fb0): In function `cut': > : undefined reference to `__mb_sb_limit' > vi.lo(.text+0x311e): In function `cut': > : undefined reference to `__mb_sb_limit' > vi.lo(.text+0x5c29): In function `v_key_name': > : undefined reference to `__mb_sb_limit' > vi.lo(.text+0x5cf3): In function `v_key_name': > : undefined reference to `__mb_sb_limit' > vi.lo(.text+0x63b8): more undefined references to `__mb_sb_limit' follow > *** Error code 1 > > Stop in /usr/obj/usr/src/rescue/rescue. > *** Error code 1 > > Stop in /usr/src/rescue/rescue. > *** Error code 1 > > Stop in /usr/src/rescue. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > after try the classical kernel compilation ( cd /usr/src && make > -DINSTALL_NODEBUG KERNCONF=MYKERNEL) > > I've not found any related info in the net. Anyones knows about? Last > week I upgraded two others 6.2 amd boxes without problem. > > PD1. I use the "classical" method over "new" binary method because of > my kernel is customized.Neither of those methods seem to be the officially supported source update method, which includes (in order, but with some other steps left out) make buildworld make buildkernel make installkernel <REBOOT into single-user> make installworld Is that actually what you did? If not, what did you mean when you said you did "make world"?> PD2. I use -DINSTALL_NODEBUG flag because of my / partition is so > small and need to preserve the maximum space.That should be fine, and doesn't seem to be related to the symptoms.
Jordi Espasa Clofent <jespasac@minibofh.org> writes:>> Neither of those methods seem to be the officially supported source >> update method, which includes (in order, but with some other steps left >> out) make buildworld >> make buildkernel >> make installkernel >> <REBOOT into single-user> >> make installworld >> >> Is that actually what you did? > > Yes, of course. > > update sources -> OK > make buildworld -> OK > make kernel (it is a simple make buildkernel && make install > kernel short-way) --> WRONG > > The problem appears in first kernel stage, which means in "make > buildkernel". > > Is it the first time I've seen it. > >> That should be fine, and doesn't seem to be related to the symptoms. > > Yes.The errors you showed earlier looked like they came from userland, not the kernel (building /rescue). If it really does come during "make buildkernel", what kernel are you builidng? I assume you tried GENERIC before trying to report a problem?