bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Installation problems binutils-2.18 (part 2)


From: wim
Subject: Installation problems binutils-2.18 (part 2)
Date: Tue, 8 Jul 2008 21:47:39 +0200

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"


address@hidden:/bin> whatis as
as (1)               - the portable GNU assembler.

Checking the version of "as" with as --version

address@hidden:/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

Attachment: config.cache.gz
Description: GNU Zip compressed data

Attachment: config.log.gz
Description: GNU Zip compressed data

Attachment: xhost-mkfrag.gz
Description: GNU Zip compressed data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]