Re: gcc configure with arm-wince-pe

["Craig A. Vanderborgh" <craigv at voxware dot com>]

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