Am 06.03.2012 18:10, schrieb Abou Al Montacir:
On Tue, 2012-03-06 at 17:44 +0100, Lutz Lehmann wrote:
> Am 06.03.2012 17:15, schrieb Abou Al Montacir:
> > On Tue, 2012-03-06 at 16:21 +0100, Lutz Lehmann wrote:
> > FPCDIR=/usr/lib/fpc/ fpcmake-2.6.0 -v -w
> Sorry, didn't work in my installation. Same error.
Sorry, but I've copyed the wrong line :(
FPCDIR=/usr/lib/fpc/2.6.0 fpcmake -v -w
Indeed, that works. Thank you.
Indeed, the FPCDIR is versioned to allow multiple tool chains to coexist
And at the same time, that seems to be the root of the problem. From
educated
speculation I would assume that the FPCDIR is determined such that the
binary
"ppc386" resides therein. If this fails for the given environment
variable or it is
not given at all, "/usr/bin/ppc386" is assumed to be a link to the
library directory
and resolved, but only once, and not recursively.
But since the introduction of the alternatives mechanism "to allow
multiple tool chains to coexist",
the destination of "/usr/bin/ppc386" is "/etc/alternatives/ppc386". For
some reason, probably
because it was not necessary before, this is not checked to be a link as
well, so the wrong path "/etc/alternatives" results. The proper way
would be to resolve the links repeatedly
until the destination is not a link.
Anyway fpcmake is becoming obsolete, upstream is now pushing fpmake.
Hopefully, this acts more intelligently for the library path determination.
Regards, Lutz Lehmann
