From: "Ethan Du" <ethan.too@gmail.com>
To: gcc-help@gcc.gnu.org, ethan.too@gmail.com
Subject: Problem with multilib build
Date: Wed, 16 Apr 2008 09:10:00 -0000 [thread overview]
Message-ID: <578201dd0804151924r508dc296uf405910a59136174@mail.gmail.com> (raw)
In-Reply-To: <578201dd0804141950l5af68b13xef62805ee80cc62@mail.gmail.com>
Hi, guys:
I am building gcc-4.2 for arm-none-linux-eabi. I want to build
multi lib, this is what I modified in gcc/config/arm/t-linux-eabi
MULTILIB_OPTIONS = mthumb
MULTILIB_DIRNAMES = thumb
MULTILIB_OPTIONS += march=armv4t/mcpu=cortex-a8/march=armv7
MULTILIB_DIRNAMES += armv4t cortex-a8 armv7
MULTILIB_EXCEPTIONS += *mthumb/*mcpu?cortex-a8*
MULTILIB_EXCEPTIONS += *mthumb/*march?armv4t*
MULTILIB_EXCEPTIONS += march=armv7*
MULTILIB_EXCEPTIONS += mthumb
# As of at least 4.2, gcc passes the wrong -L options if some multilibs are
# omitted from MULTILIB_OSDIRNAMES
MULTILIB_OSDIRNAMES = mcpu.cortex-a8=!cortex-a8
MULTILIB_OSDIRNAMES += march.armv4t=!armv4t
MULTILIB_OSDIRNAMES += mthumb/march.armv7=!thumb2
After the build, I did get some multilib folders:
// for armv4t, I got
./lib/gcc/arm-none-linux-gnueabi/4.2.0/armv4t
./arm-none-linux-gnueabi/lib/armv4t
./arm-none-linux-gnueabi/include/c++/4.2.0/arm-none-linux-gnueabi/armv4t
// for cortex-a8, I got
./lib/gcc/arm-none-linux-gnueabi/4.2.0/cortex-a8
./arm-none-linux-gnueabi/include/c++/4.2.0/arm-none-linux-gnueabi/cortex-a8
You see, "./arm-none-linux-gnueabi/lib/cortex-a8" was missing. After
gave a check I found the binaries should be placed under
"./arm-none-linux-gnueabi/lib/cortex-a8" was actually placed under
"./arm-none-linux-gnueabi/lib".
My questions are:
I was thinking config/arm/t-linux-eabi should be the only place need
to be modified for multilib build, is that right?
I see libraries under ./arm-none-linux-gnueabi/lib/ is armv5, where
is this default arch value defined?
I already have such a toolchain installed, but without the multilib
I want. To avoid a new install, I just copied the multilib folders to
the old toolchain, and used -specs=my_new_specs to try, I defined
multilib/multilib_options... in the specs file. But it didn't work.
When calling collect2, the library path for the command is not
pointing to my multilib folder. With debug option, I saw in "options
passed", there was a "-imultilib" missing. So, will changing specs be
enough or is re-install the only way to update my gcc?
Will appraciate any hint!
PS: I was using a free codesourcery released gcc, but I think multilib
build should have no change between them.
- Ethan
next prev parent reply other threads:[~2008-04-16 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 4:28 Ethan Du
2008-04-16 9:10 ` Ethan Du [this message]
2008-04-18 18:26 ` Jim Wilson
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=578201dd0804151924r508dc296uf405910a59136174@mail.gmail.com \
--to=ethan.too@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).