After today's OpenSSH security message, I did: cd /usr rm -rf obj cd src svn update -r311916 make buildworld After a while, I got to: building shared library libc.so.7 cc (a very long compile line) ./libc.so.7: unsupported file layout *** Error code 1 Stop. make[4]: stopped in /usr/src/lib/libc *** Error code 1 Stop. make[3]: stopped in /usr/src *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src freebsd-version -ku 10.3-RELEASE-p13 10.3-RELEASE-p15 I am using a generic kernel, except for using SCHED_4BSD. If it weren't for that, I would just use freebsd-update. Googling suggests that my build tree is somehow mixing up 32 and 64 bit files. (I'm running on an amd64 machine.) How do I get this cleared up? -- George -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170111/0d3d7f2c/attachment.sig>
On Wed, Jan 11, 2017 at 12:24 PM, George Mitchell <george+freebsd at m5p.com> wrote:> After today's OpenSSH security message, I did: > > cd /usr > rm -rf obj > cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > *** Error code 1 > > Stop. > make[4]: stopped in /usr/src/lib/libc > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src > *** Error code 1 > > Stop. > make[2]: stopped in /usr/src > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > freebsd-version -ku > 10.3-RELEASE-p13 > 10.3-RELEASE-p15 > > I am using a generic kernel, except for using SCHED_4BSD. If it > weren't for that, I would just use freebsd-update. > > Googling suggests that my build tree is somehow mixing up 32 and 64 > bit files. (I'm running on an amd64 machine.) How do I get this > cleared up? -- George >While I have no suggestions about the error building libc, your statement that you can't use freebsd-update due to your use of a custom kernel is incorrect. This is a common misconception and, in cases of very limited disk space, may be true, it is rare. It is helped by the fact that the man page makes no mention of how to so this. (You do still need to build a new kernel if the update does, indeed, touch the kernel.) All you need is a GENERIC kernel in /boot/GENERIC. You can either build it or download it. See the FreeBSD Handbook Section 23.2.3.1, ?Custom Kernels with FreeBSD 9.X and Later? <https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html#freebsd-update-custom-kernel-9x> for details on downloading a GENERIC kernel. Before any upgrade, major or minor, you might wat to re-reas that section. Once the GENERIC kernel is in /boot, you may use freebsd-update and, if the GENERIC kernel is not updated, you're good to go. If it is, you will need to build and install a new custom kernel and reboot. Since most security patches don't touch the kernel, this is usually not needed. I believe that the 10.3 kernel was last touched in p11. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman at gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On 11 Jan 2017, at 21:24, George Mitchell <george+freebsd at m5p.com> wrote:> > After today's OpenSSH security message, I did: > > cd /usr > rm -rf objHmm, not sure if it is wise to completely remove the /usr/obj directory. Did you re-create it afterwards?> cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layoutIf things went correctly, the libc.so.7 file should be in /usr/obj/usr/src/lib/libc. If so, can you post the output of: file /usr/obj/usr/src/lib/libc/libc.so.7 readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 -Dimitry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170111/e9f54e2d/attachment.sig>
On 01/11/17 15:24, George Mitchell wrote:> After today's OpenSSH security message, I did: > > cd /usr > rm -rf obj > cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > *** Error code 1 > > Stop. > make[4]: stopped in /usr/src/lib/libc > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src > *** Error code 1 > > Stop. > make[2]: stopped in /usr/src > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > freebsd-version -ku > 10.3-RELEASE-p13 > 10.3-RELEASE-p15 > > I am using a generic kernel, except for using SCHED_4BSD. If it > weren't for that, I would just use freebsd-update. > > Googling suggests that my build tree is somehow mixing up 32 and 64 > bit files. (I'm running on an amd64 machine.) How do I get this > cleared up? -- George >For the sake of completeness, here's the complete build log that terminated in the above error: http://m5p.com/typescript.xz -- George -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170111/4d959863/attachment.sig>
On 01/11/17 15:24, George Mitchell wrote:> After today's OpenSSH security message, I [tried a buildworld and] > got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > [...]I never did figure out the cause of this problem, but I did my buildworld on another machine with no problem. Then I rsync'd /usr/src and /usr/obj back to the first machine and installed the world. Afterwards, I did one more buildworld on the first machine, and it succeeded. I think my original /usr/src tree might have been corrupt, though I really don't know. At least everything is working now. -- George -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170117/70b1e919/attachment.sig>