You FPC/lazarus guys ROCK.
md
On 3/10/2014 10:12 PM, Mattias Gaertner wrote:
On Mon, 10 Mar 2014 20:18:38 -0400
"m...@rpzdesign.com" wrote:
Jonas:
Where in Lazarus 1.0.14 do I put in the compiler command line option?
-WM10.9
Project Options->Compiler Options->Compilation->Compiler->Command
On Mon, 10 Mar 2014 20:18:38 -0400
"m...@rpzdesign.com" wrote:
> Jonas:
>
> Where in Lazarus 1.0.14 do I put in the compiler command line option?
> -WM10.9
>
> Project Options->Compiler Options->Compilation->Compiler->Command
No, that's the path to the compiler, no extra options.
> -WM10.9
Jonas:
Where in Lazarus 1.0.14 do I put in the compiler command line option?
-WM10.9
Project Options->Compiler Options->Compilation->Compiler->Command->
$(CompPath) -WM10.9
And when I use this setting -WM10.9, this means that I can only execute
the resulting binary on Mavericks and above
On 10 Mar 2014, at 19:07, m...@rpzdesign.com wrote:
Unfortunately, your suggestion while appreciated does not work.
For example, the actual function "__divdi3" actually lives in
/usr/lib/system/libcompiler_rt.dylib
This library does not exist on Snow Leopard. But it does exist on
Mavericks
Peter:
I must use some form of {$LINKLIB gcc}
{$LINKLIB c} still WORKS under OSX 10.9
{$LINKLIB gcc} does not work user OSX 10.9 Mavericks.
"__divdi3" unresolved reference lives in the gcc run time library chain.
md
On 3/10/2014 11:21 AM, Peter Brooks wrote:
Why are you wanting to us
Jonas,
Unfortunately, your suggestion while appreciated does not work.
For example, the actual function "__divdi3" actually lives in
/usr/lib/system/libcompiler_rt.dylib
This library does not exist on Snow Leopard. But it does exist on
Mavericks. (I do not have Lion/Mtn Lion available)
{$
Why are you wanting to use gcc instead? If I wanted to do this, I'd
just replace c with a link to gcc.
On 10 March 2014 16:14, m...@rpzdesign.com wrote:
> Peter:
>
> I was surprised too. That is why I broadcast the alarm to the FPC
> community.
>
> I am running FPC 2.6.2 - Lazarus 1.0.14
>
> Ye
Peter:
I was surprised too. That is why I broadcast the alarm to the FPC
community.
I am running FPC 2.6.2 - Lazarus 1.0.14
Yes, I can recompile FPC from scratch on Mavericks.
I can compile perfectly well on Mavericks too.
No, I cannot issue the {$LINKLIB gcc } command on Mavericks OSX 10.9
On 10 Mar 2014, at 05:15, m...@rpzdesign.com wrote:
> After diving deeply into the dependency tree,
>
> there are 2 libraries that are involved in this particular problem:
>
> /usr/lib/libSystem.B.dylib
> /usr/lib/libgcc_s.1.dylib
>
> But I cannot figure out yet how to call up the libgcc_s.1.d
I'm a bit surprised. As it happens, just this week I compiled the fpc
compiler from scratch on Mavericks. It worked perfectly well, and is
compiling perfectly well - version 2.6.0.
I was wondering, though, whether there was any enhanced support for
features on the Intel 'Sandy-Bridge' and 'Ivy-Bri
After diving deeply into the dependency tree,
there are 2 libraries that are involved in this particular problem:
/usr/lib/libSystem.B.dylib
/usr/lib/libgcc_s.1.dylib
But I cannot figure out yet how to call up the libgcc_s.1.dylib
{$LINKLIB /usr/lib/gcc [many variations tried] }
The mystery c
Now that OSX Mavericks 10.9 is running full speed, it has broken the
{$LINKLIB gcc} compiler directive.
{$LINKLIB c} still WORKS.
But {$LINKLIB gcc} does not.
The reason is that Mavericks does not use GCC any more, it is using clang,
a new compiler.
So now Freepascal users need to know how to r
12 matches
Mail list logo
