On 2021-Jan-15, at 20:37, bob prohaska <fbsd at www.zefox.net> wrote:
> While playing with -current on armv7 using a raspberry pi 2 v1.1 > an error crops up with recent kernels while building world: > > ++: error: linker command failed with exit code 1 (use -v to see invocation) > *** [clang.full] Error code 1 > > make[5]: stopped in /usr/freebsd-src/usr.bin/clang/clang > > How does one invoke -v in this situation? Going a different direction: Going to publish the build log someplace? There is likely more there of interest to isolating the issue(s). I use META_MODE builds. One thing they do is record the command used to try to produce each file. So in that kind of context, identifying what it was trying to build allows finding the related NAME.meta file and looking in it. An example failure for armv7 and 1 GiByte of RAM could be a simple memory allocation failure: unable to get a sufficiently large contiguous range from the address space for some request. (So it never gets to the point of using swap for it.) Are you controlling how many threads the linker uses? > For the record, uname -a reports > FreeBSD www.zefox.com 13.0-CURRENT FreeBSD 13.0-CURRENT #6 > main-c950-gff1a307801: Wed Jan 13 19:02:18 PST 2021 > b...@www.zefox.com:/usr/obj/usr/freebsd-src/arm.armv7/sys/GENERIC-MMCCAM arm > > The present sources are a day or two newer. > > Nothing is obviously wrong; swap usage is small, no warnings or errors on the > console. > > In past occurrences, an old kernel (pre-git) worked through the problem. > If a restart of make buildworld doesn't get past the stoppage I'll check > again. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
