I already deleted the posting that Dima is replying to.  I misread the 
instructions and omit the 'make' step,

On Friday, August 22, 2014 2:24:15 PM UTC, Dima Pasechnik wrote:
>
> On 2014-08-22, Daniel Friedan <dfri...@gmail.com <javascript:>> wrote: 
> > ------=_Part_1227_548338737.1408715857673 
> > Content-Type: text/plain; charset=UTF-8 
> > 
> > My OS X 10.6.8 machine does have and Intel Core 2 Duo processor. 
> > 
> > Volker's recipe did not work.  Here's what it produced: 
> > 
> > I tried following Volker's instructions for building the app bundle 
> under OS X 10.6.8, but it failed. 
>
> this the an unclear error message: 
>
> > find: /Volumes/4TB-1/Sage_building/sage/local/var/lib/sage/installed: No 
> such file or directory 
>
> that is to say, "no, Sage was not installed, one didn't even try..." 
>
> He skipped 'make'. 
>
> After 
>
> $ git clone git://github.com/sagemath/sage.git 
> $ cd sage 
>
> you need to build sage 
>
> by running 'make'. To use 2 cores, do the following 
>
> $ export MAKE="make -j2" 
> $ $MAKE 
>
> (better do it overnight, as it will take a while, and you might also need 
> to disable 
> sleeping on your laptop...) 
>
>
>
>
> > 
> > OS X 10.6.8 
> > 
> > $ cd /Volumes/4TB-1 
> > $ mkdir Sage_building 
> > $ cd Sage_building/ 
> > $ git clone git://github.com/sagemath/sage.git 
> > Cloning into 'sage'... 
> > remote: Counting objects: 246211, done. 
> > remote: Compressing objects: 100% (675/675), done. 
> > remote: Total 246211 (delta 1082), reused 992 (delta 779) 
> > Receiving objects: 100% (246211/246211), 74.73 MiB | 7.38 MiB/s, done. 
> > Resolving deltas: 100% (172257/172257), done. 
> > Checking connectivity... done. 
> > Checking out files: 100% (4220/4220), done. 
> > 
> > $ cd sage 
> > $ git checkout 6.3 
> > Note: checking out '6.3'. 
> > 
> > You are in 'detached HEAD' state. You can look around, make experimental 
> > changes and commit them, and you can discard any commits you make in 
> this 
> > state without impacting any branches by performing another checkout. 
> > 
> > If you want to create a new branch to retain commits you create, you may 
> > do so (now or later) by using -b with the checkout command again. 
> Example: 
> > 
> >   git checkout -b new_branch_name 
> > 
> > HEAD is now at 00199fb... Updated Sage version to 6.3 
> > 
> > $ export SAGE_APP_DMG=yes 
> > $ export SAGE_APP_BUNDLE=yes 
> > $ ./sage -bdist 
> > find: /Volumes/4TB-1/Sage_building/sage/local/var/lib/sage/installed: No 
> such file or directory 
> > Sage version 6.3, release date 2014-08-10 
> > rm -rf config configure build/Makefile-auto.in 
> >   % Total    % Received % Xferd  Average Speed   Time    Time     Time 
>  Current 
> >                                  Dload  Upload   Total   Spent    Left 
>  Speed 
> > 100 89470  100 89470    0     0   105k      0 --:--:-- --:--:-- --:--:-- 
>  215k 
> > Cloning into 
> '/Volumes/4TB-1/Sage_building/sage/tmp/sage-6.3-i386-Darwin'... 
> > warning: templates not found 
> /Volumes/4TB-1/Sage_building/sage/local/share/git-core/templates 
> > done. 
> > Checking out files: 100% (4220/4220), done. 
> > Checking connectivity: 246211, done. 
> > Finished cloning Sage sources 
> > Copying files over to tmp directory 
> > tar: local: Cannot stat: No such file or directory 
> > tar: Error exit delayed from previous errors. 
> > cp: /Volumes/4TB-1/Sage_building/sage/local/bin/sage-README-osx.txt: No 
> such file or directory 
> > $ 
> > 
> > 
> > 
> > 
> > On Friday, August 22, 2014 1:47:15 PM UTC, Dima Pasechnik wrote: 
> >> 
> >> On 2014-08-22, Daniel Friedan <dfri...@gmail.com <javascript:>> wrote: 
> >> > ------=_Part_5_1837348027.1408711654748 
> >> > Content-Type: text/plain; charset=UTF-8 
> >> > 
> >> > I've done a couple of experiments with the latest version of Sage 
> (6.3) 
> >> > under OS X 10.6.8, using the official 10.7 and 10.6 binaries 
> available 
> >> for 
> >> > download. 
> >> 
> >> Please also pay attention to the CPU type. If you want your binary to 
> run 
> >> on all 
> >> the machines capable of running OSX 10.6.8, you might need to be more 
> >> careful than just 
> >> running Volker's recepy. 
> >> Specifically, Core2 Duo chips are pretty much screwed up under OSX 
> 10.6, 
> >> as their 64-bit 
> >> capabilities aren't really well-supported. 
> >> 
> >> At least it would be important to know the CPU type you use exactly. 
> >> 
> >> Just in case, 
> >> Dima 
> >> 
> >> > 
> >> > (1) *sage-6.3-x86_64-Darwin-OSX_10.7_x86_64.dmg* 
> >> >< 
> >> 
> http://boxen.math.washington.edu/home/sagemath/sage-mirror/osx/intel/sage-6.3-x86_64-Darwin-OSX_10.7_x86_64.dmg>
>  
>
> >> 
> >> > 
> >> > This is an app version (the file name should be changed to 
> >> > *sage-6.3-x86_64-Darwin-OSX_10.7_x86_64-app.dmg* 
> >> >< 
> >> 
> http://boxen.math.washington.edu/home/sagemath/sage-mirror/osx/intel/sage-6.3-x86_64-Darwin-OSX_10.7_x86_64.dmg>
>  
>
> >> 
> >> > ). 
> >> > 
> >> > It runs on OS X 10.6.8 (though I didn't test much). 
> >> > 
> >> > It seems large, 4.53 GB. 
> >> > 
> >> > (2) *sage-6.3-x86_64-Darwin-OSX_10.6_x86_64.dmg* 
> >> >< 
> >> 
> http://boxen.math.washington.edu/home/sagemath/sage-mirror/osx/intel/sage-6.3-x86_64-Darwin-OSX_10.6_x86_64.dmg>
>  
>
> >> 
> >> > 
> >> > This is the non-app version.  I turned it into an app version by the 
> >> > following: 
> >> >       1.  moved sage/ out of sage-6.2.app/Contents/Resources/ 
> >> >       2.  copied sage-6.2.app/ and named the copy sage-6.3.app/ 
> >> >       3.  moved the 6.3 version of sage/ into 
> >> > sage-6.3.app/Contents/Resources/ 
> >> >       4.  edit a few lines in sage-6.3.app/Contents/Info.plist 
> >> (actually, I 
> >> > should have but didn't bother). 
> >> > 
> >> > So it seems trivial to make an OS X 10.6 app version from a OS X 10.6 
> >> > non-app version. 
> >> > 
> >> > The size is 3.55 GB, smaller by about 1GB than the official OS X 10.7 
> >> app 
> >> > version. 
> >> > 
> >> > For comparison, the official sage-6.2-app is 3.32 GB. 
> >> > 
> >> > Daniel 
> >> > 
> >> > 
> >> > 
> >> 
> >> 
> > 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to