[Pkg-pascal-devel] release candidate of fpc 3.2.0 in git

[Abou Al Montacir]

Hi Paul,
On Sat, 2020-05-23 at 22:08 +0200, Paul Gevers wrote:
> Dear all,
> I just pushed my efforts to package fpc 3.2.0~rc1 to our git archive. Ifailed
> to get it to build. I had to drop a piece fromfix-units-path-to-be-multi-arch-
> safe.patch because the upstream partthat was patched was dropped. This may or
> may not be related.
> The first failure happens during building of the
> documentation:/usr/bin/ld.bfd: /<<PKGBUILDDIR>>/fpcsrc/rtl/units/x86_64-
> linux/prt0.o:in function `_start':(.text+0x8e): undefined reference to
> `FPC_SysEntry'<and more like those>
> If I skip building documentation it fails during the binary
> phase:/usr/bin/ppcx64 src/fpmkunit.pp -n -Fu../../rtl/units/x86_64-linux-
> FUunits_bs/x86_64-linux -Fu../paszlib/src -Fu../hash/src-Fi../paszlib/src
> -Cg  -Fi../fcl-process/src/unix -Fu../fcl-process/src-Fi../fcl-
> process/src/linux -Fi../fcl-process/src/dummy
> -Fu../libtar/src@/<<PKGBUILDDIR>>/debian/deb-build-fpc.cfgPPU Loading
> /<<PKGBUILDDIR>>/fpcsrc/rtl/units/x86_64-linux/system.ppuPPU Invalid Version
> 207Fatal: Can't find unit system used by fpmkunitFatal: Compilation aborted
> I'm not surprised that the system version of ppcx64 doesn't know the
> newversion of PPU yet, but normally these kind of mismatches aren't aproblem
> during the build.
> Paul
I would wait until the 3.2.0 is officially released. There are many changes and
more may happen between release candidates.-- 
Cheers,
Abou Al Montacir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20200601/ec85ff7e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20200601/ec85ff7e/attachment.sig>