Sign in Join

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

Mailing lists / fpc-devel / 2013-11

FPC 2.6 fixes error building arm wince

11 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

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

Dimitrios Chr. Ioannidis

Hi all,

i needed to build a wince arm cross compiler in windows 7 and when i tried i've got this error :

"C:/Users/dimitris/Programming/Tools/fpc/2.6.x/bin/i386-win32/gmkdir.exe -p units
/arm-wince
../bin2obj.exe -o css.inc -c DefaultCSS fpdoc.css
process_begin:
CreateProcess(C:\Users\dimitris\Programming\Tools\fpc\2.6.x\sourc e\utils\bin2obj.exe, ../bin2obj.exe -o css.inc -c DefaultCSS fpdoc.css, ...) fai
led.
make (e=193): Error 193make[3]: *** [css.inc] Error 193"

I use fpc 2.6.3 fixes rev. 25932 and the command line is the following :

"C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source>make all install INSTALL_PR
EFIX=C:\Users\dimitris\Programming\Tools\fpc\2.6.x OS_TARGET=wince CPU_TARGET=ar
m CROSSOPT="-g -gl" "

I didn't had this kind of error before. Can someone give me a hint on how to procede ?

regards,

Dimitrios Chr. Ioannidis

Reply by email

Jonas Maebe
to Dimitrios Chr. Ioannidis
Dimitrios Chr. Ioannidis wrote 17 lines
i needed to build a wince arm cross compiler in windows 7 and when i tried i've got this error : "C:/Users/dimitris/Programming/Tools/fpc/2.6.x/bin/i386-win32/gmkdir.exe -p units /arm-wince ../bin2obj.exe -o css.inc -c DefaultCSS fpdoc.css process_begin: CreateProcess(C:\Users\dimitris\Programming\Tools\fpc\2.6.x\sourc e\utils\bin2obj.exe, ../bin2obj.exe -o css.inc -c DefaultCSS fpdoc.css, ...) fai led. make (e=193): Error 193make[3]: *** [css.inc] Error 193" I use fpc 2.6.3 fixes rev. 25932 and the command line is the following : "C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source>make all install INSTALL_PR EFIX=C:\Users\dimitris\Programming\Tools\fpc\2.6.x OS_TARGET=wince CPU_TARGET=ar m CROSSOPT="-g -gl" " I didn't had this kind of error before. Can someone give me a hint on how to procede ?

Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it?

Jonas

Reply by email

Dimitrios Chr. Ioannidis
to Jonas Maebe

Hi Jonas,

Στις 5/11/2013 4:37 μμ, ο/η Jonas Maebe έγραψε:

Show quoted text 20 lines
On 05 Nov 2013, at 12:37, Dimitrios Chr. Ioannidis wrote: > i needed to build a wince arm cross compiler in windows 7 and when i tried i've got this error : > > "C:/Users/dimitris/Programming/Tools/fpc/2.6.x/bin/i386-win32/gmkdir.exe -p units > /arm-wince > ../bin2obj.exe -o css.inc -c DefaultCSS fpdoc.css > process_begin: CreateProcess(C:\Users\dimitris\Programming\Tools\fpc\2.6.x\sourc > e\utils\bin2obj.exe, ../bin2obj.exe -o css.inc -c DefaultCSS fpdoc.css, ...) fai > led. > make (e=193): Error 193make[3]: *** [css.inc] Error 193" > > I use fpc 2.6.3 fixes rev. 25932 and the command line is the following : > > "C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source>make all install INSTALL_PR > EFIX=C:\Users\dimitris\Programming\Tools\fpc\2.6.x OS_TARGET=wince CPU_TARGET=ar > m CROSSOPT="-g -gl" " > > I didn't had this kind of error before. Can someone give me a hint on how to procede ? Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it?

Yes it exists but doesn't regognized by the win 7 64 as an executable.

regards,

Dimitrios Chr. Ioannidis

Reply by email

Jonas Maebe
to Dimitrios Chr. Ioannidis
Dimitrios Chr. Ioannidis wrote
Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it? Yes it exists but doesn't regognized by the win 7 64 as an executable.

It's probably an ARM/wince binary. You can probably work around the problem by first performing a native build in the checkout directory (so that the css.inc file is newer than fpdoc.css). Alternatively, you can simply "touch" utils/fpdoc/css.inc (I don't know whether we ship the "touch" utility with FPC; if not, any way that makes the "modified data" of css.inc newer than that of fpdoc.css is fine). This kind of problem can occur depending on the order in which svn checks out files and on the speed at which this happens.

Jonas

Reply by email

Marco van de Voort
to Jonas Maebe

In our previous episode, Jonas Maebe said:

Show quoted text 7 lines
> Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it? > > Yes it exists but doesn't regognized by the win 7 64 as an executable. It's probably an ARM/wince binary. You can probably work around the problem by first performing a native build in the checkout directory (so

No, this is generally broken since r22079

------------------------------------------------------------------------ r22079 | michael | 2012-08-14 20:47:57 +0200 (Tue, 14 Aug 2012) | 1 line Changed paths:
M /trunk/utils/fpdoc/Makefile
M /trunk/utils/fpdoc/Makefile.fpc
A /trunk/utils/fpdoc/css.inc
M /trunk/utils/fpdoc/dw_html.pp

* Added functionality to create fpdoc.css from internal copy

when a dependence on a just built binobj was introduced (rather than using a global installed data2inc as for similar cases before that).

Reply by email

Michael Van Canneyt
to Marco van de Voort
Marco van de Voort wrote 23 lines
In our previous episode, Jonas Maebe said: > >> Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it? >> >> Yes it exists but doesn't regognized by the win 7 64 as an executable. > > It's probably an ARM/wince binary. You can probably work around the > problem by first performing a native build in the checkout directory (so No, this is generally broken since r22079 ------------------------------------------------------------------------ r22079 | michael | 2012-08-14 20:47:57 +0200 (Tue, 14 Aug 2012) | 1 line Changed paths: M /trunk/utils/fpdoc/Makefile M /trunk/utils/fpdoc/Makefile.fpc A /trunk/utils/fpdoc/css.inc M /trunk/utils/fpdoc/dw_html.pp * Added functionality to create fpdoc.css from internal copy when a dependence on a just built binobj was introduced (rather than using a global installed data2inc as for similar cases before that).

Hmmm.
To my knowledge binobj is older than data2inc.
I've been using it since version 0.x of FPC.
So why is it not installed ?

Michael.

Reply by email

Jonas Maebe
to Michael Van Canneyt
Michael Van Canneyt wrote 12 lines
On Tue, 5 Nov 2013, Marco van de Voort wrote: > In our previous episode, Jonas Maebe said: >> >>> Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it? >>> >>> Yes it exists but doesn't regognized by the win 7 64 as an executable. >> >> It's probably an ARM/wince binary. You can probably work around the >> problem by first performing a native build in the checkout directory (so > > No, this is generally broken since r22079

The fact that it's broken since that release is not in contradiction with what I said. You can work around the problem introduced in that revision by first performing a native build, because bin2obj is only called if the css.inc file is out-of-date.

Show quoted text 5 lines
> when a dependence on a just built binobj was introduced (rather than using a > global installed data2inc as for similar cases before that). Hmmm. To my knowledge binobj is older than data2inc. I've been using it since version 0.x of FPC. So why is it not installed ?

The problem is not that it's not installed. It's that you try to use the just-compiled version of that binary (by explicitly calling ../bin2obj), which may have been cross-compiled and hence non-functional on the current build system, rather than the globally installed one.

Jonas

Reply by email

Marco van de Voort
to Jonas Maebe

In our previous episode, Jonas Maebe said:

Show quoted text 15 lines
>> In our previous episode, Jonas Maebe said: >>> >>>> Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it? >>>> >>>> Yes it exists but doesn't regognized by the win 7 64 as an executable. >>> >>> It's probably an ARM/wince binary. You can probably work around the >>> problem by first performing a native build in the checkout directory (so >> >> No, this is generally broken since r22079 The fact that it's broken since that release is not in contradiction with what I said. You can work around the problem introduced in that revision by first performing a native build, because bin2obj is only called if the css.inc file is out-of-date.

I meant to say it wasn't always like this, iow to stress that that is workaround.

The prerequisites for crosscompiling used to be an installed release (new archs excluded). Not a native build first.

Reply by email

Michael Van Canneyt
to Jonas Maebe: The fact that it's broken since that release is not in contradiction with what I said.…
Jonas Maebe wrote 25 lines
On 05 Nov 2013, at 18:04, Michael Van Canneyt wrote: > On Tue, 5 Nov 2013, Marco van de Voort wrote: > >> In our previous episode, Jonas Maebe said: >>> >>>> Does C:\Users\dimitris\Programming\Tools\fpc\2.6.x\source\utils\bin2obj.exe exist and is it executable? What happens if you try to execute it? >>>> >>>> Yes it exists but doesn't regognized by the win 7 64 as an executable. >>> >>> It's probably an ARM/wince binary. You can probably work around the >>> problem by first performing a native build in the checkout directory (so >> >> No, this is generally broken since r22079 The fact that it's broken since that release is not in contradiction with what I said. You can work around the problem introduced in that revision by first performing a native build, because bin2obj is only called if the css.inc file is out-of-date. >> when a dependence on a just built binobj was introduced (rather than using a >> global installed data2inc as for similar cases before that). > > Hmmm. To my knowledge binobj is older than data2inc. I've been using it since version 0.x of FPC. > So why is it not installed ? The problem is not that it's not installed. It's that you try to use the just-compiled version of that binary (by explicitly calling ../bin2obj), which may have been cross-compiled and hence non-functional on the current build system, rather than the globally installed one.

A valid point, easily fixable.

Michael.

Reply by email

Marco van de Voort
to Michael Van Canneyt: Hmmm. To my knowledge binobj is older than data2inc. I've been using it since version 0.x…

In our previous episode, Michael Van Canneyt said:

Show quoted text 5 lines
> when a dependence on a just built binobj was introduced (rather than using a > global installed data2inc as for similar cases before that). Hmmm. To my knowledge binobj is older than data2inc.

You would need pre 1.0 CVS to check that I guess. But afaik data2inc was older, and bin2obj was only sb wasn't aware that data2inc had an option for it.

But the point is before that release building had no dependency on bin2obj, and suddenly it had that, and worse a just-built relation that "broke" crosscompiling. (or at least required an extra step, I never considered it that way till Jonas mentioned it).

Utils/ and compiler/utils have used data2inc quite some time (at least since fpcmake, maybe even earlier)

P.s. I've no problem whatsoever with data2inc being phased out. Though I prefer both being phased out and having a minimal option for it in the compiler :-)

Reply by email