working again: sysbuild of netbsd-10 from netbsd-10 fails after upgrade of itself
"Greg A. Woods" <[email protected]>
| Newsgroups | gmane.os.netbsd.current,gmane.os.netbsd.general |
|---|---|
| Organization | Planix, Inc. |
| Message-ID | <[email protected]> |
> Yesterday (2024/10/06) I finally did an upgrade of the system itself > from yesterday's build, and this morning I find the following failure in > the latest log: Just to let everyone know, the self-build of netbsd-10 on i386 is working A-OK again. There was one hiccup with the tools/compat stuff due to changes to visibility of some inlined functions in <sys/endian.h>. That was fixed by removing the tools/compat objects, thus forcing the build to re-run the configure script there again. There was one other weird problem with an object file in the MONOLITHIC kernel build directory, if_xge.o, that somehow didn't have a SUNW_ctf section and nbctfmerge was bailing out as a result: ERROR: nbctfmerge: Input file if_xge.o was partially built from C sources, but no CTF data was present Removing that file allowed the build to succeed. So, removing the whole object tree would have solved the problem, but I wanted to figure out the details to see if there was anything that could or should be done to make such an upgrade path a bit smoother. At this point I don't think anything better could be done to automatically fix an incremental build for the <sys/endian.h> fixes. However maybe a note should be (have been!) included in src/UPDATING about this issue. However it looks like src/UPDATING is effectively stale on the release branch, so maybe that's not the right place? As far as I can tell there was no note added about this for -current either -- did anyone encounter the same problem with -current at the time? (that would be 2024-09-09) As for the missing SUNW_ctf information -- that's just weird as all the other existing files compiled at the same time in that directory have the section. Now I need to remember to do more timely upgrades from the daily builds. Perhaps I should just have a cron script run sysupgrade and then reboot.... It's just a test machine for now after all. -- Greg A. Woods <[email protected]> Kelowna, BC +1 250 762-7675 RoboHack <[email protected]> Planix, Inc. <[email protected]> Avoncote Farms <[email protected]>
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCaOlz+wAKCRBmfXG3eL/0 f7orAJ4srRJl0YOLlLIw3w2Ab5GisUv4MACeJ6tszNxB9n53dTch86dGC+4qInk= =K/RV -----END PGP SIGNATURE-----