Skip to contentSkip to conversation

Recent problems with host library leakage into the build

DISCUSSION Stefan Schmidt 2 participants 4 messages Mar 1, 2011

lore
Share & tools
lore
#0 lore raw

Hello.

I just stumbled over two problems in the testing-release bracnh that have wrong path to the libs while linking the binaries and fail due to ld not being happy to link x86_64 with ARM :)

openjdk-6_6b18-1.8:

| arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/home/stefan/oe-dev/build/tmp/sysroots/armv7a-angstrom-linux-gnueabi -shared -Wl,--whole-archive ../../src/fdlibm/.libs/libfdlibm.a ../../src/mm/.libs/libmm.a ../../src/native/.libs/libnative.a ../../src/threads/.libs/libthreads.a ../../src/toolbox/.libs/libtoolbox.a ../../src/vm/.libs/libvm.a ../../src/vmcore/.libs/libvmcore.a -Wl,--no-whole-archive -L/usr/lib -lz -lpthread -ldl -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb -Wl,--version-script=../../contrib/mapfile-vers-product -Wl,-O1 -Wl,--hash-style=gnu -Wl,-soname -Wl,libjvm.so -o .libs/libjvm.so

| /usr/lib/libz.so: file not recognized: File format not recognized
| collect2: ld returned 1 exit status
| libtool: install: error: relink `libjvm.la' with the above command before

installing it

I imagine that I have seen something similar for freetype, but I can't reproduce it right now.

Anyone an idea what causes this? If not I'm going to bisect it. Its just painful as openjdk needs tons of time to build.

regards
Stefan Schmidt

#1 lore raw
Quoted 24 lines · Stefan Schmidt

Hello.

I just stumbled over two problems in the testing-release bracnh that have wrong path to the libs while linking the binaries and fail due to ld not being happy to link x86_64 with ARM :)

openjdk-6_6b18-1.8:

| arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon

(quoted diff) +0 -3
-mfloat-abi=softfp -mthumb-interwork -mno-thumb
--sysroot=/home/stefan/oe-dev/build/tmp/sysroots/armv7a-angstrom-linux-gnueabi
-shared  -Wl,--whole-archive ../../src/fdlibm/.libs/libfdlibm.a

../../src/mm/.libs/libmm.a ../../src/native/.libs/libnative.a ../../src/threads/.libs/libthreads.a ../../src/toolbox/.libs/libtoolbox.a ../../src/vm/.libs/libvm.a ../../src/vmcore/.libs/libvmcore.a

(quoted diff) +0 -4
-Wl,--no-whole-archive  -L/usr/lib -lz -lpthread -ldl  -march=armv7-a
-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-Wl,--version-script=../../contrib/mapfile-vers-product -Wl,-O1
-Wl,--hash-style=gnu -Wl,-soname -Wl,libjvm.so -o .libs/libjvm.so
| /usr/lib/libz.so: file not recognized: File format not recognized
| collect2: ld returned 1 exit status
| libtool: install: error: relink `libjvm.la' with the above command before

installing it

Quoted 8 lines

I imagine that I have seen something similar for freetype, but I can't reproduce it right now.

Anyone an idea what causes this? If not I'm going to bisect it. Its just painful as openjdk needs tons of time to build.

regards
Stefan Schmidt

Hi,

seems I fixed it only for the newer 1.8.5 release. Problem is with cacao which is configured from the icedtea Makefile. It's needing autoreconf and --with-libtool-sysroot

Have a look at the cacao-libtoolize.patch

Bye Henning

#2 lore raw

Hello.

Quoted 25 lines · Henning Heinold
Quoted 24 lines · Stefan Schmidt

Hello.

I just stumbled over two problems in the testing-release bracnh that have wrong path to the libs while linking the binaries and fail due to ld not being happy to link x86_64 with ARM :)

openjdk-6_6b18-1.8:

| arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon

(quoted diff) +0 -3
-mfloat-abi=softfp -mthumb-interwork -mno-thumb
--sysroot=/home/stefan/oe-dev/build/tmp/sysroots/armv7a-angstrom-linux-gnueabi
-shared  -Wl,--whole-archive ../../src/fdlibm/.libs/libfdlibm.a

../../src/mm/.libs/libmm.a ../../src/native/.libs/libnative.a ../../src/threads/.libs/libthreads.a ../../src/toolbox/.libs/libtoolbox.a ../../src/vm/.libs/libvm.a ../../src/vmcore/.libs/libvmcore.a

(quoted diff) +0 -4
-Wl,--no-whole-archive  -L/usr/lib -lz -lpthread -ldl  -march=armv7-a
-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-Wl,--version-script=../../contrib/mapfile-vers-product -Wl,-O1
-Wl,--hash-style=gnu -Wl,-soname -Wl,libjvm.so -o .libs/libjvm.so
| /usr/lib/libz.so: file not recognized: File format not recognized
| collect2: ld returned 1 exit status
| libtool: install: error: relink `libjvm.la' with the above command before

installing it

Quoted 2 lines
Quoted 2 lines

I imagine that I have seen something similar for freetype, but I can't reproduce it right now.

Forgot about this one. It was on a private branch. Nothing in OE.

Quoted 6 lines
Quoted 5 lines

Anyone an idea what causes this? If not I'm going to bisect it. Its just painful as openjdk needs tons of time to build.

regards
Stefan Schmidt

Quoted 7 lines

Hi,

seems I fixed it only for the newer 1.8.5 release. Problem is with cacao which is configured from the icedtea Makefile. It's needing autoreconf and --with-libtool-sysroot

Have a look at the cacao-libtoolize.patch

Thanks a lot. Will do after lunch.

regards
Stefan Schmidt

#3 lore raw

Hello.

Quoted 8 lines · Stefan Schmidt
Quoted 6 lines

seems I fixed it only for the newer 1.8.5 release. Problem is with cacao which is configured from the icedtea Makefile. It's needing autoreconf and --with-libtool-sysroot

Have a look at the cacao-libtoolize.patch

Thanks a lot. Will do after lunch.

I decided for going with the newer release as it does fix some security issues as well. I just pushed a patch which updates the default version in angstrom-jalimo and openjdk-6 builds fine again.

If somebody really wants to go with the old version, I see no reason, it would need to get a libtool fix like henning did for the new version. But I would prefer to remove it as it is a version with known security problems.

regards
Stefan Schmidt