build error while building binutils for i686-pc-cygwin

[Dan Kegel]

cathy cobb wrote:
> when I do configure in build-binutils as below:
>   ../configure --target=m68k-coff --prefix=/bar
> and then I do
>   make all 
> I get below error:
 > ...
> gcc -c -DHAVE_CONFIG_H -g -O2 -I.
> -I../../libiberty/../include  -W -Wall -Wtraditional
> -pedantic ../../libiberty/xstrerror.c -o xstrerror.o  
>                   if [ x"" != x ]; then \             
>                                              gcc -c
> -DHAVE_CONFIG_H -g -O2 -I.
> -I../../libiberty/../include  -W -Wall -Wtraditional
> -pedantic  ../../libiberty/mkstemps.c -o
> pic/mkstemps.o; \             else true; fi           
>                                                       
> gcc -c -DHAVE_CONFIG_H -g -O2 -I.
> -I../../libiberty/../include  -W -Wall -Wtraditional
> -pedantic ../../libiberty/mkstemps.c -o mkstemps.o    
>                   rm -f libiberty.a pic/libiberty.a   
>                                            ar rc
> libiberty.a \                                         
>                      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 lrealpath.o
> make-relative-prefix.o make-temp-file.o objalloc.o
> obstack.o partition.o physmem.o pex-unix.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  basename.o insque.o
> mkstemps.o sigsetmask.o stpcpy.o stpncpy.o            
>                                     ar: argv.o: No
> such file or directory                                
>           make[1]: *** [libiberty.a] Error 1          
>                                    make[1]: Leaving
> directory
> `/cygdrive/c/downloads/binutils-2.14/binutils-2.14/build-binutils/libiberty'

You probably have to look at the log yourself (you didn't post
enough of it) to see why argv.o wasn't found.  I'd suggest removing
your build-binutils directory, creating it again and configuring again,
then doing
   make all > log 2>&1
(assuming you're using bash)
and then looking carefully at the log to see if you can see what's
up with argv.o.

(Try not to post huge logs like that if you can.  Better to put them
on a web site and post a link if you really need to post a big one;
usually just posting 20 lines will do.)

In other words, you may have to *gasp* understand how binutils' Makefile
works.  Yes, it's painful, but sometimes there's no alternative to
reading the source.
- Dan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com