Hi All,
I noticed a strange behavior with the following program:
program tt;
{$mode objfpc}{$H+}
uses sysutils;
var
res: Integer;
mask1, mask2: QWord;
begin
mask1 := $ shr 24;
WriteLn(IntToHex(mask1, 16));
res := 24;
mask2 := $ shr res;
WriteLn(IntToH
On 2015-08-16 20:16, Fred van Stappen wrote:
> Aaargh, I have to take a rest...
Why don't you start again. Remove all copies of FPC, no matter the
versions. Remove all copies of the fpc.cfg too. Look in /usr/local/etc
and $HOME.
Then download the official FPC release install:
http://sourceforg
Am 16.08.2015 21:17 schrieb "Fred van Stappen" :
>
> Re-re- hello Pierre,
>
> Aaargh, I have to take a rest...
>
> No, the image is ok, first command use full path to compiler (and message
are not ok) and second command use full path of the symlink to compiler.
>
> So, to resume (and sorry for all
Re-re- hello Pierre,
Aaargh, I have to take a rest...
No, the image is ok, first command use full path to compiler (and message are
not ok) and second command use full path of the symlink to compiler.
So, to resume (and sorry for all this doubts):
Using full path to compiler to run it, like =>
Re-hello Pierre.
Oops, indeed, sorry for previous post, both commands are using full path in
image.
I have to recheck all, clean everything to know what was wrong and where.
Write you later.
Fre;D
___
fpc-p
Hello Pierre and thank to help.
> Did you notice that the date of compilation is also different
> in both cases...
>
> Are you really sure that the symlink points to the same file?
Bien vu ! (well seen).
Indeed. Before to find the "trick", i have installed many different fpc
version, compiled
Did you notice that the date of compilation is also different
in both cases...
Are you really sure that the symlink points to the same file?
If this is true, it probably means that it reads a different
configuration file in both cases.
Try using -va to activate all debug output,
and look
Ok, I get it (but it was a hard battle before to find it).
If in console =>
# /usr/local/lib/fpc/2.6.4/ppcx64 myprog.pas
=> messages not readable. ;-(
if creating a symlink to ppcx64 in /usr/local/bin
then in console =>
# ppcx64 myprog.pas
=> messages readable. ;-)
See image in attachment.
On Sunday 16 August 2015 15:14:23 Chris Moody wrote:
>
> Thanks for that Martin, my app is actually just console based (I used
> Lazarus because I didn't want to use the text based IDE), would you
> still recommend this route?
>
Sure. MSEide opens on the X86 PC a xterm where the gdb remote session
On 08/15/2015 11:37 PM, Martin Schreiber wrote:
On Sunday 16 August 2015 02:33:24 Chris Moody wrote:
Hi all,
I think my project is almost done, wanted to see how fast it ran under
the Pi which its destined to be on. After spending a long time trying to
get it to compile there I decided I'd se
10 matches
Mail list logo