From: Jacky Cao <cao.zhong1@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: mip64 cross gcc build problem
Date: Mon, 07 Feb 2011 18:17:00 -0000 [thread overview]
Message-ID: <AANLkTikwTQ6ctMYJxj=E3ktOUsXYF8dDEHgr7dFWw9io@mail.gmail.com> (raw)
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?
next reply other threads:[~2011-02-07 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 18:17 Jacky Cao [this message]
2011-02-07 23:04 ` Kai Ruottu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikwTQ6ctMYJxj=E3ktOUsXYF8dDEHgr7dFWw9io@mail.gmail.com' \
--to=cao.zhong1@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).