delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/03/30/10:34:45

Message-Id: <199803301535.RAA33576@ieva06.lanet.lv>
From: "Andris Pavenis" <pavenis AT lanet DOT lv>
To: djgpp AT delorie DOT com, bpaddock AT csonline DOT net
Date: Mon, 30 Mar 1998 18:32:49 +0000
MIME-Version: 1.0
Subject: Re: Building gcc-2.8.1 for DJGPP
In-reply-to: <6ZsH1UQy8UjK092yn@csonline.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980323131715 DOT 1968K-100000 AT is>

 From:          bpaddock AT csonline DOT net (Bob Paddock)

> Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> >
> >On Mon, 23 Mar 1998, Andris Pavenis wrote:
> >> 1) edit configure and replace CONFIG_SHELL=/bin/sh to /djgpp/bin/sh.exe
> >
> >The correct way (IMHO) is to set CONFIG_SHELL=bash in the environment 
> >before running the configure script.
> 
> So far the only thing I've gotten to work is to put sh.exe
> in C:/BIN/.  Any ideas why?
> 
> I've tried "set CONFIG_SHELL=/djgpp/bin/sh.exe" at the DOS
> command line (/bash.exe acts the same, as well as leaving off
> the .exe part).  I also have my djgpp.env set like so:
> 
> ------------------------
> DJDIR=%:/>DJGPP%
> 
> +USER=dosuser
> +TMPDIR=%DJDIR%/tmp
> +EMU387=%DJDIR%/bin/emu387.dxe
> +LFN=Y
> +SHELL=%DJDIR%/bin/sh.exe
> +CONFIG_SHELL=%DJDIR%/bin/sh.exe
> ------------------------

I suggest to add extra environment parameters in djconfig.sh and 
djmake.sh than rather than to edit DJGPP.ENV to add something
to environment You nead for one task only . 

> 
> Doing  "sh djconfig.sh" comes back and says
> "djconfig.sh C:/bin/sh no such file or directory (ENOENT)".
> 
> Also tried:
> #!/djgpp/bin/sh [and tried /sh.exe] as the first line of
> djconfig.sh.

Yes I know this. Unfortunatelly CONFIG_SHELL is not used 
anywhere we need. Therefore for building gcc-2.8.1 it is neaded
to have /bin/sh.exe (You can make this by copying bash.exe to
/bin/sh.exe on the same drive You have gcc sources.

> 
> Is any of this showing I have some thing configured wrong
> some place?
> 

One note about building gcc-2.8.1. If somebody simply transfers
changes Robert did to port gcc-2.8.0 to DJGPP he perhaps will get
most of problems port of 2.8.0 had (as I got initially). There it is 
necessary to do some other changes to fix problems that appeared after 
release of port of 2.8.0 (including problems with exceptions, unnecesary 
use of long filanemes for temporary files in some situations)

I have now version of port of gcc-2.8.1 that fixes 2 problems I mentioned 
above. Perhaps some more testing is still neaded. 

Andris 

- Raw text -


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