public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Korn <dkorn@pixelpower.com>
To: 'Robert Drehmel' <robert@gizmo.quizbot.org>, gcc-help@gcc.gnu.org
Subject: RE: Problems building gcc-2.95 as cross compiler.
Date: Mon, 12 Feb 2001 02:22:00 -0000	[thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A5642694@EXCHANGESERVER> (raw)

>Hi.
>I have some problems building a gcc-2.95 cross compiler from sources
>on a FreeBSD/i386 5.0-CURRENT system.  Target should be mips (r3000).
>The build directory I use is 'gcc_build', so I did a
>
>$ cd gcc_build
>$ ../gcc-2.95/configure --target=mips-ecoff 
>--prefix=~robert/gcc_install
>[...]
>$ make
>
>After a while, I get complains from xgcc that as does not accept a
>'-G' parameter.  I did a binutils 2.10 build with the same target
>before, so I backed up the original and moved binutils_build/gas/as-new
>to /usr/libexec/elf/as.

  Rule #1: Always use the same --prefix for your cross-binutils as you
want for the cross-compiler

>$ cd gcc
>$ make mips-tfile
>
>gcc -c -DCROSS_COMPILE -DIN_GCC    -g   -DHAVE_CONFIG_H    -I. 
>-I../../gcc-2.95/gcc -I../../gcc-2.95/gcc/config 
>-I../../gcc-2.95/gcc/../include ../../gcc-2.95/gcc/mips-tfile.c
>../../gcc-2.95/gcc/mips-tfile.c:673: mips/a.out.h: No such 
>file or directory
>*** Error code 1

  You have got your target headers installed, haven't you?

       DaveK
-- 
we are not seats or eyeballs or end users or consumers.
we are human beings - and our reach exceeds your grasp.
                    deal with it.                      - cluetrain.org 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

             reply	other threads:[~2001-02-12  2:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12  2:22 David Korn [this message]
2001-02-12  2:39 ` Robert Drehmel
  -- strict thread matches above, loose matches on Subject: below --
2001-02-15  1:49 David Korn
2001-02-12  5:57 David Korn
2001-02-14 18:51 ` Robert Drehmel
2001-02-12  2:50 David Korn
2001-02-12  3:12 ` Robert Drehmel
2001-02-10 15:28 Robert Drehmel

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=718D38CAB6E0D011B2C90060970C28A5642694@EXCHANGESERVER \
    --to=dkorn@pixelpower.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=robert@gizmo.quizbot.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).