Mailinglist Archive: opensuse-packaging (129 mails)

< Previous Next >
[opensuse-packaging] Different gcc behaviour in osc chroot and on host system
While trying to build customized openjdk package, I've encountered interesting
thing... The command, listed below, works fine on host system but fails on
chrooted system (both systems are openSUSE 13.2 with stock gcc). Experimenting
with it showed that it starts to work as soon as I move '-lz' from the
beginning of the command to the very end.

The failure is exactly like here, with undefined references to zlib:

I've found the fix on openSUSE Java:Factory project, so the question is about
difference between host and chroot. What can be the cause of such a different
behaviour? Is there some additional package that may be installed on my host
system but was not dragged by dependencies to the chrooted system? Or some env
flag or config file?

The command:
/usr/bin/gcc-4.8 -lz -Xlinker -z -Xlinker defs -Xlinker -O1 -Xlinker --allow-
shlib-undefined -Xlinker -Xlinker -z -Xlinker origin -
Xlinker -rpath -Xlinker \$ORIGIN -lc -Xlinker -version-
vers-unpack200 -o /home/user/dev/java//build/jdk/objs/unpackexe/unpack200
/home/user/dev/java//build/jdk/objs/unpackexe/zip.o -Wl,-Bstatic -lstdc++ -
lgcc -Wl,-Bdynamic


To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >