Opened 5 years ago

Last modified 5 years ago

#11194 new bug

Problems with build_packages

Reported by: axeld Owned by: bonefish
Priority: low Milestone: R1
Component: Build System Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description (last modified by axeld)

Using OpenSUSE 13.1 on x64. It could not find <solv/pool.h>; it obviously uses the wrong header location. When I installed libsolv-devel, it would get a bit further, and would then not find <solv/repo_haiku.h>.

This is the compilation line:

cc -c "/home/axeld/develop/haiku/haiku/src/kits/package/solver/LibsolvSolver.cpp" -O2 -Wall -Wno-trigraphs -Wno-ctor-dtor-privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign-compare -Wno-multichar -include BeOSBuildCompatibility.h -fPIC -DARCH_x86_64 -D_NO_INLINE_ASM -Dx86_64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DSTDC_FORMAT_MACROS -DSTDC_LIMIT_MACROS -DHAIKU_HOST_USE_XATTR_REF -DHAIKU_HOST_PLATFORM_LINUX -DHAIKU_HOST_PLATFORM_64_BIT -DHAIKU_PACKAGING_ARCH=\"x86_gcc2\" -iquote /home/axeld/develop/haiku/haiku/build/user_config_headers -iquote /home/axeld/develop/haiku/haiku/build/config_headers -iquote src/build/libpackage/solver -iquote /home/axeld/develop/haiku/haiku/generated/objects/common/build/libpackage/solver -iquote /home/axeld/develop/haiku/haiku/generated/objects/linux/x86_64/common/build/libpackage/solver -iquote /home/axeld/develop/haiku/haiku/generated/objects/haiku/x86_gcc2/common/build/libpackage/solver -iquote /home/axeld/develop/haiku/haiku/src/kits/package/solver -iquote /home/axeld/develop/haiku/haiku/generated/build_packages/libsolv-0.3.0_haiku_2013_10_01-1-x86_gcc2/develop/headers/solv -I /home/axeld/develop/haiku/haiku/generated/build_packages/libsolv-0.3.0_haiku_2013_10_01-1-x86_gcc2/develop/headers -I /home/axeld/develop/haiku/haiku/headers/private/shared -I /home/axeld/develop/haiku/haiku/headers/build/host/linux -I /home/axeld/develop/haiku/haiku/headers/build -I /home/axeld/develop/haiku/haiku/headers/build/os -I /home/axeld/develop/haiku/haiku/headers/build/os/add-ons/registrar -I /home/axeld/develop/haiku/haiku/headers/build/os/app -I /home/axeld/develop/haiku/haiku/headers/build/os/drivers -I /home/axeld/develop/haiku/haiku/headers/build/os/kernel -I /home/axeld/develop/haiku/haiku/headers/build/os/interface -I /home/axeld/develop/haiku/haiku/headers/build/os/locale -I /home/axeld/develop/haiku/haiku/headers/build/os/storage -I /home/axeld/develop/haiku/haiku/headers/build/os/support -I /home/axeld/develop/haiku/haiku/headers/build/private -o "/home/axeld/develop/haiku/haiku/generated/objects/linux/x86_64/release/build/libpackage/solver/LibsolvSolver.o" ;

Change History (5)

comment:1 by axeld, 5 years ago

Description: modified (diff)

comment:2 by bonefish, 5 years ago

The include paths look good ("-I /home/axeld/develop/haiku/haiku/generated/build_packages/libsolv-0.3.0_haiku_2013_10_01-1-x86_gcc2/develop/headers/solv -I /home/axeld/develop/haiku/haiku/generated/build_packages/libsolv-0.3.0_haiku_2013_10_01-1-x86_gcc2/develop/headers"). Have you checked that the packages have been extracted correctly?

Installing the libsolv-devel package might be detrimental. IIRC the -I paths are searched after the built-in paths (/usr/include), so that our headers would be shadowed.

comment:3 by axeld, 5 years ago

Okay, I've looked into it now: the build stopped the first time, as I had forgotten to install curl-devel. This probably somehow caused the build_packages/libsolv directory to be empty. After removing that directory, things are now progressing as they should.

Should we keep this open or not? While it would be nice to be able to prevent such things from happening, I'm not sure if it's ultimately worth the effort.

comment:4 by waddlesplash, 5 years ago

Priority: blockerhigh
Summary: Libsolv linux build failsProblems with build_packages

Since this has a workaround and does not prevent building Haiku on openSUSE, I'm downgrading the priority.

comment:5 by bonefish, 5 years ago

Priority: highlow

I don't think I'll work on this anytime soon. It really isn't high priority IMO. Leaving the ticket open just to track the issue... in case someone else feels motivated.

Note: See TracTickets for help on using tickets.