Le vendredi 27 mai 2011 à 05:02 +0100, peter green a écrit : > > > > Can you please try again with 2.4.4. This includes multiples changes > > in example script packaging and should fix your issue. > ok boostrap recipie below (this pretty much represents what I did but > with some screwups edited out). Note that the instructions below assume > starting in an empty directory > > wget > ftp://193.224.143.39/pub/fpc/dist/2.4.4/i386-freebsd/fpc-2.4.4.i386-freebsd8.tar > tar -xf fpc-2.4.4.i386-freebsd8.tar > tar -xf binary.i386-freebsd.tar > tar -zxf base.i386-freebsd.tar.gz > tar -zxf utils.i386-freebsd.tar.gz > export PATH=$PATH:$PWD/bin > export PATH=$PATH:$PWD/lib/fpc/2.4.4 > apt-get source -b fpc > > -------------At this point install any missing build-dependencies > -------------EXCEPT fp-compiler fp-units-base fp-units-fcl and fp-utils > cd fpc-2.4.4 > -------------Apply the patch attatched to this mail to debian/rules and > debian/moveexamples > dpkg-buildpackage -B -d > dpkg -i ../*.deb > apt-get -f install > > Unfortunately it seems while the build was sucessful the binary packages are > incomplete and unusable. Further research is needed into why things are > breaking. > but my guess is further discrepancies in upstream install locations between > linux builds and freebsd builds. > > Some notes on the patch > 1: I changed the use of DEB_*_ARCH to DEB_*_ARCH_CPU, this makes it do the > right thing for > kfreebsd and also eliminates the need to special case armel. > 2: I added a new variable $(OS_TARGET) derived from DEB_HOST_ARCH_OS. This is > now used for > setting FPCTARGET (which afaict is only used for generating package > descriptions) > and for the conditional below > 3: to deal with some different upstream makefile behaviour on freebsd > regarding > examples I had to modify debian/moveexamples and the code that supplies > it's parameters > (including adding an extra parameter) > 4: I noticed that the new versioned packages were restricted to a very > limited set of arches > (not including the one I was building on) while the "compatability" > packages that depend > on them were arch any. This didn't make any sense to me and prevented the > building of > usable packages on kfreebsd so I changed the versioned packages to be arch > any. > > I have not yet tried a boostrap on kfreebsd-amd64. I'll try that if and when > I get the > kfreebsd-i386 builds working.
Hi FPC core, Can anyone help on this please ? Cheers,
signature.asc
Description: This is a digitally signed message part
