On 2011-02-03 15:02, Volker Braun wrote:
> Use "make distclean" to evict every file than doesn't pay rent. The next
> "make" will compile everything from scratch.
This might be true, but I still agree with Dima that "make clean" should
also clean all spkgs.
--
To post to this group, send an emai
On 02/ 2/11 04:50 PM, Volker Braun wrote:
On Wednesday, February 2, 2011 3:55:27 PM UTC, Dr. David Kirkby wrote:
There is never any point in setting SAGE64=no. [...] ONLY if it is set
to "yes" will anything different happen. That is usually adding the
compiler flag "-m64", though in some cases
Use "make distclean" to evict every file than doesn't pay rent. The next
"make" will compile everything from scratch.
--
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,
On Wednesday, February 2, 2011 7:52:08 PM UTC, John H Palmieri wrote:
>
> if [ "$SAGE64" = "yes" ]; then
>echo "64 bit build"
>CFLAGS="-O2 -g -fPIC -m64 "; export CFLAGS
>LDFLAGS="-m64"; export LDFLAGS
> fi
>
Just overwrite CFLAGS/LDFLAGS, no ap/prepending? Nice.
if [ "x`uname -sm`" =
On Wednesday, February 2, 2011 8:50:36 AM UTC-8, Volker Braun wrote:
>
> Dave, can you elaborate on what SAGE64 is good for besides adding -m64?
> Adding the compiler flag could easily be done in the gcc wrapper:
>
> http://trac.sagemath.org/sage_trac/ticket/10572
>
> Sorry if this is slightly O
On Wednesday, February 2, 2011 3:55:27 PM UTC, Dr. David Kirkby wrote:
>
> There is never any point in setting SAGE64=no. [...] ONLY if it is set
> to "yes" will anything different happen. That is usually adding the
> compiler flag "-m64", though in some cases it's a bit more complex.
>
Dave, can y
On 1 February 2011 20:17, jtyard wrote:
> Thanks Georg,
>
> Before I posted my question, I had tried an earlier build with
> SAGE64="yes", but (of course) that didn't work and I received the same
> error that I posted. Then I had set SAGE64="no", tried again and got
> the same error.
There is ne
Dima,
It looks like it is getting set pretty early, so I'm just posting here
the beginning of the install.log, rather than the whole huge file.
But it sounds to me that somehow the problem is that "make clean"
leaves too much behind. For instance, it seems to want to start
building r right away,
Thanks Georg,
Before I posted my question, I had tried an earlier build with
SAGE64="yes", but (of course) that didn't work and I received the same
error that I posted. Then I had set SAGE64="no", tried again and got
the same error. I then ran "make clean" and got the same error. I
even reboote
It would be useful if you put the complete install.log somewhere, so
that one could see where the 64-bit setting comes from...
On Jan 29, 7:02 am, Jon Yard wrote:
> Hello,
>
> I am having trouble building sage 4.6.1 on an iMac8,1 (2.4 GHz Intel Core 2
> Duo) running OS X 10.5.8. Below is the las
Hmm,
the important information seem to be:
a)
You try to build Sage on Mac OS X 10.5 (Leopard).
b)
There's a "-m64" in the third line of your output, i.e. the build
system tries to build a "64-bit" library.
(Then it seems that qdCocoa.o is only a 32-bit object file, hence
rejected, hence later s
11 matches
Mail list logo
