In our previous episode, Vincent Snijders said:
> > Please file a bug anyway, with as much details as possible. It would be
> > really great if you could get the "strace" output of the compiler run in
> > both cases.
>
> Yes, but where to download strace for win32?
Correct. Then settle for -va ou
On 14 Oct 2008, at 15:56, Vincent Snijders wrote:
Marco van de Voort schreef:
Please file a bug anyway, with as much details as possible. It
would be
really great if you could get the "strace" output of the compiler
run in
both cases.
Yes, but where to download strace for win32?
More o
Marco van de Voort schreef:
Please file a bug anyway, with as much details as possible. It would be
really great if you could get the "strace" output of the compiler run in
both cases.
Yes, but where to download strace for win32?
Vincent
___
fpc-pasc
In our previous episode, Carsten Bager said:
> > I doubt it really is a samba problem, more some problem that certain
> > heuristics that cause the libctype detection are somehow different (do you
> > happen to use -Xd on the samba drive?)
>
> Yes and on the local drive. Every thing is the same (I
> I doubt it really is a samba problem, more some problem that certain
> heuristics that cause the libctype detection are somehow different (do you
> happen to use -Xd on the samba drive?)
Yes and on the local drive. Every thing is the same (I copy everything to the
local drive).
>
> Anyway, a
In our previous episode, Carsten Bager said:
> When moving from the 205 compiler to the 222 compiler I have got a strange
> problem with
> the cross compiler for Windows
I suspect this is a bug, or something fixed with newer functionality. Iirc
Florian worked on this (autodetection of glibc type
When moving from the 205 compiler to the 222 compiler I have got a strange
problem with
the cross compiler for Windows
---
(Free Pascal Compiler version 2.2.2 [2008/08/26] for arm)
---
When I compile a project on a Samba drive it works ok.
But when I copy everything (compiler, l
