Date: Sun, 6 Jan 2019 13:02:06 +0100 From: Gary Jennejohn <gljennjohn@gmail.com> To: "Julian H. Stacey" <jhs@berklix.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" (RPI/arm64) Message-ID: <20190106130206.56332774@ernst.home> In-Reply-To: <201901060714.x067DqZP016183@fire.js.berklix.net> References: <20181227140706.748bf173@ernst.home> <201901060714.x067DqZP016183@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 06 Jan 2019 08:13:52 +0100 "Julian H. Stacey" <jhs@berklix.com> wrote: > > > > $ chrome > > > > ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" > > [ Delayed report (as it took about 2 days to build chrome from ports/)] ... > > I too am still seing from chrome: > ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" > which I first saw from chrome after a pkg add, but now too from a ports/ build > > My src/ was maybe a week or so old. To be precise on next failure report, > I've since added WITHOUT_REPRODUCIBLE_BUILD="YES" to /etc/src.conf > & finished a buildworld on .svn_revision 342785, now running buildkernel > IIRC the problem was attributed to some flags being passed to the compiler or linker. Don't know exactly which reply, but it should be findable in the mail-list database. AFAIK it was never verified that it was the cause. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190106130206.56332774>