public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* Re: gcc binary format output
       [not found]         ` <44BBE453.6000604@mbnet.fi>
@ 2006-07-18 12:25           ` Kai Ruottu
  2006-07-18 18:26             ` Mike Frysinger
  0 siblings, 1 reply; 2+ messages in thread
From: Kai Ruottu @ 2006-07-18 12:25 UTC (permalink / raw)
  Cc: Victor Roman Archidona, gcc-help, binutils

Kai Ruottu kirjoitti:
> Victor Roman Archidona kirjoitti:
>> Thanks for your feedback Kai. In the binutils mailing list has been
>> sent a patch that fixes the problem. The URL for anyone interested in
>> it is:
>>
>> http://www.sourceware.org/ml/binutils/2006-07/msg00192.html
>>   
> lets see what the 'x86_64-freebsd6.1' ones will do now.
The given patches weren't enough :-(   The resulted GNU linker complained
about not finding the output format etc.  A quick "how these things were 
done
in 'alpha', 'i386' etc." comparison revealed that also the 'ld/emulparams'
directory required the following patch in the current 
'binutils-2.17.50.0.3' :

---------------- clip ----------------------------
*** elf_x86_64_fbsd.sh.orig     Thu Mar  7 21:52:39 2002
--- elf_x86_64_fbsd.sh  Tue Jul 18 15:06:58 2006
***************
*** 1,2 ****
--- 1,3 ----
  . ${srcdir}/emulparams/elf_x86_64.sh
  . ${srcdir}/emulparams/elf_fbsd.sh
+ OUTPUT_FORMAT="elf64-x86-64-freebsd"
---------------- clip ----------------------------


After adding this the produced binutils gave right labeled executables and
more importantly the crosscompilers to the 'x86_64-freebsd6.1' target
could be built, giving seemingly OK shared libraries with the following:

kai@Dell:/data1/home/src/gcc-4.0.3/build/gcc> readelf -h libgcc_s.so.1
ELF Header:
  Magic:   7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00
  Class:                             ELF64
  Data:                              2's complement, little endian
  Version:                           1 (current)
  OS/ABI:                            UNIX - FreeBSD
  ABI Version:                       0
  Type:                              DYN (Shared object file)
  Machine:                           Advanced Micro Devices X86-64
  Version:                           0x1


output got via the 'readelf -h'...

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: gcc binary format output
  2006-07-18 12:25           ` gcc binary format output Kai Ruottu
@ 2006-07-18 18:26             ` Mike Frysinger
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Frysinger @ 2006-07-18 18:26 UTC (permalink / raw)
  To: binutils; +Cc: Kai Ruottu, Victor Roman Archidona, gcc-help

[-- Attachment #1: Type: text/plain, Size: 521 bytes --]

On Tuesday 18 July 2006 08:37, Kai Ruottu wrote:
> The given patches weren't enough :-(   The resulted GNU linker complained
> about not finding the output format etc.  A quick "how these things were
> done
> in 'alpha', 'i386' etc." comparison revealed that also the 'ld/emulparams'
> directory required the following patch in the current
> 'binutils-2.17.50.0.3' :

Victor already posted this fix ... best if you follow the new thread on the 
binutils list rather than continuing this cross-posted one
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-07-18 18:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <44B4500F.4010406@unixevil.info>
     [not found] ` <44B64336.1040107@mbnet.fi>
     [not found]   ` <17590.16794.458483.581617@zebedee.pink>
     [not found]     ` <44B67AE5.8050307@mbnet.fi>
     [not found]       ` <44B8F528.1000401@unixevil.info>
     [not found]         ` <44BBE453.6000604@mbnet.fi>
2006-07-18 12:25           ` gcc binary format output Kai Ruottu
2006-07-18 18:26             ` Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).