Hints on investigating 'invalid ELF header' on ia64-hp-openvms

David SAUVAGE - AdaLabs Ltd david.sauvage@adalabs.com
Wed Jul 29 08:51:00 GMT 2015



Hi,

Using a crossed native build of binutils running on ia64-hp-openvms, 
object file built [2] from assembly file [3] is invalid [1]

As the cross binutils build produces valid object files on the target, 
the issue seems to be related to the crossed native build process.
I am looking for hints on how to further investigate and solve this issue.

Best regards,

[1]

||$ MCR DISK$USERS:[ADALABS]ld.exe -v simple.o -o simple.exe
$ link /exe=SIMPLE.EXE simple.opt_tmpfile/opt
|%ILINK-E-INVLDHDR, invalid ELF header; field 'ehdr$b_ei_mag0' has invalid value
%X00
         module: <unassigned>
         file: DISK$USERS:[ADALABS]SIMPLE.O;6|


[2]

|$ MCR DISK$USERS:[ADALABS]as.exe  -o simple.o simple.s|


[3] simple.s

|     .file    "simple.c"
     .pred.safe_across_calls p1-p5,p16-p63
     .text
     .align 16
     .global main#
     .type    main#, @function
     .proc main#
main:
     .prologue 2, 2
     .vframe r2
     mov r2 = r12
     .body
     nop 0
     ;;
     .restore sp
     mov r12 = r2
     br.ret.sptk.many b0
     ;;
     .endp main#
     .ident    "GCC: (GNU) "|





-- 

David SAUVAGE

Software Agile Architect, Director
AdaLabs Ltd - Mauritius
http://adalabs.com
+230 542 818 32
skype sauvaged
BRN C10097052



More information about the Binutils mailing list