Date: Thu, 27 Dec 2018 20:20:37 -0500 From: Ed Maste <emaste@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: Ryan Stone <rysto32@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: buildworld falure: truncated or malformed archive Message-ID: <CAPyFy2CV99wiLOrJab8sbWbLmjgPfkGg8q%2Bwn9fs%2BM2xbr%2BOng@mail.gmail.com> In-Reply-To: <CANCZdfr1DmYvDFHhfmK4MZ2ZtVOewVa3-KHrXEhnvPANNhHkog@mail.gmail.com> References: <CAFMmRNyPq5O5Wj1T4PDxW6U8R=oV-wGy_vH_2QdMTg621V0R6A@mail.gmail.com> <CAPyFy2DWh94JM5gErJPsZRxPQ6ZL8Ba5Vz9kMFdYDYeTdhR7Hg@mail.gmail.com> <CANCZdfr1DmYvDFHhfmK4MZ2ZtVOewVa3-KHrXEhnvPANNhHkog@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Dec 2018 at 19:16, Warner Losh <imp@bsdimp.com> wrote: > > On Thu, Dec 27, 2018, 5:29 PM Ed Maste <emaste@freebsd.org wrote: >> >> On Thu, 27 Dec 2018 at 14:35, Ryan Stone <rysto32@gmail.com> wrote: >> > >> > I seem to recall something about libarchive or ar having a bug >> > creating archives > 4GB, >> >> Indeed, FreeBSD's bespoke ar does not support the /SYM64/ format >> needed for offsets >4GB. imp@ also ran into this; I'm not sure what's >> causing libclang.a to be >4GB. Is there one object file that's >> unreasonably large? > > > For me it was a DEBUG_FLAGS=-g I had in make.conf that I'd forgotten about. > > Ar should fail to create a .a that's >4GB. Yes - at least, one with a symbol table. It's PR234454. Next month two co-op students will start working for the FreeBSD Foundation and adding 64-bit /SYM64/ support to ar will probably make a good starting project for one of them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CV99wiLOrJab8sbWbLmjgPfkGg8q%2Bwn9fs%2BM2xbr%2BOng>