Build fails at creating haiku_source.hpkg

[bullfrog]

Can be duplicated in most hrev52711 and beta1. Basic/plain ./configure; jam -j4

AddExtractFileToContainerExtractFilesScript <HaikuImage>haiku.image-extract-files-dummy-home/config/settings/WebPositive-src/apps/webpositive/bookmarks/WebPositiveBookmarks.zip

haiku.hpkg: mimeset'ing package contents ...

haiku.hpkg: Creating the package ...

haiku_source.hpkg: mimeset'ing package contents ...

haiku_source.hpkg: Creating the package ...

BUILD FAILURE:

...failed updating 1 target(s)...

...skipped 25 target(s)...

...updated 1293 target(s)...

[waddlesplash]

It appears to have succeeded in making the package. "Failed updating 1 targets" doesn't mean it's the last target that failed, only that one of the targets failed.

Please attach a text file with the full build output.

[bullfrog]

Full output of last build attempt.

[waddlesplash]

ld: generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/bios_ia32/boot_platform_bios_ia32.o: in function `BIOSDrive::WriteAt(void*, long long, void const*, unsigned long)':
	(.text+0xff0): undefined reference to `__divmoddi4'
...

This is the actual problem. It looks like your cross-tools don't contain a working 32-bit libgcc.

Are you building Haiku on Haiku?

[bullfrog]

Haiku on haiku. This has been occurring on a couple fresh git clones on both beta and the last 3 or so nightly hrevs. All 64bit. Should I be specifying x86_64 in the ./configure? This could be the problem? I don't recall having to do so on previous successful builds. But those were on a different box.

[waddlesplash]

Then this is just a duplicate of #10815. The problem is that our "gcc" package does not include multilib (32-bit) libraries. You can work around this by just building the cross-tools, as one must do on non-Haiku platforms also.

[nielx]

Remove milestone for tickets with status = closed and resolution != fixed