On 2015-08-17 14:53, fredvs wrote:
I am very happy to have find the solution.
Well done! I'm glad you finally got it sorted out.
Regards,
- Graeme -
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Well done! I'm glad you finally got it sorted out.
Regards,
- Graeme -
Thanks Graeme.
After trying many fpc releases, install all FreeBSD distros that exist,
re-compiling fpc, changing the background image of desktop, the battery of the
netbook, my haircut, finally it works ...
Happy
On 2015-08-17 15:41, Fred van Stappen wrote:
...changing the background image of desktop, the battery of the
netbook, my haircut, finally it works ...
LOL - I've had many such days, so know exactly how you feel.
Regards,
- Graeme -
___
Hello everybody.
Many, many thank to help.
I have find the guilty. ;-)
This code, in fpc.cfg was the cause of the strange characters: =
# path to the messagefile, not necessary anymore but can be used to override
# the default language
-Fr/usr/local/lib/fpc/$fpcversion/msg/errore.msg
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.
de fredvs
Envoyé : dimanche 16 août 2015 20:17
À : fpc-pascal@lists.freepascal.org
Objet : Re: [fpc-pascal] FreeBSD and fpc messages.
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
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
___
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 =
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 new
Am 16.08.2015 21:17 schrieb Fred van Stappen fi...@hotmail.com:
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
On 12/08/15 22:48, fredvs wrote:
What libraries are used by fpc to render the output messages?
FPC does not use any library. Which language are you using for the messages?
By the way, does it exist a list of all the external dependencies (not the
fpc one) needed to compile a simple fpc
What libraries are used by fpc to render the output messages?
FPC does not use any library. Which language are you using for the messages?
I use the default language (En).
What i do not understand is that, in console, gcc gives messages ok and fpc
only hexa characters.
By the way, does
All it needs is binutils (and in case of i386 and x86-64 on ELF
platforms such as FreeBSD, only the binutils linker).
Hello.
I have try with old binutils but same result.
See attachment.
Thanks.
Fre;D
Hello.
I did a recent update of all libraries in FreeBSD64 to the trunk versions.
Now, all the message given by fpc,while compiling, are no more readable.
The compilation is ok, but all the output message have un-readable
characters.
Changing LANG var did not change anything.
What libraries are
14 matches
Mail list logo
