Pierre Free Pascal wrote:
https://archive.raspbian.org/raspbian/pool/main/f/fpc/
The 2.6.4 release is able to successfully compile
a 2.7.1 trunk compiler.
:) Thanks for confirming.
Several files are missing in this source release:
The source package which is made up of fpc_2.6.4
> -Message d'origine-
> De : fpc-devel-boun...@lists.freepascal.org [mailto:fpc-devel-
> boun...@lists.freepascal.org] De la part de peter green
> Envoyé : mardi 21 octobre 2014 10:32
> À : FPC developers' list
> Objet : Re: [fpc-devel] Building 2.7.1 on current Raspbian fails
>
> Paul M
Good point, thanks. From a brief look, tree.log retains enough
information to rebuild the source. I'll see if I can work with that...
On 10/22/2014 4:44 AM, Nikolay Nikolov wrote:
The compiler already supports dumping the parse tree when you use the
-vp option. But it's more intended for debugg
>> deb http://plugwash.raspbian.org/wsf wheezy-wsf main
Thanks. So what exactly does it do? How does one access?
It's an apt repository I just set up for fixes to dependency problems
caused by the foundations webkit-related packages (they shipped an
updated webkit and a load of related updates
Thanks. So what exactly does it do? How does one access? Just for wheezy or
will it work on jessie too? John
On 22 October 2014 00:08, peter green wrote:
> peter green wrote:
>
>> So it would seem FPC is currently broken on
>>> stable Raspbian which is a pity.
>>>
>>>
>> It's fine on plain raspb
On 10/22/2014 12:23 AM, Vsevolod Alekseyev wrote:
Hi all,
I wonder where in the FPC compilation flow would be a good spot to
dump the parsed syntax tree of a source?
Here's why I'm asking. For a while now, I've been struggling to adapt
a bunch of Pascal code to various mobile platforms. It's
