public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: "Frank W. Miller" <fwmiller@cornfed.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Building cross compiler for x86_64
Date: Sat, 16 Feb 2008 00:00:00 -0000	[thread overview]
Message-ID: <47B62760.D8FE6067@dessent.net> (raw)
In-Reply-To: <1203100254.14109.5.camel@localhost.localdomain>

"Frank W. Miller" wrote:

> This gets me an error saying x86_64-elf is not a supported target.  I

I think you'll need to use a more recent version.  The support for bare
metal x86_64 wasn't added until r127798:
<http://gcc.gnu.org/viewcvs?view=rev&revision=127798>.  You could
probably just apply that patch to whatever version you're using.

> source tree and starting over).  I get this error somewhere down the
> line:
> 
> source='../.././libdecnumber/decimal128.c' object='decimal128.o'
> libtool=no gcc  -I../.././libdecnumber -I.  -g -O2 -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -Wmissing-format-attribute -Wcast-qual -pedantic
> -Wno-long-long  -I../.././libdecnumber -I.
> -c ../.././libdecnumber/decimal128.c
> rm -f libdecnumber.a
> ar cru libdecnumber.a decNumber.o decContext.o decUtility.o decimal32.o
> decimal64.o decimal128.o
> ranlib libdecnumber.a
> make[2]: Leaving directory
> `/home/fwmiller/Desktop/gcc-4.2.3/host-i686-pc-linux-gnu/libdecnumber'
> make[1]: Target `all-host' not remade because of errors.
> make[1]: Target `all-target' not remade because of errors.
> make[1]: Leaving directory `/home/fwmiller/Desktop/gcc-4.2.3'
> make: *** [all] Error 2

That's not the error per se.  The actual error was earlier in the
process, but because of -k it kept continuing to build things that
didn't depend on the makefile target that errored.  So the above doesn't
really say anything, other than that something went wrong earlier.

BTW you're definitely going to want to disable things like libmudflap,
libssp, libdecnumber, libgomp, etc. if any of them turn out to be
enabled by default.

Brian

  reply	other threads:[~2008-02-16  0:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 17:14 Forward declaration of classes needed when using GCJ? Andrew W
2008-02-11 17:50 ` David Daney
     [not found]   ` <47B098D1.1050200@iee.org>
2008-02-11 18:58     ` David Daney
2008-02-11 21:56   ` Andrew W
2008-02-11 22:37     ` David Daney
2008-02-12 16:02       ` Andrew W
2008-02-12 17:48         ` Andrew Haley
2008-02-15 18:24         ` Andrew W
2008-02-15 18:31           ` Building cross compiler for x86_64 Frank W. Miller
2008-02-16  0:00             ` Brian Dessent [this message]
2008-02-16  0:14               ` Frank W. Miller
2008-02-16  0:33                 ` Brian Dessent
2008-02-16 20:06             ` Frank W. Miller
2008-02-17  2:52               ` Brian Dessent
2008-02-17  2:55                 ` NightStrike
2008-02-18  4:39                   ` Frank W. Miller
2008-02-15 19:51           ` Forward declaration of classes needed when using GCJ? Andrew Haley

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=47B62760.D8FE6067@dessent.net \
    --to=brian@dessent.net \
    --cc=fwmiller@cornfed.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).