[fpc-pascal] Issues with fpc-build-3.0.0

Tony Whyman tony.whyman at mccallumwhyman.com
Fri Jan 29 14:49:20 CET 2016

I am not convinced that it is a good idea for the default install to 
result in a broken system.

Wouldn't it be better to have a "NOSYMLINK" environment variable instead 
to handle the developer versions? Failing that a "README" file giving 
basic build instructions could be useful or a final message on install 
completion saying something like "Now run make -C complier 
installsymlink to complete the installation".

BTW, the most up-to-date instructions I have been able to find on 
building fpc from source is buried in the wiki under a page titled 
"Installing Lazarus", and that suggests creating the symlink manually.

On 29/01/16 13:35, Jonas Maebe wrote:
>>> The symlink is only installed with the installsymlink make target in 
>>> the compiler directory.
>> Why?
> Because "make install" is often used to install development versions 
> of FPC, and the you don't necessarily want it to change the default 
> compiler version at the same time.

More information about the fpc-pascal mailing list