Maybe, something for you? teTeX-2.0.2 containes texinfo 4.5.

Thomas

----- Forwarded message from vin gui <[EMAIL PROTECTED]> -----

X-Authentication-Warning: leo.dbs.uni-hannover.de: mdom set sender to [EMAIL 
PROTECTED] using -f
Date: Fri, 04 Apr 2003 14:51:12 +0200
From: vin gui <[EMAIL PROTECTED]>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: fr, en-us, en
To: [EMAIL PROTECTED]
Subject: Compilation problem
Precedence: bulk
X-UIDL: XDL"!!"k"!H~C!![i'!!

Hello,

I hope that this is the right place for this question.
I have a compilation problem with tetex ( version 2.0.2).
It seems to occur in texinfo, and seems to be related to ncurses.

Here are the last few lines of the output of make world:
_________________________________________________________________________
gcc  -g -O2   -o ginfo  dir.o display.o dribble.o echo-area.o filesys.o 
footnotes.o gc.o indices.o info-utils.o info.o infodoc.o infomap.o m-x.o 
man.o nodemenu.o nodes.o search.o session.o signals.o terminal.o tilde.o 
variables.o window.o doc.o key.o  ../lib/libtxi.a  -lncurses
/usr/bin/ld: Warning: size of symbol `ospeed' changed from 2 to 4 in 
/lib/libncurses.so
collect2: ld returned 1 exit status
make[4]: *** [ginfo] Error 1
make[4]: Leaving directory 
`/home2/install/tetex-src-2.0.2/utils/texinfo/info'
make[3]: *** [all] Error 2
make[3]: Leaving directory 
`/home2/install/tetex-src-2.0.2/utils/texinfo/info'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home2/install/tetex-src-2.0.2/utils/texinfo'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home2/install/tetex-src-2.0.2/utils/texinfo'
make: *** [all] Error 1
____________________________________________________________________________

I can attach configure.log or the whole output of make world if necessary...

Many thanks !

Vincent.

----- End forwarded message -----


_______________________________________________
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo

Reply via email to