* mip64 cross gcc build problem
@ 2011-02-07 18:17 Jacky Cao
2011-02-07 23:04 ` Kai Ruottu
0 siblings, 1 reply; 2+ messages in thread
From: Jacky Cao @ 2011-02-07 18:17 UTC (permalink / raw)
To: gcc-help
I want build cross gcc (version 4.4.5) with binutils 2.21, glibc
2.12.1, and prepared lib32 for n32 abi, lib for o32 and lib64 for n64.
I configured second pass gcc with:../../gcc-4.4.5/configure
--prefix=/usr/home/Jacky/xtools/xlp-toolchain
--target=mipsisa64r2-linux-gnu --with-mips-plt
--with-headers=/usr/home/Jacky/xtools/xlp-toolchain/mipsisa64r2-linux-gnu/usr/include
--enable-__cxa_atexit --enable-c99 --disable-libssp
--disable-libmudflap --enable-libgomp --enable-threads=posix
--enable-multilib --enable-shared --with-dwarf2
--enable-languages=c,c++ --enable-symvers=gnu --with-gmp=/usr/local
--with-mpfr=/usr/local --with-system-zlib
but the building process stuck at 32/64 libgcc mulitlib, because the
line in configure "FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET'
-B$(build_tooldir)/bin/ -B$(build_tooldir)/lib/ -isystem
$(build_tooldir)/include -isystem $(build_tooldir)/sys-include'" wired
.../lib/ to all multilib buildings while it's suppose to be .../lib/
.../lib32/ .../lib64/ for each.
I took the suggestion from CLFS powerpc64 cross building book, removed
"-B$(build_tooldir)/lib/", then cross ld can't find crti.o; In my
situation, the crti.o was in the same directory with libc.so,
libc.so.6 and so on.
I've looked at configure and Makefile.in, and can manually adjust it
to choose the right lib but I believe there has been a simple solution
already, or is there anything I did wrong?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mip64 cross gcc build problem
2011-02-07 18:17 mip64 cross gcc build problem Jacky Cao
@ 2011-02-07 23:04 ` Kai Ruottu
0 siblings, 0 replies; 2+ messages in thread
From: Kai Ruottu @ 2011-02-07 23:04 UTC (permalink / raw)
To: gcc-help
7.2.2011 19:57, Jacky Cao kirjoitti:
> I want build cross gcc (version 4.4.5) with binutils 2.21, glibc
> 2.12.1, and prepared lib32 for n32 abi, lib for o32 and lib64 for n64.
> I configured second pass gcc with:../../gcc-4.4.5/configure
> --prefix=/usr/home/Jacky/xtools/xlp-toolchain
> --target=mipsisa64r2-linux-gnu --with-mips-plt
> --with-headers=/usr/home/Jacky/xtools/xlp-toolchain/mipsisa64r2-linux-gnu/usr/include
Using a 1-to-1 sysroot for the glibcs would be easier I think...
--with-sysroot=/usr/home/Jacky/xtools/xlp-toolchain/sysroot
and putting :
lib
lib32
lib64
usr/include
usr/lib
usr/lib32
usr/lib64
there in the (final) native scheme for easy copying (Of course you are
going to copy these to the native MIPS target platform later?)
> I took the suggestion from CLFS powerpc64 cross building book, removed
> "-B$(build_tooldir)/lib/", then cross ld can't find crti.o; In my
> situation, the crti.o was in the same directory with libc.so,
> libc.so.6 and so on.
Using the "traditional" $prefix/$target install scheme for binutils and
target C library ties one to use only one 'lib' there, for the default
libs, '64'?, and using subdirs '32' and 'n32' ? in it for the multilibs.
> I've looked at configure and Makefile.in, and can manually adjust it
> to choose the right lib but I believe there has been a simple solution
> already, or is there anything I did wrong?
As was told, using a sysroot for the target C libraries installed there
in their native scheme ('lib*', 'usr/lib*', usr/include'), is the
standard nowadays... Using the traditional scheme is not recommended
and maybe not even supported :o(
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-02-07 18:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-07 18:17 mip64 cross gcc build problem Jacky Cao
2011-02-07 23:04 ` Kai Ruottu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).