gmake all -j 5 FPMAKEOPT="-T 8" FPC=$COMPILER
gmake install INSTALL_PREFIX=/data/devel/fpc-2.7.1/$TARGET/ FPC=$COMPILER
------------------[ end ]---------------------
The compiling of fpdoc fails with a linking error. Unable to find
libiconv, but what exactly is it looking for? If you look further down
my email, the libiconv *is* installed on my FreeBSD system, in the
usual location of /usr/local/lib/
So what am I missing, to resolve this compilation issue?
On 2013-03-04 18:20, Marco van de Voort wrote:
> This is normal, pass -Fl/usr/local/lib in opt (for releases, makepack from
> fpcbuild does this)
Thanks, that worked. Now FPC 2.7.1 compiles without problems, and it
install fine [or so it appears].
Last night I wanted to test with FPC 2.7.1 again. So did the whole
"update from Trunk", rebuild and install. It all seems to have gone
well.... but I can't compile any of my projects with 2.7.1 (but I can
In seems that the 'gmake install' doesn't install the *.a files that FPC
generates, so my apps fail to link. I did a comparison between my 2.7.1
and 2.6.0 (installed from official installer) directories. In 2.6.0 the
*.a files are found in the lib/fpc/2.6.0/... directories, but in 2.7.1
they are not (they only appear in the FPC 'src' directory tree).
Has the 'gmake install' changed in 2.7.1 compared to how it worked
before? Or is there again something special required for FreeBSD systems?
Here is my go.sh script I use to build and install FPC 2.7.1
> In seems that the 'gmake install' doesn't install the *.a files that FPC
> generates, so my apps fail to link. I did a comparison between my 2.7.1
> and 2.6.0 (installed from official installer) directories. In 2.6.0 the
> *.a files are found in the lib/fpc/2.6.0/... directories, but in 2.7.1
> they are not (they only appear in the FPC 'src' directory tree).
> Has the 'gmake install' changed in 2.7.1 compared to how it worked
> before? Or is there again something special required for FreeBSD systems?
Did you check what happens when you call
gmake install ?
One of the problems I often get is that
I have a release compiler in the path.
In that case the outcome of 'fpc-iSOSP..'
is used to generated the sub-directory into which
the generated libraries will be stored...
So often I end up with
which contains the newly installed linraries...
I don't exactly know when, and when not,
this problem shows up.
A good solution to avoid it is to put
your trunk compiler binary in the path before the release
On 2013-03-15 16:40, Pierre Free Pascal wrote:
> So often I end up with
> but also
> which contains the newly installed linraries...
No, that is not the case. I only have a lib/fpc/2.7.1/ directory tree.
My build script was posted in my earlier message. I have used that same
script since about FPC 2.4.0
> A good solution to avoid it is to put
> your trunk compiler binary in the path before the release
I explicit specify the compiler and install prefix to avoid such issues.
This has worked for many years. It seems it might be a fpmake issue to
me. Everything is done correctly, except the lib*.a files are not copied
to the INSTALL_PREFIX path.
On 2013-03-15 21:22, Marco van de Voort wrote:
> Try adding RELEASE=1
It still fails. Do you Marco, or anybody else, know where the actual
code is in fpmake or Makefiles that says "copy all *.ppu, *,o and *.a
files to INSTALL_PREFIX"?
I don't really understand Makefile syntax that well (never used them in
any of my projects), and a quick search through the FPC files didn't
reveal anything obvious to me. But I would like to debug this problem on
my system, and get it to work. The released FPC versions are correct,
and contain the lib*.a files, but no matter what I try, those files are
not copied during my FPC 2.7.1 build & install process.
On 2013-03-15 10:46, Graeme Geldenhuys wrote:
> In seems that the 'gmake install' doesn't install the lib*.a files that FPC
> generates, so my apps fail to link.
Just as a test. I checked out the 'fixes_2_6' branch, and used my same
build script as I did before. It successfully built and installed FPC
2.6.3 _with_ the lib*.a files in the INSTALL_PREFIX directory tree.