Date: Wed, 17 May 2017 17:03:58 -0700 From: Mark Millard <markmi@dsl-only.net> To: Jonathan Chen <jonc@chen.org.nz> Cc: tech lists <tech-lists@zyxst.net>, freebsd-arm@freebsd.org Subject: Re: build failure with crochet for rpi3 using freebsd-11-stable sources Message-ID: <343BCB48-F1EB-4A87-8E88-FA69F6E176D7@dsl-only.net> In-Reply-To: <CAJuc1zP1KOO%2B8hsSAWo%2BRdReC33B=wKcVeWD1VUwt=oxEK0Mug@mail.gmail.com> References: <20170517135047.0803ad60@pumpkin.growveg.org> <CAJuc1zP1KOO%2B8hsSAWo%2BRdReC33B=wKcVeWD1VUwt=oxEK0Mug@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-May-17, at 4:19 PM, Jonathan Chen <jonc@chen.org.nz> wrote: > On 18 May 2017 at 00:50, tech lists <tech-lists@zyxst.net> wrote: >> Hello list, >> >> Building on a r318366 freebsd-11-stable machine, using >> freebsd/crochet installed today with fresh (r318397) sources, I'm >> getting the following error trying to build, for the raspberry pi3, a >> freebsd-11-stable image: >> >> --- libc.so.7.full --- >> /usr/local/aarch64-freebsd/bin/ld: getutxent.pico(.debug_info+0x3b): >> R_AARCH64_ABS64 used with TLS symbol >> udb /usr/local/aarch64-freebsd/bin/ld: >> getutxent.pico(.debug_info+0x58): R_AARCH64_ABS64 used with TLS symbol >> uf /usr/local/aarch64-freebsd/bin/ld: utxdb.pico(.debug_info+0x5a): >> R_AARCH64_ABS64 used with TLS symbol >> futx_to_utx.ut /usr/local/aarch64-freebsd/bin/ld: >> jemalloc_tsd.pico(.debug_info+0x3c): R_AARCH64_ABS64 used with TLS >> symbol __je_tsd_tls /usr/local/aarch64-freebsd/bin/ld: >> jemalloc_tsd.pico(.debug_info+0x1433): R_AARCH64_ABS64 used with TLS >> symbol __je_tsd_initialized /usr/local/aarch64-freebsd/bin/ld: >> cxa_thread_atexit_impl.pico(.debug_info+0x3b): R_AARCH64_ABS64 used >> with TLS symbol dtors /usr/local/aarch64-freebsd/bin/ld: >> xlocale.pico(.debug_info+0x403): R_AARCH64_ABS64 used with TLS symbol >> __thread_locale /usr/local/aarch64-freebsd/bin/ld: >> setrunelocale.pico(.debug_info+0x3c): R_AARCH64_ABS64 used with TLS >> symbol _ThreadRuneLocale cc: error: linker command failed with exit >> code 1 (use -v to see invocation) *** [libc.so.7.full] Error code 1 >> > > There's a bug report filed: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218198 > > The workaround is add the following in /etc/src.conf: > WITHOUT_DEBUG_FILES=yes Comments 6 and 8 on bugzilla 218198 indicate that the following combination will fail: WITH_DEBUG= WITHOUT_DEBUG_FILES= So it is WITH_DEBUG= that must be avoided (explicit or implicit). There is another workaround that I've added as Comment 11 and 12 (a correction to what I typed in 11), one that keeps most debug information in a usable form: A workaround for svnlite/svn folks that use source builds is to do something like: svnlite update -r436731 /usr/ports/devel/*binutils to revert to the source for 2.27 vintage binutils and then rebuild the binutils that you use. Then use these older binutils. Because of slave-port relationships the main host binutils needs to be reverted as part of this, not just the target machine's binutils. This will still produce the warnings but changes the return code from ld to allow things to continue with somewhat messed up debug information. 2.28's return code is probably correct long term and this is just a temporary hack until the input to ld is correct so that 2.28 has nothing to cause the non-zero return code. === Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?343BCB48-F1EB-4A87-8E88-FA69F6E176D7>