On Mon, 17 Nov 2014 16:13:40 +0100
Jonas Maebe wrote:
>
> Dmitry Boyarintsev wrote on ma, 17 nov 2014:
>
> > So based on the bug report description: "There is no problem with other LCL
> > components"
> > I guess LCL itself was compiled with PIC flag as well (though, not
> > mentioned in the re
On Mon, Nov 17, 2014 at 10:13 AM, Jonas Maebe
wrote:
>
> Yes, fpcmake automatically adds -Cg/-fPIC for x86-64 platforms, exactly
> because of this issue.
>
Aha... now it makes sense. Lazarus and LCL itself are products of fpcmake,
while Lazarus packages are not.
This has to be addressed in Lazar
Dmitry Boyarintsev wrote on ma, 17 nov 2014:
So based on the bug report description: "There is no problem with other LCL
components"
I guess LCL itself was compiled with PIC flag as well (though, not
mentioned in the report).
Yes, fpcmake automatically adds -Cg/-fPIC for x86-64 platforms,
e
On Mon, Nov 17, 2014 at 2:51 AM, Jonas Maebe
wrote:
> All global data, exported or not, need special code to be accessed in a
> position-independent way on most targets (including x86-64).
>
Thanks for clarification.
So based on the bug report description: "There is no problem with other LCL
co
On Sun, Nov 16, 2014 at 4:21 PM, Noel Duffy
wrote:
> On Sun, 16 Nov 2014 11:06:09 -0300, silvioprog wrote:
>
> > On Sat, Nov 15, 2014 at 5:10 AM, Noel Duffy <
> hobcraft-...@yahooxtra.co.nz>
> > wrote:
> >
> >
> >> I am running fpc 2.6.4 on Debian stable and on Fedora 20, and both
> >> display t
On Sun, 16 Nov 2014 11:06:09 -0300, silvioprog wrote:
> On Sat, Nov 15, 2014 at 5:10 AM, Noel Duffy
> wrote:
>
>
>> I am running fpc 2.6.4 on Debian stable and on Fedora 20, and both
>> display the same behaviour.
>
>
> Compiled like a charm in FPC 2.7.1 from trunk. So this problem will not
>
