[sage-devel] Re: Sage build from source problems

I had not run ". ./.homebrew-build-env"; it is working now. Thanks a lot, Matthias! On Wednesday 17 January 2024 at 21:24:55 UTC-5 Matthias Koeppe wrote: > From sageliblog: > >gcc -bundle -undefined dynamic_lookup > -L/Users/aashrayajha/GitHub/Sage/sage/local/lib > -Wl,-rpath,/Users/

[sage-devel] Re: Sage build from source problems

>From sageliblog: gcc -bundle -undefined dynamic_lookup -L/Users/aashrayajha/GitHub/Sage/sage/local/lib -Wl,-rpath,/Users/aashrayajha/GitHub/Sage/sage/local/lib -L/Users/aashrayajha/GitHub/Sage/sage/local/lib -Wl,-rpath,/Users/aashrayajha/GitHub/Sage/sage/local/lib -Wl,-rpath,/Users/a

[sage-devel] Re: Sage build from source fails on OS X 10.9

It may be useful to mention here that I did manage to build with my default .bashrc in the end, so with Homebrew installed and /usr/local/ in the PATH. The issue here, as far as I understand, is that Homebrew has an installation option --with-default-names, which, if set, places utils in /usr/l

[sage-devel] Re: Sage build from source fails on OS X 10.9

I opted for kicking my .bashrc out of the way and exporting a different PATH. Regardless, I now have a working Sage build! Thank you for solving my problem in two sentences :-) On Sunday, August 9, 2015 at 6:40:58 PM UTC-4, Volker Braun wrote: > > Building with homebrew in /usr/local is not su

[sage-devel] Re: Sage build from source fails on OS X 10.9

Building with homebrew in /usr/local is not supported and likely to fail. Move /usr/local out of the way and try again. On Sunday, August 9, 2015 at 11:53:51 PM UTC+2, Jeroen Sijsling wrote: > > Dear all, > > Today I tried to build Sage from source, for now just for the heck of it, > but also

[sage-devel] Re: sage build error

leif wrote: leif wrote: Elliot Findley wrote: Hello. I tried to build sage-6.1.1 on Ubuntu 14.04 LTS. My laptop is an Asus Ux31A notebook. Note that Sage 6.2 has been released a couple of weeks ago (although that presumably won't fix this particular issue). Or it probably will. (Sage 6.2 i

[sage-devel] Re: sage build error

leif wrote: Elliot Findley wrote: Hello. I tried to build sage-6.1.1 on Ubuntu 14.04 LTS. My laptop is an Asus Ux31A notebook. Note that Sage 6.2 has been released a couple of weeks ago (although that presumably won't fix this particular issue). Or it probably will. (Sage 6.2 includes the f

[sage-devel] Re: sage build error

Elliot Findley wrote: Hello. I tried to build sage-6.1.1 on Ubuntu 14.04 LTS. My laptop is an Asus Ux31A notebook. Note that Sage 6.2 has been released a couple of weeks ago (although that presumably won't fix this particular issue). It built for an hour before failing when trying to build

[sage-devel] Re: Sage build system

Another bullet point, related to being able to package and store the installed files: - downgrades should work and be fast, so you can easily go back to an old ticket -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gro

[sage-devel] Re: Sage build fails. But restarts OK after typing "make" again ???

kcrisman wrote: On Saturday, March 2, 2013 8:04:09 AM UTC-5, Jeroen Demeyer wrote: On 2013-03-02 12:28, David Kirkby wrote: > I tried to build Sage 5.8.beta2 on a Sun Blade 2000 SPARC. The build > fails, but install.log does not indicate why. I assume this was a parallel buil

[sage-devel] Re: Sage Build from source not working for 5.1 nor 5.2

Here is the relevant file. On Friday, August 3, 2012 6:49:13 PM UTC-5, Volker Braun wrote: > > The problem is > > > /usr/bin/ld: warning can't open dynamic library: > /Applications/sage-5.2/spkg/build/pari-2.5.1.p3/src/Odarwin-i386/libpari-gmp.dylib > > referenced from: /Applications/sage-5.2/

[sage-devel] Re: Sage Build from source not working for 5.1 nor 5.2

The problem is /usr/bin/ld: warning can't open dynamic library: /Applications/sage-5.2/spkg/build/pari-2.5.1.p3/src/Odarwin-i386/libpari-gmp.dylib referenced from: /Applications/sage-5.2/local/lib/libcsage.dylib (checking for undefined symbols may be affected) (No such file or directory, e

Re: [sage-devel] Re: Sage build time

On 2012-01-21 07:38, Dima Pasechnik wrote: > perhaps it's also important to see how fast 'sage -b' goes after a large > change. Currently it seems that as it runs scons, and not make, scons > only uses one processor. (scons has a -j switch, but is does not seem to > be used). It uses scons for buil

Re: [sage-devel] Re: Sage build time

On Jan 20, 2012 10:38 PM, "Dima Pasechnik" wrote: > > perhaps it's also important to see how fast 'sage -b' goes after a large change. Currently it seems that as it runs scons, and not make, scons only uses one processor. (scons has a -j switch, but is does not seem to be used). > It would be grea

[sage-devel] Re: Sage build time

perhaps it's also important to see how fast 'sage -b' goes after a large change. Currently it seems that as it runs scons, and not make, scons only uses one processor. (scons has a -j switch, but is does not seem to be used). It would be great to be able to do something like 'sage -b -j64', no?

Re: [sage-devel] Re: Sage build time

On 2012-01-21 00:00, RegB wrote: > Do you have a (good) idea of where diminishing returns cuts in ? > I imagine the number of cores (threads) doesn't help much above a > fairly small number due to sequential dependencies ? I'm pretty sure I hit the diminishing returns already. ATLAS and R (both in

[sage-devel] Re: Sage build time

Do you have a (good) idea of where diminishing returns cuts in ? I imagine the number of cores (threads) doesn't help much above a fairly small number due to sequential dependencies ? More memory is always "nice to have" but does it really help HERE ? Did you set the atlas_architecture environment

[sage-devel] Re: Sage build time

On 1/20/12 7:25 AM, Jeroen Demeyer wrote: Some observations from building sage-4.8 on a very fast system (32 cores, 512G RAM) using "make -j64 -l32". First of all, apply the patch from #12329 to prune many unneeded dependencies of the Sage library (needs_review by the way...): Total time for "m

[sage-devel] Re: Sage build failed

The problem is that Atlas installation does timing of the system (its processor, etc) and when the collected data is not consistent it, eventually, fails. On a multi-user virtual host like yours, it's no surprise it fails. Can you install a system-wide Atlas on your system? (It should be a packag

[sage-devel] Re: Sage build problem involving Python

It sounds like I need more memory or a different machine. Mr. Braun, I appreciate all your help! -- 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 h

[sage-devel] Re: Sage build problem involving Python

I think you need at least 512MB RAM. You can try to install your distribution's ATLAS shared libraries and use them with the SAGE_ATLAS_LIB environment variable. Though I suspect the build will fail at some other point due to low memory. -- To post to this group, send an email to sage-devel@go

[sage-devel] Re: Sage build problem involving Python

I should probably have mentioned earlier that this system has only 256 MB of RAM. Could that be the problem? -- 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 thi

[sage-devel] Re: Sage build problem involving Python

Ok, I added the package as you recommended. The build messages seem a bit different, but the end result is similar: - Finished configuring ATLAS. ATLAS failed to build, possibly because of a loaded system.

[sage-devel] Re: Sage build problem involving Python

You can try the new ATLAS spkg from http://trac.sagemath.org/sage_trac/ticket/10226. Just put it in SAGE_ROOT/spkg/standard -- 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

[sage-devel] Re: Sage build problem involving Python

As a matter of fact, I did! I re-ran make without the option and I got past the Python error only to run aground on the ATLAS installation: - STAGE 2-3-2: CacheEdge DETECTION make -f Makefile INSTALL_LOG/at

[sage-devel] Re: Sage build problem involving Python

Did you set the SAGE_CHECK environment variable by any chance? Don't do that. -- 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://groups.googl

[sage-devel] Re: sage build : Error testing package ** python-2.6.4.p9 **

I tried without setting SPKG_CHECK and it worked! Although I would have been happier if all tests too had been worked. :) Thanks. -- 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 mo

[sage-devel] Re: sage build : Error testing package ** python-2.6.4.p9 **

On Monday, May 23, 2011 6:52:04 AM UTC-7, Dima Pasechnik wrote: > > do you mean to say you run with SPKG_CHECK=yes? > AFAIK, python spkg never passes all its tests. > IMHO, you can ignore these. > Thus, do not build Sage with SPKG_CHECK set. > Well, don't build the Python part of Sage with S

[sage-devel] Re: sage build : Error testing package ** python-2.6.4.p9 **

do you mean to say you run with SPKG_CHECK=yes? AFAIK, python spkg never passes all its tests. IMHO, you can ignore these. Thus, do not build Sage with SPKG_CHECK set. On May 22, 10:40 am, Digvijay Patankar wrote: > Hi all, > > I am trying to build sage4.6.2 from source. > I get the following err

[sage-devel] Re: sage build : Error testing package ** python-2.6.4.p9 **

no one to suggest something? -- 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://groups.google.com/group/sage-devel URL: http://www.sagemath.or

Re: [sage-devel] Re: Sage build and `pwd` craziness

It seems very fragile to me to reply on a particular syntax in the operating system's way of displaying a symbolic link to find out the name of the current branch. Why not store the branch's name in a file and read that? Then it would not matter whether it was a link or not. John On 23 August 2

[sage-devel] Re: Sage build and `pwd` craziness

This seems to work. Thanks! On Aug 23, 10:17 am, Ryan Hinton wrote: > You're right, the symbolic link had been dereferenced, so devel/sage > and devel/sage-main were both normal directories.  In my sandbox, it > worked to remove devel/sage and recreate it as a link to sage-main. > We'll try it o

[sage-devel] Re: Sage build and `pwd` craziness

Jason, I think I can avoid relocating the sage tree on my own system, but probably not on the "public" installs I have worked on. I'll take a look at your patch, but I'm not sure I'm qualified to review it. :-) - Ryan On Aug 21, 1:12 am, Jason Grout wrote: > On 8/20/10 2:44 PM, Ryan Hinton wro

[sage-devel] Re: Sage build and `pwd` craziness

You're right, the symbolic link had been dereferenced, so devel/sage and devel/sage-main were both normal directories. In my sandbox, it worked to remove devel/sage and recreate it as a link to sage-main. We'll try it on the real install soon. Thanks! - Ryan On Aug 21, 2:34 am, Mitesh Patel wr

Re: [sage-devel] Re: Sage build and `pwd` craziness

On 08/21/2010 02:12 AM, Jason Grout wrote: > On 8/20/10 2:44 PM, Ryan Hinton wrote: >> I have a build of Sage at school that I occasionally update when a bug >> or upgrade affects me. I'm the only one who uses it, but it's >> installed in a public location (i.e. not writable by me) in case >> some

[sage-devel] Re: Sage build and `pwd` craziness

On 8/20/10 2:44 PM, Ryan Hinton wrote: I have a build of Sage at school that I occasionally update when a bug or upgrade affects me. I'm the only one who uses it, but it's installed in a public location (i.e. not writable by me) in case someone else *might* use it. And because I don't have enou

[sage-devel] Re: Sage build error (atlas build)

Throttling is off. Build error: STAGE 2-1-2: CacheEdge DETECTION make -f Makefile INSTALL_LOG/atlas_cacheedge.h pre=d 2>&1 | ./ xatlas_tee INSTALL_LOG/dMMCACHEEDGE.LOG make[3]: *** [build] Ошибка 255 make[3]: Выход из каталога `/mnt/data/Distr/Sage/sage-4.4.4/spkg/build/ atlas-3.8.3.p12/ATLAS-buil

[sage-devel] Re: Sage build error (atlas build)

> There does seem to be a few reports of ATLAS failures. See the ticket > > http://trac.sagemath.org/sage_trac/ticket/9385 > > One (very very remote) possibility is that MAKEFLAGS was recently unset in > ATLAS, though if anything I would expect that to make the build more stable, > not > less so.

[sage-devel] Re: Sage build hangs on fplll

Robert Miller wrote: One of the patches recently merged into rc0 is causing fplll to take forever to compile on {sage, boxen...}.math: building 'sage.libs.fplll.fplll' extension gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -Wall -g -Wall -g -fPIC - I/mnt/usb1/scratch/rlm/sage-4.3.1.alpha3/local

[sage-devel] Re: sage build progress indicator

On Aug 13, 6:19 pm, William Stein wrote: > You should include this with sage. You could make it > >    SAGE_ROOT/local/bin/sage-progress Yes, sounds good to me. I just have to tweak it further to be really useful and more intelligent. H --~--~-~--~~~---~--~~ To p

[sage-devel] Re: sage build progress indicator

On Thu, Aug 13, 2009 at 9:10 AM, Harald Schilly wrote: > > Just for fun I've written a script that tells me how far Sage has come > when building from scratch: > http://sage.math.washington.edu/home/schilly/sage_progress > I'm not sure if it is counting the spkgs correctly or if it really > ends a

[sage-devel] Re: Sage build log query (clisp)

Thanks Michael, just making sure. John 2009/5/5 mabshoff : > > > > On May 5, 5:50 am, John Cremona wrote: >> Should I be worried about the following seen in the middle of a Sage build: > > No, it is a just a workaround for a problem if you build Sage with > nohup on any operating system *or* o

[sage-devel] Re: Sage build log query (clisp)

On May 5, 5:50 am, John Cremona wrote: > Should I be worried about the following seen in the middle of a Sage build: No, it is a just a workaround for a problem if you build Sage with nohup on any operating system *or* on OSX, so no need to worry about anything. > Working around nohup probl

[sage-devel] Re: Sage build

On Tue, 24 Feb 2009 at 12:42AM +0100, Ralf Hemmecke wrote: > > What should happen if I say > > tar xf sage-3.3.tar > cd sage-3.3 > make > make > > i.e. if I issue 'make' a second time? > > Before I try to do that, I'd like to know whether I can expect a build > time less than a minute (instead

[sage-devel] Re: Sage build failure

On Wed, Apr 23, 2008 at 9:46 AM, <[EMAIL PROTECTED]> wrote: > > The install.log file is at > > This fails with "internal compiler error": '__pyx_pf_4sage_7modules_18real_double_vector_28RealDoubleVectorSpaceElement___init_

[sage-devel] Re: Sage Build, a few more hiccups

On 8/10/07, Pete Chvany <[EMAIL PROTECTED]> wrote: > William-- > > Thanks, I will work through these issues and let you know what the > results are. Actually, I think in each case the result is "I (william) need to fix something", so there really isn't much for you to do at present. > I've been

[sage-devel] Re: Sage Build, a few more hiccups

(I've cc'd this to FriCAS since Axiom and FriCAS are mentioned below in reference to OS X.) On 8/10/07, Pete Chvany <[EMAIL PROTECTED]> wrote: > Hi William-- > > Shakedown cruise of SAGE 2.7.3 installation continues. I've got four > final optional packages I'm trying to set up, with various error

[sage-devel] Re: SAGE build error

Hello William, I had trouble building sage-1.5-alpha8 on Mac OS X 10.4/PPC. It built fine, but I could not start sage correctly; it complained about the line 'import bz2' and the bz2 module not being found. I fixed the problem by rm ./spkg/installed/python-2.5.p3 ./sage -i python-2.5.p3 and t

[sage-devel] Re: SAGE build error

On Thu, 07 Dec 2006 23:44:48 -0800, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Dec 7, 2006, at 11:39 PM, William Stein wrote: >> >> On Thu, 07 Dec 2006 23:31:53 -0800, Robert Bradshaw >> <[EMAIL PROTECTED]> wrote: >> >>> Another error, this time with the gd library. >> >> This is an unsolve

[sage-devel] Re: SAGE build error

On Dec 7, 2006, at 11:39 PM, William Stein wrote: > > On Thu, 07 Dec 2006 23:31:53 -0800, Robert Bradshaw > <[EMAIL PROTECTED]> wrote: > >> Another error, this time with the gd library. > > This is an unsolved problem for OS X Powerpc, that needs to be fixed > before we can release sage-1.5. (Or

[sage-devel] Re: SAGE build error

On Thu, 07 Dec 2006 23:31:53 -0800, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > Another error, this time with the gd library. This is an unsolved problem for OS X Powerpc, that needs to be fixed before we can release sage-1.5. (Or all the gd stuff has to be removed for sage-1.5.) Your options