Mail Archives: djgpp/1998/03/22/20:54:48
>On Thu, 19 Mar 1998, Salvador Eduardo Tropea (SET) wrote:
>> > This is needed only, if you don't have a /bin/sh.exe on the
>> > drive, where you build gcc. So created that and you don't need
>> > to modify the Makefile.
>>
>You do NOT need sh.exe in /bin, you can have it in *any* directory on
>your PATH. Both Make and Bash will find it and invoke it whenever a
>script or a Makefile calls for "/bin/sh".
Unless I make a C:\BIN then copy sh.exe to it, I can't build
GCC-2.80, this is what happens:
C:\DJGPP\gnu\gcc>sh djmake.sh
if [ -f libgcc2.ready ] ; then \
true; \
else \
touch libgcc2.ready; \
fi
C:\TEMP/dj100000: c:/bin/sh: No such file or directory (ENOENT)
make.exe: [libgcc2.ready] Error 126 (ignored)
C:\TEMP/dj200000: c:/bin/sh: No such file or directory (ENOENT)
C:\TEMP/dj300000: c:/bin/sh: No such file or directory (ENOENT)
make.exe: *** [cplib2.ready] Error 126
So whats a Error 126?
--
For information on any of the following check out my WEB site at:
http://www.biogate.com/bpaddock/
Chemical Free Air Conditioning/No CFC's, Chronic Pain Relief, Electromedicine,
Electronics, Explore!, Free Energy, Full Disclosure, KeelyNet, Matric Limited,
Neurophone, Oil City PA, Philadelphia Experiment.
- Raw text -