This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gcc configure with arm-wince-pe


hello:
    I am trying to build mingw32 3.2 with configuration
--target=arm-wince-pe. I had built it with --target=arm-pe, but i think
something goes wrong with file format it generated. With
arm-pe-objdump.exe -d(or -S), i couldn't dump disassemble code for
object file, but i COULD do it for arm exe files. Meanwhile dumpbin.exe(
tool provided by wince SDK) could not disassemble gcc ARM exe file,
either. 

    Then I want to see if I could get more compatibility when target is
arm-wince-pe. I had built binutils then gcc, but something unexpected
happened after some warnings:
    ../../gcc/config/arm/lib1funcs.asm:452: Error: cannot represent
BFD_RELOC_THUMB_PCREL_BRANCH23 relocation in this object file format

    I search this error info in google and some one said:
[ref]
It means that gcc hasn't been ported to wince for the ARM (indeed it may

not have been ported to wince for anything).  The ARM-pe port was done
for 
a different project and will almost certainly not work with wince as is.

Patches would of course be welcome...
[end of ref]

So my questions are:
1 . How much difference between gcc ARM/PE and wince PE binary file
format? 
2. Is it true that "gcc hasn't been ported to wince for the ARM "?

My environment is win2k, MinGW-2.0.0-3.exe,MSYS1.08,source packages
:binutils-2.13-20020903-1-src.tar.gz,gcc-3.2-20020817-1.src.tar.gz,newli
b-1.10.0.tar.gz

Best regard
wreckor


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]