fpcup 3.1.1 Update

[vfclists]

I am running fpcup using these settings and I get this error message:

Could the error be related to running a 32bit fpcup on a 64bit system?

Here is the inisection, and I am running 32bit fpcup on Windows 7 64bit.

Code: [Select]

[lazarus_fixes_160_311]
fpcURL=3.1.1
lazURL=fixes1.6
cputarget=i386
ostarget=win32
crossbindir=M:\Lazarus\FpcUpExes\crossBinDir
crosslibdir=M:\Lazarus\FpcUpExes\crossLibDir
lclplatform=win32
fpcdir=M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win32\fpc
lazdir=M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win32
fpcbootstrapdir=M:\Lazarus\FpcUpExes\fpcbootstrap
binutilsdir=M:\Lazarus\FpcUpExes\binutils
primary-config-path=M:\Lazarus\Configs\Lazarus_Fixes_160_311_Win32
fpcuplinkname=M:\Lazarus\Configs\Lazarus_Fixes_160_311_Win32_FPCup_Update
lazlinkname=M:\Lazarus\Configs\Lazarus_Fixes_160_311_Win32


I changed it again to Win64 with these settings - avoiding anything which looks like it might trigger cross compilation, just plain trunk.

Code: [Select]

[lazarus_fixes_160_311_Win64]
fpcURL=3.1.1
lazURL=fixes1.6
; cputarget=x86_64
; ostarget=win64
crossbindir=M:\Lazarus\FpcUpExes\crossBinDir
crosslibdir=M:\Lazarus\FpcUpExes\crossLibDir
; lclplatform=win32
fpcdir=M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc
lazdir=M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\lazarus
fpcbootstrapdir=M:\Lazarus\FpcUpExes\fpcbootstrap
binutilsdir=M:\Lazarus\FpcUpExes\binutils
primary-config-path=M:\Lazarus\Configs\Lazarus_Fixes_160_311_Win64
fpcuplinkname=M:\Lazarus\Configs\Lazarus_Fixes_160_311_Win64_FPCup_Update
lazlinkname=M:\Lazarus\Configs\Lazarus_Fixes_160_311_Win64

And it still give the cross compiler error. Is FPCup downloading the correct cross compilers, or is the compiler too bleeding edge for cross compilation to be working?

Code: [Select]

fpclazup: info: Running Make crossinstall (FPC crosscompiler: x86_64-win64)
Executing : M:\Lazarus\FpcUpExes\binutils\make.exe "--jobs=2" "FPC=M:\Lazarus\FpcUpExes\fpcbootstrap\intermediate_ppcx64.exe" "INSTA
LL_PREFIX=M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc" "UPXPROG=echo" "COPYTREE=echo" "crossinstall" "OS_TARGET=win64" "CPU_
TARGET=x86_64" "OPT=-vi-n-h-" (working dir: M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc)
M:/Lazarus/FpcUpExes/binutils/make install CROSSINSTALL=1
make[1]: Entering directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc'
M:/Lazarus/FpcUpExes/binutils/make installbase FPC=M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/compiler/ppcx64.exe ZIPDESTDI
R=M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc FPCMAKE=M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/utils/fpcm/bin/x86
_64-win64/fpcmake.exe
make[2]: Entering directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc'
M:/Lazarus/FpcUpExes/binutils/ginstall.exe -m 755 -d M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc
M:/Lazarus/FpcUpExes/binutils/ginstall.exe -m 755 -d M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc/bin/x86_64-win64
M:/Lazarus/FpcUpExes/binutils/make compiler_install FPC=M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/compiler/ppcx64.exe ZIPD
ESTDIR=M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc FPCMAKE=M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/utils/fpcm/bi
n/x86_64-win64/fpcmake.exe
make[3]: Entering directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc'
M:/Lazarus/FpcUpExes/binutils/make -C compiler install
make[4]: Entering directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/compiler'
M:/Lazarus/FpcUpExes/binutils/make -C utils install
make[5]: Entering directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/compiler/utils'
make[5]: Nothing to be done for `install'.
make[5]: Leaving directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/compiler/utils'
echo ppcrossx64.exe
ppcrossx64.exe
M:/Lazarus/FpcUpExes/binutils/ginstall.exe -m 755 -d M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc/bin/x86_64-win64
M:/Lazarus/FpcUpExes/binutils/cp.exe -fp ppcrossx64.exe M:\Lazarus\Binaries\Lazarus_Fixes_160_311_Win64\fpc/bin/x86_64-win64/ppcross
x64.exe
cp.exe: ppcrossx64.exe: No such file or directory
make[4]: *** [exeinstall] Error 1
make[4]: Leaving directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc/compiler'
make[3]: *** [compiler_install] Error 2
make[3]: Leaving directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc'
make[2]: *** [installbase] Error 2
make[2]: Leaving directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc'
make[1]: *** [installall] Error 2
make[1]: Leaving directory `M:/Lazarus/Binaries/Lazarus_Fixes_160_311_Win64/fpc'
make: *** [crossinstall] Error 2
fpclazup: ERROR: FPC: Problem installing crosscompiler for x86_64-win64.
fpclazup: ERROR: Error running BuildModuleCustom for module FPC
fpclazup: info: Error running fpcup. Technical details: error executing sequence fpc; line: 5, param: FPC
fpclazup: info: Error running fpcup. Technical details: error executing sequence Default; line: 3, param: fpc
Fpclazup failed.
Please check log for details. Possible troubleshooting steps:
- run again with --verbose and check for make, lazbuild errors etc.
- if compiling Lazarus, make sure your lhelp is closed.
- try removing all intermediate files by running fpcup with the --clean option
  and/or manually deleting all *.ppu/*.a/*.o followed by svn up
- if that does not work: use the --uninstall option to remove all files
  including your FPC and Lazarus directories
- remove the files in the bootstrap directory. fpcup will redownload if required.
fpclazup: info: 04/07/2016 17:01:20: fpcup finished.


[DonAlfredo]

Strange error. Fpcup is looking for crosscompilers where it shouldn't.

My advice in these situations: run a most simple fpclazup command from a clean directory:
(a clean directory is a directory with only a single file to start with: fpclazup.exe)

Code: Pascal  [Select][+][-]

1. fpclazup.exe --installdir="M:\Lazarus\Binaries\MyFpcupTest"

It will also give you the base for cross-compiling.

So, start simple and try to debug.

[vfclists]

Strange error. Fpcup is looking for crosscompilers where it shouldn't.

My advice in these situations: run a most simple fpclazup command from a clean directory:
(a clean directory is a directory with only a single file to start with: fpclazup.exe)

Code: Pascal  [Select][+][-]

1. fpclazup.exe --installdir="M:\Lazarus\Binaries\MyFpcupTest"

It will also give you the base for cross-compiling.

So, start simple and try to debug.

I got it work by building for the same CPU and operating system, by excluding the cputarget, ostarget and lclplatform options.

One more thing the Help | About screen shows FRET_UNKNOWN_REVISION for the Lazarus revision

[DonAlfredo]

Ok.
About FRET_UNKNOWN_REVISION.
Seen it. Will have a look into it !

[zbyna]

One more thing the Help | About screen shows FRET_UNKNOWN_REVISION for the Lazarus revision

Same for me.

Code: [Select]

fpclazup.exe --fpcURL="trunk" --lazURL="trunk" --verbose --installdir="E:\Development\"
...
[2016-07-12 15:30:01.708 Info] SVN client found: E:\Program Files (x86)\CollabNet\svn.exe


[vfclists]

Ok.
About FRET_UNKNOWN_REVISION.
Seen it. Will have a look into it !

Have you managed to fix the FRET_UNKNOWN_REVISION issue?

[DonAlfredo]

Looking at it again right now.
Was not able to reproduce.

[DonAlfredo]

One more thing the Help | About screen shows FRET_UNKNOWN_REVISION for the Lazarus revision

Same for me.

Code: [Select]

fpclazup.exe --fpcURL="trunk" --lazURL="trunk" --verbose --installdir="E:\Development\"
...
[2016-07-12 15:30:01.708 Info] SVN client found: E:\Program Files (x86)\CollabNet\svn.exe


Again, I am not able to reproduce.
Tried all kinds of settings. All showing correct revision.
Do you use the latest fpclazup ?

But I also have seen this error on my system before.
Remains a mistery for me ...

[Thaddy]

See if doing away with the 2.6.2 (really old) starting compiler works...
I can also reproduce this, but intermittantly and not consistently over platforms.
It may be that some platform code is an issue because of 2.6.2 instead of 2.6.4.
AFAIK 2.6.4. is now current on most distributions outside of the FPC community itself, where 3.0 is of course current.

To support your efforts I can put starting compilers on freepascal.thaddy.com on a regular basis. ATM there are little if no downloads there, but my servers are high speed and capable of high volume. Maybe we should discuss such an option. I think it would still be in the spirit of BigChimp. (my servers are up for decades, some since 2000)

[rvk]

About FRET_UNKNOWN_REVISION.

For me, after running fpclazup_linux_x64 it does say:

Code: [Select]

fpclazup: info: Checking out/updating FPC sources...
fpclazup: info: INFO: directory /home/rik/development/fpc is not an SVN repository (or a repository with the wrong remote URL).
fpclazup: info: INFO: creating directory /home/rik/development/fpc for SVN checkout.
fpclazup: info: Running SVN checkout or update.and

Code: [Select]

fpclazup: info: SVN client found: /usr/bin/svn
fpclazup: info: Checking out/updating Lazarus sources:
fpclazup: info: INFO: directory /home/rik/development/lazarus is not an SVN repository (or a repository with the wrong remote URL).
fpclazup: info: INFO: creating directory /home/rik/development/lazarus for SVN checkout.
fpclazup: info: Running SVN checkout or update.
fpclazup: info: Lazarus is now at: revision FRET_UNKNOWN_REVISION
fpclazup: info: Updating Lazarus version info.
fpclazup: info: Result true
But afterwards:

Code: [Select]

rik@rik-VirtualBox ~/development $ svn info fpc
svn: E155007: '/home/rik/development/fpc' is not a working copy
rik@rik-VirtualBox ~/development $ svn info lazarus
svn: E155007: '/home/rik/development/lazarus' is not a working copy
rik@rik-VirtualBox ~/development $ cd lazarus
rik@rik-VirtualBox ~/development/lazarus $ svn info
svn: E155007: '/home/rik/development/lazarus' is not a working copy
rik@rik-VirtualBox ~/development/lazarus $
So somehow the svn doesn't create a valid working copy for svn (which would result in the FRET_UNKNOWN_REVISION).

This is on Linux Mint 18 Sarah Cinnamon 64-bit with fpclazup_linux_x64:
Lazarus 1.6 rFRET_UNKNOWN_REVISION FPC 3.0.0 x86_64-linux-gtk 2

[rvk]

Ok, I had not given the --getfullrepo option. When using that option the SVN Revision is correct (for me).

If --getfullrepo is not given (or set in settings) there is an "export" done. Otherwise a "checkout" is done.
But svnclient.pas checks with "svn info localdir" what revision is downloaded. That results in an error when "export" is used so you get a FRET_UNKNOWN_REVISION.

Wouldn't it be better for fpclazup to do a "svn info $repourl" so the online version is taken? That would work with checkout as well as export. (or if "checkout" is used you could do "svn info localdir" but for "export" check against the $reprourl)

And if you want to distinguish between "checkout" and "export" use "SVN Revision: 52677M (export)" instead of "SVN Revision: 52677M".

[DonAlfredo]

@Thaddy
I think BigChimp wanted everything from official sources. That's also the reason why there are no bootstrap compilers hosted on fpcup GitHub.
However, we could move forward without loosing his spirit, by offering home made bootstrappers as an extra option.
E.g. --usespecialbootstrap.
These can easily be hosted on GitHub.
But I would value your feedback on this.

@rvk
Thanks !
I will use your feedback to dig deeper !
Will report back.

[rvk]

That's also the reason why there are no bootstrap compilers hosted on fpcup GitHub.

Valid... but isn't there any chance to just get proper bootstrap compilers for all platforms in
ftp://ftp.freepascal.org/pub/fpc/dist/3.0.0/bootstrap

There are a lot in
ftp://ftp.freepascal.org/pub/fpc/dist/2.6.4/bootstrap
and even more in
ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap

What's the reason they were not made for 3.0.0 ?

(is there a difference between for example ppc386.exe in bootstrap and the on in the official complete FPC binary package?)

[DonAlfredo]

This has already been discussed on the FPC mailing list !

http://lists.freepascal.org/pipermail/fpc-devel/2016-June/037172.html

[rvk]

Ok, so even the bootstrap 2.6.2 from ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap/ (which fpcup uses) isn't officially "supported" 

I'll guess I'll keep downloading the 42.8MB package of FPC 3.0.0 to use the compiler (2.8MB) from there