<html><head></head><body><div>On Mon, 2015-11-02 at 19:11 +0000, Edmund Grimley Evans wrote:</div><blockquote type="cite"><pre>Paul Gevers <<a href="mailto:elbrus@debian.org">elbrus@debian.org</a>>:
<blockquote type="cite">
<blockquote type="cite">
Well, it seems to have built everywhere except ppc64. Thanks for that.
Are you going to wait for the real 3.0.0 before uploading to unstable?
</blockquote>
I am not going to put the rc in unstable, now. And after that I am even
unsure, as the official lazarus binary is build against 2.6.4, I don't
know how well we do if we build that against 3.0.0. I like to have
Abou's opinion on this.
</blockquote></pre></blockquote><div>FPC uses PPU files which are compiler and RTL version depending. This means that you can generally not use a PPU compiled with an older version of FPC with new FPC version.</div><div>Now what we call Lazarus is a mix of an IDE and a component library (LCL). The IDE itself should work with any reasonably compatible version with the one it was compiled with. However the LCL will need the very same RTL PPU files it was compiled with. So if you install a different FPC version you will end with an error stating that FPC could not compile RTL units.</div><div><br></div><div>Now we have a partial fix for that, as users that already installed Lazarus will see the old FPC version kept (that is why we have versioned package names). But Lazarus will become non installable on any new system as it depends on a package that no more exist (old FPC/RTL). This will block migration of FPC to testing too.</div><blockquote type="cite"><pre>
That sounds reasonable. I understand that an IDE interacts with the
compiler in more ways than just being built by it.
</pre></blockquote><div>Yes, more than any other IDE is interacting with any other compiler. Lazarus/FPC have a kind of very strong dependency relationship as explained above. It is not only an IDE, it is a library extension in addition to the intrinsic FPC way of handling PPU.</div><blockquote type="cite"><pre>
<blockquote type="cite">
<blockquote type="cite">
I might try building some of the 20 packages that depend on fpc, just
to see what happens. According to my list, they are:
</blockquote>
Please start with lazarus... I may start doing this in experimental,
just to see what happens. But before I do that I need to inform the
maintainers.
</blockquote>
I was able to build libqt4pas, lazarus and pasdoc using the new fpc.
I just had to update the symbols file for libqt4pas.
</pre></blockquote><div>That is great. I assume you also launched Lazarus just to ensure it does not crash!</div><blockquote type="cite"><pre>
<blockquote type="cite">
<blockquote type="cite">
cqrlog
ddrescueview
doublecmd
dozzaqueux
easymp3gain
gearhead
gearhead2
imapcopy
lazarus
libqt4pas
mricron
nbc
optgeo
pasdoc
transgui
tuxcmd
tuxcmd-modules
view3dscene
winff
ztex-bmp
</blockquote>
>From the top of my head, I am missing castle-game-engine in this list.
</blockquote>
That package is only built on amd64 and i386. Is there a good reason
for that?
</pre></blockquote><div>This is a game engine, I'm not aware anybody tested it on other architecture, but I think also there were some dependency missing. I'd let <span style="background-color: rgb(237, 237, 237);">Michalis</span> comment ont that.</div><div>-- </div><div class="-x-evo-signature-wrapper"><span><pre>Cheers,
Abou Al Montacir
</pre><div><br></div></span></div></body></html>