Alright, its compiling! It was wrong path in fpc.cfg. The DEB
installation creates a directory structure under the fpc directory that
matches this:
/lib/fpc/3.1.1/units/$fpctarget
Thanks again!
On 08/16/2017 11:22 PM, Tomas Hajny wrote:
On Wed, August 16, 2017 23:08, kapibara via fpc-pascal
To be sure fpc.cfg is found I started the compilation from fpc's bin
directory where the fpc.cfg is located.
roger@bikupan:~/fpc/fpc_svn/
bin$ ./fpc /home/roger/fpc/fptest_working/fptest.pas
Free Pascal Compiler version 3.1.1 [2017/08/16] for x86_64
Copyright (c) 1993-2015 by Florian Klaempfl an
On Wed, August 16, 2017 23:08, kapibara via fpc-pascal wrote:
> The old SVN version is now in play, so far so good! But then "Can't find
> unit system" happened:
You need RTL (and other required units, e.g. from packages) compiled with
that compiler version and provide path to it either using fpc.
The old SVN version is now in play, so far so good! But then "Can't find
unit system" happened:
roger@bikupan:~/fpc/fptest_working$ fpc fptest.pas
Free Pascal Compiler version 3.1.1 [2017/08/16] for x86_64
Copyright (c) 1993-2015 by Florian Klaempfl and others
Target OS: Linux for x86-64
Compili
You're right, now I fixed that and "which fpc" reports the SVN version!
On 08/16/2017 10:15 PM, Tomas Hajny wrote:
On Wed, August 16, 2017 21:15, kapibara via fpc-pascal wrote:
I meant to say that system fpc is put AFTER the SVN fpc in the path.
Due to the missing slash at the beginning of th
On Wed, August 16, 2017 22:16, kapibara via fpc-pascal wrote:
> Ah, so FP has no versions other than the official releases then? (2.6.0,
> 2.6.2, 2.6.4 and so on)
>
> Why doesn't FP use the same compiler revision as the SVN sources it
> comes with? Because the fp executable is compiled at the same
On Wed, August 16, 2017 21:15, kapibara via fpc-pascal wrote:
> I meant to say that system fpc is put AFTER the SVN fpc in the path.
Due to the missing slash at the beginning of the PATH value? ;-)
Obviously, that only answers the reason of the 'which fpc' command,
whereas the compiler version use
Ah, so FP has no versions other than the official releases then? (2.6.0,
2.6.2, 2.6.4 and so on)
Why doesn't FP use the same compiler revision as the SVN sources it
comes with? Because the fp executable is compiled at the same time as fpc?
Alright then, I'll try instead:
fpc test.pas
Btw,
In our previous episode, kapibara via fpc-pascal said:
>
> I want to use the fp editor to run the test, but it seems as the
> "systemic" 2.6.4 is being used for compiling instead of the SVN version.
Then you use a 2.6.4 FP. FP does not call the compiler, it has an own
version of it internally.
I meant to say that system fpc is put AFTER the SVN fpc in the path.
On 08/16/2017 09:09 PM, kapibara wrote:
PATH=home/roger/fpc/fpc_svn/bin:/home/roger/fpc/fpc_svn/compiler:/usr/local/bin:/usr/bin:/bin
export
PATH=home/roger/fpc/fpc_svn/bin:/home/roger/fpc/fpc_svn/compiler:/usr/local/bin:/us
For debugging reasons I have installed fpc 2.6.4 on Debian so I can
compile some old SVN revisions, number 32959 for example.
I want to use the fp editor to run the test, but it seems as the
"systemic" 2.6.4 is being used for compiling instead of the SVN version.
The bug doesn't show up in 2.6
11 matches
Mail list logo
