On Thu, Dec 14, 2000 at 07:53:58PM -0500, Alan Shutko wrote:
> Informative post on the bug. It is indeed a compiler bug... I haven't
> seen if there's been a compiler update yet, but there should be soon,
> I'd guess. Or it may already be in rawhide.
>
Indeed, it is, and that compiler makes a
Eventually, I filed a bugreport, and it can be found at
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=22253
It seemed to me that the `-O2' optimization got confused with the
declaration
unsigned limit;
All my books on C tell me that one should use
unsigned int limit;
but `unsigned var
So now I made a selfcontained ource file which exhibits the `dirname'
problem.
The file is at
http://thales.memphis.edu/~tetex/try3.c
See if you can get, on your RH 7.0 system,
# gcc -Wall -O2 try3.c
# ./a.out
name /p/q/a-b-c/kpsewhich, dirname /p/q/a-b-c
name /p/q/a-b-c, dirname /p/q/a-b
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
nux/2.96/specs
> > gcc version 2.96 20000731 (Red Hat Linux 7.0)
>
> And still: I think that your compiler is broken.
>
> Thomas
--
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
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
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...
>
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
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
On Sat, Dec 09, 2000 at 10:00:50AM +0100, Thomas Esser wrote:
> Hi Mate,
>
> I just have noticed, that you have unsuccessfully tried to extend the
> TEXMF list. You did uncomment
> TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN,$HOME}
> but you did not comment
> TEXMF = !!$TEXMFMAIN
>
> (the
/var/qmail/bin:/usr/local/teTeX/bin:/home/tetex/bin
[tetex@thales tetex]$ which xdvi
/usr/local/teTeX/bin/xdvi
My system is a RedHat 7.0 Linux (kernel-2.2.16).
Thx for any help.
--
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
On Thu, Nov 23, 2000 at 08:55:32AM +0100, Thomas Esser wrote:
> Hi Mate,
>
> is xdvi installed in the same directory as kpsewhich? I guess not and
> I guess that this is the problem. Please, check that the location is ok
> and that the right programs are found along $PATH.
I have
which xdvi
/u
On Wed, Nov 22, 2000 at 10:38:41PM +0100, Thomas Esser wrote:
> > $ xdvi a&
> > $ kpathsea: Running mktexpk --mfmode ljfivemp --bdpi 600 --mag 1+0/600
> > --dpi 600 pbkl7t
> > mktexpk: Running mf \mode:=ljfivemp; mag:=1+0/600; nonstopmode; input
> > pbkl7t
>
> The problem is that xdvi does not fi
I am trying to compile
\documentclass{article}
\usepackage{bookman}
\begin{document}
Hello
\end{document}
In fact, compilation goes fine, but then when I try to preview, and I get
$ xdvi a&
$ kpathsea: Running mktexpk --mfmode ljfivemp --bdpi 600 --mag 1+0/600
--dpi 600 pbkl7t
mktexpk: Runnin
OK, so I recompiled teTeX-1.07 against XFree86-4.0.1, and the buttons
are back. But what a pain.
This also means that RH 7.0 users will not complain since they get a
tetex package which is compiled against the new XFree86.
Mate
> > > xdvi +expert
> > > the 'x' keystroke
> >
> > No buttons with xdvik. Or, more precise, the place for the buttinlist
> > is there, but it is empty.
>
> Is this different from what you were reporting earlier?
If we are talking about xdvik: using the `x' keystroke while xdvi open
or ope
I have "updated" my system to RedHat 7.0, and now my xdvi does not
have any of the buttons (Quit and friends).
I'd like to emphasize that I have my own tetex installation, and I am
not using the RH rpms, so the only thing that changed is XFree and
bash to bash2 as the link to sh. I got
$ rpm -q
the same.
On the other hand, you can always do two things:
1) run
texconfig confall
and see if any suspicious (obsolete) directories get picked up.
2) Ask the teTeX deb maintainer/mailing list.
Mate
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
On Thu, Jun 15, 2000 at 11:44:16PM +0200, Reinhard Kotucha wrote:
> > "Julian" == Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > The "find" suggestion is more interesting, perhaps. Maybe the
> > output of the find commands should be piped into something like
> > "grep '^[-A-Za-z
Is there a tetex (perhaps beta or alpha) with the new amslatex in it?
Thx
Mate
Has it been considered to detect and then use stow by the installation
and texconfig to manage symlinks from the tetex tree to common places?
http://www.gnu.org/software/stow/
Best,
Mate
--
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Perhaps you can just put the new amslatex in texmf.local? Make sure
texmf.local is searched before texmf. There are no fmt files to worry
about, I believe.
Then, when the new tetex comes out, you can just delete it.
Mate
Please fix your mailer. In your message, it does not include rfc822
required headers like To: and Subject:, and it makes my mailer (and
probably other people's) scream.
Mate
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
23 matches
Mail list logo
