Karl Berry �����:

>     1. change mktemp on mkstemp due to gcc-3.1 assumes usage of mktemp as error
> 
> Why does gcc do that?  Seems wrong.  I doubt mkstemp is as portable as mktemp.
> 

well, that's the build error:
===================
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I../intl 
-DLOCALEDIR=\"/usr/local/share/locale\"    -g -O2 -c `test -f texindex.c 
|| echo './'`texindex.c
gcc  -g -O2   -o texindex  texindex.o ../lib/libtxi.a
/usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
texindex.o: In function `main':
/home/lb/Soft/texinfo-4.2/util/texindex.c:184: the use of `mktemp' is 
dangerous, better use `mkstemp'
collect2: ld returned 1 exit status
====================
i've decided that was gcc-3.1 specific thing because gcc-3.0.4 works 
fine with this mktemp giving the "dangerous" message as warning. i've 
search the gcc changelog on this issue but found nothing.

>     2. ospeed variable conflicts with ncurces from ASP Linux
> 
> Maybe so, but we have to define/declare ospeed for other systems (that
> use termcap, according to the ancient comment there).  configure already
> checkes for <ncurses/termcap.h> and <termcap.h>, and if either is found,
> it doesn't try to declare ospeed and the other termcap variables
> itself.  Doesn't "ASP Linux" provide those header files?
> 
the package ncurces provides. it's placed in  /usr/include/ncurses/termcap.h
but it was'nt found by configure script:
============= config.h
/* Define to 1 if you have the <ncurses/termcap.h> header file. */
/* #undef HAVE_NCURSES_TERMCAP_H */
==============
that's the error message:
======
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 
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.1/../../../libncurses.so
collect2: ld returned 1 exit status
======

but, after checking for ncurses/termcap.h i suppose this name conflict 
is because the header not used.

>     3. when creating $infopath/dir there's no comma after node name, so info 
>     can't find top node
> 
> Hmm, the comma should not be required as far as I know.  I'll look into
> this more.
> 

i've checked the problem a bit more carefully. this error appears if the 
first character after the node name isn't comma or tab. in default 
compilation it's space char. check the sample dir in attach -- i have it 
unworking.

lb
description

File: dir,      Node: Top 

Reply via email to