gdb-19990510/libiberty failure

[Elena Zannoni]

Yes, there is some problem due to changes coming from egcs, that were 
not completed at the time of the snapshot.

This is a patch that should get libiberty building again for the short term
(from Stan Shebs):

Index: Makefile.in
===================================================================
RCS file: /cvs/cvsfiles/devo/libiberty/Makefile.in,v
retrieving revision 1.152
diff -u -r1.152 Makefile.in
--- Makefile.in 1999/05/06 23:40:20     1.152
+++ Makefile.in 1999/05/11 22:42:32
@@ -87,7 +87,7 @@
        "RANLIB=$(RANLIB)" \
        "SHELL=$(SHELL)"
 
-all: stamp-picdir $(TARGETLIB) needed-list required-list all-subdir
+all: stamp-picdir $(TARGETLIB) needed-list required-list
        @$(MULTIDO) $(FLAGS_TO_PASS) multi-do DO=all
 
 .PHONY: check installcheck




Elena




Philippe De Muyter writes:
 > On both m68k-motorola-sysv and powerpc-ibm-aix4.1.5.0, compiling gdb fails
 > with :
 > 
 > echo argv.o choose-temp.o concat.o cplus-dem.o fdmatch.o fnmatch.o getopt.o geto
 > pt1.o getruntime.o hex.o floatformat.o objalloc.o obstack.o pexecute.o spaces.o
 > splay-tree.o strerror.o strsignal.o xatexit.o xexit.o xmalloc.o xstrdup.o xstrer
 > ror.o > required-list
 > gnumake[2]: Entering directory `/usr/local/build/gdb/libiberty/testsuite'
 > gnumake[2]: *** No rule to make target `all'.  Stop.
 > gnumake[2]: Leaving directory `/usr/local/build/gdb/libiberty/testsuite'
 > gnumake[1]: *** [all-subdir] Error 2
 > gnumake[1]: Leaving directory `/usr/local/build/gdb/libiberty'
 > gnumake: *** [all-libiberty] Error 2
 > 
 > Previously, the log-file was as follows :
 > echo argv.o choose-temp.o concat.o cplus-dem.o fdmatch.o fnmatch.o getopt.o geto
 > pt1.o getruntime.o hex.o floatformat.o objalloc.o obstack.o pexecute.o spaces.o
 > splay-tree.o strerror.o strsignal.o xatexit.o xexit.o xmalloc.o xstrdup.o xstrer
 > ror.o > required-list
 > gnumake[1]: Leaving directory `/backup/tmp/gdbss/libiberty'
 > gnumake[1]: Entering directory `/backup/tmp/gdbss/texinfo'
 > 
 > Is there a new directory `testsuite' in `libiberty' that is not handled
 > correctly ?
 >