Posted-Date: Sun, 26 Jan 1997 20:17:16 -0600 (CST)
Message-Id: <199701270217.UAA11256@mail.texoma.net>
From: "Mark S. Teel" <mteel AT texoma DOT net>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: "DJGPP" <djgpp AT delorie DOT com>
Subject: Re: Difficulty re-building gcc
Date: Sun, 26 Jan 1997 20:25:06 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

:Note that in order to step into a 
:library function and see its source code (not the disassembled machine 
:instructions), you will need to also have the source of that library 
:function handy, which usually isn't the case, so the whole point might be 
:a moot one.

I obviously have the sources available in this case...

> 2) There was a plethora of EXEs generated in addition to cc1.exe - what
> files need to be
> moved into the bin directory, lib directory, etc?

:As far as I can remember, you only need cpp.exe, gcc.exe, cc1.exe and 
:libgcc.a, but you can verify this using (1) the contents of gcc2721b.zip 
:archive; and (2) the install: target of the Makefile in the gcc 
:distribution, which should show you exactly which files it moves to which 
:directories.

I ran configure from the ./config/msdos directory and then ran make, but
the install 
target was not executed.  When I do make install, I get the following
error:
syntax error
Bad command or file name
make.exe: *** [config.status] Error -1

When I run make -n install, I get:
ln cccp cpp > /dev/null 2>&1 \
 || cp cccp cpp
make.exe: *** No rule to make target 'objc-runtime', needed by
'objective-c'. Stop.

Am I doing something unusual?  I would think many people have rebuilt gcc,
and further, I would expect these types of things would have already been
worked out :-(  Please fill me in.
Thanks.   MST

> An interesting observation is that while I was building gcc, I received
> mail via M$ Internet
> Mail and it caused the compiler to crash!?!

If you still got the crash traceback (or can reproduce the crash), you
could run symify on the compiler and see where does the crash happen.  It 
might be some real problem in DJGPP.

I'll let you know if I can reproduce it...