[sage-devel] Sage build from source problems

Hello, I have tried to build Sage from source but have had no success. David Roe suggested I contact this email for assistance; I am attaching a couple of log files. https://drive.google.com/drive/folders/1OoD4bJlGjOlYyMOsJtO0-4vg70L5EiNq?usp=drive_link My laptop is a Macbook 14 inch with Apple

Re: [sage-devel] sage build fail

On Mon, Aug 12, 2019 at 3:34 PM Holley Friedlander wrote: > > I did reinstall/update xcode and command line tools. I then ran ./sage -f > python2 and make and I believe it's working correctly now. At least the > ./sage appears to run normally and I was able to checkout a branch. Thanks > for yo

Re: [sage-devel] sage build fail

I did reinstall/update xcode and command line tools. I then ran ./sage -f python2 and make and I believe it's working correctly now. At least the ./sage appears to run normally and I was able to checkout a branch. Thanks for your help! On Fri, Aug 9, 2019 at 10:38 AM E. Madison Bray wrote: > On

Re: [sage-devel] sage build fail

On Wed, Aug 7, 2019 at 8:54 PM Dima Pasechnik wrote: > > On Wed, Aug 7, 2019 at 9:29 PM Holley Friedlander wrote: > > > > I tried > > > > ls /usr/lib/system/libsystem_darwin.dylib > > > > but I get the message "no such file or directory". Maybe I am looking in > > the wrong place? Thanks. > > no

Re: [sage-devel] sage build fail

On Wed, Aug 7, 2019 at 9:29 PM Holley Friedlander wrote: > > I tried > > ls /usr/lib/system/libsystem_darwin.dylib > > but I get the message "no such file or directory". Maybe I am looking in the > wrong place? Thanks. no, this means that this fix didn't work. Perhaps you ought to reinstall/upg

Re: [sage-devel] sage build fail

I tried ls /usr/lib/system/libsystem_darwin.dylib but I get the message "no such file or directory". Maybe I am looking in the wrong place? Thanks. On Wednesday, August 7, 2019 at 1:21:41 PM UTC-5, Dima Pasechnik wrote: > > On Wed, Aug 7, 2019 at 9:15 PM Holley Friedlander > wrote: > > >

Re: [sage-devel] sage build fail

On Wed, Aug 7, 2019 at 9:15 PM Holley Friedlander wrote: > > Thank you. So I ran the line you suggested below. Is there a way to check it > or should I retype "make" now? This is the warning from my original error > message. Should I change this environment variable? How do I do this? Is it > s

Re: [sage-devel] sage build fail

Thank you. So I ran the line you suggested below. Is there a way to check it or should I retype "make" now? This is the warning from my original error message. Should I change this environment variable? How do I do this? Is it something I type after make? I apologize, I am new to this. The buil

Re: [sage-devel] sage build fail

indeed, you will see in the log ld: file not found: /usr/lib/system/libsystem_darwin.dylib for architecture x86_64 which indicates that your Xcode installation is somewhat broken. Internet says you'd need to run sudo xcode-select -s /Library/Developer/CommandLineTools to fix this. (YMMV, natura

Re: [sage-devel] sage build fail

So the sqlite module of Python2 was not built correctly, it seems. Please post logs/pkgs/python2-2.7.15.p1.log On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander wrote: > > Thank you. I tried the ./sage and this is the crash report (attached). > > On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5,

Re: [sage-devel] sage build fail

Thank you. I tried the ./sage and this is the crash report (attached). On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray wrote: > > Hello, > > This happens in general because the sagenb package uses sage itself as > a dependency, so once the build process gets to installing sagen

Re: [sage-devel] sage build fail

Hello, This happens in general because the sagenb package uses sage itself as a dependency, so once the build process gets to installing sagenb (specifically building its documentation) if something is wrong with the *sage* build your build will fail here. There have been many cases of this. Jus

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

New sagenb issue : https://github.com/sagemath/sagenb/issues/472 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view t

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

I have tested your fix with python3 and it works. Thanks. Le vendredi 26 juillet 2019 16:59:32 UTC+2, vdelecroix a écrit : > > This is indeed Python3 invalid. I would replace the string by > > u'(^|(? > That is Python2 and Python3 valid. > > Le 26/07/2019 à 16:52, Vincent Klein a écrit : > > 8.

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

This is indeed Python3 invalid. I would replace the string by u'(^|(? 8.9.beta3 On unbuntu 16.04 after a "make distclean && ./configure --with-python=3" i get the following error : [sagenb-1.1.2] byte-compiling /home/vklein/odk/sage/local/var/tmp/sage/build/sagenb-1.1.2/inst/home/vklein/odk/

Re: [sage-devel] Sage build error

it should be clear from the log what happened. you need internet access to run the build On Fri, 24 May 2019 16:42 Rithesh K, wrote: > I rectified that error. The python3 package was not built properly. > > But now I have got another error. Please refer to the log attached. > > And also, how can

Re: [sage-devel] Sage build error

I rectified that error. The python3 package was not built properly. But now I have got another error. Please refer to the log attached. And also, how can I retain the configuration for the next build? On Friday, May 24, 2019 at 1:30:15 PM UTC+5:30, Dima Pasechnik wrote: > > the error seems to ha

Re: [sage-devel] Sage build error

the error seems to happen while building zlib (if it was built at all) do you have logs/pkg/zlib*.log ? On Fri, May 24, 2019 at 8:32 AM Rithesh K wrote: > > I am trying to build Sage from the GitHub source code using make and I'm > getting an error. Please look into the log file attached and le

[sage-devel] Sage build error

I am trying to build Sage from the GitHub source code using *make* and I'm getting an error. Please look into the log file attached and let me know what the error is. *Hardware*: MacBook Pro (Retina, 15-inch, Early 2013) Processor: 2.7 GHz Intel Core i7 *OS*: MacOS Mojave (Version 10.14.5 (18F1

Re: [sage-devel] sage build clangs

If I understand correctly, thanks to the work in - Sage Trac ticket 12426 Make Sage build with clang (3.7+) and make it the default on OS X https://trac.sagemath.org/ticket/12426 building Sage with clang works since Sage 8.2, but this makes Sage build with clang only under macOS >= 10.11 "El

Re: [sage-devel] sage build clangs

clang: error: clang frontend command failed with exit code 70 (use -v to see invocation) Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn) We support building with Xcode 7 (based on clang 3.7) but never tried to go back further. Do you have access to a newer Xcode on that machine? Yo

[sage-devel] sage build clangs

I am trying to build sage from source (version 8.3rc2) on Mac OS X Version 10.9.5 with 2.8 GH Intel core i7. The log is attached. --Mark -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fro

Re: [sage-devel] Sage build failure with MPFR

In that log I do not see any place where libmpfr.so.4.1.5 is actually built. Normally on Linux/gcc I would expect to see libtool: link: gcc -shared ... -Wl,-soname -Wl,libmpfr.so.4 -o .libs/libmpfr.so.4.1.5 But nothing like this in the log. Shared lib was not built, fullstop. On Sunday, July 2

Re: [sage-devel] Sage build failure with MPFR

What do you have in /home/josh/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/.libs/ ? The log is not especially enlightening, I must say. François > On 24/07/2017, at 06:15, Joshua Wall wrote: > > Hello all. I'm currently attempting to build from the git source repo on a > new ASUS Zenb

[sage-devel] sage build problems on Cygwin64 from sage-6-7.tar.gz and from https://github.com/sagemath/git-trac-c

After finding problems sage-6-7.tar.gz Now I succeeded with git clone https://github.com/sagemath/git-trac-command.git But in compiling on Cygwin64 I run into a problem with ecm-6.4.4 After leaving ~/sage-git/sage/local/var/tmp/sage/build/givaro-3.7.1/src I got: The following package(s) may have f

[sage-devel] Sage build system

[top-posted reply to start an appropriately-named thread] On Monday, January 13, 2014 12:26:30 AM UTC-5, William wrote: > I don't think this is off topic and I think you make a very good > point. Relocation (as I defined it) is not the goal. The goal is to > build user-installable binaries. I

[sage-devel] Sage build system

[changed subject to end up top-posted] On Monday, January 13, 2014 12:26:30 AM UTC-5, William wrote: > > I don't think this is off topic and I think you make a very good > point. Relocation (as I defined it) is not the goal. The goal is to > build user-installable binaries. If what you sugges

[sage-devel] sage build system project progress

Hi there. A draft of the build systems for sage is now available on github [1]. The commits are based on the "working" branch, which represents the current transition from hg to git. The top level build system now not only disables unneeded packages automatically (e.g. gcc, iconv), but also allow

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

On 2 March 2013 13:04, 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 build? > > I'm sure it does indicate why, just not at the

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

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 build? > > I'm sure it does

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

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 build? I'm sure it does indicate why, just not at the end of the file. When make encounters an errors, it con

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

I tried to build Sage 5.8.beta2 on a Sun Blade 2000 SPARC. The build fails, but install.log does not indicate why. Restarting the build appears to solve the problem. Writing /export/home/drkirkby/sage-5.8.beta2/local/lib/python2.7/site-packages/scipy-0.11.0-py2.7.egg-info running install_clib re

[sage-devel] Sage build critical path

Purely for information, this is the critical path for building Sage in parallel using "make -j" (unlimited number of jobs). This is after applying #13392 (remove GNUTLS-related packages). prereq bzip2 patch termcap readline sqlite python atlas r rpy2 By far the most time taken is taken by R and

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

Hi William, I would worry about losing compatibility with other systems if I updgrade my OS too much, but when I am done traveling, an upgrade to Mac OS 10.5 should be possible. However, talking to several others last week, at FPSAC it appears that this is not a problem unique to me though, ma

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

On Fri, Aug 3, 2012 at 4:30 PM, Gregg wrote: > Hi all, > > I have tried to install the last two versions of Sage from source, and can > no longer build Sage on my machine. > > Sage 5.0.1 built just fine, but I get similar error messages with Sage 5.1 > and Sage 5.2. > > My machine is running Mac O

Re: [sage-devel] Sage build time

On Jan 21, 2012, at 16:10 , Jeroen Demeyer wrote: > On 2012-01-21 19:30, Justin C. Walker wrote: >> I tried this on my system (Mac Pro, Dual 6-core Xeon, 10.6.8, 24 GB RAM) >> with 4.8.rc0, using "-j24". For 'make build', I got >> >> real23m34.692s >> user159m17.675s >> sys 22m54.6

Re: [sage-devel] Sage build time

On 2012-01-21 19:30, Justin C. Walker wrote: > I tried this on my system (Mac Pro, Dual 6-core Xeon, 10.6.8, 24 GB RAM) with > 4.8.rc0, using "-j24". For 'make build', I got > > real23m34.692s > user159m17.675s > sys 22m54.627s > > Lots of parallelism. For 'make doc', I got > > re

Re: [sage-devel] Sage build time

On 2012-01-21 23:56, Justin C. Walker wrote: > Jeroen: did you apply these patches for your tests, or did you apply other > magic? No, I didn't use anything special (apart from #12329 which has nothing to do with doc). -- To post to this group, send an email to sage-devel@googlegroups.com To uns

Re: [sage-devel] Sage build time

On Jan 21, 2012, at 11:10 , Volker Braun wrote: > Sphinx works serial only. The patch at > http://trac.sagemath.org/sage_trac/ticket/6495 aims to break the reference > manual into bits that can be processed in parallel. Thanks for the pointer, but the patches don't apply cleanly to 4.8.rc0. P

Re: [sage-devel] Sage build time

Sphinx works serial only. The patch at http://trac.sagemath.org/sage_trac/ticket/6495 aims to break the reference manual into bits that can be processed in parallel. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-dev

Re: [sage-devel] Sage build time

On Jan 20, 2012, at 05:25 , 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...):

Re: [sage-devel] Sage build time

On 2012-01-20 14:39, Martin Albrecht wrote: > Seems I should improve my tuning code: building M4RI is very quick, but the > find-the-cache-size-via-tuning stuff takes a lot of time. I don't think it's a big deal really. libm4ri isn't in the critical path, and it's only the 10th slowest package.

Re: [sage-devel] Sage build time

> The 10 slowest packages to build (slowest first): > r > atlas > scipy > polybori > maxima > ntl > singular > ecl > sage > libm4ri Seems I should improve my tuning code: building M4RI is very quick, but the find-the-cache-size-via-tuning stuff takes a lot of time. Cheers, Martin -- name: Mart

[sage-devel] Sage build time

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 "make build" was 27 minutes, total time for "m

[sage-devel] Sage build failed

Sage build failed. Platform is Amazon EC2 Linux AMI 32 bit (CentOS like linux) Apparently there was a problem with the Atlas portion of the process after about 14 hours into the build. Thanks for any help that you can offer. Install log follows: /home/ec2-user/sage-4.7.2/spkg/build/atlas-3.8

[sage-devel] Sage build problem involving Python

Hi, I'm trying to compile the most recent version of Sage on an old Linux system: Dell Inspiron 8000, PIII. It's running Salix, a Slackware derivative. I'm completely new to Sage and fairly new to Linux (this is my first attempt to compile a large program). It gets a fair ways into the proc

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

Hi all, I am trying to build sage4.6.2 from source. I get the following error and sage is not building. As the message tells : the python is installed properly but test on it fails. Because of which sage is also unable to build. Here is info about my system : Fedora : 2.6.34.8-68.fc13.i686.PAE gc

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

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 enough disk space in my personal quota. :-)

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

On 07/ 8/10 09:06 PM, Ренат Ескенин wrote: sage: An error occurred while installing atlas-3.8.3.p12 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of .../install.log. Describe your computer, operating system, etc. erro

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

Ultimately, this was caused by #7818 removing the -fno-strict-aliasing option. This only effects -O3 compiled code, which is where gcc starts using strict aliasing if it can. Thanks to RWB for helping with this. On Fri, Jan 15, 2010 at 10:08 AM, Craig Citro wrote: >>> 1) Kill the -O3, and see if

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

>> 1) Kill the -O3, and see if the file compiles. If so, start bumping it >> back up until you see the hang. > > With -O2, it compiles fine. With -O3, it seems to hang. > Well, this means we've got an easy workaround for the time being. Glancing at the two sets of warning messages below, I don't s

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

> 1) Kill the -O3, and see if the file compiles. If so, start bumping it > back up until you see the hang. With -O2, it compiles fine. With -O3, it seems to hang. > 2) Kill the -w at the end, so you can at least see some commentary > from the compiler. (-w suppresses all warnings.) * With -O3, w

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

So I have no idea what's causing this, but here are at least some reasonable things to try: > 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/include/fplll -I/mnt/ > usb1/scratch/r

[sage-devel] Sage build hangs on fplll

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/include/fplll -I/mnt/

[sage-devel] sage build progress indicator

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 at 100%, but maybe someone else likes it, too ;) Also, is there some

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

Should I be worried about the following seen in the middle of a Sage build: Configure findings: FFI:no (user requested: default) readline: yes (user requested: yes) libsigsegv: no, consider installing GNU libsigsegv As you requested, we will proceed without libsigsegv... ./makemak

[sage-devel] Sage build

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 of 3 hours). Thanks Ralf --~--~-~--~~~---~--~~ T

[sage-devel] Sage build failure

The install.log file is at This fails on fedora 5 [EMAIL PROTECTED] sage-3.0]# uname -a Linux localhost.localdomain 2.6.18-1.2239.fc5 #1 Fri Nov 10 13:04:06 EST 2006 i686 i686 i386 GNU/Linux You have new mail in /var/spool/mail/root [EMAIL PROTECT