[fpc-pascal] MacOSX Mojave
mail at michael-ring.org
Tue Oct 9 21:06:28 CEST 2018
Until now you could compile trunk without such specific opts, so making
OPT= something mandatory for future builds of trunk to work at all does
not sound like a good plan to me.
and no, at least in my installation there are no crt1* files in
/usr/lib, if there were any we would not have this discussion here ;-)
I am not trying to solve something for myself, my own builds are working
for quite a long time on Mojave, just wanted to make sure that compiling
trunk keeps as straightforward as ever....
Am 09.10.18 um 19:51 schrieb Jonas Maebe:
> On 08/10/18 23:19, Michael Ring wrote:
>> I just realized on a freshly set up computer that there is one more
>> issue, I tried to build the trunk x86_64 compiler and compile fails:
>> /bin/mkdir -p x86_64/units/x86_64-darwin
>> /Applications/Xcode.app/Contents/Developer/usr/bin/make ./msg2inc
>> /usr/local/bin/ppcx64 -Ur -Xs -O2 -n -Fux86_64 -Fusystems
>> -Fu/Users/ring/devel/fpc/rtl/units/x86_64-darwin -Fix86_64 -FE.
>> -FUx86_64/units/x86_64-darwin -dRELEASE -dx86_64 -dGDB
>> -dBROWSERLOG -Fux86 -Sew -FE. utils/msg2inc.pp
>> ld: file not found: /usr/lib/crt1.10.5.o
>> An error occurred while linking
>> msg2inc.pp(822,51) Error: Error while linking
>> msg2inc.pp(822,51) Fatal: There were 1 errors compiling module, stopping
>> Fatal: Compilation aborted
>> problem is that ppcx64 is called with option -n so fpc.cfg gets ignored.
>> I guess the only way to fix this is to change the makefile itself.
> As Colin mentioned, you can pass the necessary options to make via
> OPT="-option1 -option2"
>> Also, one thing I do not understand in /etc/fpc.cfg installed by the
>> 3.0.4a installer, why if -Fl ifdef'ed for i386 only?
>> #ifdef cpui386
> It's because the necessary files for x86-64 can be found in /usr/lib,
> where the compiler looks by default.
> fpc-pascal maillist - fpc-pascal at lists.freepascal.org
More information about the fpc-pascal