Build of Haiku fails while writing image

[markh]

Building Haiku from source on Haiku itself fails on my machine with the following error (complete log attached):

Creating image ...
Writing boot code to "/boot/home/haiku/generated/haiku.image" (partition offset: 0 bytes, start offset = 0) ...
Populating image ...
Extracting src/apps/webpositive/bookmarks/WebPositiveBookmarks.zip ...
Resolving package dependencies ...
Error while writing to file `/myfs/system/packages/libxml2-2.9.9-4-x86_gcc2.hpkg': No space left on device
Error: Command failed: No space left on device
Error: Command was:
  cp -f :generated/download/libxml2-2.9.9-4-x86_gcc2.hpkg /myfs/system/packages

export imagePath="generated/haiku.image"
export isImage="1"
export isVMwareImage=""
build/scripts/build_haiku_image /boot/home/haiku/generated/haiku.image-init-vars /boot/home/haiku/generated/haiku.image-make-dirs /boot/home/haiku/generated/haiku.image-copy-files /boot/home/haiku/generated/haiku.image-extract-files

...failed BuildHaikuImage1 generated/haiku.image ...
...removing generated/haiku.image

BUILD FAILURE:
...failed updating 1 target(s)...
...skipped 1 target(s)...
...updated 1471 target(s)...

[markh]

Complete logof build

[diver]

No space left on device

[waddlesplash]

@anyboot-image

I don't think this profile works anymore (and it should probably be removed.) Try @minimum-anyboot or @nightly-anyboot (whichever you need) instead.

[markh]

Ok, those work. But what about @image that is mentioned at ​https://www.haiku-os.org/guides/building/compiling-x86? I am getting the same failure as with @anyboot-image. Is that one also not supported?

[waddlesplash]

I don't know. CC PulkoMandy and kallisti5: Why do we have these profiles, anyway? Aren't they deprecated in favor of @mininum-, @nightly-, @release-? (Or are these the "regular" profiles...?) Not sure the docs should mention them either.

[kallisti5]

@(profile)-(media)

To be honest, i've never heard of @image and don't think it's valid.

​https://git.haiku-os.org/haiku/tree/build/jam/DefaultBuildProfiles#n34

I remember building haiku-image back in the day (no @), but it isn't recommended anymore.

Profiles:

• bootstrap -- When bootstrapping an architecture
• minimum -- Minimum set of packages
• nightly -- Normal nightly build. You should be using this.
• release -- "Full release", generally only used for things like R1B1, etc.

Media:

• raw -- raw disk image
• cd -- iso image, non-booting on USB flash drives (we don't use this anymore)
• vmware -- this used to work, but few folks use it anymore. vmdk
• anyboot -- iso image, boots as a CD or from USB flash drives
• mmc -- sd card image, used on arm (or anywhere else an SD card image is needed.. essentially just raw with a partition table)

[pulkomandy]

I think @image predates the introduction of "profiles" as you call them.

It is part of a small set of special profiles set at the end of DefaultBuildProfiles alongside anyboot-image, cd-image, vmware-image, and install. Of these I think only @install is important (it allows to build form haiku and put the resulting files directly in a mounted bfs partition, bypassing the use of bfs_shell for generating a filesystem image).

I don't think these were ever formally deprecated, especally as our compiling-x86 build instructions still advertise them :)

I'm not against some cleanup, however. But we need to keep at least @install anyway, or maybe make that @minimum-install?

It does not look too hard to fix anyway. Does @minimum-raw still works? I think they are both very similar and we need to increase the HAIKU_DEFAULT_IMAGE_SIZE (currently 300MB) for both?

[waddlesplash]

Minimum raw still works, I use it a lot. 300 MB is more than enough, the minimum image only uses about 150MB I think.