From: Alexandre Oliva <aoliva@redhat.com>
To: angel@datatekcorp.com
Cc: gcc@gcc.gnu.org
Subject: Re: Build Error on 3.0
Date: Thu, 06 Dec 2001 12:59:00 -0000 [thread overview]
Message-ID: <ork7w0t6dh.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Angel Gomez's message of "Thu, 06 Dec 2001 08:02:40 -0800"
On Dec 6, 2001, Angel Gomez <angel@datatekcorp.com> wrote:
> The build script claims the cross-compiler doesn't work. The target is
> arm-coff. Do you have any clues?
Have you build binutils for that target already? (probably, otherwise
you'd get failures while building libgcc)
Do you have newlib in the source tree? (this would cause the problem
at this point; you need newlib build before libiberty)
If you don't want to build a unified tree with binutils, gcc and
newlib, install as much of gcc as you've already got to build, use
that to build newlib, then get back and complete the target-libraries
build.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
prev parent reply other threads:[~2001-12-06 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 9:20 Angel Gomez
2001-12-06 10:18 ` Neil Booth
2001-12-06 12:59 ` Alexandre Oliva [this message]
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=ork7w0t6dh.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=angel@datatekcorp.com \
--cc=gcc@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).