X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	"deckerben" <deckerben AT freenet DOT de>
Newsgroups:	comp.os.msdos.djgpp
References:	<3c84dfb6$0$4080$9b622d9e AT news DOT freenet DOT de> <3c84f79a DOT sandmann AT clio DOT rice DOT edu> <3c84fe5f$0$12305$9b622d9e AT news DOT freenet DOT de> <3c850cc1 DOT sandmann AT clio DOT rice DOT edu>
Subject:	Re: Version info
Date:	Tue, 5 Mar 2002 21:58:19 +0100
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Lines:	139
Message-ID:	<3c852e3d$0$169$9b622d9e@news.freenet.de>
NNTP-Posting-Host:	213.6.235.199
X-Trace:	1015361086 news.freenet.de 169 213.6.235.199
X-Complaints-To:	abuse AT freenet DOT de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Here are the file sizes:

D:\>dir %DJGPP%\..\bin\bash.exe
 Datenträger in Laufwerk D: hat keine Bezeichnung.
 Datenträgernummer: 1849-13F0

 Verzeichnis von D:\USER\DJGPP\bin

02/03/2002  11:04a           1,767,127 bash.exe


The other bash you saw is from the simtel distribution (like I said before).
Configure only runs when I have the Simtel version in \bin. ????

    My biggest problem, though, is that I can't seem to make my own
makefiles. The problem definitely seems to be in the makefiles
"DJGPP-win2000" is creating. Why do I say that? Because I can make zlib and
allegro WITHOUT A SINGLE PROBLEM. What is the difference between zlib,
allegro and libxslt? I think one very important one is that zlib and allegro
come already with DJGPP makefiles ready-to-go.

I tried running a test. Instead of using makefile.dj(what it comes with) to
build allegro, I did the following:
bash
autoconf
./configure
make

then the same darn errors as with libxslt. I could send the two makefile
versions(default and mine) to you per e-mail for comparison if it helps.

Here is what happens:
make -d -k all:
..running
....until...
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
rm -f .libs/xslt.lo
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

NOW the error:
..
long list of errors similar to -->
..
..
d:\user\djgpp\tmp\cchKzH6c.s:8872: Error: cannot represent relocation type
BFD_RELOC_386_GOTOFF
d:/user/djgpp/bin/as.exe: bfd assertion fail
/djgpp/gnu/binutl-2.112/bfd/coff-i386.c:529
d:\user\djgpp\tmp\cchKzH6c.s:8875: Error: cannot represent relocation type
BFD_RELOC_386_GOT32
d:/user/djgpp/bin/as.exe: bfd assertion fail
/djgpp/gnu/binutl-2.112/bfd/coff-i386.c:529
d:\user\djgpp\tmp\cchKzH6c.s:8877: Error: cannot represent relocation type
BFD_RELOC_386_GOT32
d:/user/djgpp/bin/as.exe: bfd assertion fail
/djgpp/gnu/binutl-2.112/bfd/coff-i386.c:529
d:\user\djgpp\tmp\cchKzH6c.s:8883: Error: cannot represent relocation type
BFD_RELOC_386_GOT32
Putting child 0x00221090 (xslt.lo) PID 123 on the chain.
Live child 0x00221090 (xslt.lo) PID 123
Reaping losing child 0x00221090 PID 123
make.exe[2]: *** [xslt.lo] Error 1
Removing child 0x00221090 PID 123  from chain.
make.exe[2]: Leaving directory `d:/download/libxslt-1.0.12/libxslt'
Putting child 0x000e4d30 (all-recursive) PID 123 on the chain.
Live child 0x000e4d30 (all-recursive) PID 123
Reaping losing child 0x000e4d30 PID 123
make.exe[1]: *** [all-recursive] Error 1
Removing child 0x000e4d30 PID 123  from chain.
make.exe[1]: Leaving directory `d:/download/libxslt-1.0.12'
Putting child 0x000e4f10 (all-recursive-am) PID 124 on the chain.
Live child 0x000e4f10 (all-recursive-am) PID 124
Reaping losing child 0x000e4f10 PID 124
make.exe: *** [all-recursive-am] Error 2
Removing child 0x000e4f10 PID 124  from chain.

Then it just stops.
regarding this problem, Daniel Veillard (if I may quote him) wrote:
  "You have a mismatch between what the gcc code generator produced and
what your assembler is able to digest. It's actually  a problen in the
library handling the binary format possibly the same kind of error as
compiling
in the "small" model instead of using "huge" pointer that were the problems
of the day 10 years ago ...

In a nutshell your compiler takes
correct C code and can't generate a binary object from it. Seems your
compiler
is in error. Not libxslt related. you should report the bug, upgrade your
compiler or switch to another one IMHO. The fix is not at the libxslt level
I'm afraid. tweaking compiler flags may solve this too,

Daniel"

I think maybe you should know about this.

Many regards,
Ben





"Charles Sandmann" <sandmann AT clio DOT rice DOT edu> wrote in message
news:3c850cc1 DOT sandmann AT clio DOT rice DOT edu...
> > Here is my version info:
>
> > D:\>bash --version
> > GNU bash, version 2.05a.0(6)-release (i686-pc-msdosdjgpp)
> > Copyright 2001 Free Software Foundation, Inc.
>
> This image is from the v2.04 (cvs) testing tree.  It's based on a new
> version of the library (and bash) which are pre-beta.  It would
> also be nice to see a dir bash.exe output for this image
> (which provides the date and size).
>
> > D:\>cd bin
>
> > D:\bin>.\bash.exe --version
> > GNU bash, version 2.04.7(1)-release (i686-pc-msdosdjgpp)
> > Copyright 1999 Free Software Foundation, Inc.
>
> This version of bash could be almost anything - I would need
> the output from "dir d:\bin\bash.exe" to know what it is.  If
> it is not dated in December 2001 it's probably not Win2K compatible.
> There is a bash 2.04 on Simtel (and clio in the 2.03 directory)
> which were compiled with the Win2K patches.
>
> > BTW, I would like not to have a \bin dir as well! How are you building?
>
> searches for \bin\sh should find it in the djgpp bin directory.  I didn't
> do anything special (just set the path and DJGPP environment variable).
>

- Raw text -