wim wrote: > 1 Output of make: make.log.gz > > 2 Logfile of configure: config.log.gz > > 3 config.status config.status.gz > > 4 Makefile Makefile.gz
The error occurs when configuring inside the libiberty subdirectory, but you've attached the config.log from the toplevel. Each directory that runs configure has its own config.log, so the nature of the error will be evident from the config.log under libiberty not the one attached. Also, this seems a little worrying: configure:3372: checking whether gcc accepts -g configure:3393: gcc -c -g conftest.c >&5 /tmp/ccSkXtzK.s: Assembler messages: /tmp/ccSkXtzK.s:14: Warning: Missing string /tmp/ccSkXtzK.s:14: Error: Rest of line ignored. First ignored character is `1'. /tmp/ccSkXtzK.s:15: Error: Unknown pseudo-op: `.loc' /tmp/ccSkXtzK.s:27: Error: Unknown pseudo-op: `.loc' /tmp/ccSkXtzK.s:29: Error: Unknown pseudo-op: `.loc' It seems what whatever this assembler is doesn't accept Dwarf-2 debug directives, which is strange for a linux system. Are you sure you didn't accidently get a cross-assembler for another target installed in /bin somehow? What is the result of "`gcc -print-prog-name=as` --version"? Brian _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
