Forum > Linux

What is the difference between fpc and ppcx64 ?

<< < (2/2)

MarkMLl:

--- Quote from: lazer on October 20, 2022, 04:08:08 pm ---OK we'll call that a draw on the silly mistakes !  :D

Thanks for the explanations.

--- End quote ---

I'm not sure of the developers' position on this, but my experience is that the fpc wrapper is backward-compatible (i.e. works reliably with versions of ppc* significantly older than itself) and that it's fairly happy if ppcx64 etc. is symlinked to e.g. ppcx64-3.2.2 which is itself symlinked to /usr/local/lib/fpc/3.2.2/ppcx64. This is also compatible with the fpc -V option, although whether that works reliably is patchy.

Apart from fpc, fp and fpcres all the binaries that would normally have gone into /usr/local/bin are actually in e.g. /usr/local/bin/fpc.d/3.2.2

Both the above are with the caveat that I adopted that convention a significant number of years ago, and more recent "official" alternatives might be more reliable.

MarkMLl

marcov:

--- Quote from: MarkMLl on October 20, 2022, 10:30:41 pm ---
--- Quote from: lazer on October 20, 2022, 04:08:08 pm ---OK we'll call that a draw on the silly mistakes !  :D

Thanks for the explanations.

--- End quote ---

I'm not sure of the developers' position on this, but my experience is that the fpc wrapper is backward-compatible (i.e. works reliably with versions of ppc* significantly older than itself) and that it's fairly happy if ppcx64 etc. is symlinked to e.g. ppcx64-3.2.2 which is itself symlinked to /usr/local/lib/fpc/3.2.2/ppcx64. This is also compatible with the fpc -V option, although whether that works reliably is patchy.

--- End quote ---

No guarantee on it, but using an older "fpc" binary isn't the riskiest thing to do.  I've used -V myself for years, and never found much problems with it (it simply appends the argument to the formed (-P) binary name )
 

--- Quote ---Apart from fpc, fp and fpcres all the binaries that would normally have gone into /usr/local/bin are actually in e.g. /usr/local/bin/fpc.d/3.2.2

Both the above are with the caveat that I adopted that convention a significant number of years ago, and more recent "official" alternatives might be more reliable.

--- End quote ---

fp contains the ppc* compiler so that policy is on shaky grounds philosophically.

MarkMLl:

--- Quote from: marcov on October 20, 2022, 10:45:03 pm ---No guarantee on it, but using an older "fpc" binary isn't the riskiest thing to do.  I've used -V myself for years, and never found much problems with it (it simply appends the argument to the formed (-P) binary name )

--- End quote ---

In practice I copy over the newest, hence my comment about it being backward compatible.
 

--- Quote ---fp contains the ppc* compiler so that policy is on shaky grounds philosophically.

--- End quote ---

Thanks, I hadn't spotted that. In practical terms I tend not to use it.

MarkMLl

marcov:
Also fpcres might be safer on the longer term, but currently still mutates heavily and might contain bugfixes important to lazarus.

MarkMLl:

--- Quote from: marcov on October 21, 2022, 09:55:35 am ---Also fpcres might be safer on the longer term, but currently still mutates heavily and might contain bugfixes important to lazarus.

--- End quote ---

Yes, and as I said that's one of the few binaries I copy over.

MarkMLl

Navigation

[0] Message Index

[*] Previous page

Go to full version