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: > > > > This is because /usr/lib/fpc is not a valid FPCDIR path > > > > How is that, since it is used below? > >> Please check if there is something like a reference to the path of > >> args[0] hard-coded in the sources or build script. > > I'll have a look to that soon. For now I have a quick workaround that I > > tested is working: > > 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, the FPCDIR is versioned to allow multiple tool chains to coexist > 2.4.4 was freshly installed, already with this problem, then recently > updated to 2.6.0. Is there something that could > be cleaned up or reconfigured? > Some lazarus bugs seem to have the same problem, rtl not found by > fpcmake. Their workaround was to remove fpcmake from the compilation chain. Anyway fpcmake is becoming obsolete, upstream is now pushing fpmake.
Cheers,
signature.asc
Description: This is a digitally signed message part
