Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2006-11

WinCE compiler compilation is broken

17 messages · 9 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Gabor Boros

Hi,

The error message is:
math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you use the correct run time library.

Gabor

Reply by email

Yury Sidorov
to Gabor Boros: The error message is: math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you…

From: "Gabor Boros"
Subject: [fpc-devel] WinCE compiler compilation is broken

Show quoted text 5 lines
Hi, The error message is: math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you use the correct run time library.

The problem is caused by revision 5192 by Peter.
It also adds strange notes like this:
convutil.inc(372,5) Note: Local variable "$hiddenTHEUNITS" not used

Yury Sidorov.

Reply by email

Peter Vreman
to Yury Sidorov
you wrote 10 lines
From: "Gabor Boros" Subject: [fpc-devel] WinCE compiler compilation is broken >Hi, >The error message is: >math.pp(2063,14) Fatal: Unknown compilerproc "SUBS". Check if you >use the correct run time library. The problem is caused by revision 5192 by Peter. It also adds strange notes like this: convutil.inc(372,5) Note: Local variable "$hiddenTHEUNITS" not used

This is a known issue and will be solved in time. Don't forget that Trunk is the development branch and can be broken/unstable from time to time.

Peter

Reply by email

Yury Sidorov
to Peter Vreman

From: "Peter Vreman"

Show quoted text 6 lines
>The problem is caused by revision 5192 by Peter. >It also adds strange notes like this: >convutil.inc(372,5) Note: Local variable "$hiddenTHEUNITS" not used This is a known issue and will be solved in time. Don't forget that Trunk is the development branch and can be broken/unstable from time to time.

Sure. It just for info :)

Yury.

Reply by email

Christian Ulrich
to Yury Sidorov

Are there new options or something else ?
when i try to compiler the compiler or rtl or fcl with TARGET_OS and TARGET_CPU
it generates always code for i386-win32 in actual svn

best regards
Christian

Reply by email

Michael Van Canneyt
to Christian Ulrich: Are there new options or something else ? when i try to compiler the compiler or rtl or…
Christian Ulrich wrote
Are there new options or something else ? when i try to compiler the compiler or rtl or fcl with TARGET_OS and TARGET_CPU it generates always code for i386-win32 in actual svn

How do you specify these options ? They're only meaningful in the Makefile. The compiler itself does not use these variables AFAIK.

Michael.

Reply by email

Michael Van Canneyt
to Christian Ulrich: make cycle CPU_TARGET=x86_64 OS_TARGET=win64 make cycle CPU_TARGET=arm OS_TARGET=wince…
Christian Ulrich wrote 18 lines
Michael Van Canneyt schrieb: > On Mon, 6 Nov 2006, Christian Ulrich wrote: > > > > Are there new options or something else ? > > when i try to compiler the compiler or rtl or fcl with TARGET_OS and > > TARGET_CPU > > it generates always code for i386-win32 in actual svn > > > > How do you specify these options ? They're only meaningful in the Makefile. > The compiler itself does not use these variables AFAIK. > > make cycle CPU_TARGET=x86_64 OS_TARGET=win64 make cycle CPU_TARGET=arm OS_TARGET=wince both builds i386-win32 for me.

You can't cycle a cross-compiler.

Simply try
make CPU_TARGET=x86_64 OS_TARGET=win64
make CPU_TARGET=arm OS_TARGET=wince

Michael.

Reply by email

Marco van de Voort
to Michael Van Canneyt
Show quoted text 7 lines
On Mon, 6 Nov 2006, Christian Ulrich wrote: You can't cycle a cross-compiler. Simply try make CPU_TARGET=x86_64 OS_TARGET=win64 make CPU_TARGET=arm OS_TARGET=wince

D:\repo\fpcex\compiler>make CPU_TARGET=x86_64 OS_TARGET=win64 d:/pp11/bin/i386-win32/ppc386.exe -Twin64 -Px86_64 -XPx86_64-win64- -Xc -Xr -Fux
86_64 -Fusystems -Fu../rtl -Fix86_64 -FE. -FUx86_64/units/x86_64-win64 '-Xi' -d
x86_64 -dGDB -dBROWSERLOG -Fux86 pp.pas
Error: Illegal parameter: -Twin64
Max Memory used/heapsize: 14/768 Kb

Reply by email

Florian Klaempfl
to Marco van de Voort
Show quoted text 16 lines
> On Mon, 6 Nov 2006, Christian Ulrich wrote: > > You can't cycle a cross-compiler. > > Simply try > make CPU_TARGET=x86_64 OS_TARGET=win64 > make CPU_TARGET=arm OS_TARGET=wince D:\repo\fpcex\compiler>make CPU_TARGET=x86_64 OS_TARGET=win64 d:/pp11/bin/i386-win32/ppc386.exe -Twin64 -Px86_64 -XPx86_64-win64- -Xc -Xr -Fux 86_64 -Fusystems -Fu../rtl -Fix86_64 -FE. -FUx86_64/units/x86_64-win64 '-Xi' -d x86_64 -dGDB -dBROWSERLOG -Fux86 pp.pas Error: Illegal parameter: -Twin64 Max Memory used/heapsize: 14/768 Kb

The correct way to build a cross environment is
cd fpc/
make clean all CPU_TARGET=arm OS_TARGET=wince

_______________________________________________ fpc-devel maillist - http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply by email

Christian Ulrich
to Michael Van Canneyt: How do you specify these options ? They're only meaningful in the Makefile. The compiler…
Show quoted text 13 lines
On Mon, 6 Nov 2006, Christian Ulrich wrote: > Are there new options or something else ? > when i try to compiler the compiler or rtl or fcl with TARGET_OS and > TARGET_CPU > it generates always code for i386-win32 in actual svn > How do you specify these options ? They're only meaningful in the Makefile. The compiler itself does not use these variables AFAIK.

make cycle CPU_TARGET=x86_64 OS_TARGET=win64
make cycle CPU_TARGET=arm OS_TARGET=wince

both builds i386-win32 for me.

Reply by email

Marco van de Voort
to Florian Klaempfl: The correct way to build a cross environment is cd fpc/ make clean all CPU_TARGET=arm…
Show quoted text 9 lines
Marco van de Voort schrieb: > x86_64 -dGDB -dBROWSERLOG -Fux86 pp.pas > Error: Illegal parameter: -Twin64 > Max Memory used/heapsize: 14/768 Kb The correct way to build a cross environment is cd fpc/ make clean all CPU_TARGET=arm OS_TARGET=wince

I know (chapter 3, paragraph 3.1 of the buildfaq), but I did this to check the line Michael provided.

I think the problem is that the line Michael that provided only works if the starting compiler supports the target OS too. (e.g. freebsd-x86 -> linux-x86_64). In that case a shortcut is possible.

Reply by email

Felipe Monteiro de Carvalho
to Michael Van Canneyt: You can't cycle a cross-compiler. Simply try make CPU_TARGET=x86_64 OS_TARGET=win64 make…
Michael Van Canneyt wrote
You can't cycle a cross-compiler.

Of course you can. That's the default instruction to compile arm crosscompiler on the Wiki:

http://www.freepascal.org/wiki/index.php/WinCE_port

And I used those instructions a lot, and always worked. I didn't try recent revisions however.

Felipe Monteiro de Carvalho

Reply by email

Christian Ulrich
to Michael Van Canneyt: You can't cycle a cross-compiler. Simply try make CPU_TARGET=x86_64 OS_TARGET=win64 make…
Show quoted text 6 lines
You can't cycle a cross-compiler. Simply try make CPU_TARGET=x86_64 OS_TARGET=win64 make CPU_TARGET=arm OS_TARGET=wince

for sure ? last week that is working great for arm-wince by the way have trioed also make all TARGET_CPU=arm TARGET_OS=wince result: an i386-win32 compiler

Show quoted text 6 lines
Michael. _______________________________________________ fpc-devel maillist - http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply by email