Date: Wed, 2 Jan 2019 22:26:44 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" Message-ID: <8185af76-8ff1-5e16-c186-2df2c5a5df2c@FreeBSD.org> In-Reply-To: <CAPrugNrDdE-=ZGAy3pAHLXMKuCNrMBZt-souzCqXAR4fGLXvjg@mail.gmail.com> References: <antoine@freebsd.org> <CAALwa8neThcas8V4ytdz1LuJnjYY0j0qHB__MHsE6uz4FohkeA@mail.gmail.com> <201812282055.wBSKtW0e037582@slippy.cwsent.com> <20190102055219.GA3050@c720-r342378> <CAPrugNphKWFJDVmSgFcK1fzdUSWKDY01QW5PgCUeSMS3CFjDAg@mail.gmail.com> <CAPrugNrDdE-=ZGAy3pAHLXMKuCNrMBZt-souzCqXAR4fGLXvjg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/01/2019 4:56 pm, Matthew Macy wrote: > I just updated world/kernel/ports to today's HEAD and packages and > pkg "upgraded" chrome to be broken in this way. This isn't an isolated > issue. > > On Tue, Jan 1, 2019 at 9:55 PM Matthew Macy <mat.macy@gmail.com> wrote: >> >> I just updated world/kernel/ports to today's HEAD and packages and >> pkg "upgraded" chrome to be broken in this way. This isn't an isolated >> issue. >> >> On Tue, Jan 1, 2019 at 9:53 PM Matthias Apitz <guru@unixarea.de> wrote: >>> >>> El día viernes, diciembre 28, 2018 a las 12:55:32p. m. -0800, Cy Schubert escribió: >>> >>>> In message <CAALwa8neThcas8V4ytdz1LuJnjYY0j0qHB__MHsE6uz4FohkeA@mail.gma >>>> il.com> >>>> , Antoine Brodin writes: >>>>> On Fri, Dec 28, 2018 at 8:39 PM Graham Perrin <grahamperrin@gmail.com> wrote: >>>>>> >>>>>> On Fri, 28 Dec 2018 at 16:31, Emiel Kollof <coolvibe@hackerheaven.org> wrot >>>>> e: >>>>>> >>>>>>> Confirmed with Chromium on my CURRENT box: >>>>>> >>>>>> … >>>>>> >>>>>> Thanks folks. Should I report it as a bug with devel/glib20? >>>>> >>>>> Hi, >>>>> >>>>> I think it's a regression in the toolchain (the problem doesn't occur >>>>> on 11.2 or 12.0), so it should be reported to freebsd-toolchain@ >>>> >>>> No issue here however I rebuilt glib on Dec 21. >>> >>> I see the same with www/chromium on r342378 and ports, both from Dec 23. >>> >>> matthias >>> >>> -- The issue is being tracked in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220103 Per my last comment (comment 36), any base change(s) required to resolve the issue, once identified, should be tracked separately as a blocking issue.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8185af76-8ff1-5e16-c186-2df2c5a5df2c>