This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
My emailer (Pegasus) takes the 'Sender' field as the default reply address, so this message seemed to have originally gone to wrong address... ------- Forwarded message follows ------- From: Kai Ruottu <kai.ruottu@luukku.com> To: crossgcc-owner@sources.redhat.com, crossgcc@sources.redhat.com Subject: Re: arm-wince-pe: output problem w/GCC 3.2 Send reply to: kai.ruottu@luukku.com Date sent: Tue, 19 Nov 2002 16:23:26 +0200 Craig Vanderborgh wrote: > > Hello all: > > > > We are determined to get a cross-compiler for arm-wince-pe working > > on RedHat 7.1. Some progress has been made in this direction. We now > > have builds of binutils-2.13 and gcc-3.2 that create running binaries. > > However the results are "not quite there yet"... Quickly seen the FSF-gcc-3.x-sources DON'T support 'arm-wince-pe' at all, only the 'generic' 'arm-pe' (do any embedded people use this?) and the 'arm-epoc-pe'. There are other gcc-3.x sources with the 'support' (at least it looks so...) though... So, what extra was done in order to add the needed ARM/WinCE support ? > Presumably the startup code or something else is wrong, but I am > unsure what I should do next. I have only the WinCE2.0 libs for MIPS and SH (and for the x86-emu), and they had no separate 'startups' ('crt*.obj' or something), only the libraries ('*.lib'). Does the WinCE3.0-stuff have some separate startup files? Which startups and libs you linked against when creating the executable? In the MIPS and SH cases the 'coredll.lib' and 'corelibc.lib' seemed to be the basic C-libraries and one of these had the C-startups included. How did you fix the WinCE-headers, so that they would be compatible with GCC ? My tries with the MIPS and SH toolchains showed the MS- headers needing very much fixing for GCC... The Cygwin and Mingw GCCs don't use the equivalent 'Platform SDK' headers for Win32, but instead the own 'w32api' headers... Maybe the MS-provided headers can be fixed to work with GCC, but the standard 'fixinc' in the GCC-build doesn't do this... As you can see, nobody else can do the same you did and then see what happens... Telling what you did with the gcc-3.2 sources, what possible patches and from where, you did install, could be a good start. Otherwise don't expect others being capable to help you here. The ARM/EPOC has used probably quite the same 'arm-pe' format as ARM/WinCE, and if you ask Nokia, Motorola, Samsung, Siemens etc., they probably claim that GCC works with EPOC when using the 'arm-epoc-pe' target, at least in the EPOC's own SDKs with GCC... (available free, Nokia snailmails the SDK6 CDROM if one cannot download it) BTW, the Intel/RedHat XScale-toolchain distribution (gcc-3.1) seems to have the 'arm-wince-pe' support straight from the box. What were the experiences with this? Cheers, Kai ------- End of forwarded message ------- ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |