Mail Archives: djgpp/1998/02/10/03:01:19
From: | Robert Zubek <rob-spam AT cs DOT nwu DOT edu>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | recompiling gcc: msdos->mips, part 2
|
Date: | Tue, 10 Feb 1998 01:38:46 -0600
|
Organization: | Northwestern University, Evanston, IL, US
|
Lines: | 38
|
Message-ID: | <34E00406.931B3E72@cs.nwu.edu>
|
NNTP-Posting-Host: | robzilla.res-hall.nwu.edu
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
and so, the cross-compiler compilation saga continues... :)
i finally got binutils to work, with the advice from the newsgroup
(thanks, eli!), and now is the time for gcc itself. everything went
smoothly, until i came across one weird compilation dependency.
i'm trying to make an msdos->mips xcompiler, so i run this:
configure --host=i386-go32-msdos --target=mips-mips-elf --with-gnu-ld
--with-gnu-as
(this host seems to be the only one valid for dos...)
and then:
make LANGUAGES=c
and after chewing on the the files for some time, make complaints that
it can't find file stab.h needed for compiling dbxout.o - and no wonder,
since stab.h does NOT come with the gcc source distribution, and it's
not mentioned in the makefile itself! (obviously some source file asks
for it...) a file with this name does, however, come with djgpp, but
a gcc installation should not require files from outside its
distribution, should it?
so i was wondering - should i make all the djgpp header files available
for gcc? or is this maybe due to some bug/problem in the gcc
configuration script? any ideas?
since i've never had much to do with compiling gcc itself, any help or
ideas would be appreciated...
thanks!
rob
--
** please remove '-spam' from my email address before replying, **
** until i get a decent spam filter... :) **
- Raw text -