gcc 4.10 build errors

gcc 4.10 build errors

Post by Mike Steve » Thu, 23 Mar 2006 03:29:19


Hi, I'm trying to build the new version of gcc on my winxp box, and have
come across some problems. make was still running when I left work
yesterday, so I just let it chug along and deal with any issues today.
Make had generated some errors, so I re-ran it to see what I was up
against. It produced some rather scary looking segmentation faults from
application ??UNKNOWN?? (sic), but when I redirected stderr to a text
file, they were not reproduced. What I am getting though is this
(including the command generating the error):

rc ./libiberty.a \
./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./alloca.o ./argv.o
/choose-temp.o ./concat.o ./cp-demint.o ./dyn-string.o ./fdmatch.o
/fibheap.o ./floatformat.o ./fnmatch.o ./fopen_unlocked.o ./getopt.o
/getopt1.o ./getpwd.o ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o
/lrealpath.o ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o
/obstack.o ./partition.o ./pexecute.o ./physmem.o ./pex-common.o
/pex-one.o ./pex-djgpp.o ./safe-ctype.o ./sort.o ./spaces.o
/splay-tree.o ./strerror.o ./strsignal.o ./ternary.o
/unlink-if-ordinary.o ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o
/xstrdup.o ./xstrerror.o ./xstrndup.o ./asprintf.o ./mempcpy.o
/mkstemps.o ./snprintf.o ./sigsetmask.o ./stpncpy.o ./strndup.o
/strverscmp.o ./vasprintf.o ./vsnprintf.o
make.exe[2]: *** [libiberty.a] Error -1
make.exe[2]: Leaving directory
`c:/gnu/gcc-4.10/build-i386-pc-msdosdjgpp/libiber
ty'
make.exe[1]: *** [all-build-libiberty] Error 2
make.exe[1]: Leaving directory `c:/gnu/gcc-4.10'
make.exe: *** [all] Error 2

While copying that, I noticed that the command preceding it seems to be
deleting libiberty.a. Any suggestions on how I can resolve this?

Cheers,
Mike
 
 
 

gcc 4.10 build errors

Post by Mike Steve » Thu, 23 Mar 2006 08:30:18

> against. It produced some rather scary looking segmentation faults from

Sorry to reply to myself, but please ignore this bit. There are a few
things I'm working on at present, and this came up in something else
unrelated to djgpp stuff. Thanks again.

Mike