Opened 11 years ago
Closed 11 years ago
#10806 closed bug (no change required)
[ZlibCompressor] zconf.h is missing when cross-compiling from Ubuntu 14.04
Reported by: | starsseed | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Build System | Version: | R1/Development |
Keywords: | zlib | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
zconf.h (from package zlib1g-dev) is assumed to be in /usr/include (which was correct in ubuntu 64-bit 12.04 and 32-bit 13.10, bot not in 14.04) https://bugzilla.mozilla.org/show_bug.cgi?id=865856
In file included from headers/build/../private/package/hpkg/ZlibCompressor.h:9:0, from headers/build/private/package/hpkg/ZlibCompressor.h:1, from headers/build/../private/package/hpkg/DataWriters.h:11, from headers/build/private/package/hpkg/DataWriters.h:1, from src/kits/package/hpkg/DataWriters.cpp:8: /usr/include/zlib.h:34:19: fatal error: zconf.h: Aucun fichier ou dossier de ce type #include "zconf.h"
Change History (3)
comment:1 by , 11 years ago
Component: | Kits/Package Kit → Build System |
---|---|
Keywords: | zlib added; ubuntu cross-compile X86_64 zlib1g-dev zconf.h zlib.h removed |
Resolution: | → no change required |
Status: | new → closed |
comment:2 by , 11 years ago
Resolution: | no change required |
---|---|
Status: | closed → reopened |
No it's not a misconfiguration in Ubuntu : zconf.h has been move because zlib1g-dev designer think it is a plateform specific header. I think, haiku's build system should not rely on a 64Bit specific header for building a 32 bit haiku image.
comment:3 by , 11 years ago
Resolution: | → no change required |
---|---|
Status: | reopened → closed |
The status of the ticket in Ubuntu's bug tracker isn't "Confirmed" for no reason. Apparently their tool chain has not been configured correctly to include the respective multi-arch include directory.
This is apparently a misconfiguration in Ubuntu. It is tracked in https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1155307. According to that bug report the issue is specific to 32-bit builds. So you simply shouldn't force that (I assume you did by configuring with
--use-32bit
).