On Sep 9, 12:13 pm, "Dr. David Kirkby"
wrote:
> I think the issue is that gcc is not such a good linker as 'ld'.
I really do not care. The important thing is: if you use a particular
C compiler, it is most likely that you will have to use that compiler
for linking. This was pointed out before in
Juanjo wrote:
>
> On Sep 8, 8:18 pm, David Kirkby wrote:
>> If CFLAGS is not being passed to the compiler (which is what I thought
>> before), and LDFLAGS is passed to the compiler, then this could
>> explain why you need to set LDFLAGS.
>
>>From Autoconf manual:
>
> If a compiler option affec
On Sep 8, 8:18 pm, David Kirkby wrote:
> If CFLAGS is not being passed to the compiler (which is what I thought
> before), and LDFLAGS is passed to the compiler, then this could
> explain why you need to set LDFLAGS.
>From Autoconf manual:
If a compiler option affects only the behavior of the
Hi guys,
hopefully we're getting closer to the root of the misunderstanding(s)
here. Under Mac OS X, things might not be as you expect them to be,
given that "gcc" (or some version of it) is used. I've tried to help a
bit with libSingular in the past, from there my experience stems from.
Let's s
2009/9/8 Juanjo :
>
> On Sep 8, 2:36 pm, David Kirkby wrote:
>> I will be impossible to convince!!!
>> I have no problem accepting the *compiler* needs -m64. That option
>> tells the *compiler* to create 64-bit object files. But once the
>> linker is asked to link the object files, it should be a
X-D
On Sep 8, 6:21 pm, William Stein wrote:
> On Tue, Sep 8, 2009 at 9:15 AM,
>
>
>
>
>
> Juanjo wrote:
>
> > On Sep 8, 2:36 pm, David Kirkby wrote:
> >> I will be impossible to convince!!!
> >> I have no problem accepting the *compiler* needs -m64. That option
> >> tells the *compiler* to crea
On Tue, Sep 8, 2009 at 9:15 AM,
Juanjo wrote:
>
> On Sep 8, 2:36 pm, David Kirkby wrote:
>> I will be impossible to convince!!!
>> I have no problem accepting the *compiler* needs -m64. That option
>> tells the *compiler* to create 64-bit object files. But once the
>> linker is asked to link the
On Sep 8, 2:36 pm, David Kirkby wrote:
> I will be impossible to convince!!!
> I have no problem accepting the *compiler* needs -m64. That option
> tells the *compiler* to create 64-bit object files. But once the
> linker is asked to link the object files, it should be able to work
> out whether
>> > 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.
>>
>> Can you show me where it is documented that the linker has a '-m64' flag?
>
> Dav
On Sep 8, 7:38 am, "Dr. David Kirkby" wrote:
> 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-deve
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 EC
On Mon, Sep 7, 2009 at 8:12 AM, Dr. David Kirkby wrote:
> I created a new .spkg file:
>
> http://sage.math.washington.edu/home/kirkby/Solaris-fixes/ecl-9.8.4.p0-4th-attempt/ecl-9.8.4.p0.spkg
>
> which sets the ABI, but I get an odd error. See below.
> if (echo c gc gmp | grep gmp); then \
>
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 EC
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 EC
14 matches
Mail list logo
