Sign in Join

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

Mailing lists / fpc-devel / 2012-04

Compilation error

4 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

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

Vincent Snijders

Hi,

When I compile fpc trunk for arm-wince on win32 I get this error: [ 93%] Skipped package uuid which has been disabled for target arm-wince Start compiling package winceunits for target arm-wince. Warning: Source file "activex.pp" from package winceunits not found for arm-wince
Compiling ..\winunits-base\src\comobj.pp
The installer encountered the following error:
External command
"c:/lazarus/source/fpcbuild/trunk/fpcsrc/compiler/ppcrossarm.exe -Twince -FUunits\arm-wince
-FuC:\lazarus\source\fpcbuild\trunk\fpcsrc\rtl\units\arm-wince -Twince -Parm -XParm-wince- -Xr -Ur -Xs -O2 -n
-FuC:/lazarus/source/fpcbuild/trunk/fpcsrc/rtl/units/arm-wince -FDc:\lazarus\source\binutils\arm-wince -darm -dRELEASE -Ur -viq ..\winunits-base\src\comobj.pp" failed with exit code 1. Console output:
Target OS: WinCE for ARM
Compiling ..\winunits-base\src\comobj.pp
Fatal: Can't open file "comobj.pp"
Fatal: Compilation aborted

I don't why this happens. How can I fix this?

Vincent

Reply by email

Marco van de Voort
to Vincent Snijders

In our previous episode, Vincent Snijders said:

Show quoted text 9 lines
-FDc:\lazarus\source\binutils\arm-wince -darm -dRELEASE -Ur -viq ..\winunits-base\src\comobj.pp" failed with exit code 1. Console output: Target OS: WinCE for ARM Compiling ..\winunits-base\src\comobj.pp Fatal: Can't open file "comobj.pp" Fatal: Compilation aborted I don't why this happens. How can I fix this?

I don't know this error, but I just saw your bugreport, so there are multiple people on multiple targets having the problem.

I saw that Pierre regenerated all makefiles yesterday evening. (r20723), maybe that was done with an outdated tool or so.

Reply by email

Jonas Maebe
to Marco van de Voort
Marco van de Voort wrote
I saw that Pierre regenerated all makefiles yesterday evening. (r20723), maybe that was done with an outdated tool or so.

No, since he did it to add support for new platforms so he had to use the most recent fpcmake (and if you look at the Makefile diffs, you can see the only changes are extra x86_64-openbsd things). Joost also made changes to fpmake yesterday, I guess those are the problem. I also got really strange errors in the testsuite builds from last night:

darwin/ppc:

[ 8%] Compiled package paszlib
Start compiling package univint for target powerpc-darwin. Warning: Source file "AUComponent.ppu" from package univint not found for powerpc-darwin Compiling src/MacOSAll.pas
The installer encountered the following error:
External command "/Users/fpc/snapshot/fpc-2.3/compiler/ppcppc -Tdarwin -FUunits/powerpc-darwin -Fu/Users/fpc/snapshot/fpc-2.3/rtl/units/powerpc-darwin -Ur -Xs -O2 -n -Fu/Users/fpc/snapshot/fpc-2.3/rtl/units/powerpc-darwin -ap -dpowerpc -dRELEASE -Mmacpas -viq src/MacOSAll.pas" failed with exit code 1. Console output: Target OS: Darwin for PowerPC
Compiling src/MacOSAll.pas
Fatal: Can't open file "MacOSAll.pas"
Fatal: Compilation aborted

darwin/ppc64:

[ 47%] Compiled package numlib
The installer encountered the following error:
External command "/Users/fpc/snapshot/fpc-2.3/compiler/ppcppc64 -Tdarwin -FUunits/powerpc64-darwin -Fu/Users/fpc/snapshot/fpc-2.3/rtl/units/powerpc64-darwin -Fusrc -Ur -Xs -O2 -n -Fu/Users/fpc/snapshot/fpc-2.3/rtl/units/powerpc64-darwin -ap -dpowerpc64 -dRELEASE -viq BuildUnit_opengles.pp" failed with exit code 1. Console output: Target OS: Darwin for PowerPC64
Compiling BuildUnit_opengles.pp
BuildUnit_opengles.pp(4,1) Fatal: Can't find unit gles11 used by BuildUnit_opengles Fatal: Compilation aborted

(that package shouldn't even be compiled for darwin, but that's unrelated to the build error)

It looks like fpmake is changing the pwd before the compilation has started or so.

Jonas

Reply by email

Vincent Snijders
to Jonas Maebe

Op 7 april 2012 12:38 heeft Jonas Maebe
het volgende geschreven:

Show quoted text 10 lines
On 07 Apr 2012, at 12:19, Marco van de Voort wrote: > I saw that Pierre regenerated all makefiles yesterday evening. (r20723), > maybe that was done with an outdated tool or so. No, since he did it to add support for new platforms so he had to use the most recent fpcmake (and if you look at the Makefile diffs, you can see the only changes are extra x86_64-openbsd things). Joost also made changes to fpmake yesterday, I guess those are the problem. I also got really strange errors in the testsuite builds from last night: (that package shouldn't even be compiled for darwin, but that's unrelated to the build error) It looks like fpmake is changing the pwd before the compilation has started or so.

As noted in http://bugs.freepascal.org/view.php?id=21672, it is cause by r20724. I assigned the issue to Josst.

Vincent

Reply by email