On 24/12/2020 17:52, Joubert Nel via fpc-devel wrote:
> When I delete the "fpc.cfg" file in my compilation directory, the
> problem goes away.
> The same error occurs if I have an ".fpc.cfg" file in my home directory
> so I avoid that too.
Add the following line at the start of your custom
I've run into the same issue, but under different circumstances.
In some sense, my scenario is simpler: I'm not compiling FPC, just
compiling my own project.
Able to work around it for my particular case and thought I'd share in case
it helps others.
SCENARIO
When I have an "fpc.cfg" file in the
On 15/11/2020 17:16, Karoly Balogh (Charlie/SGR) via fpc-devel wrote:
> e neither, but it's been like that ever since I upgrade to Mojave, that
> these libs and objects are no longer in /usr/lib on my system. I used
> Sierra on the same machine before, and that worked, then I updated to
> Mojave
Hi,
On Sun, 15 Nov 2020, Jonas Maebe via fpc-devel wrote:
> On 15/11/2020 15:19, Karoly Balogh (Charlie/SGR) via fpc-devel wrote:
> >
> > Yes, I already had to dothis in my build scripts on Mojave. I defined an
> > "FIXMOJAVE" environment var, which contains that -XR/Library/... path you
> >
On 15/11/2020 15:19, Karoly Balogh (Charlie/SGR) via fpc-devel wrote:
>
> Yes, I already had to dothis in my build scripts on Mojave. I defined an
> "FIXMOJAVE" environment var, which contains that -XR/Library/... path you
> wrote above, and in all my build scripts I just do:
>
> make
Hi,
On Sun, 15 Nov 2020, Jonas Maebe via fpc-devel wrote:
> > my Macs that the timestamp of that file changed), but this will not help
> > for compiling the compiler as the compiler is beeing compiled with the
> > flag -n which effectively turns off reading /etc/fpc.cfg.
>
> Indeed, I glossed
On 14/11/2020 16:51, Michael Ring via fpc-devel wrote:
> Hi Jonas, thank you for your answer!
>
> I cannot say if I did see a warning or not when installing fpc-package
> but I did not reinstall commandline tools before or after installing the
> 3.2.0 compiler. They have been on all of my Macs
Hi Jonas, thank you for your answer!
I cannot say if I did see a warning or not when installing fpc-package
but I did not reinstall commandline tools before or after installing the
3.2.0 compiler. They have been on all of my Macs for years.
What are you doing in the installer that creates
On 2020-11-14 11:03, Michael Ring via fpc-devel wrote:
> I recently upgraded to Big Sur on two devices and tried to compile
> trunk based on official 3.2.0 compiler freshly downloaded from
> sourceforge but compilation fails:
That looks like you did not install the Xcode command line tools
Problem is more simple, path to SDK tools is missing in linker script:
-arch
x86_64
-macosx_version_min
10.8
-L/usr/lib/
-L./x86_64/
-L./systems/
-L/Users/ring/devel/fpc/rtl/units/x86_64-darwin/
-L./x86/
-L/usr/local/bin/
*-L/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/lib/*
-lc
I recently upgraded to Big Sur on two devices and tried to compile trunk
based on official 3.2.0 compiler freshly downloaded from sourceforge but
compilation fails:
make all
/usr/local/bin/ppcx64 -Ur -Xs -O2 -n -Fux86_64 -Fusystems
-Fu/Users/ring/devel/fpc/rtl/units/x86_64-darwin
11 matches
Mail list logo
