RE: build errors --bfd directory

["Dave Korn" <dave dot korn at artimi dot com>]

On 27 March 2006 17:48, sean yang wrote:

> Here is what I did to make a binutils tool and the corresponding error
> messages. How to fix it?
> 
> 
> home>mkdir mybinutils
> home>cd binutils-2.16.1
> binutils-2.16.1>./configure --prefix=/home/mybinutils
> binutils-2.16.1>make
> ......
> make[3]: Entering directory `/home/binutils-2.16.1/bfd'
> /bin/sh ./libtool --mode=link gcc -W -Wall -Wstrict-prototypes
> -Wmissing-prototypes -g -O2   -o libbfd.la -rpath /home/mybinutils/lib
> -release 2.16.1  archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo cache.lo
> coffgen.lo corefile.lo format.lo init.lo libbfd.lo opncls.lo reloc.lo
> section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.lo tekhex.lo
> ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo simple.lo archive64.lo `cat
> ofiles`
> ar cru .libs/libbfd.a  archive.o archures.o bfd.o bfdio.o bfdwin.o cache.o
> coffgen.o corefile.o format.o init.o libbfd.o opncls.o reloc.o section.o
> syms.o targets.o hash.o linker.o srec.o binary.o tekhex.o ihex.o stabs.o
> stab-syms.o merge.o dwarf2.o simple.o archive64.o elf32-i386.o elf32.o elf.o
> elflink.o elf-strtab.o elf-eh-frame.o dwarf1.o i386linux.o aout32.o
> efi-app-ia32.o peigen.o cofflink.o elf32-gen.o cpu-i386.o trad-core.o
> ar: archive.o: No such file or directory

  The question is, why doesn't archive.o exist?  Is there anything earlier in
the logfile (in the bits you replaced with '......') where you can see it
trying to compile archive.c to generate archive.o (not archive.lo)?  If so,
what went wrong?  If not, maybe something went wrong at configure time...


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....