> On 22/10/2015, at 0819, Christian Nassau wrote:
>
> On 21.10.2015 21:11, John H Palmieri wrote:
>> The latest beta version of Sage should build on OS X 10.11. It has a serious
>> limitation: you can't move the installation once it has been built. I don't
>> know if anyone is working on fixing
On 10/06/2014, at 1738, john_perry_usm wrote:
>
> Mavericks is up-to-date; extra packages installed. I'm not finding an option
> for "command-line tools" in Preferences->Downloads as per the README,
Here's your problem - you're reading the readme in the wrong place (this is the
ML instructions
On 10/06/2014, at 1738, john_perry_usm wrote:
>
> Right now I'm reinstalling Xcode from scratch, in the hope that this will fix
> it (as opposed to using the Xcode upgrade made when upgrading from 10.6 to
> Mavericks). If that works, I'll report it.
That might work.
You need to get the latest
On 9/05/2014, at 2005, Oskar Till wrote:
>
> Maybe I should try and build from source then. How do I uninstall the version
> I have now, is it enough to just drag the Applications/sage folder into the
> trash?
Yes.
--
You received this message because you are subscribed to the Google Groups
On 28/04/2014, at 1809, Andrew wrote:
>
> sh: line 1: 45940 Trace/BPT trap: 5
> /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk / -find
> strip 2> /dev/null
> xcrun: error: unable to find utility "strip", not a developer tool or in PATH
> install: child process failed:
On 20/04/2014, at 0853, Justin C. Walker wrote:
>
> it means that you can't. I don't recall when Apple stopped supporting
> Rosetta (the mechanism used to run PPC code on x86 CPUs). It's available on
> 10.6, but it's definitely not on 10.9 (Mavericks).
10.7.
--
You received this message be
On 21/03/2014, at 1751, Andrew wrote:
>
> As far as I can see sage is compiling and running on mavericks. From those
> who have made the switch,would you recommend upgrading to mavericks?
Yes.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
On 21/01/2014, at 0312, Volker Braun wrote:
>
> I'd also like to know what the expectations for the OSX binaries are. Why are
> there two separate ones to start with? Should I change something in how they
> are built?
One (the non-app version) is just built the "normal" way - get the source co
On 16/11/2013, at 2126, Jeroen Demeyer wrote:
>
> On 2013-10-23 02:48, yomcat wrote:
>>
>>
>> On Wednesday, 23 October 2013 10:48:00 UTC+13, yomcat wrote:
>>
>>
>>
>>On Wednesday, 23 October 2013 10:04:57 UTC+13, yomcat wrote:
>>
>>
>>I'll go hunting for dev tools.
>>
>>
>>
On 23/10/2013, at 1936, Jeroen Demeyer wrote:
> Can you build Sage with MAKE="make -k"? This will force the build to continue
> as much as possible, even if some package fails. Please report which other
> packages (if any) fail to build.
It's finished:
The following package(s) may have faile
On 24/10/2013, at 0701, John H Palmieri wrote:
> - You might also need to manually install the command-line tools: from the
> terminal, run
>
> xcode-select --install
>
> and click "Install" in the pop-up. (I don't know if this step is required,
> but I did it.)
This step is required, but
On 25/05/2013, at 1:09 AM, William Stein wrote:
>
> And it has 100% doctest coverage. (It does, right?)
Yes, it does. We made sure of that before submitting.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and st
On 3/05/2013, at 9:08 PM, Jeroen Demeyer wrote:
>
> Patch ready at http://trac.sagemath.org/sage_trac/ticket/14521
In order to review, do I need to run it on 10.4? (I'm new to this stuff)
NSInteger is just a pointer to int/long, so I don't see any problems with it...
Michael
--
You received
On 20/04/2013, at 8:13 AM, Jean-Pierre Flori wrote:
> On Friday, April 19, 2013 8:58:15 PM UTC+2, yomcat wrote:
>>
>> On 20/04/2013, at 4:43 AM, Jean-Pierre Flori >
>> wrote:
>>> Dear all,
>>>
>>> We are currently updating the "install from source" doc at #14465, but
>> I'm
>>> a little los
On 20/04/2013, at 4:43 AM, Jean-Pierre Flori wrote:
> Dear all,
>
> We are currently updating the "install from source" doc at #14465, but I'm
> a little lost about what to say for Mac OS X, see
> http://trac.sagemath.org/sage_trac/ticket/14465#comment:4.
> It has been previously stated that th
On 13/02/2013, at 11:09 AM, Ivan Andrus wrote:
> On Feb 12, 2013, at 2:17 PM, Michael Welsh wrote:
>
>> On 13/02/2013, at 9:53 AM, kcrisman wrote:
>>> Hi! Thanks to very hard work by Ivan Andrus, we have Sage double-clicking
>>> sws files on Mac. We just
On 13/02/2013, at 9:53 AM, kcrisman wrote:
> Hi! Thanks to very hard work by Ivan Andrus, we have Sage double-clicking
> sws files on Mac. We just need one more test to make it complete.
>
> If you DO have OS X 10.8 Mountain Lion but have NOT ever made something
> that makes sws files open wi
On 13/02/2013, at 9:53 AM, kcrisman wrote:
>
> We particularly would like people who don't even have
> Sage.app to try this, since with multiple versions of Sage.app there can be
> natural confusion as to which one is supposed to open the file, though in
> principle this should work there as w
On 1/02/2013, at 8:19 AM, kcrisman wrote:
>
> Sounds viable to me. Any other ideas? Presumably this can be considered a
> problem, since we want people who know nothing about App Store prefs
> downloading Sage :)
IIRC, the default setting is "MAS and registered developers", so we could
theo
On 13/11/2012, at 4:16 PM, Nils Bruin wrote:
>
> Incidentally: Are PPC-OSX4 (or where-ever the problem earlier arose)
> and i686 both 32 bit platforms?
Yes.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sa
On 16/10/2012, at 7:17 PM, Paul-Olivier Dehaye
wrote:
> Is it always encouraged to upgrade spkgs to more current stable
> upstream version?
> Right now scipy is at 0.9, applied with patches to fix a bug that is
> now corrected in version 0.11 (normally, I have not tested yet). The
> patch does no
I'm trying to build 5.4-beta2 on ML (using the changes from #13541), and it all
went fine. I then applied the changes in #13541 in order to run doctests
(manually, but that shouldn't matter). Now, make ptestlong returns this error:
Running Sphinx v1.1.2
Traceback (most recent call last):
File
On 26/09/2012, at 9:45 AM, JBT wrote:
> Hi, John,
>
> Thanks for the tip. I tried it, but no luck :-( The 'make' got stuck pretty
> much at the same place.
1. Did you try again from scratch? Either by running 'make clean' or unpacking
the source again.
2. Did you delete the older scipy spkg?
On 24/09/2012, at 4:29 PM, ancienthart wrote:
> Is *this* an error ... :/
Yes. In the documentation, not the test.
See http://trac.sagemath.org/sage_trac/ticket/13524
>
> On Monday, 24 September 2012 14:25:38 UTC+10, ancienthart wrote:
>>
>> Hi everyone,
>> In the documentation:
>>
>> http://w
On 6/09/2012, at 10:27 AM, Michael Welsh wrote:
> On 6/09/2012, at 10:21 AM, William Stein wrote:
>>
>> Relevant Question: Does anybody know how to robustly and successfully
>> start a script when OS X boots, so when the lab machine mentioned
>> above is reboo
On 6/09/2012, at 10:21 AM, William Stein wrote:
>
> Relevant Question: Does anybody know how to robustly and successfully
> start a script when OS X boots, so when the lab machine mentioned
> above is rebooted, the ssh tunnel remains?
Does just making the script and dumping it in your startup it
On 3/08/2012, at 4:08 PM, Dima Pasechnik wrote:
>
> On Thursday, 2 August 2012 23:00:23 UTC+8, kfiz wrote:
>>
>> yes, I'm trying to build sage in the "Applications" folder.
>
>
> I'm not a big OSX expert, but I might expect that one needs to use sudo
> sometimes to change things there proper
On 3/08/2012, at 2:12 AM, Anna Haensch wrote:
>
> What's the protocol then for reviewing patches on my machine at the moment?
> I guess it's impossible to get "all tests passed" with my current install.
Try building from source. It should work on 10.6.8, with all doctests passing.
--
--
To
I'm trying to install Sage 5.0.1 from source on this machine (running
Archlinux).
Linux lagrange.msor.vuw.ac.nz 3.2.4-1-ARCH #1 SMP PREEMPT Sat Feb 4 11:21:15
UTC 2012 i686 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linux
The full install log is at http://yomcat.geek.nz/sage/la
On 23/05/2012, at 6:50 PM, Jeroen Demeyer wrote:
>
> What are these "command line tools"?
They're hiding in the preferences for XCode. The Sage readme has the exact
place.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
s
On 26/10/2011, at 12:56 PM, John H Palmieri wrote:
>
> Meanwhile, I believe that binary versions
> of Sage for OS X 10.6 should work on OS X 10.7.
They do. I've been using them since I upgraded.
Michael
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
On 25/09/2010, at 10:52 AM, Justin C. Walker wrote:
> Just checking: is anyone else seeing duplicate mail from sage-devel?
Yes.
--
http://yomcat.geek.nz
--
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.
Is sagenb down?
There's a proxy error there ATM
Cheers,
Michael
--
http://yomcat.geek.nz
--
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://
I've got 32K/32K (which may mean 64K) according to
http://www.everymac.com/systems/apple/imac/stats/imac-core-2-duo-2.66-20-inch-aluminum-early-2009-specs.html
On 28/10/2009, at 10:18 AM, Martin Albrecht wrote:
> does your C2D have 64K of L1? (IIRC there are no C2D with 64K data
> L1, but I
>
I dunno. How do I find out?
On 28/10/2009, at 10:18 AM, Martin Albrecht wrote:
> does your C2D have 64K of L1? (IIRC there are no C2D with 64K data
> L1, but I
> do get confused by Intel's marketing from time to time)
--
http://yomcat.geek.nz
--~--~-~--~~~---~--~-
OSX Dore 2 Duo.
Gordon:Downloads yomcat$ ./cache
8 0.004 1.944
16 0.008 2.010
32 0.019 2.413
64 0.066 3.501
128 0.226 3.405
256 0.479 2.121
512 0.983 2.055
1024 1.997 2.031
2048 4.043 2.025
409
This is an educated guess, but
5.x.0 x \leq 5
6.y.0 y \leq 8
7.z.0 z \leq 9
That's if Apple sticked to the naming scheme they claim to use
(http://lists.apple.com/archives/darwin-development/2001/Nov/msg00188.html
)
On 23/10/2009, at 2:18 PM, David Kirkby wrote:
> Do you know what versions a
I would say anything strictly less than 8.0. There are versions
missing from that table on Wikipedia.
On 23/10/2009, at 1:45 PM, Dr. David Kirkby wrote:
> If that is so, does it seem reasonable to display a message about
> being
> unsupported for Darwin versions 1.3.1, 1.4.1, 6.0.1 and 7.0 ?
On 23/10/2009, at 1:02 PM, Dr. David Kirkby wrote:
>
> Michael Welsh wrote:
>> 10.0.0 is current for darwin.
>>
>> Darwin numbers are different to OS X numbers.
>
> So if 10.0.0 is current, what would be too old to be supported on
> Sage? I'm
> tryin
10.0.0 is current for darwin.
Darwin numbers are different to OS X numbers.
On 23/10/2009, at 12:53 PM, Dr. David Kirkby wrote:
> The 10.0.0 would suggest this is quite old, but the fact it's dated
> 2009 would
> suggest it is not very old.
>
> Any Mac gurus who can resolve this?
--
http://yo
10.6 has darwin 10
10.5 has darwin 9
10.4 has darwin 8
I'm not sure about more depth, but my machine (10.6.1 Intel) has
Gordon:~ yomcat$ uname -r
10.0.0
My G4 with 10.5.8 has
Charlie:~ charlie$ uname -r
9.8.0
On 23/10/2009, at 9:03 AM, Dr. David Kirkby wrote:
> Does anyone know what this pa
On OS X (64-bit Snow Leopard), I get 93MB max.
On 30/09/2009, at 11:04 AM, Jason Grout wrote:
> For ubuntu 9.04, if I right-click on a 3d
> plot and choose About Jmol, it says that there is a maximum of 64MB
> available.
--
http://yomcat.geek.nz
--~--~-~--~~~---~--~
I can get to about 15.
On 30/09/2009, at 11:04 AM, Jason Grout wrote:
> By trial and error, I can get about 10 3d plots on a worksheet.
--
http://yomcat.geek.nz
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscr
43 matches
Mail list logo
