Re: Installation problems binutils-2.18 (part 2)
wim <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]:/bin> as --version > GNU assembler 2.9 > Copyright 1997 Free Software Foundation, Inc. SUSE Linux 8.0 originally came with binutils 2.11.92.0.10, which is quite a bit newer than what you have, despite already being several years old. Also, it didn't provide the file /bin/as in the first place. (Btw, putting "." first in $PATH is a very bad thing to do. If you really want "." in $PATH you should at most put it last.) Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: Installation problems binutils-2.18 (part 2)
wim wrote: > About the output of the following command: > gcc -print-prog-name=as > > The output is simply: > > as That was meant to be one single command: `gcc -print-prog-name=as` --version But anyway, that doesn't really matter. > [EMAIL PROTECTED]:/bin> as --version > GNU assembler 2.9 > Copyright 1997 Free Software Foundation, Inc. > This program is free software; you may redistribute it under the terms of > the GNU General Public License. This program has absolutely no warranty. > This assembler was configured for a target of `i686-pc-linux-gnu'. So you somehow have a modern gcc 4.2.4 and this ancient 11 year old assembler? That's the cause of your problem: configure:4657: gcc -o conftest -O2 conftest.c >&5 /tmp/ccBCyz5e.s: Assembler messages: /tmp/ccBCyz5e.s:23: Warning: Bad .section directive: want a,w,x in string /tmp/ccBCyz5e.s:23: Error: Rest of line ignored. First ignored character is `M'. gcc is outputting directives that the assembler doesn't understand because it's much older. You can't really expect tools with this large of a version dicrepancy to work together. I don't even understand how you managed to compile this version of gcc because it's supposed to do configure checks of the assembler in order to enable functionality, but that's neither here nor there. I suggest that you ditch this self-compiled gcc and use whatever compiler came with your distro, as it will at least work harmoniously with this ancient binutils. Use that combination to build a modern binutils, then rebuild a modern gcc and make sure it uses the updated binutils (e.g. by putting the new binutils first in PATH before the old one or by specifying --with-as and --with-ld.) Brian ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Installation problems binutils-2.18 (part 2)
Dear Brian ! Thank you for your fast response and your analysis ! In the directory ~libiberty I have the following files -rw-r--r--1 wim users 0 Jul 8 21:25 config.cache -rw-r--r--1 wim users 27174 Jul 8 21:25 config.log -rw-r--r--1 wim users 71 Jul 8 21:25 xhost-mkfrag See the attachments for details About the output of the following command: gcc -print-prog-name=as The output is simply: as looking in /bin with the command "whatis as" [EMAIL PROTECTED]:/bin> whatis as as (1) - the portable GNU assembler. Checking the version of "as" with as --version [EMAIL PROTECTED]:/bin> as --version GNU assembler 2.9 Copyright 1997 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. This assembler was configured for a target of `i686-pc-linux-gnu'. I hope this info is useful to tackle the problem Many thanks and looking for your response Wim Eijsenga -- On Tuesday 08 July 2008 06:07, you wrote: > 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 config.cache.gz Description: GNU Zip compressed data config.log.gz Description: GNU Zip compressed data xhost-mkfrag.gz Description: GNU Zip compressed data ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
