cegcc-devel Mailing List for CeGCC - Cross development for Pocket PC

Dear all,

I am trying to build the latest webkit for wince, however, it requires 
the compiler to support C++11, and the VC++ is unable to do it.  (VC2013 
can do, but it can only be used for wince2013, and also the wince2013 
sdk headers and toolchain don't support c++11 as well, which cause lots 
of problems)

I have spent some times on upgrading cegcc to gcc 4.9.2.

Currently, i can make the cegcc build for arm mingw32   with gcc 4.9.2 
and binutils-2.25.1, but it still have lots of issues still exist.

1. only for arm build, no X86
2. only for mingw32
3. only build on cygwin
4. need to hack one of the binutils file to make the linker work.

Actually the work so far i have done can build the webkit for wince6 and 
wince7, I just wonder anybody would like to take what i have to make it 
properly, as i don't think i will go further on this, except to make 
cegcc to support thumb build (i.e. for wince2013)

Cheers,

Fred

Am 06.05.2012 09:09, schrieb Vincent Torri:
> On Sun, May 6, 2012 at 7:54 AM, Max Kellermann <ma...@du...> wrote:
>> On 2012/05/06 05:49, Pavel Pavlov <pa...@su...> wrote:
>>> Now, with WinPhone8 it rejects the libs as invalid. Upcoming
>>> VisualStudio and Windows 8 have ARM support out of the box. armasm
>>> (which looks too similar to armasm that comes with arm's dev tools)
>>> lists three types of machine targets: arm, thumb, armce. Any idea
>>> what's different? Do they use different object format (quite
>>> unlikely), or they simply added different CPU id for otherwise
>>> identical objects?
>>
>> Reportedly, WinPhone8 is based on the Windows 8 (desktop) kernel, not
>> on the WinCE kernel.  That may make a difference, even if only for the
>> OS declaration.  Try objdump on WinPhone7 and 8 (native) binaries and
>> look for differences.
>>
>> Since there is only official support for CIL code on WinPhone, there
>> was no need for native code compatibility.
> 
> i don't know if i have already suggested this to you, but you should
> try to contact mingw-w64 developpers to see if you can integrate your
> work in mingw-w64

It seems i wrote the same idea in the wrong thread :)
Here's what i wrote:

> It would be great to generate a mingw-arm that can compile for WoA (Win8 on ARM) and maybe also for CE.
> mostly you need to change the machine type and provide the libs and includes (partly already there for the x86 stuff).
> WoA makes use of Thumb2, but there's no need to have compiler support for it.
> I'd guess it's not that hard when you're familiar with the code.
> We could make use of that in Wine for example.
> E.g. crosscompiling Wine dlls missing in WoA to add additional functions, or simply crosscompile the testsuite.
> I already was able to run WoA PEs (compiled with VS11beta) in Wine...
> Thoughts?

I had a look at it and tried very hard to get mingw-w64 compiling for arm, but everything seems to target x86/x64 even if they have the ce libs (mmh, maybe for x86 CE, not sure).
So I bet that it's so much easier to integrate the big library set (the one used for x86) into cegcc and change the target to IMAGE_FILE_MACHINE_ARMNT.
There are plenty of reasons to do so and much people would use it, so it's not just a fun project.
I'll try that some day, but it's most likely faster if someone else does :)
Anyone?


-- 

Best Regards, André Hentschel

(Continuing with an old thread because of context)

Hi,

I have downloaded Max's cegcc fork (mail below), and built the mingw32ce
toolchain. Build has been successful on 32-bit Ubuntu 12.04 LTS. Simple
programs work fine. However, if I have a simple program with a "virtual"
function, it throws a Data Abort. The program that I am trying to run is
reproduced below:

/* tv1.cpp */
#include <iostream>

using namespace std;

class TVA {
    public:
    int pm() { return 10; }
    virtual int vm();
};

int TVA::vm() { return 20; }

int main() {
    cout << "tv1-begin";

    TVA a1;
    int rv = a1.pm();
    cout << rv;

    cout << "tv1-end";
    return 0;
}

Command line: arm-mingw32ce-g++ tv1.cpp -o tv1.exe
Note: Result is same whether enable-auto-import is used or not used

Is the support for "virtual" broken in this toolchain too?

Thanks,
Avtar



  *[Cegcc-devel] cegcc/mingw32ce with gcc
4.6.3<http://sourceforge.net/mailarchive/message.php?msg_id=28977117>
*
From: Max Kellermann <max@du...> - 2012-03-13 22:13

Hi,

I have updated my cegcc fork to gcc 4.6.3, here's my release
2012-03-13:

 http://max.kellermann.name/projects/cegcc/
 http://max.kellermann.name/download/xcsoar/devel/cegcc/

Max

> > Hello all, it seems that cegcc is quite dead, or people who use it
> > are happy with it (just like me).
>
> Did you know that I published cegcc with gcc 4.6.3 and other updates?
>
> I started the 4.7 update, but ran into so many merge conflicts that I
> postponed it.


Yes, I saw that. I also tried to port changes at some point to newer gcc, but eventually I had problems with some dll's so I kept using older builds.


> > Now, with WinPhone8 it rejects the libs as invalid. Upcoming
> > VisualStudio and Windows 8 have ARM support out of the box. armasm
> > (which looks too similar to armasm that comes with arm's dev tools)
> > lists three types of machine targets: arm, thumb, armce. Any idea
> > what's different? Do they use different object format (quite
> > unlikely), or they simply added different CPU id for otherwise
> > identical objects?
>
> Reportedly, WinPhone8 is based on the Windows 8 (desktop) kernel, not
> on the WinCE kernel.  That may make a difference, even if only for the
> OS declaration.  Try objdump on WinPhone7 and 8 (native) binaries and
> look for differences.
>
> Since there is only official support for CIL code on WinPhone, there
> was no need for native code compatibility.


Yes, it seems that WinPhone8 sdk uses almost identical build of cl for arm as Windows8 (only a couple of revisions different and some CRT quirks as usual). I tried to see why exiting pure arm libs from WinCE aren't acceptable by tools from WinPhone8 and it seems that the issue is only in that Machine type header: now it needs to be IMAGE_FILE_MACHINE_ARMNT (for Thumb-2, value is 0x01c4, not sure if it's already published) instead of IMAGE_FILE_MACHINE_ARM or IMAGE_FILE_MACHINE_THUMB. Otherwise, it's pretty much the same. So, cegcc tools could be patched to use different value for machine type and possibly it could be accepted by tools from WP8.

Am 13.03.2012 23:13, schrieb Max Kellermann:
> Hi,
> 
> I have updated my cegcc fork to gcc 4.6.3, here's my release
> 2012-03-13:
> 
>  http://max.kellermann.name/projects/cegcc/
>  http://max.kellermann.name/download/xcsoar/devel/cegcc/

It would be great to generate a mingw-arm that can compile for WoA (Win8 on ARM) and maybe also for CE.
mostly you need to change the machine type and provide the libs and includes (partly already there for the x86 stuff).
WoA makes use of Thumb2, but there's no need to have compiler support for it.
I'd guess it's not that hard when you're familiar with the code.
We could make use of that in Wine for example.
E.g. crosscompiling Wine dlls missing in WoA to add additional functions, or simply crosscompile the testsuite.
I already was able to run WoA PEs (compiled with VS11beta) in Wine...
Thoughts?


-- 

Best Regards, André Hentschel

On Sun, May 6, 2012 at 7:54 AM, Max Kellermann <ma...@du...> wrote:
> On 2012/05/06 05:49, Pavel Pavlov <pa...@su...> wrote:
>> Hello all, it seems that cegcc is quite dead, or people who use it
>> are happy with it (just like me).
>
> Did you know that I published cegcc with gcc 4.6.3 and other updates?
>
> I started the 4.7 update, but ran into so many merge conflicts that I
> postponed it.
>
>> Now, with WinPhone8 it rejects the libs as invalid. Upcoming
>> VisualStudio and Windows 8 have ARM support out of the box. armasm
>> (which looks too similar to armasm that comes with arm's dev tools)
>> lists three types of machine targets: arm, thumb, armce. Any idea
>> what's different? Do they use different object format (quite
>> unlikely), or they simply added different CPU id for otherwise
>> identical objects?
>
> Reportedly, WinPhone8 is based on the Windows 8 (desktop) kernel, not
> on the WinCE kernel.  That may make a difference, even if only for the
> OS declaration.  Try objdump on WinPhone7 and 8 (native) binaries and
> look for differences.
>
> Since there is only official support for CIL code on WinPhone, there
> was no need for native code compatibility.

i don't know if i have already suggested this to you, but you should
try to contact mingw-w64 developpers to see if you can integrate your
work in mingw-w64

regards

Vincent Torri

On 2012/05/06 05:49, Pavel Pavlov <pa...@su...> wrote:
> Hello all, it seems that cegcc is quite dead, or people who use it
> are happy with it (just like me).

Did you know that I published cegcc with gcc 4.6.3 and other updates?

I started the 4.7 update, but ran into so many merge conflicts that I
postponed it.

> Now, with WinPhone8 it rejects the libs as invalid. Upcoming
> VisualStudio and Windows 8 have ARM support out of the box. armasm
> (which looks too similar to armasm that comes with arm's dev tools)
> lists three types of machine targets: arm, thumb, armce. Any idea
> what's different? Do they use different object format (quite
> unlikely), or they simply added different CPU id for otherwise
> identical objects?

Reportedly, WinPhone8 is based on the Windows 8 (desktop) kernel, not
on the WinCE kernel.  That may make a difference, even if only for the
OS declaration.  Try objdump on WinPhone7 and 8 (native) binaries and
look for differences.

Since there is only official support for CIL code on WinPhone, there
was no need for native code compatibility.

Max

Hello all, it seems that cegcc is quite dead, or people who use it are happy with it (just like me).

I'm building my code for WinPhone7 and everything worked out of the box. I mainly use cegcc for code with att-style asm, or I use gnu assembler. I compile static libs with it and link it with regular tools from MS.

Now, with WinPhone8 it rejects the libs as invalid. Upcoming VisualStudio and Windows 8 have ARM support out of the box. armasm (which looks too similar to armasm that comes with arm's dev tools) lists three types of machine targets: arm, thumb, armce. Any idea what's different? Do they use different object format (quite unlikely), or they simply added different CPU id for otherwise identical objects?

Since Windows 8 ads native arm support, perhaps gcc/mingw will add full support for windows/arm as well. Any info on that?

Hi,

I have updated my cegcc fork to gcc 4.6.3, here's my release
2012-03-13:

 http://max.kellermann.name/projects/cegcc/
 http://max.kellermann.name/download/xcsoar/devel/cegcc/

Max

just swap Rm and Rn:
mul Rd, Rn, Rm      ->     mul Rd, Rm, Rn

read arm reference for exaplanation



-----Original Message-----
From: James Tyou [mailto:jam...@gm...] 
Sent: Tuesday, February 28, 2012 13:43
To: ceg...@li...
Subject: [Cegcc-devel] Rd and Rm should be different in mul?

Hello There,

I compile some c source with
\bin>arm-mingw32ce-gcc --version
arm-mingw32ce-gcc (GCC) 4.5.3

and switchs:
-mcpu=arm1176jzf-s -Wa,-mcpu=arm1176jzf-s

but at last it shows some error:
ccvEiUjA.s:322: Rd and Rm should be different in mul

why?
is this a bug of mingw32ce?


regards,
jz

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Cegcc-devel mailing list
Ceg...@li...
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Hello There,

I compile some c source with
\bin>arm-mingw32ce-gcc --version
arm-mingw32ce-gcc (GCC) 4.5.3

and switchs:
-mcpu=arm1176jzf-s -Wa,-mcpu=arm1176jzf-s

but at last it shows some error:
ccvEiUjA.s:322: Rd and Rm should be different in mul

why?
is this a bug of mingw32ce?


regards,
jz

Hi All,

Can somebody comment on the support for pthreads in the latest CeGCC
project source files? Is it supported?

Regards,
Prageeth

Hi,

We are working with arm-cegcc toolchain, v0.55, on Ubuntu Linux. It looks
like the POSIX porting layer is missing mmap support. This is our
understanding:

(a) There is no mmap (and related in-memory management functions) support
either in v0.55 or v0.59.

(b) Searching this mailing list shows the following thread that has a patch
for mmap:
http://www.mail-archive.com/ceg...@li.../msg01459.html

Our questions:

1. Does the latest CeGCC project source files have mmap support?

2. If not, is anyone using the above patch in any of their live projects
now?

Thanks,
Prageeth

Am 03.01.2012 22:59, schrieb Max Kellermann:
> On 2011/12/29 01:17, Ismail Khatib<ik...@im...>  wrote:
>> got the following error; I've also tried to do a fresh checkout, but
>> got the same error:
> [..]
>> fatal: reference is not a tree: 2c5a5ea1a5f0eb9711d44033e754ef02a3962852
>> Unable to checkout '2c5a5ea1a5f0eb9711d44033e754ef02a3962852' in
>> submodule path 'gcc-4.4.0'
>>
>> Could you please check what the problem is?
> I added a new commit to the build repository, but forgot to push the
> gcc submodule repository as well.
>
> I've pushed the new gcc commit and I added the release tag
> "2011-12-23" to the build repository.  Hope this works now.
>
> Max
Thank you! Everything works perfectly now, a fresh clone as well as a 
pull of the source.

Ismail

On 2011/12/29 01:17, Ismail Khatib <ik...@im...> wrote:
> got the following error; I've also tried to do a fresh checkout, but
> got the same error:
[..]
> fatal: reference is not a tree: 2c5a5ea1a5f0eb9711d44033e754ef02a3962852
> Unable to checkout '2c5a5ea1a5f0eb9711d44033e754ef02a3962852' in
> submodule path 'gcc-4.4.0'
> 
> Could you please check what the problem is?

I added a new commit to the build repository, but forgot to push the
gcc submodule repository as well.

I've pushed the new gcc commit and I added the release tag
"2011-12-23" to the build repository.  Hope this works now.

Max

Am 23.12.2011 15:13, schrieb Max Kellermann:
> Hi,
>
> the build 2011-12-23 of my cegcc fork comes with gcc 4.6.2 and
> binutils 2.22.  For the first time, gcc's link time optimization (LTO)
> works on Windows CE!
>
>   http://max.kellermann.name/projects/cegcc/
>   http://max.kellermann.name/download/xcsoar/devel/cegcc/
>
> Max
Great news!
I've just tried these binaries with the current ScummVM sources from 
master and it seems to work fine for me.
However, I've tried to update my (previously cloned) cegcc repository 
(cloned from your git server), but I
got the following error; I've also tried to do a fresh checkout, but got 
the same error:

Cloning into gcc-4.4.0...
remote: Counting objects: 20902, done.
remote: Compressing objects: 100% (10676/10676), done.
remote: Total 20902 (delta 12011), reused 18261 (delta 9381)
Receiving objects: 100% (20902/20902), 65.60 MiB | 1.80 MiB/s, done.
Resolving deltas: 100% (12011/12011), done.
fatal: reference is not a tree: 2c5a5ea1a5f0eb9711d44033e754ef02a3962852
Unable to checkout '2c5a5ea1a5f0eb9711d44033e754ef02a3962852' in 
submodule path 'gcc-4.4.0'

Could you please check what the problem is?
Thanks in advance!

Ismail

Le 23.12.2011 15:13, Max Kellermann a écrit :
> Hi,
>
> the build 2011-12-23 of my cegcc fork comes with gcc 4.6.2 and
> binutils 2.22.  For the first time, gcc's link time optimization 
> (LTO)
> works on Windows CE!
>
>  http://max.kellermann.name/projects/cegcc/
>  http://max.kellermann.name/download/xcsoar/devel/cegcc/
>
> Max
>

Congratulations!
Don't know if windows ce will still be alive in a few months/year but 
that's a
good performance. Now you just need to backport SEH exception from 
mingw-w64 and you will get a
perfect open source compiler ;-)

Hi,

the build 2011-12-23 of my cegcc fork comes with gcc 4.6.2 and
binutils 2.22.  For the first time, gcc's link time optimization (LTO)
works on Windows CE!

 http://max.kellermann.name/projects/cegcc/
 http://max.kellermann.name/download/xcsoar/devel/cegcc/

Max

I tried as follows:

fpin=fopen("//Software//myfile.avs","rb+");  
fpin=fopen("/Software/myfile.avs","rb+");
fpin=fopen("\\Software\\myfile.avs","rb+");
("myfile.avs" is put under "Software" directory)

fpin still returns NULL!

2011-12-01 



hdzhang264 



发件人： Andy Wu 
发送时间： 2011-12-01  21:08:07 
收件人： hdzhang264 
抄送： Vincent Torri; cegcc-devel 
主题： Re: [Cegcc-devel] fopen() failed? 
 
You should use absolute path on ce.
On 2011-12-1 下午9:06, "hdzhang264" <hdz...@12...> wrote:

I am using mingw32ce on Linux.

the code follows:

FILE *fpin;
fpin=fopen("myfile.avs","rb+");  

In makefile, i used arm-mingw32ce-gcc, make is ok.

But when it runs on wince5.0,  the fpin returns NULL always. 

"myfile.avs" and excutable file lies in the same directory.


2011-12-01 



hdzhang264 



发件人： Vincent Torri 
发送时间： 2011-11-30  20:10:43 
收件人： hdzhang264 
抄送： cegcc-devel 
主题： Re: [Cegcc-devel] where are the target files? 



2011/11/30 hdzhang264 <hdz...@12...>



I installed from a binary distribution "cegcc_mingw32ce_cygwin1.7_r1375.tar.bz2 ".
I am using arm-wince-mingw32ce tools. 
I am using Linux platform  to develop. 

What is strange to me is that you use a "cygwin" toolchain to cross-compile on a linux platform.

Vincent Torri

 
What is the nature of your problem ?  --------can not found the target file (.o file). 
Can you send us a small source that demonstrates the problem ? 
        When compile my project, none of error occurs. But after compile, none of the target file is found under the project folder.  (If I use arm-linux-gcc/arm-linux-as，the target file is right.)
:
the output shows no one error or warning. 
just like "arm-mingw32ce-gcc.exe -o *.c -o *.o","arm-mingw32ce-as.exe -o *.o *.s".
I found it did not compile the file ever, because it did not point any error even i put some obvious wrong code in my files.
2011-11-29 



hdzhang264 

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Cegcc-devel mailing list
Ceg...@li...
https://lists.sourceforge.net/lists/listinfo/cegcc-devel





------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Cegcc-devel mailing list
Ceg...@li...
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

You should use absolute path on ce.
On 2011-12-1 下午9:06, "hdzhang264" <hdz...@12...> wrote:

> **
> I am using mingw32ce on Linux.
>
> the code follows:
>
> FILE *fpin;
> fpin=fopen("myfile.avs","rb+");
>
> In makefile, i used arm-mingw32ce-gcc, make is ok.
>
> But when it runs on wince5.0,  the fpin returns NULL always.
>
> "myfile.avs" and excutable file lies in the same directory.
>
>
> 2011-12-01
> ------------------------------
>  hdzhang264
> ------------------------------
> *发件人：* Vincent Torri
> *发送时间：* 2011-11-30  20:10:43
> *收件人：* hdzhang264
> *抄送：* cegcc-devel
> *主题：* Re: [Cegcc-devel] where are the target files?
>
>
> 2011/11/30 hdzhang264 <hdz...@12...>
>
>> **
>>
>>
>> I installed from a binary distribution
>> "cegcc_mingw32ce_cygwin1.7_r1375.tar.bz2 ".
>>
>>  I am using *arm-wince-mingw32ce* tools.
>>
>>  I am using Linux platform  to develop.
>>
>
> What is strange to me is that you use a "cygwin" toolchain to
> cross-compile on a linux platform.
>
> Vincent Torri
>
>
>
>>   What is the nature of your problem ?  --------can not found the target
>> file (.o file).
>>
>> Can you send us a small source that demonstrates the problem ?
>>
>>         When compile my project, none of error occurs. But after compile,
>> none of the target file is found under the project folder.  (If I use
>> arm-linux-gcc/arm-linux-as，the target file is right.)
>>
>> :
>>
>> the output shows no one error or warning.
>>
>> just like "arm-mingw32ce-gcc.exe -o *.c -o *.o","arm-mingw32ce-as.exe -o
>> *.o *.s".
>>
>> I found it did not compile the file ever, because it did not point any
>> error even i put some obvious wrong code in my files.
>> 2011-11-29
>> ------------------------------
>> hdzhang264
>>
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> _______________________________________________
>> Cegcc-devel mailing list
>> Ceg...@li...
>> https://lists.sourceforge.net/lists/listinfo/cegcc-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Cegcc-devel mailing list
> Ceg...@li...
> https://lists.sourceforge.net/lists/listinfo/cegcc-devel
>
>

I am using mingw32ce on Linux.

the code follows:

FILE *fpin;
fpin=fopen("myfile.avs","rb+");  

In makefile, i used arm-mingw32ce-gcc, make is ok.

But when it runs on wince5.0,  the fpin returns NULL always. 

"myfile.avs" and excutable file lies in the same directory.


2011-12-01 



hdzhang264 



发件人： Vincent Torri 
发送时间： 2011-11-30  20:10:43 
收件人： hdzhang264 
抄送： cegcc-devel 
主题： Re: [Cegcc-devel] where are the target files? 



2011/11/30 hdzhang264 <hdz...@12...>



I installed from a binary distribution "cegcc_mingw32ce_cygwin1.7_r1375.tar.bz2 ".
I am using arm-wince-mingw32ce tools. 
I am using Linux platform  to develop. 

What is strange to me is that you use a "cygwin" toolchain to cross-compile on a linux platform.

Vincent Torri

 
What is the nature of your problem ?  --------can not found the target file (.o file). 
Can you send us a small source that demonstrates the problem ? 
        When compile my project, none of error occurs. But after compile, none of the target file is found under the project folder.  (If I use arm-linux-gcc/arm-linux-as，the target file is right.)
:
the output shows no one error or warning. 
just like "arm-mingw32ce-gcc.exe -o *.c -o *.o","arm-mingw32ce-as.exe -o *.o *.s".
I found it did not compile the file ever, because it did not point any error even i put some obvious wrong code in my files.
2011-11-29 



hdzhang264 

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Cegcc-devel mailing list
Ceg...@li...
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

I`m so sorry , i have installed the correct version.

and now , I have two enviroment: mingw32ce-cygwin on cygwin , and mingw32ce on Linux.

But under cygwin enviroment, any target file can not found.
under linux enviroment, I found a error: "PLD" instruction can not be supported!

so I have to add the following codes according some people said:
#ifndef HAVE_PLD
.macro pld reg
.endm
#endif

after this,
still errors about 'pld':
"too many posiontoinal arguments"

the code : "pld [r1,#124]"



2011-12-01 



hdzhang264 



发件人： Vincent Torri 
发送时间： 2011-11-30  20:10:43 
收件人： hdzhang264 
抄送： cegcc-devel 
主题： Re: [Cegcc-devel] where are the target files? 
 



2011/11/30 hdzhang264 <hdz...@12...>



I installed from a binary distribution "cegcc_mingw32ce_cygwin1.7_r1375.tar.bz2 ".
I am using arm-wince-mingw32ce tools. 
I am using Linux platform  to develop. 

What is strange to me is that you use a "cygwin" toolchain to cross-compile on a linux platform.

Vincent Torri

 
What is the nature of your problem ?  --------can not found the target file (.o file). 
Can you send us a small source that demonstrates the problem ? 
        When compile my project, none of error occurs. But after compile, none of the target file is found under the project folder.  (If I use arm-linux-gcc/arm-linux-as，the target file is right.)
:
the output shows no one error or warning. 
just like "arm-mingw32ce-gcc.exe -o *.c -o *.o","arm-mingw32ce-as.exe -o *.o *.s".
I found it did not compile the file ever, because it did not point any error even i put some obvious wrong code in my files.
2011-11-29 



hdzhang264 

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Cegcc-devel mailing list
Ceg...@li...
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

I am using mingw32ce under linux.

I encoutered " error:selected processor does not support 'pld[r1]". 

Pld is supported only on arm5 or higher.

Doed  Cegcc only support arm4? 
2011-11-29 



hdzhang264 cc/

2011/11/30 hdzhang264 <hdz...@12...>

> **
>
>
> I installed from a binary distribution
> "cegcc_mingw32ce_cygwin1.7_r1375.tar.bz2 ".
>
> I am using *arm-wince-mingw32ce* tools.
>
> I am using Linux platform  to develop.
>

What is strange to me is that you use a "cygwin" toolchain to cross-compile
on a linux platform.

Vincent Torri



> What is the nature of your problem ?  --------can not found the target
> file (.o file).
>
> Can you send us a small source that demonstrates the problem ?
>
>         When compile my project, none of error occurs. But after compile,
> none of the target file is found under the project folder.  (If I use
> arm-linux-gcc/arm-linux-as，the target file is right.)
>
> :
>
> the output shows no one error or warning.
>
> just like "arm-mingw32ce-gcc.exe -o *.c -o *.o","arm-mingw32ce-as.exe -o
> *.o *.s".
>
> I found it did not compile the file ever, because it did not point any
> error even i put some obvious wrong code in my files.
> 2011-11-29
> ------------------------------
> hdzhang264
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Cegcc-devel mailing list
> Ceg...@li...
> https://lists.sourceforge.net/lists/listinfo/cegcc-devel
>
>

I installed from a binary distribution "cegcc_mingw32ce_cygwin1.7_r1375.tar.bz2 ".
I am using arm-wince-mingw32ce tools. 
I am using Linux platform  to develop. 
What is the nature of your problem ?  --------can not found the target file (.o file). 
Can you send us a small source that demonstrates the problem ? 
        When compile my project, none of error occurs. But after compile, none of the target file is found under the project folder.  (If I use arm-linux-gcc/arm-linux-as，the target file is right.)
2011-11-29 



hdzhang264