Re: [fpc-pascal] FreeBSD failure compiling fpdoc 2.7.1
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. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FreeBSD failure compiling fpdoc 2.7.1
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. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FreeBSD failure compiling fpdoc 2.7.1
On 2013-03-15 16:40, Pierre Free Pascal wrote: So often I end up with BASE_271_DIR/lib/fpc/2.7.1 but also BASE_271_DIR/lib/fpc/2.6.0 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 compiler. 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. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FreeBSD failure compiling fpdoc 2.7.1
On 2013-03-15 18:08, Marco van de Voort wrote: You install using the bootstrap compiler, not the generated one. OK, I changed the 'gmake install' in my scrip to use the generated compiler. It made no difference. my script: I used your script (nice by the way), and it produced the exact same results as mine. No lib*.a files in the INSTALL_PREFIX directory tree. I'm using FreeBSD 9.1 64-bit My starting compiler is FPC 2.6.2 (installed from binary release). Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE: [fpc-pascal] FreeBSD failure compiling fpdoc 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 BASE_271_DIR/lib/fpc/2.7.1 but also BASE_271_DIR/lib/fpc/2.6.0 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 compiler. Pierre ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FreeBSD failure compiling fpdoc 2.7.1
In our previous episode, Graeme Geldenhuys said: #gmake clean gmake all -j 5 FPMAKEOPT=-T 8 FPC=$COMPILER FPCOPT=-Fl/usr/local/lib/ OPT=-Fl/usr/local/lib/ gmake install INSTALL_PREFIX=/data/devel/fpc-2.7.1/$TARGET/ FPC=$COMPILER You install using the bootstrap compiler, not the generated one. my script: #!/usr/bin/env bash # -dSHOWUSEDMEM (this argument to the compiler) ARCH=`uname -m` echo ARCH is $ARCH export ARGS= -gl -viwn -Sg -Fl/usr/local/lib CPU_TARGET=i386 PP=ppcrel NEWPP=ppc386 if [ $ARCH = amd64 ] ; then CPU_TARGET=x86_64 echo selecting 64 - bit PP=ppcrel_x64 NEWPP=ppcx64 ARGS+= -gw2 fi echo $CPU_TARGET if [ $ARCH = i386 ] ; then ARGS+=-Cppentium3 -gl fi cd ~/src/fpc gmake -j 2 clean CPU_TARGET=$CPU_TARGET PP=$PP OPT=$ARGS ~/cleanlog gmake -j 2 all CPU_TARGET=$CPU_TARGET PP=$PP OPT=$ARGS ~/buildlog if [ ! $? = 0 ] ; then echo Build failed, again else gmake install OPT=$ARGS CPU_TARGET=$CPU_TARGET INSTALL_PREFIX=~/src/builded PP=~/src/fpc/compiler/$NEWPP ~/installog if [ ! $? = 0 ] ; then echo INSTALL failed | tee ~/outcome else echo Everything _should_ be fine.| tee ~/outcome fi fi ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FreeBSD failure compiling fpdoc 2.7.1
In our previous episode, Graeme Geldenhuys said: Below is the script I use to compile FPC 2.7.1. I am using FPC 2.6.0 (I noticed it is still allowed for a while, even though 2.6.2 is out). This is normal, pass -Fl/usr/local/lib in opt (for releases, makepack from fpcbuild does this) Also see http://www.stack.nl/~marcov/buildfaq/#toc-Subsection-1.6.4 ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
