Opened 3 years ago
Last modified 3 years ago
#17428 new bug
Build fails: Failed to init MIME DB
Reported by: | humdinger | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Build System | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev55664, 64bit Haiku source is at hrev55667.
Buildtools are up-to-date. My "generated" folder sits on a separate volume and is linked to the "haiku" top folder. I've removed generated/objects.
I successfully configured from within the "generated" folder with:
/HaikuSrc/haiku/configure -j8 --distro-compatibility official --target-arch x86_64 --cross-tools-source /HaikuSrc/buildtools --build-cross-tools x86_64
jam -qj1 DiskProbe
fails with:
/HaikuSrc/haiku> jam -qj1 DiskProbe Starting build of type regular ... Asked for bios_ia32 target boot platform Unknown path to handle adding to image Asked for pxe_ia32 target boot platform Unknown path to handle adding to image ...patience... ...patience... ...found 14218 target(s)... ...updating 6 target(s)... Link generated/objects/haiku/x86_64/release/system/libroot/libroot.so SetType1 generated/objects/haiku/x86_64/release/system/libroot/libroot.so MimeSet1 generated/objects/haiku/x86_64/release/system/libroot/libroot.so mimeset: Failed to init MIME DB: File or Directory already exists LIBRARY_PATH="$LIBRARY_PATH:/HaikuSrc/haiku/generated/objects/haiku_host/lib" \ generated/objects/haiku_host/x86_64/release/tools/mimeset -f --mimedb "generated/objects/common/data/mime_db/mime_db" "generated/objects/haiku/x86_64/release/system/libroot/libroot.so" ...failed MimeSet1 generated/objects/haiku/x86_64/release/system/libroot/libroot.so ... ...removing generated/objects/haiku/x86_64/release/system/libroot/libroot.so BUILD FAILURE: ...failed updating 1 target(s)... ...skipped 2 target(s)...
Attachments (1)
Change History (5)
follow-up: 3 comment:2 by , 3 years ago
My "generated" folder sits on a separate volume and is linked to the "haiku" top folder. I've removed generated/objects.
Ah, I missed this detail last time, this is probably the cause. For now, try sym-linking the "generated" directory to the other volume from within the "haiku" checkout, and see if that works for now.
Some parts of the build system may assume everything happens on the same volume, though. (When did this stop working?)
comment:3 by , 3 years ago
Replying to waddlesplash:
My "generated" folder sits on a separate volume and is linked to the "haiku" top folder. I've removed generated/objects.
Ah, I missed this detail last time, this is probably the cause. For now, try sym-linking the "generated" directory to the other volume from within the "haiku" checkout, and see if that works for now.
I don't think I quite understand... Isn't that what I already had? I've now put all generated folders in a subfolder on the "Generator" volume (before those were directly in the root folder of the volume).
/HaikuSrc/haiku> ls -la lrwxrwxrwx 1 user root 20 Jan 28 09:29 generated -> /Generator/generated
In any case, still does not work. Attached is the strace output you suggested above.
Some parts of the build system may assume everything happens on the same volume, though. (When did this stop working?)
I've been getting that error for a few months now.
I guess I'll be moving the source to the "Generator" volume and try doing all on the same volume. 10 GiB free space should do, I guess.
comment:4 by , 3 years ago
FWIW, moving the source to the "Generator" volume and building it all on that one volume works.
Please run the command with strace. That is:
and attach the output here.