On 17 Jul 2012, at 07:15, Sergei Gorelkin wrote:
I'm afraid this isn't entirely correct. The problems arise when using -n in
the command line (one example is compiling fpmake for packages directory). In
this case any paths from fpc.cfg are ignored. Moreover, compiler silently
ignores the
Sven Barth schrieb:
Am 11.07.2012 16:36, schrieb Konstantin:
Hello!
Free Pascal has been designed to run on several platforms on many
architectures which is a neat feature. The executable name is chosen
accordingly - ppc386, ppcx64 etc. to be able to have many at the same
time on the same
On 17 Jul 2012, at 00:36, Konstantin wrote:
The bad thing is
that these paths are determined by the FPC function
librarysearchpath.FindFile and as this function does not honor the
target architecture. It always returns /usr/lib/. as the default
architecture version of these files is
17.07.2012 2:51, Jonas Maebe пишет:
On 17 Jul 2012, at 00:36, Konstantin wrote:
The bad thing is
that these paths are determined by the FPC function
librarysearchpath.FindFile and as this function does not honor the
target architecture. It always returns /usr/lib/. as the default
Hello!
Free Pascal has been designed to run on several platforms on many
architectures which is a neat feature. The executable name is chosen
accordingly - ppc386, ppcx64 etc. to be able to have many at the
same time on the same system. When building from source it
Am 11.07.2012 16:36, schrieb Konstantin:
Hello!
Free Pascal has been designed to run on several platforms on many
architectures which is a neat feature. The executable name is chosen
accordingly - ppc386, ppcx64 etc. to be able to have many at the same
time on the same system. When building
