public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Drehmel <robert@gizmo.quizbot.org>
To: gcc-help@gcc.gnu.org
Subject: Problems building gcc-2.95 as cross compiler.
Date: Sat, 10 Feb 2001 15:28:00 -0000	[thread overview]
Message-ID: <200102102328.f1ANSmB13364@gizmo.quizbot.org> (raw)

[ Please keep me CC'd, as I am not on this list. ]

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.  After that, the error seems to be gone, but
xgcc stops with

$ make
make all-recursive
Making all in intl
Making all in lib
Making all in makeinfo
(cd intl && make all)
rm -f tmplibgcc1.a libgcc1.S
cp ../../gcc-2.95/gcc/config/mips/mips16.S libgcc1.S
for name in _m16addsf3 _m16subsf3 _m16mulsf3 _m16divsf3  _m16eqsf2 _m16nesf2 _m1
6gtsf2 _m16gesf2 _m16lesf2 _m16ltsf2  _m16fltsisf _m16fixsfsi  _m16adddf3 _m16su
bdf3 _m16muldf3 _m16divdf3  _m16extsfdf2 _m16trdfsf2  _m16eqdf2 _m16nedf2 _m16gt
df2 _m16gedf2 _m16ledf2 _m16ltdf2  _m16fltsidf _m16fixdfsi _m16retsf _m16retdf 
 _m16stub1 _m16stub2 _m16stub5 _m16stub6 _m16stub9 _m16stub10  _m16stubsf0 _m16s
tubsf1 _m16stubsf2 _m16stubsf5 _m16stubsf6  _m16stubsf9 _m16stubsf10  _m16stubdf
0 _m16stubdf1 _m16stubdf2 _m16stubdf5 _m16stubdf6  _m16stubdf9 _m16stubdf10;  do
  echo ${name};  /usr/home/robert/gcc_build/gcc/xgcc -B/usr/home/robert/gcc_buil
d/gcc/ -B/home/robert/gcc_install/mips-ecoff/bin/ -I/home/robert/gcc_install/mip
s-ecoff/include -O2  -DCROSS_COMPILE -DIN_GCC    -g -O2 -I./include 
 -G 0 -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I../../gcc-2.95/gcc -I../.
./gcc-2.95/gcc/config -I../../gcc-2.95/gcc/../include -c -DL${name} libgcc1.S;  
if [ $? -eq 0 ] ; then true; else exit 1; fi;  mv libgcc1.o ${name}.o;  mips-eco
ff-ar rc tmplibgcc1.a ${name}.o;  rm -f ${name}.o;  done
_m16addsf3 
xgcc: installation problem, cannot exec `mips-tfile': No such file or directory
*** Error code 1

Stop in /usr/home/robert/gcc_build/gcc.
*** Error code 1

Stop in /usr/home/robert/gcc_build.

Hmm... so I tried

$ 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

Stop in /usr/home/robert/gcc_build/gcc.

How can I build this thing?

ciao,
-robert

             reply	other threads:[~2001-02-10 15:28 UTC|newest]

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

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=200102102328.f1ANSmB13364@gizmo.quizbot.org \
    --to=robert@gizmo.quizbot.org \
    --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).