Re: now I think this is a bug

2000-12-12 Thread Alan Shutko
Mate Wierdl <[EMAIL PROTECTED]> writes: > Perhaps one should collect the necessary defines from the .h files > into a single one, and send it along with try2.c to the gcc > developers so that they have a standalone test suite. That would be a good idea, but if you're using the RHL7 gcc, you sho

Re: now I think this is a bug

2000-12-12 Thread Mate Wierdl
I now did fresh cd teTeX-1.0/texk/kpathsea ./configure make mkdir a-b-c cp -a kpsewhich a-b-c and got ./a-b-c/kpsewhich -expand-var='$SELFAUTODIR' /usr/local/src/teTeX-1.0/texk/kpathsea/a-b So I now try to isolate the problem. First off, simple optimization `-O' is no problem; the problem oc

Re: now I think this is a bug

2000-12-12 Thread Clayton Weaver
Do you still have a kgcc (gcc-2.91.66) with RH 7.0 for compiling kernels? Try compiling it with that. If it works, you don't have to give up optimization to accomodate a gcc-2.96 bug. Regards, Clayton Weaver (Seattle) "Everybody's ignorant, just in different subjects.

Re: now I think this is a bug

2000-12-12 Thread David Lloyd
Hmmm! > > # gcc -v > > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs > > gcc version 2.96 2731 (Red Hat Linux 7.0) > > And still: I think that your compiler is broken. RedHat GCC 2.96 cannot compile the kernel. Try using kgcc and see what comes up... DL -- The new cent

Re: now I think this is a bug

2000-12-11 Thread Alan Shutko
Tom Kacvinsky <[EMAIL PROTECTED]> writes: > I thought it was a known fact that Red Hat boobooed and used a > *prerelease* version of gcc (2.96) to make the system libs and what > not for RH 7.0. Which is probably the cause of the problems. I > don't know what to recommend in this case. The p

Re: now I think this is a bug

2000-12-11 Thread Mate Wierdl
If I turn off optimization, all is well (xdvi is working fine too). So I just did env CC=cc CFLAGS='-g' \ sh -c './configure --prefix=/usr/local/teTeX >configure.log 2>&1' & Mate On Mon, Dec 11, 2000 at 10:28:46PM +0100, Thomas Esser wrote: > > # kpsewhich -expand-var='$SELFAUTOLOC -- $SELFAUTO

Re: now I think this is a bug

2000-12-11 Thread Tom Kacvinsky
I thought it was a known fact that Red Hat boobooed and used a *prerelease* version of gcc (2.96) to make the system libs and what not for RH 7.0. Which is probably the cause of the problems. I don't know what to recommend in this case. Switch to Debian? Not trying to start a flame war with th

Re: now I think this is a bug

2000-12-11 Thread Thomas Esser
> # kpsewhich -expand-var='$SELFAUTOLOC -- $SELFAUTODIR -- $SELFAUTOPARENT' > /usr/local/teTeX/bin/i686-pc-linux-gnu -- /usr/local/teTeX/bin/i686-pc-linux -- >/usr/local/teTeX/bin/i686-pc Looks very broken. This sould be impossible. Look at the kpathsea code (progname.c, I think). Must be a c

Re: now I think this is a bug

2000-12-11 Thread Mate Wierdl
On Mon, Dec 11, 2000 at 09:58:13AM +0100, Harald Hanche-Olsen wrote: > + Mate Wierdl <[EMAIL PROTECTED]>: > > | So I decided to reinstall teTeX without doing any configuration: > | > | # rm -rf /usr/local/teTeX/ > | # mkdir -p /usr/local/teTeX/share/texmf > | # gzip -dc teTeX-texmf-1.0.tar.gz |

Re: now I think this is a bug

2000-12-11 Thread Mate Wierdl
On Mon, Dec 11, 2000 at 12:51:38PM +, Joao Palhoto Matos wrote: > On Mon, 11 Dec 2000, Thomas Esser wrote: > > > This glibc is a very recent version. So, the rest of your system is > > likely to be very "bleeding edge", too? > > > > Well, I suspect that we run into some compiler bug here... >

Re: now I think this is a bug

2000-12-11 Thread Mate Wierdl
On Mon, Dec 11, 2000 at 07:47:50AM +0100, Thomas Esser wrote: > > export PATH=/usr/local/teTeX/bin/i686-pc-linux-gnu:$PATH > ... > > TEXMFMAIN ``/usr/local/teTeX/bin/i686-pc/share/texmf'' seems to have > > Whow. Cool. Can you please > $ kpsewhich -expand-var='$SELFAUTOLOC -- $SELFAUTODIR -- $SE

Re: now I think this is a bug

2000-12-11 Thread Joao Palhoto Matos
On Mon, 11 Dec 2000, Thomas Esser wrote: > This glibc is a very recent version. So, the rest of your system is > likely to be very "bleeding edge", too? > > Well, I suspect that we run into some compiler bug here... > > Thomas > Hi again: This is the same problem I had reported on some time ago

Re: now I think this is a bug

2000-12-11 Thread Harald Hanche-Olsen
+ Mate Wierdl <[EMAIL PROTECTED]>: | So I decided to reinstall teTeX without doing any configuration: | | # rm -rf /usr/local/teTeX/ | # mkdir -p /usr/local/teTeX/share/texmf | # gzip -dc teTeX-texmf-1.0.tar.gz | (umask 0; cd /usr/local/teTeX/share/texmf; tar |xf -) | # gzip -dc teTeX-src-1.0.

Re: now I think this is a bug

2000-12-10 Thread Thomas Esser
> export PATH=/usr/local/teTeX/bin/i686-pc-linux-gnu:$PATH ... > TEXMFMAIN ``/usr/local/teTeX/bin/i686-pc/share/texmf'' seems to have Whow. Cool. Can you please $ kpsewhich -expand-var='$SELFAUTOLOC -- $SELFAUTODIR -- $SELFAUTOPARENT' I, for example, get the following output: /x/t/i/teTeX/bi

now I think this is a bug

2000-12-10 Thread Mate Wierdl
So I decided to reinstall teTeX without doing any configuration: # rm -rf /usr/local/teTeX/ # mkdir -p /usr/local/teTeX/share/texmf # gzip -dc teTeX-texmf-1.0.tar.gz | (umask 0; cd /usr/local/teTeX/share/texmf; tar xf -) # gzip -dc teTeX-src-1.0.tar.gz | tar xvf - # cd teTeX-1.0 # sh -c './conf