Hi again,
OK, I've got it. Making a debug version of the library and using gdb
showed me it was threading code that triggers the error.
Adding 'cthreads' to the uses clause resolved this error.
Puh,
Marc
--
Marc Santhoff
___
fpc-pascal maillist -
On Fr, 2015-02-13 at 07:33 +0100, Jonas Maebe wrote:
> On 12/02/15 00:42, Marc Santhoff wrote:
> > Some data points:
> > fpc 2.6.2 x86_64
>
> Always use the latest FPC release, in this case 2.6.4. I think even some
> x86-64 calling convention issues were fixed between 2.6.2 and 2.6.4.
Wow, comple
Please excuse me for not answering you before ...
On Wed, Feb 11, 2015 at 4:59 AM, Michael Van Canneyt wrote:
>
> On Tue, 10 Feb 2015, silvioprog wrote:
>>
>>
>> Buddy, I finally could make a draft of a FastCGI application running in
>> multi-thread in proxy mode. =)
>>
>
> Congratulations !!
T
On Fr, 2015-02-13 at 09:07 +, Tony Whyman wrote:
> A pity, because that would have been an easy fix. This type of error
> comes from either mis-matched calling conventions or incompatible
> argument lists.
No easy solution in sight...
> >From having done this sort of thing before all I can ad
On Fr, 2015-02-13 at 07:33 +0100, Jonas Maebe wrote:
> On 12/02/15 00:42, Marc Santhoff wrote:
> > Some data points:
> > fpc 2.6.2 x86_64
>
> Always use the latest FPC release, in this case 2.6.4. I think even some
> x86-64 calling convention issues were fixed between 2.6.2 and 2.6.4.
Done, no ch
Hi Gustavo!
Can you build shared libraries with FPC and load it with another FPC
program on RPi?
2015-02-13 11:33 GMT-02:00 Gustavo Enrique Jimenez :
> Thank you very much to all Freepascal and Lazarus developers. Today I
> was able to compile all my applications within "Raspberry Pi". I am
>
Thank you very much to all Freepascal and Lazarus developers. Today I
was able to compile all my applications within "Raspberry Pi". I am
very happy. Many thanks to everyone for this amazing tool that you
gave to the world.
Gustavo
___
fpc-pascal mailli
A pity, because that would have been an easy fix. This type of error
comes from either mis-matched calling conventions or incompatible
argument lists.
>From having done this sort of thing before all I can advise is to go
through each function argument one by one and make sure that each
argument ty
