Re: SID configury, libtoolery updated

Dave Brolley <[email protected]>
Newsgroups gmane.comp.emulators.sid.devel
Message-ID <[email protected]>
Jim Blandy wrote:

>I've upgraded SID's libtool, autoconf, and automake machinery, fixed
>some warnings, and fixed a long-standing problem with components that
>link against libiberty.
>
>
>  
>
I seem to be having trouble building sid now. Specifically

o The generate libtool scripts seem to expect the environment variable 
SED to be set to a working sed
o I'm getting this error when linking in cgen-cpu

/bin/sh ./libtool --tag=CXX --mode=link c++ -g     -o libcgencpu.la 
-rpath /notnfs/brolley/sources/install/i686-pc-linux-gnu/lib/sidcomp 
-module -no-undefined compCGEN.lo tracedis.lo ms1/libms1.la  
-L../../../libiberty/pic -liberty cgen-asm.lo cgen-dis.lo cgen-opc.lo 
dis-buf.lo dis-init.lo -lpthread -lm
./libtool: line 1: cd: ../../../libiberty/pic: No such file or directory

...worked around by creating an empty libibrty/pic directory) but then 
later...

if c++ -DHAVE_CONFIG_H -I. -I/home/brolley/sources/src/sid/main/dynamic 
-I. -I. -I../../include 
-I/home/brolley/sources/src/sid/main/dynamic/../../include 
-I/home/brolley/sources/src/sid/main/dynamic/../../../include    -g -MT 
commonCfg.o -MD -MP -MF ".deps/commonCfg.Tpo" -c -o commonCfg.o 
/home/brolley/sources/src/sid/main/dynamic/commonCfg.cxx; \
then mv -f ".deps/commonCfg.Tpo" ".deps/commonCfg.Po"; else rm -f 
".deps/commonCfg.Tpo"; exit 1; fi
make[4]: *** No rule to make target 
`../../../libiberty/pic/libiberty.a', needed by `sid'.  Stop.


I've refreshed libiberty and rebuilt it from scratch, bit I don't get a 
libiberty/pic directory in my build tree. Is there some configure option 
I need? I'm using autoconf 2.59, automake 1.9.5 and libtool 1.5.18

uname -a says

Linux to-hpws2.toronto.redhat.com 2.4.21-27.0.2.ELsmp #1 SMP Wed Jan 12 
23:35:44 EST 2005 i686 i686 i386 GNU/Linux

src/config.guess says

i686-pc-linux-gnu

Thanks,
Dave
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.