cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1998/07/29/06:52:07

Date: Wed, 29 Jul 1998 13:48:55 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: Gerhard Gruber <sparhawk AT eunet DOT at>, djgpp AT delorie DOT com
Subject: Re: HElp During configure ....Bad command or file name
In-Reply-To: <Pine.SUN.3.91.980729113814.8425L-100000@is>
Message-ID: <Pine.A32.3.91.980729134146.115668A-100000@ieva05.lanet.lv>
MIME-Version: 1.0


On Wed, 29 Jul 1998, Eli Zaretskii wrote:

> 
> On Tue, 28 Jul 1998, Gerhard Gruber wrote:
> 
> > >You are configuring GCC for building with MSVC or with Cygwin32 tools, not 
> > >with DJGPP.  That is what configure.bat does.
> > 
> > Does this mean that I can build gcc with MSVC???
> 
> The first stage of GCC can in general be built with any compiler.
> That is how you build GCC the first time on a machine where no
> previous versions of GCC are available.  Stage 2 then rebuilds GCC
> with itself.
> 
> I haven't tried to build with MSVC, so I don't know whether it is
> practically possible, but it isn't inconceivable.

Once more. The initial message of this thread shows that the problem
is likely connected with attempt to build gcc-2.8.1 from original
FSF distribution of gcc. This perhaps will not work and even if there
will be success in building gcc many of changes that were done in
latest updates of DJGPP port of gcc-2.8.1 will not be available.

I saw this because source archive of DJGPP port of gcc-2.8.1 does not
contain configur.bat in directory gcc-2.8.1 (and there is no such directory
as gcc-2.8.1). The location of this file is as from original GNU 
distribution.

The best here is to download source archive of DJGPP port of gcc-2.8.1
(gcc281s.zip) as there were rather many DJGPP specific changes.

After unpacking this archive information how to build it is in 
directory gnu/gcc-2.81/readme.djgpp

> 
> > What about DJGPP, it's the same source, isn't it?
> 
> You forget the system- and compiler-specific #ifdef's.  So no, it's
> not the same source.
> 
> > What code does it produce? Windows or DOS or both?
> 
> That depends on how GCC is configured, and what Binutils does it use.
> These are the two factors which define the output format.  Recall that
> GCC just generates assembly, it relies on an assembler to produce
> machine code in the appropriate object format.
> 
> Again, this is theory.  I have never done that myself with MSVC
> (neither will I try, if it depends on me ;-).
> 

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019