Mail Archives: djgpp/2002/03/05/18:15:08
> When I have the Simtel bash in my %DJGPP%\bin, I get all the crazy errors
> that seem to indicate something is seriously wrong with my distribution (it
> could be because all of my DJGPP tools are the ones downloaded from rice.edu
> for 204 - I do not have the Simtel loaded at the moment):
The files from "204" are test files and may not work properly in all cases;
if the ones from 203 update work better you should use them and report the
problems (as you are doing) with the test images.
> d:/user/djgpp/bin/as.exe: bfd assertion fail
> /dj204/gnu/binutl-2.112/bfd/coff-i386.c:529
> d:\user\djgpp\tmp\cc0mzF8o.s:8883: Error: cannot represent relocation type
> BFD_RELOC_386_GOT32
> make.exe[2]: *** [xslt.lo] Error 1
These are caused by trying to build shared/relocatable images which the
binutils were not configured to support.
> When I swap the Simtel bash out, and put in the one from rice.edu(the one I
> already described to you), I get a different error:
>
> D:\\USER\\DJGPP\\bin\\gcc.exe -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../libxslt
> -I/dev/env/DJDIR/include/libxml2/libxml -I/dev/env/DJDIR/include/libxml2 -g
> -O2 -c xslt.c -fPIC -DPIC -o .libs/xslt.lo
> .../libtool: D:\USER\DJGPP\bin\gcc.exe: command not found
It's possible there are some incompatibilites - this is a test release.
> This is what I think: Simtel bash is incompatible with my rice.edu
> installation - make needs bash to run and they have to be compatible.
> But it just so happens that the rice.edu bash binary doesn't work... (can't
> find my compiler, anyhow)
When you say "Simtel bash" - it's still not clear to me which release of
Simtel bash you might be running. There is a mirror of the most recent
Simtel bash 2.04 on clio.rice.edu in the v2.03 update directory. Is that
what you are running? If it's something older than that, there may be all
sorts of Win2K problems with an earlier version.
> I think bash from rice.edu needs to be fixed.
Someone has to reproduce the problem, find the cause, and write code to
fix it first. This could be a configuration problem. It could be a bash
2.05 vs 2.04 issue. It could be a CVS library bug. Without more information,
it can't get fixed.
- Raw text -