View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0021948FPCCompilerpublic2012-05-05 22:002012-05-27 01:33
ReporterDavidB 
Assigned ToJonas Maebe 
PrioritynormalSeverityblockReproducibilityalways
StatusresolvedResolutionsuspended 
PlatformWindowsOSVista SP2OS Version64 Bits
Product Version2.7.1Product Build21239 
Target VersionFixed in Version 
Summary0021948: Compilation fails on Vista 64 bits
DescriptionHi,

Just updated FCP SVN today after a couple of weeks.

When I try to compile using 2.6.0. I got this error and coompiles stop:

make[7]: *** No rule to make target `iso7185.ppu', needed by `fpc_units'. Stop.
Steps To ReproduceTry to compile FPC SVN Trunk with 2.6.0

I use this bat file inside my C:\fpcsvn folder:

@echo on

set FPC_UTILS=C:\\fpc\\2.6.0
set FPC_BUILD=C:\\fpcsvn
set INSTALL_PREFIX=C:\\fpc\\2.7.1
set DATA2INC=%INSTALL_PREFIX%/bin/x86_64-win64/data2inc.exe

set PATH=%INSTALL_PREFIX%\bin\x86_64-win64;%FPC_UTILS%\bin\x86_64-win64;%PATH%
pause

cd %INSTALL_PREFIX%
rmdir /S /Q .
cd %FPC_BUILD%

make clean all install OPT="-gwl -godwarfsets" > buildlog.txt 2>builderror.txt
pause

cd %INSTALL_PREFIX%\bin\x86_64-win64
del /F /Q %INSTALL_PREFIX%/bin/x86_64-win64/fpc.cfg
fpcmkcfg.exe -d basepath=c:/fpc/2.7.1 -o .\fpc.cfg
pause
cd ..\..\..
:eof
Additional InformationI atacched the buildlog.txt file that this line generates:

make clean all install OPT="-gwl -godwarfsets" > buildlog.txt 2>builderror.txt

The OPT="-gwl -godwarfsets" was suggested by Paul ishenin on IRC this morning. I tried WITHOUT that OPT and doesn't work either.

builderror.txt contained:

make[7]: *** No rule to make target `iso7185.ppu', needed by `fpc_units'. Stop.
make[6]: *** [win64_all] Error 2
make[5]: *** [rtl] Error 2
make[4]: *** [next] Error 2
make[3]: *** [ppc1.exe] Error 2
make[2]: *** [cycle] Error 2
make[1]: *** [compiler_cycle] Error 2
make: *** [build-stamp.x86_64-win64] Error 2

Thanks in advance,
David
TagsNo tags attached.
FPCOldBugId
Fixed in Revision
Attached Filestxt file icon buildlog.txt [^] (41,794 bytes) 2012-05-05 22:00 [Show Content]

- Relationships

-  Notes
(0059278)
Marco van de Voort (manager)
2012-05-05 22:26
edited on: 2012-05-05 22:30

Some observations?

(1) you have no PP=xxx or FPC=xxx line in your make line to set the last compiler,
(2) your script puts %INSTALL_PREFIX%\bin\x86_64-win64; first in the path. I assume that the default compiler is taken from there
(3) but install_prefix is C:\\fpc\\2.7.1 ?
(4) afaik there is no x86_64 win64 2.6.0 starting compiler? Where exactly did you get it? Or do you crosscycle from 32-bit?

So I doubt you really cycle using 2.6.0 as starting compiler. Could you add some -viwh to your OPT line and check the output of the log of 2.6.0 is really used?

I build a snapshot on vista64 (in 64-bit mode) just last night, and that went fine.

(0059294)
DavidB (reporter)
2012-05-06 10:56
edited on: 2012-05-06 10:58

Hi marco,

Thanks for your suggestions. With the help of my friend jameel I managed to compile FPC 2.7.1. from SVN.

The problem is I was NOT using the binutils from 2.4.4.

My dir structure is this:

C:\fpcsvn <- The SVN Checkout dir.
C:\fpc\2.4.4 <- FPC 2.4.4
C:\fpc\2.6.0 <- FPC 2.6.0
C:\fpc\2.7.1 <- The dir where FPC 2.7.1 will be built.

NONE of those dirs are on my PATH variable.

I have MingW 4.6.2 (64 bits) and msys on the path. With MingW with higher pirority.

Then I modified my bat file as suggested by my friend like this:

@echo on

set FPC_2_6_0=C:\\fpc\\2.6.0
set FPC_UTILS=C:\\fpc\\2.4.4
set FPC_BUILD=C:\\fpcsvn
set INSTALL_PREFIX=C:\\fpc\\2.7.1
set DATA2INC=%INSTALL_PREFIX%/bin/x86_64-win64/data2inc.exe

set PATH=%INSTALL_PREFIX%\bin\x86_64-win64;%FPC_2_6_0%\bin\x86_64-win64;%FPC_UTILS%\bin\x86_64-win64;%PATH%
pause

REM Added to check FPC used is 2.6.0
fpc -iDW
pause

cd %INSTALL_PREFIX%
rmdir /S /Q .
cd %FPC_BUILD%

make clean all install OPT="-viwh -gwl -godwarfsets" > buildlog.txt 2>builderror.txt
pause

cd %INSTALL_PREFIX%\bin\x86_64-win64
del /F /Q %INSTALL_PREFIX%/bin/x86_64-win64/fpc.cfg
fpcmkcfg.exe -d basepath=c:/fpc/2.7.1 -o .\fpc.cfg
pause
cd ..\..\..
:eof

Now i will try to compile it again without the OPT.

Thanks for the suggestions by the way! :) I posted all this in case can be useful for someone else.

(0059349)
Jonas Maebe (manager)
2012-05-07 13:37

You should not add %INSTALL_PREFIX%\bin\x86_64-win64 to the path. Even if your "fpc -iDW" shows that this points to a 2.6.0 binary, that statement adds 2.7.1 to the path and will cause troubles from time to time.

I also don't understand what that "utils" directory is. No FPC installer puts any executable files on Windows under either c:\fpc\2.4.4 or c:\fpc\2.6.0 afaik.

Please only build with a straight FPC installation in your path (no msys, no mingw, no special utilities directories, really nothing else except for the standard Windows path) that you did not reorganise or modify in any way (no moving stuff to utils directories etc). That is the only configuration we can and do support.
(0059987)
Jonas Maebe (manager)
2012-05-27 01:33

No feedback from submitter.

- Issue History
Date Modified Username Field Change
2012-05-05 22:00 DavidB New Issue
2012-05-05 22:00 DavidB File Added: buildlog.txt
2012-05-05 22:26 Marco van de Voort Note Added: 0059278
2012-05-05 22:26 Marco van de Voort Status new => feedback
2012-05-05 22:30 Marco van de Voort Note Edited: 0059278
2012-05-06 10:56 DavidB Note Added: 0059294
2012-05-06 10:58 DavidB Note Edited: 0059294
2012-05-07 13:37 Jonas Maebe Note Added: 0059349
2012-05-27 01:33 Jonas Maebe Status feedback => resolved
2012-05-27 01:33 Jonas Maebe Resolution open => suspended
2012-05-27 01:33 Jonas Maebe Assigned To => Jonas Maebe
2012-05-27 01:33 Jonas Maebe Note Added: 0059987



MantisBT 1.2.12[^]
Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker