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

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> 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)

This is not what I meant. Please put '-v' into *each* invocation when
compiling cfengine, e.g.

gcc -v -o foo foo.c

> 
> >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:

I'm not certain whether this is really the case, only gcc -v can tell
what the compiler actually does. With 'gcc -dumpspecs', you can find
out the value of asm_cpu_default.

Also, if you link in a library that contains SPARC32PLUS binaries, the
resulting binary will also be SPARC32PLUS.

Regards,
Martin

P.S. I removed bug-cfengine@gnu.org from the CC: