Date: Sun, 6 Aug 2017 05:34:40 -0400 From: Ed Maste <emaste@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: Aijaz Baig <aijazbaig1@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: buildworld fails while building static clang library Message-ID: <CAPyFy2Cabrn7BCDc%2Bhw=tebJuTgr3iiS2KdvkmJuzG=b=QW9pg@mail.gmail.com> In-Reply-To: <37395FD6-09E5-4C11-A189-7B3050E9A541@FreeBSD.org> References: <CAHB2L%2BfM8xtRWo8XU59yT=vrtUjv6v_JEkg_8ehyMDp3ME%2BvsQ@mail.gmail.com> <9C14A21D-1C17-44F9-882B-4A01C311E164@FreeBSD.org> <CAHB2L%2BeKi2XaaVwzn0KBmn-xQd52f7hxex_8CPx_YGi5B14pWg@mail.gmail.com> <37395FD6-09E5-4C11-A189-7B3050E9A541@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 August 2017 at 16:16, Dimitry Andric <dim@freebsd.org> wrote: > > I remember there being an issue with ar and/or ranlib choking when the > .a files become too big. Ed, does that ring any bells? Our ar (and ranlib, which is the same binary) will produce a corrupt symbol table if the .a archive output is larger than 4GB, because we support only 32-bit offsets in the older "/" symbol table format, not the "/SYM64/" format and 64-bit offsets. As with GNU ar from binutils 2.17.50 we silently truncate if the offset does not fit in 32 bits. I'll have a patch for review soon to exit on error rather than produce corrupted output, and hope to look at adding /SYM64/ support later on.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Cabrn7BCDc%2Bhw=tebJuTgr3iiS2KdvkmJuzG=b=QW9pg>