public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Douglas Jerome <douglas@ttylinux.org>
To: crossgcc@sourceware.org
Subject: Building armv7  "cross-native" GCC
Date: Fri, 23 Mar 2012 06:27:00 -0000	[thread overview]
Message-ID: <4F6C17A3.90404@ttylinux.org> (raw)
In-Reply-To: <CANLjY-nNjr+7bQXdEhVdN5E-Tr05UKMVO7RAyCXLagzeJc0Nyg@mail.gmail.com>

Sorry if this is off-topic...

I have an armv7 cross-toool chain, which I made and it seems to
be OK as I use it to cross-build a small armv7 Linux distribution.

Now I am trying to use it to cross-build GCC itself so as to have
a native GCC in the arm Linux system I make.

I am using gcc-4.4.6, gmp-4.3.2 and mpfr-2.4.2 in both the
cross-tool chain and for the cross-native build.

For the cross-native build I copy the gmp and mpfr directories
into the gcc directory and cross-build; this works for similar
PowerPC, i686 and x86_64 cross-built systems. But for the armv7 I
get an undefined reference to `__gmpn_invert_limb' in divrem_1.c

I'm looking through the gmp source code... great fun, but I'm
not yet finding what is going wrong.

Does anyone have some experience with this and have a good
suggestion or two?

-- 
Douglas Jerome


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2012-03-23  6:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  1:23 GCC support libraries and sysroot Michael Hope
2012-03-23  6:27 ` Douglas Jerome [this message]
2012-03-25 14:37 ` Yann E. MORIN
2012-03-25 15:16   ` Paul Smith
2012-03-25 18:28     ` Khem Raj
2012-03-25 19:26       ` Michael Hope
2012-05-06 16:37 ` Thomas Petazzoni
2012-05-06 20:24   ` Michael Hope
2012-05-09  8:26     ` Thomas Petazzoni
2012-07-16  8:03 ` Maurizio Vitale
2012-07-20  3:56   ` Michael Hope

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=4F6C17A3.90404@ttylinux.org \
    --to=douglas@ttylinux.org \
    --cc=crossgcc@sourceware.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).