Juan Jose Garcia-Ripoll wrote:
> It seems that in OS X, when using "gcc" to link the object files into
> an executable, the flag -m64 is needed _again_ to specify that it is a
> 64-bits build. This is regarding David's question in the sage-devel
> group.
>
> Now, this is one of the reasons why ECL does not build on OS X when
> compiling with CFLAGS="-m64" Since the linker needs the -m64 flag, ECL
> is not capable of finding your copy of the MPIR library.
>
> To avoid this problem, ECL now understands an ABI=64 configuration
> option. It only works with OS X but it does not hurt other ports.
>
> There were other problems, though, which involve misusing the C
> calling conventions. This can be done for Intel/32 bits ABI, but not
> in other modes. Since OS X misidentifies the operating system as 32
> bits (uname -a), ECL was thinking it could use this optimization. I
> have changed it.
>
> Now ECL builds on my MacBook using ABI=64
>
> Juanjo
>
I do not believe there is any linker flag '-m64' on OS X. If there is,
it is not documented in the man page.
[kir...@bsd ~]$ man ld | grep 64
Specifies which architecture (e.g. ppc, ppc64, i386,
x86_64)
is 4KB. On 64-bit architectures, the default size if 4GB.
The ppc64 architecture has some special cases. Since
Mac OS X
zero size for ppc64 will be 4KB unless
-macosx_version_min is
ppc64 will only work if the code is placed in the
lower 2GB
I'll try setting ABI=64 and trying that.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
