gmane.linux.lfs.clfs.devel

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

lee sudo — 2012-05-26T04:32:27

Dear Andrew,
I find the compiler from android and
http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/both
build cross compile just use static library. So they dont depend on
dynamic
library and can be changed the path.
This is the result after i compile kernel by compile from www.mentor.com(you
can see the "static linked"), and i check the script in the source code of
mentor's compile, i'm sure they only use static libraies.
----------------------------------------------------
[Lee]~/source/3.0.30$ file vmlinux
vmlinux: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically
linked, BuildID[sha1]=0xe1b9d7b6e9edc66715eb1b4d47bf983fa9ff6745, not
stripped
----------------------------------------------------
But when i build libraries as static, the library cloog-ppl-0.15.11 cannot
be built passed, so much errors.
Now i'm very very confused.

On Fri, May 25, 2012 at 12:33 AM, Andrew Bradford <
andrew< at >bradfordembedded.com> wrote:

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

lee sudo — 2012-05-25T02:06:19

Dear Andrew,
I perform "gcc -v", and this is the result:
Using built-in specs.
Target: arm-eabi
Configured with:
/home/jingyu/projects/gcc/android-toolchainsrc/build/../gcc/gcc-4.4.3/configure
--prefix=/usr/local --target=arm-eabi --host=x86_64-linux-gnu
--build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld
--enable-languages=c,c++
--with-gmp=/home/jingyu/projects/gcc/toolchain_build/gingerbreadobj/temp-install
--with-mpfr=/home/jingyu/projects/gcc/toolchain_build/gingerbreadobj/temp-install
--disable-libssp --enable-threads --disable-nls --disable-libmudflap
--disable-libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions
--disable-shared --disable-tls --with-float=soft --with-fpu=vfp
--with-arch=armv5te --enable-target-optspace --with-abi=aapcs
--with-gcc-version=4.4.3 --with-binutils-version=2.19
--with-gmp-version=4.2.4 --with-mpfr-version=2.4.1 --with-gdb-version=7.1.x
--with-arch=armv5te --with-multilib-list=mandroid
--with-sysroot=/usr/local/google/home/android/cupcake_rel_root
--enable-gold=both/gol

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-24T16:33:28

On Thu, 24 May 2012 22:45:10 +0800
lee sudo <desoxydate< at >gmail.com> wrote:


Thanks, I did.


Sorry, I don't know.  Read through the GCC manual [1] for the version
of GCC you want to use, it should say how to.

[1]: http://gcc.gnu.org/onlinedocs/

-Andrew

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

lee sudo — 2012-05-24T14:45:10

Dear Andrew,

1, You can get android's C toolchain there:

git clone https://android.googlesource.com/platform/prebuilt
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
(FROM: http://source.android.com/source/building-kernels.html)

2, >try building your toolchain with relative paths
HOW to?
(You can modify my script direct)



On Thu, May 24, 2012 at 7:36 PM, Andrew Bradford <
andrew< at >bradfordembedded.com> wrote:

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-24T13:56:13

On Thu, 24 May 2012 07:52:51 -0500
DJ Lucas <dj< at >linuxfromscratch.org> wrote:


Thanks! I question Google's need for putting compiled gcc versions in a
git tree, but that's a separate debate :)

It looks like Google's Android gcc, so long as you move the entire
'prebuilt/linux-x86/toolchain/$ARCH' directory structure around as one
unit, is using relative paths for their GCC.  Their gcc, for example,
looks for libs in '../lib/gcc/$ARCH/$GCC_VERSION', relative to the gcc
binary.

If you build your GCC like Google does, you should get the same
effect.  CLFS doesn't have you do it the Google way, CLFS is more like
how Emdebian's cross compilers are built, with explicit paths to find
libs.  I don't know how to tell you how to do it the Google way, but
the GCC manuals should.

-Andrew

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-24T13:49:05

On Thu, 24 May 2012 07:47:04 -0400
Andrew Bradford <andrew< at >bradfordembedded.com> wrote:


OK, so that output isn't where gcc searches for things.  It's just the
info provided when gcc was configured and built.  The actual search
path can be different.

Better switches to see where gcc looks for things is
'-print-search-dirs' which will show you where gcc will look.

-Andrew

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

DJ Lucas — 2012-05-24T12:52:51

http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/ 
is what I use for kernel development. The AOSP code tree contains a more 
complete cross toolchain as well. git 
clone|https://android.googlesource.com/platform/manifest||for the whole 
schebang, or dig a little deeper for only the toolchain, I believe 
platform/||prebuilt/linux-x86/toolchain/arm-eabi-${GCC_VERSION}||.|
||

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-24T12:21:50

On Wed, 23 May 2012 19:28:18 +0800
lee sudo <desoxydate< at >gmail.com> wrote:


Also, this should probably have gone to the -support mailing list, not
the -dev list.  It's more of a support type question than a
development (of CLFS itself) question. Just FYI for the future.

For this thread, let's just keep it here for now. Attempting to migrate
to -support will just be messy.

-Andrew

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-24T11:47:04

On Thu, 24 May 2012 00:49:46 -0500
DJ Lucas <dj< at >linuxfromscratch.org> wrote:


I'd agree with you, except (especially) on a multi-arch system (or
anything with cross compilers and cross libs), the shared libs for the
target arch are going to be in rather different places than the shared
libs for the host arch. I'm not sure LD_LIBRARY_PATH will do much for
you here.

On my Debian system, I have arm cross compilers from Emdebian and native
x86_64 compiler from Debian Squeeze, and I don't have LD_LIBRARY_PATH
even set (echo $LD_LIBRARY_PATH comes back empty).  I have no problem
cross compiling or native compiling.

For example, output from my armel GCC shows where it expects includes
and libs:

andrew< at >bradford:~/calc/linux$ arm-linux-gnueabi-gcc -v
Target: arm-linux-gnueabi
Configured with: <snip>
--libdir=/usr/lib --includedir=/usr/arm-linux-gnueabi/include
--build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=arm-linux-gnueabi --with-headers=/usr/arm-linux-gnueabi/include
--with-libs=/usr/arm-linux-gnueab

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-24T11:36:15

On Thu, 24 May 2012 13:03:12 +0800
lee sudo <desoxydate< at >gmail.com> wrote:


Good.


I'm not familiar with Android's C toolchain. Can you point me towards
where I can get one already compiled like you are using? I'm curious to
see what their GCC setup is.  That might shed some light.  I don't have
time to build yet another toolchain, thus the ask for a binary, I can
get the info I want out of a binary.


I believe you should be able to compile the Linux kernel even if GCC
can't find any of the libraries.  It's a kernel and all "library" calls
made in it exist as source within it.  You don't need things like libc
or mpfr to build Linux.  It's everything that runs on Linux that
probably will want the libs.


For now, I'm going to chalk this one up to you should just keep your
toolchain where you built it.  Don't move it.

It's like if you go to the doctor complaining, "Every time I stab
myself in the face with this knife, it hurts."  The doctor will tell
you, "Stop stabbing yourself in the face with a knife!"

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

DJ Lucas — 2012-05-24T05:49:46

Unfortunately, I am not well versed in cross compilers (always relied on 
the CodeSorcery scripts for arm), so this response could possibly be a 
wild goose chase (but I think it's correct). I suspect you are looking 
for LD_LIBRARY_PATH...at least that's what works on native compilers, 
though I suspect the same with cross compilers since it runs native, 
just the output is for different arch. If my guess is right, you'll want 
something like the following in your working environment:

LD_LIBRARY_PATH="/home/sudolee/cross_toolchain/lib"
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/home/sudolee/your/final/project/output/dir/rootfs/lib"
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/home/sudolee/your/final/project/output/dir/rootfs/usr/lib"
export LD_LIBRARY_PATH

Add any additional library paths in your project anddrop that into a 
shell script in your home dir. Execute it any time you intend to compile 
for your project. If that turns out not to work, there should be 
something similar for cross compilers I would think. The

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

lee sudo — 2012-05-24T05:03:12

Dear Andrew,

Thanks for your answer.
It works well after put it all back where it was as you said.

But I find some cross toolchains (e.g. cross toolchain in android source
code) could work well after change its path(anywhere).
This is the script i tested lasy night, it works well and finally succeed.
And i cross compile kernel3.0.23 a moment ago, it also works well.

If i change its path from "/home/sudolee/cross/cross_toolchain" to
"/home/sudolee/cross_toolchain/", this issue occured.
Pls check the log below.
-----log-----
/home/sudolee/cross_toolchain/bin/../libexec/gcc/arm-none-
linux-gnueabi/4.6.0/cc1:
error while loading shared libraries: libcloog.so.0: cannot open shared
object file: No such file or directory
---------------

i know this issue occured due to the path changed, but i want find a way to
avoid this.
Maybe compiling all the library as static could avoid this issue(all the
libaray set by disable-shared). But i
tried many times, build process will abort with some errors, the error log
list

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Andrew Bradford — 2012-05-23T17:27:17

On Wed, 23 May 2012 19:28:18 +0800
lee sudo <desoxydate< at >gmail.com> wrote:


When you built the toolchain, you told it where to find the libraries
and everything else it needs (your $PREFIX and $PRO_ROOT variables it
looks like). Now you've moved the toolchain and the libraries, so it
can't find them anymore. Put it all back where it was when you built
the toolchain, then it should work.  Or, when compiling other sources,
you can tell each thing you are compiling where to find the libraries
(this may be easier said than done depending on the build system being
used).

To see this, if you run the gcc you built with the '-v' switch, it'll
tell you where it expects to find libraries.  Yours probably aren't
there anymore.  Put them back and it should be happy.

-Andrew

Re: HELP ME: issue about arm cross toolchain (cannot find gmp.so, mpfr.so...)

Spam — 2012-05-23T13:32:07

We need more information, specificly errorcodes.  Please paste whole 
build log (including error) here.  Make sure that you include 
everything.  My suggestion is to run make once, then run it again using 
2>&1 $LOGFILE so you don't include any successful compiling to keep the 
paste as small as possible.

On 5/23/2012 7:28 AM, lee sudo wrote:

_______________________________________________
Clfs-dev mailing list
Clfs-dev< at >lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org

HELP ME: issue about arm cross toolchain (cannot findgmp.so, mpfr.so...)

lee sudo — 2012-05-23T11:28:18

Dear all,

I built arm cross toolchain using the script in attachment. And finally
succeed.
But I moved the toolchain from the dir (it was) to another one, e.g.
from "/home/sudolee/toolchain/cross_toolchain"
to "/home/sudolee/".
Then i compile my source code by new cross toolchain, but it cannot find
some *.so, e.g. gmp.so mpfr.so cloog.so...

Anybody know about this issue?
Could anybody kindly help me?

Re: Error at cross compiler final stage at Cross-Compiled Linux From Scratch - Sysroot - Version SVN-0.0.1-20090726-ARM

Andrew Bradford — 2012-05-10T14:15:09

On Tue, 8 May 2012 10:43:05 +0800
zxx zxx <zxxkevin< at >gmail.com> wrote:


<snip>


Can you try using GCC 4.4.0?  Or GCC 4.3.x?  I believe this is a GCC
4.4.1 issue, going to a slightly older GCC may fix it.

-Andrew

Error at cross compiler final stage at Cross-Compiled Linux From Scratch - Sysroot - Version SVN-0.0.1-20090726-ARM

zxx zxx — 2012-05-08T02:43:05

Hi all,
I am a newbie for cfs and want to build linux system for my arm board.
Because I haven't find arm with eglibc in clfs1.2. So I have to choose
Cross-Compiled Linux From Scratch - Sysroot - Version
SVN-0.0.1-20090726-ARM book to build my arm linux system.

I meet a problem when I build gcc-4.4.1 cross compiler final according to
"5.12 gcc-4.4.1-cross compiler final" , here is a error log:

-------------------------------------------------------------------------------------------------------------------------------------
checking for arm-unknown-linux-gnu-strip...
/home/zxx/sysroot/clfs/cross-tools/arm-unknown-linux-gnu/bin/strip
checking for arm-unknown-linux-gnu-gcc...
/home/zxx/sysroot/build/gcc-build/./gcc/xgcc
-B/home/zxx/sysroot/build/gcc-build/./gcc/
-B/home/zxx/sysroot/clfs/cross-tools/arm-unknown-linux-gnu/bin/
-B/home/zxx/sysroot/clfs/cross-tools/arm-unknown-linux-gnu/lib/ -isystem
/home/zxx/sysroot/clfs/cross-tools/arm-unknown-linux-gnu/include -isystem
/home/zxx/sysroot/clfs/cross-tools/arm

Re: eglibc patches GIT-20120314-x86_64-Multilib

Jonathan Norman — 2012-05-07T15:44:04

Come onto #cross-lfs support on irc.freenode.net and ask nicely.

Cosmo~

On 7 May 2012, at 16:42, John Harrigan wrote:

Re: eglibc patches GIT-20120314-x86_64-Multilib

John Harrigan — 2012-05-07T15:42:40

* berzerkula< at >cox.net (May 06, 2012 < at > 07:25-0500):

Sorry for the dumb question, but how do I create a Trac account
so that I can create a new ticket?

Re: Re Latest Pure x64 build

Martin Ward — 2012-05-06T13:21:42

Thanks

Martin

Re: Re Latest Pure x64 build

William Harrington — 2012-05-06T12:28:49

For final libc if you want to use fstack-protector-all   first build  
the libraries without that by adding build-programs=no in configrams,  
then directly build again with build-programs removed and add your  
CFLAGS for fstack-protector-all and whatever else.  That should work.  
Worked for Robert back in the day with his hardening builds!

-William