On Thu, Sep 19, 2019 at 8:29 AM Mark Millard via freebsd-toolchain
wrote:
>
> [This is from a system-clang 8 based FreeBSD context for
> powerpc64 [ELFv1], not the usual gcc 4.2.1 based context.]
>
> In attempting to update the ports I normally build, jumping
> ahead from -r509171 to ports head
On Thu, Dec 13, 2018 at 3:25 AM Mark Millard via freebsd-toolchain
wrote:
> Looks like this might have been from a race condition or some such.
> Rerunning the meta-mode build again had no such problem and completed.
It is also happening in clean build, I've filed a PR about this:
On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>
> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>
> > On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
> >> Li-Wen reported that the build is done in a 11.1-rel jail though, so
> >> the libarchive (
.freebsd.org is running r331373 now.
--
Li-Wen Hsu
https://lwhsu.org
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
t; *** [libclang_rt.asan_cxx-i386.a] Error code 70
> >>
> >>
> >> (Notice the variability in what .a the ranlib's fail for.)
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
t; >>>
> >>> make[5]: stopped in /usr/src/kerberos5/lib/libkafs5
> >>> --- libkafs5.a ---
> >>> *** [libkafs5.a] Error code 70
> >>>
> >>> and:
> >>>
> >>>
> >>> --- lib__L ---
> >>> ranlib -D l
since aarch64-binutils upgraded to 2.28 on pkg.freebsd.org.
Should we revert this change for now? Or the fix is being prepared?
Best,
Li-Wen
--
Li-Wen Hsu <lw...@freebsd.org>
https://lwhsu.org
___
freebsd-toolchain@freebsd.org mailing list
https:
