Re: buildworld falure: truncated or malformed archive
On Wed, Jan 2, 2019, 1:42 PM John Baldwin On 12/31/18 12:08 PM, Warner Losh wrote: > > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone > > >> Does this mean that it's currently impossible to build a world with > >> debug symbols? > >> > > > > Yes. Clang is simply too big until 64 bit offset support goes in. > > We actually build clang (and llvm) with stripped down debug symbols by > default. If you don't put any DEBUG_* foo in src.conf you will get debug > symbols for all of the world including the limited ones for clang. (We > use -gline-tables-only or some > Yea, DEBUG_FLAGS=-g is what breaks it... Warner > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
On 12/31/18 12:08 PM, Warner Losh wrote: > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone >> Does this mean that it's currently impossible to build a world with >> debug symbols? >> > > Yes. Clang is simply too big until 64 bit offset support goes in. We actually build clang (and llvm) with stripped down debug symbols by default. If you don't put any DEBUG_* foo in src.conf you will get debug symbols for all of the world including the limited ones for clang. (We use -gline-tables-only or some such for clang). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
There's always 'WITHOUT_CLANG=1' in src.conf. Best, Conrad On Mon, Dec 31, 2018 at 12:09 PM Warner Losh wrote: > > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone > > Does this mean that it's currently impossible to build a world with > > debug symbols? > > > > Yes. Clang is simply too big until 64 bit offset support goes in. > > Warner > > > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
On Mon, Dec 31, 2018, 1:36 PM Ryan Stone Does this mean that it's currently impossible to build a world with > debug symbols? > Yes. Clang is simply too big until 64 bit offset support goes in. Warner > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
Does this mean that it's currently impossible to build a world with debug symbols? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
On Thu, 27 Dec 2018 at 19:16, Warner Losh wrote: > > On Thu, Dec 27, 2018, 5:29 PM Ed Maste > >> On Thu, 27 Dec 2018 at 14:35, Ryan Stone 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. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
On Thu, Dec 27, 2018, 5:29 PM Ed Maste On Thu, 27 Dec 2018 at 14:35, Ryan Stone 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. Warner > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
On Thu, 27 Dec 2018 at 14:35, Ryan Stone 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? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld falure: truncated or malformed archive
On Thu, Dec 27, 2018, 2:36 PM Ryan Stone I'm trying to update an old (~May 2018) -head system to the latest, > but I'm getting a persistent error during buildworld: > > ld: error: /usr/obj/usr/src/amd64.amd64/lib/clang/libclang/libclang.a: > could not get the member for symbol > > _ZN5clang17MultiplexConsumerC1ENSt3__16vectorINS1_10unique_ptrINS_11ASTConsumerENS1_14default_deleteIS4_NS1_9allocatorIS7_: > truncated or malformed archive (terminator characters in archive > member "dC" not the correct "`\n" values for the archive member header > for tOutputExprEj > > I seem to recall something about libarchive or ar having a bug > creating archives > 4GB, but I tried doing a "make install" from > lib/libarchive and usr.bin/ar and doing a rebuild, and that doesn't > seem to have resolved the issue. I also made sure to try a build with > a clean /usr/obj with no success. Any ideas how I can get past this? > Remove any DEBUG_FLAGS. .a files can't be larger than 4GB. Clang / llvm now explodes the limit. Warner ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
buildworld falure: truncated or malformed archive
I'm trying to update an old (~May 2018) -head system to the latest, but I'm getting a persistent error during buildworld: ld: error: /usr/obj/usr/src/amd64.amd64/lib/clang/libclang/libclang.a: could not get the member for symbol _ZN5clang17MultiplexConsumerC1ENSt3__16vectorINS1_10unique_ptrINS_11ASTConsumerENS1_14default_deleteIS4_NS1_9allocatorIS7_: truncated or malformed archive (terminator characters in archive member "dC" not the correct "`\n" values for the archive member header for tOutputExprEj I seem to recall something about libarchive or ar having a bug creating archives > 4GB, but I tried doing a "make install" from lib/libarchive and usr.bin/ar and doing a rebuild, and that doesn't seem to have resolved the issue. I also made sure to try a build with a clean /usr/obj with no success. Any ideas how I can get past this? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
