Re: Binaries compiled with gcc-2.95.2 won't execute.

["Didier M. Contis" <didier at ece dot gatech dot edu>]

Here is the results from gcc -v:

>gcc -v
Reading specs from
/usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specs
gcc version 2.95.2 19991024 (release)

>grep xarch specs 
%{mcpu=v8plus:-xarch=v8plus} %{mcpu=ultrasparc:-xarch=v8plusa}
%{!mcpu*:%(asm_cpu_default)}

What I do not understand is why this is passed to the assembler in case of
cfengine, and not in the case of the compilation of other programs
like nmap:

>file nmap
nmap:           ELF 32-bit MSB executable SPARC Version 1, dynamically
linked, not stripped

In addition, the specs file has the same date has the rest of the gcc
binaries -> everything seems to have been updated when I recompiled
gcc on the SS20 - Solaris 2.6

Regards, Didier.


On Thu, 30 Dec 1999, Martin v. Loewis wrote:

> > >file cfengine
> > cfengine:       ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+
> > Required
> 
> Well, this is the problem. Somehow, -xarch=v8plus is passed to the
> assembler, or the assembler somehow assumes it should produce V8
> binaries itself. Such binaries don't work on older machines.
> 
> You can use 'gcc -v' to find out how the assembler is being
> invoked. It would also help to know how exactly the compiler was
> configured, and what assembler/linker is being used.
> 
> Regards,
> Martin
> 

-----------------------------------------------------------------------
			Research Engineer I
		   Georgia Institute of Technology
      School of Electrical Engineering, Atlanta, GA  30332-0250
		    E-MAIL: didier@ee.gatech.edu
                        PHONE: (404) 894-3872