Date: Sat, 16 Jan 2021 14:03:34 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: Current FreeBSD <freebsd-current@freebsd.org>, freebsd-arm@freebsd.org Subject: Re: Invoking -v for clang during buildworld Message-ID: <20210116220334.GA26756@www.zefox.net> In-Reply-To: <F62027C8-0813-4E6F-934A-3088F966AF8C@yahoo.com> References: <20210116043740.GA19523@www.zefox.net> <ED26508F-282D-439D-8A6A-65A136C76C84@yahoo.com> <20210116155538.GA24259@www.zefox.net> <F62027C8-0813-4E6F-934A-3088F966AF8C@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 16, 2021 at 11:17:52AM -0800, Mark Millard wrote: > > > On 2021-Jan-16, at 07:55, bob prohaska <fbsd at www.zefox.net> wrote: > > > On Fri, Jan 15, 2021 at 09:25:00PM -0800, Mark Millard wrote: > >> > >> 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've put what I hope is a useful picture at > > http://www.zefox.net/~fbsd/rpi2/buildworld/ > > Looks to me like your -DNO_CLEAN based build is reusing one or > more files with inappropriate/incomplete contents that need to > be regenerated: there are a number of undefined symbols stopping > the linker during its attempt to build the "usr.bin/clang/clang > (all)" material. See below. > [examples snipped] > > FYI: > > I found this by noting the "all_subdir_usr.bin" below and > searching backwards for prior examples and seeing what was > after those examples. > > --- all_subdir_usr.bin --- > c++: error: linker command failed with exit code 1 (use -v to see invocation) > *** [clang.full] Error code 1 > > It never dawned that I wasn't looking at the first error message. > > The undefined symbols seem unlikely to be a voltage problem. > > The zeros are from the units for the integers not being volts > but micro volts. (Which is not the same as saying measurements > reach that scale of accuracy.) > So long as they're measured values they might be worth keeping track of. I thought maybe they were some sort of input or placeholder values. > >> 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. > >> Not needed now, but worth remembering for the future. > > I see no specific evidence for a kernel problem being involved. > Agreed. The problem is the operator. Thanks for your patience! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210116220334.GA26756>