Re: Compilation fails with "skipping incompatible .../libstdc++ .. "

114 views
Skip to first unread message

Gerhard Smith

unread,
Dec 3, 2012, 1:51:38 PM12/3/12
to andro...@googlegroups.com
You need yo install the 32bit libraries.

On Monday, December 3, 2012 5:12:29 PM UTC, JPT wrote:
Hi,

I would like to install android-x86 on my Centrino convertible laptop.
I already tried a nightly build iso, which seemed to be rather old. But sometimes it worked more or less.

That's why I am now trying to compile on my own. Started on Windows but moved to Linux when it complained about a the filesystem not being case sensitive.
I already solved a ton of problems, but now I haven't got any idea left.

I am building on a Mint KDE 64 bit linux. And this seems to be the problem:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=generic_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76L
============================================
host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.so when searching for
 -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.a when searching for
-lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld gab 1 als Ende-Status zurück
make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp] Fehler 1


Why ist HOST_ARCH=x86?
I already tried to install ia86-libs, but this did not help.

Could you please give a hint?

thanks,

JPT

Marek Vasut

unread,
Dec 3, 2012, 4:59:01 PM12/3/12
to andro...@googlegroups.com, JPT
Dear JPT,
You're missing libstdc++ package (esp. -dev package if you're on debian) and
possible it's ia32 version.

Best regards,
Marek Vasut

JPT

unread,
Dec 4, 2012, 3:22:57 PM12/4/12
to andro...@googlegroups.com
I already installed ia32-libs. This did not help.
Today I tried lib32stdc++6, no change...
According to the message it did not find the newly installed library.
So the log is still the same.
Do I have to feed the library location into the build script? Or should I create a symlink somewhere?

JPT

unread,
Dec 4, 2012, 3:40:13 PM12/4/12
to andro...@googlegroups.com
Now it works.
Found a solution which said:
cd /usr/lib32
ln -s libstdc++.so.6 libstdc++.so

I don't like this, because this is the first time I have to add links in the library folders. But it works.
Is there any "clean" solution to this problem?

Thanks!

gerhard smith

unread,
Dec 5, 2012, 5:13:19 AM12/5/12
to andro...@googlegroups.com
That is the standard way that libraries are set up to point at the latest incarnation and is normally done when the library is installed/updated by the installer - so it is a 'clean' solution.
Reply all
Reply to author
Forward
0 new messages