[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Log for failed build of gcc-snapshot_20030314-1



On Sat, Mar 15, 2003 at 07:28:46AM +0100, Matthias Klose wrote:
> Christian T. Steigies writes:
> > Hi,
> > please check the log for failed build of gcc-snapshot_20030314-1 for m68k.
> > 
> > echo regex.o cplus-dem.o cp-demangle.o md5.o alloca.o argv.o choose-temp.o concat.o
> > dyn-string.o fdmatch.o fibheap.o floatformat.o fnmatch.o getopt.o getopt1.o getpwd.o getruntime.o
> > hashtab.o hex.o lbasename.o make-relative-prefix.o make-temp-file.o objalloc.o obstack.o partition.o physmem.o pexecute.o safe-ctype.o sort.o spaces.o splay-tree.o strerror.o strsignal.o
> > ternary.o xatexit.o xexit.o xmalloc.o xmemdup.o xstrdup.o xstrerror.o > required-list                        
> > make[4]: Entering directory `/build/buildd/gcc-snapshot-20030314/build/libiberty/testsuite'         
> > make[4]: Nothing to be done for `all'.                                                              
> > make[4]: Leaving directory `/build/buildd/gcc-snapshot-20030314/build/libiberty/testsuite'          
> > make[3]: Leaving directory `/build/buildd/gcc-snapshot-20030314/build/libiberty'                    
> > make[3]: Entering directory `/build/buildd/gcc-snapshot-20030314/build/zlib'                        
> > make[3]: *** No rule to make target `adler32.', needed by `libz.a'.  Stop.                          
> > make[3]: Leaving directory `/build/buildd/gcc-snapshot-20030314/build/zlib'                         
> > make[2]: *** [all-zlib] Error 2                                                                     
> > make[2]: Leaving directory `/build/buildd/gcc-snapshot-20030314/build'                              
> > s=`cat status`; rm -f status; test $s -eq 0                                                         
> > make[1]: *** [stamps/05-build-stamp] Error 1                          
> 
> strange ... could you retry this on a glibc-2.2.5 based build
> environment. I don't have any problems to build it there.

Thats a little difficult. stable comes with libc-2.2.5, but has no gcc-3.2.
Testing and unstable have gcc-3.2, but libc-2.3.1...
Can I remove the dependency on gcc-3.2?

Christian



Reply to: