Dr. David Kirkby wrote:
Jaap Spies wrote:
Dr. David Kirkby wrote:
Jaap Spies wrote:
Dr David Kirkby wrote:
From what I have read of the GNU linker documentation on the linker
'ld'
http://sourceware.org/binutils/docs-2.20/ld/Options.html#Options
there is no such flag as -m64. So I can't understand how it works.
(There is an opton -64 on the Sun linker, but it rarely needed).
Can you explain this?
There are spkgs which use g++ as linker, e.g. givaro, linbox.
Jaap
But I don't understand why that should make any difference, as
ultimately g++ will call the linker.
g++ needs the -m64 flag to produce a 64 bit shared library.
Jaap
I can understand why g++ would need it, but LDFLAGS gets passed to the
linker, so I assume that is to 'ld'. Or perhaps I am considering the
linker in a too restrictive sense. To me the linker is 'ld'.
I hope there's not going to be a rule to call 'ld' directly to do
linking in SPKGs, that would be a nightmare... to me it makes sense to
pass LDFLAGS to whatever linker should be used. That would match e.g.
Python distutils:
sage: distutils.sysconfig.get_config_var('LDSHARED') # the linker
command to use for linking extension modules
sage: 'gcc -pthread -shared'
sage: distutils.sysconfig.get_config_var('LDFLAGS') # linker flags to
use for linking extension modules
sage: '-L/mn/corcaroli/d1/dagss/sage-4.3/local/lib'
Dag Sverre
--
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
URL: http://www.sagemath.org
