Re: gcc configure with arm-wince-pe

Re: gcc configure with arm-wince-pe

[Craig A. Vanderborgh]

We are extremely interested in getting our arm-wince-pe stuff
submitted.  It seems like it is a popular target and the demand for it
is out there. I think it will be especially compelling once when we get
gcj finished.

Although I believe we have done good software engineering in the work
that we've done thus far on the toolchain and newlib, I am unsure about
how to go about submitting this stuff.  What I would really like is to
work with the maintainers to get this done, but we definitely want to
incorporate this work so others can make use of it.  We have contacted
nickc and hopefully he will be interested in getting this to happen.

regards,
craig vanderborgh
voxware incorporated

> Am I correct in assuming that you are going to be submitting fixes for
> everything to the various mailing lists?  Or has this already been
> done and you're just waiting for approval?
>
> cgf

On Tue, Mar 11, 2003 at 04:14:36PM -0700, Craig A. Vanderborgh wrote:
>we have built a complete arm-wince-pe toolchain (binutils-2.13.90,
>gcc-3.2,newlib-1.11.0) hosted on x86linux.  arm-wince-pe is not quite a
>supported configuration - we found that for the most part this port had
>"been done" but had some serious problems.  Getting them all fixed has
>been difficult for us but we are pretty much there.
>
>We have tarballs available for you.  I have a gcc/binutils/newlib
>tarball for RedHat 7.1+ that installs into /usr/local/wince and "just
>works".  You might find this of some use for debugging your
>configuration.  I could also send you the patched source tarballs if
>you desire.

Am I correct in assuming that you are going to be submitting fixes for
everything to the various mailing lists?  Or has this already been done
and you're just waiting for approval?

cgf

Re: gcc configure with arm-wince-pe

[Kai Ruottu]

longchuan wrote:

> hello:
>     I am trying to build mingw32 3.2 with configuration
> --target=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 checked this and the build gave this error when compiling the Thumb
mode (-mthumb) libgcc.a...

  So, how important it is to produce code for Thumb and for WinCE/ARM ?
This feature is broken now but does it matter ?  Producing the Thumb-
mode libgcc.a can always be disabled...

Re: gcc configure with arm-wince-pe

[Christopher Faylor]

On Tue, Mar 11, 2003 at 04:14:36PM -0700, Craig A. Vanderborgh wrote:
>we have built a complete arm-wince-pe toolchain (binutils-2.13.90,
>gcc-3.2,newlib-1.11.0) hosted on x86linux.  arm-wince-pe is not quite a
>supported configuration - we found that for the most part this port had
>"been done" but had some serious problems.  Getting them all fixed has
>been difficult for us but we are pretty much there.
>
>We have tarballs available for you.  I have a gcc/binutils/newlib
>tarball for RedHat 7.1+ that installs into /usr/local/wince and "just
>works".  You might find this of some use for debugging your
>configuration.  I could also send you the patched source tarballs if
>you desire.

Am I correct in assuming that you are going to be submitting fixes for
everything to the various mailing lists?  Or has this already been done
and you're just waiting for approval?

cgf

Re: gcc configure with arm-wince-pe

[Craig A. Vanderborgh]

hi:

we have built a complete arm-wince-pe toolchain (binutils-2.13.90,
gcc-3.2,newlib-1.11.0) hosted on x86linux.  arm-wince-pe is not quite a
supported configuration - we found that for the most part this port had
"been done" but had some serious problems.  Getting them all fixed has
been difficult for us but we are pretty much there.

We have tarballs available for you.  I have a gcc/binutils/newlib
tarball for RedHat 7.1+ that installs into /usr/local/wince and "just
works".  You might find this of some use for debugging your
configuration.  I could also send you the patched source tarballs if you
desire.

We do not yet have our arm-wince-pe stuff available via http but we will
soon.  In the meantime, I can email you these things, or upload them to
an ftp server of your choice.  Let me know what you need.

regards,
craig vanderborgh
voxware incorporated

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

gcc configure with arm-wince-pe

[longchuan]

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