System Software Overview shows '64-bit Kernel and Extensions: Yes'.
As I said I used to run it with 32-bit but I changed that with a keyboard
combination. In contrast to the other guys from the link you posted I've
successfully installed the 64-bit dmg. But building sage 5.1 from source
code so
On Saturday, 28 July 2012 01:55:13 UTC+8, kfiz wrote:
>
> Hmmh, I have a macbook pro mid 2009, Core 2 Duo. Some Core 2 Duos
> mis-represent themselves as 64 bit? How could I check wether my machine
> does that? It used to run under 32-bit, but than I switched it to 64-bit
> via an official app
Any chance of renaming this thread (says the author of eclib)?!
John
On 27 July 2012 18:55, kfiz wrote:
> Hmmh, I have a macbook pro mid 2009, Core 2 Duo. Some Core 2 Duos
> mis-represent themselves as 64 bit? How could I check wether my machine does
> that? It used to run under 32-bit, but than
Hmmh, I have a macbook pro mid 2009, Core 2 Duo. Some Core 2 Duos
mis-represent themselves as 64 bit? How could I check wether my machine
does that? It used to run under 32-bit, but than I switched it to 64-bit
via an official apple command. The systemprofiler states 64-bit...
Am Freitag, 27. J
On Friday, 27 July 2012 03:56:27 UTC+8, kfiz wrote:
>
> I also use Xcode 3.2.6 (freshly installed) , but building always crashed
> when gcc 4.6.3 was going to be installed on my machine.
> I figured that I could install the gcc package manually, downloaded it
> and ran the installation...with
I also use Xcode 3.2.6 (freshly installed) , but building always crashed
when gcc 4.6.3 was going to be installed on my machine.
I figured that I could install the gcc package manually, downloaded it and
ran the installation...with the same result.
really don't know what the problem is...
Am D
On Thursday, 26 July 2012 14:21:29 UTC+8, kfiz wrote:
>
> Ok, thanks guys. I switched methods and installed with the mac osx
> binaries.
> seems that I have serious issues updating my current gcc compiler.
> guess I'll just have to wait until apple updates xcode.
>
this is strange. I think man
Ok, thanks guys. I switched methods and installed with the mac osx binaries.
seems that I have serious issues updating my current gcc compiler.
guess I'll just have to wait until apple updates xcode.
cheers
doro
Am Mittwoch, 25. Juli 2012 13:08:40 UTC+2 schrieb kfiz:
>
> re-installed XCode. this
re-installed XCode. this time:
/usr/bin/ranlib: archive member: libbackend.a(ude) size too large (archive
member extends past the end of the file)
ar: internal ranlib command failed
make[5]: *** [libbackend.a] Error 1
make[4]: *** [all-stage2-gcc] Error 2
make[3]: *** [stage2-bubble] Error 2
make
I have the newest version of command line tools...but I'll re-download
XCode and try again, just to check.
Am Mittwoch, 25. Juli 2012 11:51:37 UTC+2 schrieb Jeroen Demeyer:
>
> On 2012-07-25 11:32, kfiz wrote:
> > downloaded the source code from source and tried again, and got this:
>
> Weird
On 2012-07-25 11:32, kfiz wrote:
> downloaded the source code from source and tried again, and got this:
Weird, are you sure your XCode setup is up-to-date?
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr.
So this error is occurring in building the gcc spkg, and not eclib.
Hence not my problem...
John Cremona
On 25 July 2012 10:32, kfiz wrote:
> downloaded the source code from source and tried again, and got this:
> (...)
> checking command to parse
> /Applications/sage-5.1/spkg/build/gcc-4.6.3/gc
12 matches
Mail list logo
