[sage-devel] Re: Error building sage on ubuntu 22.04.3 from git, develop branch, package singular-4.3.2p8, eclib

2024-01-18 Thread Dima Pasechnik
On Wednesday, January 17, 2024 at 4:36:20 PM UTC Aurore Guillevic wrote: Yes, my problem is solved. Indeed, it was caused by an old manual installation of gmp, still present in /usr/local. I ran make with --with-system-gmp=no to be sure that sage would re-build its own gmp. Finally it worked.

[sage-devel] Re: Error building sage on ubuntu 22.04.3 from git, develop branch, package singular-4.3.2p8, eclib

2024-01-17 Thread Aurore Guillevic
Yes, my problem is solved. Indeed, it was caused by an old manual installation of gmp, still present in /usr/local. I ran make with --with-system-gmp=no to be sure that sage would re-build its own gmp. Finally it worked. I uninstalled the old gmp in /usr/local too. Thanks for your help!

[sage-devel] Re: Error building sage on ubuntu 22.04.3 from git, develop branch, package singular-4.3.2p8, eclib

2024-01-16 Thread Matthias Koeppe
>From config.log: configure:13475: will use system package and not install SPKG gmp configure:13511: checking absolute name of configure:13517: checking for gmp.h configure:13517: result: yes configure:13538: result: ///usr/local/include/gmp.h Try removing the installation in /usr/local On

[sage-devel] Re: Error building sage

2022-09-08 Thread Matthias Koeppe
>From matplotlib log: === File "/Users/allisonfitisone/sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/overrides.py", line 6, in from numpy.core._multiarray_umath import ( ImportError:

Re: [sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-26 Thread Max Kölbl
Ah okay, that's good to know. I probably won't need that feature in the near future anyway. But thank you; I ran `make build` and finally the process terminated without a fatal error. I also ran it and it works fine now. dim...@gmail.com schrieb am Dienstag, 26. Juli 2022 um 18:10:20 UTC+9: >

Re: [sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-26 Thread Dima Pasechnik
documentation building is currently broken on Cygwin. instead of running 'make', run 'make build'. Anyhow, you probably have mostly functional Sage installation now. On Tue, 26 Jul 2022, 10:18 Max Kölbl, wrote: > Thank you very much for your help! > > >Install the relevant cygwin packages:

Re: [sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-26 Thread Max Kölbl
Thank you very much for your help! >Install the relevant cygwin packages: >``` >$ apt-cyg install bzip2 libbz2-devel liblzma-devel libffi-devel xz >``` >Clean up the corresponding Sage packages: >``` >$ make bzip2-clean liblzma-clean libffi-clean xz-clean > >Then configure again: >``` >$ make

Re: [sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-24 Thread Samuel Lelievre
Install the relevant cygwin packages: ``` $ apt-cyg install bzip2 libbz2-devel liblzma-devel libffi-devel xz ``` Clean up the corresponding Sage packages: ``` $ make bzip2-clean liblzma-clean libffi-clean xz-clean Then configure again: ``` $ make configure $ ./configure ``` Follow any

Re: [sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-24 Thread Dima Pasechnik
On Mon, Jul 25, 2022 at 12:49 AM Max Kölbl wrote: > > Thank you very much for your reply! > > > No, Sage accepts any system Python >= 3.8. > > Okay, that's good to know. > > > In your config.log one can see that system python3 is not rejected because > > of a version check: > > ##

[sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-24 Thread Max Kölbl
Thank you very much for your reply! > No, Sage accepts any system Python >= 3.8. Okay, that's good to know. > In your config.log one can see that system python3 is not rejected because of a version check: > ## ## > ## Checking whether

[sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-24 Thread Matthias Koeppe
On Sunday, July 24, 2022 at 10:01:08 AM UTC-7 max.w@gmail.com wrote: > Thanks! I gave it a shot but unfortunately it still didn't work. > > However, the reasons are strange because now python3 seems to be the > culprit. > Perhaps relevant: I installed openssl via apt-cyg and it seems like

[sage-devel] Re: Error building Sage 9.6 due to openssl

2022-07-23 Thread Samuel Lelievre
You could try this: ``` make openssl-clean openssl-uninstall make configure ./configure make ``` -- 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] Re: Error building Sage 9.6 due to openssl

2022-07-19 Thread Matthias Koeppe
"configure" should have printed advice on what system packages to install. See config.log On Tuesday, July 19, 2022 at 1:51:16 AM UTC-7 max.w@gmail.com wrote: > Hello everyone! > > While running the 'make' command in cygwin on my Windows 8 laptop, I > received the following output. > >

[sage-devel] Re: Error building sage r-3.6.3 (Ubuntu 18.04)

2022-04-19 Thread Emmanuel Charpentier
Well… - config can’t detect readline, and configures Sage to install the relevant SPKG. - Compilation of r fails for lack of readline. Did you check the compilation of the readline SPKG ? (You should have something matching *readline*.log somewhere under

Re: [sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread B Gillespie
Excellent, the build completed successfully with the recommended packages installed. Thanks for the help diagnosing! Best, Bryan On Monday, March 30, 2020 at 8:46:08 PM UTC-6, Dima Pasechnik wrote: > > On Tue, Mar 31, 2020 at 10:37 AM B Gillespie > wrote: > > > > My system install of

Re: [sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread Dima Pasechnik
On Tue, Mar 31, 2020 at 10:37 AM B Gillespie wrote: > > My system install of libreadline-dev shows up as version 7.0-3 in synaptic. > In a local prompt for python3, "import readline" executes without barking. could you install libncurses5-dev (that's at least what is needed on Debian together

Re: [sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread B Gillespie
My installation command was: `MAKE='make -j7' make`, so I didn't see the output of running ./configure. The configure script does indeed list a number of packages it recommends installing locally -- I'll install and try recompiling to see if that fixes the issue. Thanks, Bryan On Monday,

Re: [sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread B Gillespie
My system install of libreadline-dev shows up as version 7.0-3 in synaptic. In a local prompt for python3, "import readline" executes without barking. Bryan On Monday, March 30, 2020 at 8:33:32 PM UTC-6, Dima Pasechnik wrote: > > On Tue, Mar 31, 2020 at 10:29 AM B Gillespie > wrote: > > >

Re: [sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread Dima Pasechnik
On Tue, Mar 31, 2020 at 10:33 AM Dima Pasechnik wrote: > > On Tue, Mar 31, 2020 at 10:29 AM B Gillespie wrote: > > > > Hi Matthias, > > > > For sure, thanks for taking a look. Also, I remembered that I actually > > upgraded to Linux Mint 19 a number of months ago, in case that's relevant. > >

Re: [sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread Dima Pasechnik
On Tue, Mar 31, 2020 at 10:29 AM B Gillespie wrote: > > Hi Matthias, > > For sure, thanks for taking a look. Also, I remembered that I actually > upgraded to Linux Mint 19 a number of months ago, in case that's relevant. Do you have libreadline-dev installed? > > Best, > Bryan > > On Monday,

[sage-devel] Re: Error building Sage on Linux Mint 17.1

2020-03-30 Thread Matthias Koeppe
Hi Bryan, On Monday, March 30, 2020 at 7:35:06 PM UTC-4, B Gillespie wrote: > > I'm having trouble compiling the Sage develop branch on my Linux Mint 17.1 > laptop. It dies when compiling Python 3, and in particular in the log file > I see that it is having a failure when testing the import

Re: [sage-devel] Re: Error building Sage

2020-03-11 Thread Grigory Solomatov
The installation was successful. Thank you! On Wed, 11 Mar 2020 at 21:42, Matthias Koeppe wrote: > This looks like it may be caused by an interaction with Anaconda. > Try again after deactivating the conda environment > > On Wednesday, March 11, 2020 at 3:54:43 PM UTC-4, Grigory Solomatov

[sage-devel] Re: Error building Sage

2020-03-11 Thread Matthias Koeppe
This looks like it may be caused by an interaction with Anaconda. Try again after deactivating the conda environment On Wednesday, March 11, 2020 at 3:54:43 PM UTC-4, Grigory Solomatov wrote: > > Hi, > > I am trying to build Sage from source, but get the following error: > > " > Error building

[sage-devel] Re: Error building sage package-gfortran

2020-03-05 Thread Matthias Koeppe
This looks like an interaction with an Anaconda installation -- perhaps a conda environment was active while "configure" ran but not while "make" ran. On Thursday, March 5, 2020 at 12:40:51 AM UTC-5, Arnald Dutta wrote: > > Hi, > I am facing problem with gfortran-9.2.0 while building sage. > >

Re: [sage-devel] Re: Error Building Sage

2019-06-14 Thread E. Madison Bray
On Thu, Jun 13, 2019 at 8:28 PM Dima Pasechnik wrote: > > > > On Thu, Jun 13, 2019 at 7:21 PM Brandon Gontmacher > wrote: >> >> Hi, >> >> I did allocate more memory and this cleared up the issue! Thanks for that. >> I'm now in a situation where as expected the build is taking a lot of time >>

Re: [sage-devel] Re: Error Building Sage

2019-06-13 Thread Dima Pasechnik
On Thu, Jun 13, 2019 at 7:21 PM Brandon Gontmacher wrote: > Hi, > > I did allocate more memory and this cleared up the issue! Thanks for that. > I'm now in a situation where as expected the build is taking a lot of time > but in particular it has been on the following screen with no progress for

[sage-devel] Re: Error Building Sage

2019-06-13 Thread Brandon Gontmacher
Hi, I did allocate more memory and this cleared up the issue! Thanks for that. I'm now in a situation where as expected the build is taking a lot of time but in particular it has been on the following screen with no progress for a while now [image: Selection_001.png] I know there is still a

Re: [sage-devel] Re: error building sage for Scientific Linux 7.6

2019-06-04 Thread Dima Pasechnik
On Mon, Jun 3, 2019 at 10:29 PM Charles Campbell wrote: > > > > Hello: I do have a skylake architecture (10-core, i9-7900X), and the > assembler is as: GNU assembler version 2.27-34.base.el7. your GNU assempler (released in 2016) https://mirror.koddos.net/gnu/binutils/ is older than your CPU

[sage-devel] Re: error building sage for Scientific Linux 7.6

2019-06-03 Thread Charles Campbell
Hello: I do have a skylake architecture (10-core, i9-7900X), and the assembler is as: GNU assembler version 2.27-34.base.el7. Unfortunately make -j1 openblas also gave the same error message. I tried ./configure with_blas=atlas, and got: a new error! (that seems like an improvement,

Re: [sage-devel] Re: error building sage for Scientific Linux 7.6

2019-06-03 Thread Dima Pasechnik
On Mon, 3 Jun 2019 at 08:41, E. Madison Bray wrote: > Well, this would be a problem building OpenBLAS specifically :) > > I see this same problem mentioned here as well. Maybe it will help: > https://github.com/JuliaLang/julia/issues/30696 > > I'm not sure I understand the patch on that issue

Re: [sage-devel] Re: error building sage for Scientific Linux 7.6

2019-06-03 Thread E. Madison Bray
Well, this would be a problem building OpenBLAS specifically :) I see this same problem mentioned here as well. Maybe it will help: https://github.com/JuliaLang/julia/issues/30696 I'm not sure I understand the patch on that issue that mentions cross-compiling to a 32-bit architecture. You're

[sage-devel] Re: Error building Sage

2019-02-27 Thread Quentin Hillebrand
Thank you very much, it's working perfectly. And I am the one who's sorry for not asking in English in the first place. Le jeudi 28 février 2019 07:02:49 UTC+9, John H Palmieri a écrit : > > Please try this: > > ./sage -f zlib > ./sage -f python2 python3 > make > > and see if that fixes the

[sage-devel] Re: Error building Sage

2019-02-27 Thread John H Palmieri
Please try this: ./sage -f zlib ./sage -f python2 python3 make and see if that fixes the problem. (Apologies for not responding in French.) On Wednesday, February 27, 2019 at 1:52:02 PM UTC-8, Quentin Hillebrand wrote: > > En compilant avec make j'obtiens j'obtiens une erreure lors de la >

[sage-devel] Re: Error building Sage 8.5 on Manjaro 18.0

2019-01-02 Thread Sverre Lunøe-Nielsen
Hi again, thanks to both of you. On Wednesday, January 2, 2019 at 11:52:25 AM UTC+1, Dima Pasechnik wrote: > > pacman -S gcc-fortran > > and try again > Circumventing this step made complete the build, thank you very much. On Wednesday, January 2, 2019 at 12:18:45 PM UTC+1, Volker Braun

[sage-devel] Re: Error building Sage 8.5 on Manjaro 18.0

2019-01-02 Thread Volker Braun
This is now https://trac.sagemath.org/ticket/26996 -- 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 post to this group,

Re: [sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Timo Kaufmann
Good thing you made me check. I didn't actually include gfortran into the build environment, so its saying `checking for gfortran... no`. On Tue, Oct 30, 2018 at 4:48 PM Dima Pasechnik wrote: > Well, does ./configure outputs something like > > . > gcc-7.2.0 not installed (configure

Re: [sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Dima Pasechnik
Well, does ./configure outputs something like . gcc-7.2.0 not installed (configure check) gdb-8.2 gf2x-1.2.p0 gfan-0.6.2.p0 gfortran-7.2.0 not installed (configure check) ... If so it should not build gfortran (unless you have SAGE_INSTALL_GCC set to yes for some

Re: [sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Timo Kaufmann
No, but nixos doesn't follow FHS[0], so I am using linux namespaces (more precisely this[1]) to build sage in an environment where all the build dependencies are at their FHS locations. So sage is using nixos's gfortran, the namespaces are just so it can find it where it expects it. This worked

Re: [sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Dima Pasechnik
On Tue, Oct 30, 2018 at 4:29 PM Timo Kaufmann wrote: > > Its a bit of a complicated case, but I'm not using anaconda. I'm using nixos > and a special build environment that uses linux namespaces to make sure all > the dependencies are in the location sage expects them. I'm using that to >

Re: [sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Timo Kaufmann
Its a bit of a complicated case, but I'm not using anaconda. I'm using nixos and a special build environment that uses linux namespaces to make sure all the dependencies are in the location sage expects them. I'm using that to build sage-the-distribution when testing because that won't build

Re: [sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Dima Pasechnik
On Tue, Oct 30, 2018 at 4:01 PM Timo Kaufmann wrote: > > I just had the same issue. Why do you think "several versions of gfortran > guts" are the issue? How does sage find gfortran / why does it get confused? > What's the OS you are using? How do you install Sage? I suspect it's a conflict

[sage-devel] Re: Error building sage-8.4 on Ubuntu

2018-10-30 Thread Timo Kaufmann
I just had the same issue. Why do you think "several versions of gfortran guts" are the issue? How does sage find gfortran / why does it get confused? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

Re: [sage-devel] Re: Error building Sage

2018-09-19 Thread Kathryn Burton
I tried to build it in the same directory as before. I just created a new directory and ran the pre built binary. And that worked. Thanks! On Tue, Sep 18, 2018 at 1:33 PM Erik Bray wrote: > You have some files with the wrong permissions set on them. When you > write "I decided to rebuild the

Re: [sage-devel] Re: Error building Sage

2018-09-18 Thread Erik Bray
You have some files with the wrong permissions set on them. When you write "I decided to rebuild the newest version of sage on my new computer" were you building in the same directory as before, or from scratch in a new clone of the repository? I ask because it's doubtful that an upgrade from

Re: [sage-devel] Re: Error building Sage

2018-09-18 Thread Kathryn Burton
Attached is the log for the patch. Thanks so much for all your help! On Mon, Sep 17, 2018 at 6:47 PM John H Palmieri wrote: > The file attached to the post ends with the log for patch: > > >> [patch-2.7.5] Found local metadata for patch-2.7.5 >> [patch-2.7.5] Using cached file >>

[sage-devel] Re: Error building Sage

2018-09-17 Thread John H Palmieri
The file attached to the post ends with the log for patch: > [patch-2.7.5] Found local metadata for patch-2.7.5 > [patch-2.7.5] Using cached file > /Users/knburton12/Downloads/sage-master/upstream/patch-2.7.5.tar.gz > [patch-2.7.5] patch-2.7.5 > [patch-2.7.5]

[sage-devel] Re: Error building Sage

2018-09-17 Thread Travis Scrimshaw
What package(s) is it failing on? Can you post the log files? Thanks, Travis On Tuesday, September 18, 2018 at 7:08:56 AM UTC+10, Kathryn Burton wrote: > > I built sage for the first time in Sept 2016. I decided to rebuild the > newest version of sage on my new computer, but I keep getting the

[sage-devel] Re: Error building Sage on MacBook Pro running MacOS High Sierra version 10.13.5

2018-06-11 Thread Ars-Magna
Dear Sage Development team, I was able to resolve the issue. It seems that there is a problem with the build script which performs a parallel compilation of Sage using multiple jobs. Staying clear of any sophisticated export options works just fine. Thanks and best regards, -- You

[sage-devel] Re: error building sage

2017-09-17 Thread shivam gor
It is still giving same error. On Monday, September 18, 2017 at 4:02:06 AM UTC+5:30, Dima Pasechnik wrote: > > > > On Sunday, September 17, 2017 at 10:04:41 AM UTC+1, shivam gor wrote: >> >> Yes,it starts. >> by log ,did u mean install.log file?? >> > > OK, thanks. The doc building error looks

[sage-devel] Re: error building sage

2017-09-17 Thread Dima Pasechnik
On Sunday, September 17, 2017 at 10:04:41 AM UTC+1, shivam gor wrote: > > Yes,it starts. > by log ,did u mean install.log file?? > OK, thanks. The doc building error looks strange to me, some kind of race condition? Could you try re-running with just one CPU, that is MAKE="make -j1" make

[sage-devel] Re: error building sage

2017-09-17 Thread Dima Pasechnik
Well, does Sage start? The remaining error is in building documentation, so this is a minor problem. Can you attach the log for this failure? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] Re: error building sage

2017-09-16 Thread shivam gor
previous problem got solved ,I searched it on github and found one command "make TARGET=HASWELL"and it worked,but now there is another problem above,so please give me solution for this. On Saturday, September 16, 2017 at 12:29:28 PM UTC+5:30, shivam gor wrote: > > > The following package(s) may

[sage-devel] Re: error building sage

2017-09-16 Thread shivam gor
AttributeError: 'module' object has no attribute '__file__' Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): * documentation: dochtml log file: /home/shivam/sage/logs/pkgs/../dochtml.log what should be done now?? On

Re: [sage-devel] Re: error building sage

2017-09-16 Thread shivam gor
Ubuntu 17.04 On Sep 17, 2017 6:15 AM, "Samuel Lelievre" wrote: > Sat 2017-09-16 12:51:27 UTC, shivam gor: > > yes i have installed all prerequisites > > What operating system are you using? Probably a Linux distribution? > Which one? What version? > > -- > You received

[sage-devel] Re: error building sage

2017-09-16 Thread Samuel Lelievre
Sat 2017-09-16 12:51:27 UTC, shivam gor: > yes i have installed all prerequisites What operating system are you using? Probably a Linux distribution? Which one? What version? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Re: error building sage

2017-09-16 Thread shivam gor
yes i have installed all prerequisites On Saturday, September 16, 2017 at 6:20:42 PM UTC+5:30, shivam gor wrote: > > description: Computer > width: 64 bits > capabilities: smp vsyscall32 > *-core >description: Motherboard >physical id: 0 > *-memory >

[sage-devel] Re: error building sage

2017-09-16 Thread shivam gor
description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 7880MiB *-cpu product: Intel(R) Core(TM) i5-7200U CPU

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-22 Thread Aram Dermenjian
Just as a note to humans, we are developing a fix for this as it is becoming a bigger and bigger issue. Here is the ticket: https://trac.sagemath.org/ticket/23272 -Aram On Friday, July 21, 2017 at 6:20:44 PM UTC-4, Christopher Phoenix wrote: > > BTW, forgot to link this, but you can see the

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-21 Thread Christopher Phoenix
BTW, forgot to link this, but you can see the full list of OpenBLAS targets here: https://github.com/xianyi/OpenBLAS/blob/develop/TargetList.txt This shows the reason why ATOM isn't the default choice. It would be bad if OpenBLAS picked that and you were actually running an AMD cpu, or if you

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-21 Thread Christopher Phoenix
I'm pretty sure that's an issue for upstream, not the Sage devs, maybe we should ask the OpenBLAS devs? But I suspect that the problem here is that there isn't a default choice that covers all CPU types. Atom is a catch-all for many low-end X86_64 cpus (like my Celeron), but it's not the best

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-21 Thread John H Palmieri
I just had the same problem with a new computer (Kaby Lake processor, apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but can't detect the precise CPU? (I can't do this, but maybe someone else can.) John On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-14 Thread Christopher Phoenix
Well, I have successfully built Sage on my 11e—over a period of several hours! :-) Right now I'm running the tests with ./sage --testall to make sure everything is a-ok, but cli Sage starts, as does the notebook, so it looks good so far. Maybe I'll try building the dev version of openblas on

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-14 Thread Dima Pasechnik
Indeed, OPENBLAS_CONFIGURE="TARGET=ATOM" is a catch-all x86_64 processors target. Perhaps one can try the development version of openblas on these processors (from https://github.com/xianyi/OpenBLAS) On Friday, July 14, 2017 at 12:29:12 AM UTC+1, Christopher Phoenix wrote: > > I'm building Sage

[sage-devel] Re: Error building sage devel: package: singular-4.0.3p4

2016-11-11 Thread Simon Brandhorst
Seems I posted too fast. Sorry for the spam. They error is due to a work around which I forgot to delete before building. Now it seems to work. (still building) On Friday, November 11, 2016 at 2:36:15 PM UTC+1, Simon Brandhorst wrote: > > See the log file. > > Best > > Simon > -- You received

[sage-devel] Re: Error building sage 7.3 on Fedora 24 x86_64

2016-09-23 Thread Lennart Jern
Okay, that makes sense. I had missed gcc-gfortran, thought it was enough to have just gcc! Thank you for the help! On Thursday, September 22, 2016 at 9:06:46 PM UTC+2, Volker Braun wrote: > > The easiest solution would be to install the dependencies so that Sage > doesn't attempt to compile

[sage-devel] Re: Error building sage 7.3 on Fedora 24 x86_64

2016-09-22 Thread Volker Braun
The easiest solution would be to install the dependencies so that Sage doesn't attempt to compile its own toolchain: http://doc.sagemath.org/html/en/installation/source.html#linux-prerequisite-installation On Thursday, September 22, 2016 at 8:45:34 PM UTC+2, Lennart Jern wrote: > > Hello, > >

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread Simon Brandhorst
Sage build/upgrade complete! Dear leif thank you so much for the workaround. On Friday, September 2, 2016 at 6:36:57 PM UTC+2, Simon Brandhorst wrote: > > After renaming the libomalloc.so > > Successfully installed singular-3.1.7p1.p2 > > There were a bunch of warnings in the log but i guess

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread Simon Brandhorst
After renaming the libomalloc.so Successfully installed singular-3.1.7p1.p2 There were a bunch of warnings in the log but i guess that is okay... I'll try and build the rest now. On Friday, September 2, 2016 at 6:07:56 PM UTC+2, leif wrote: > > leif wrote: > > Simon Brandhorst wrote: > >>

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread Simon Brandhorst
[singular-3.1.7p1.p2] /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:186: undefined reference to `fmpz_get_mpz' [singular-3.1.7p1.p2] /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:187:

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread leif
leif wrote: > Simon Brandhorst wrote: >> I did it triple-safe. >> Doesn't seem to work. Here is the log. > > As guessed, the sizeof(long) test fails due to a runtime linker error. > (Singular's 'configure' uses all libs found so far even in unrelated > tests, and you seem to have some libomalloc

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread leif
Simon Brandhorst wrote: > I did it triple-safe. > Doesn't seem to work. Here is the log. As guessed, the sizeof(long) test fails due to a runtime linker error. (Singular's 'configure' uses all libs found so far even in unrelated tests, and you seem to have some libomalloc system-wide which it

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread leif
leif wrote: > leif wrote: >> Simon Brandhorst wrote: >>> Thank you leif. Sorry for taking so long to answer. I did not bring my >>> laptop to work - so I could not get the log until now. >> >> Never mind. Please post / attach >>

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-02 Thread Simon Brandhorst
I did it triple-safe. Doesn't seem to work. Here is the log. -simon On Friday, September 2, 2016 at 1:48:46 AM UTC+2, leif wrote: > > leif wrote: > > leif wrote: > >> Simon Brandhorst wrote: > >>> Thank you leif. Sorry for taking so long to answer. I did not bring my > >>> laptop to work -

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
leif wrote: > leif wrote: >> Simon Brandhorst wrote: >>> Thank you leif. Sorry for taking so long to answer. I did not bring my >>> laptop to work - so I could not get the log until now. >> >> Never mind. Please post / attach >>

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
leif wrote: > Simon Brandhorst wrote: >> Thank you leif. Sorry for taking so long to answer. I did not bring my >> laptop to work - so I could not get the log until now. > > Never mind. Please post / attach > /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
leif wrote: > Simon Brandhorst wrote: >> Thank you leif. Sorry for taking so long to answer. I did not bring my >> laptop to work - so I could not get the log until now. > > Never mind. Please post / attach > /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
Simon Brandhorst wrote: > Thank you leif. Sorry for taking so long to answer. I did not bring my > laptop to work - so I could not get the log until now. Never mind. Please post / attach /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log . > A workaround would

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread Simon Brandhorst
Thank you leif. Sorry for taking so long to answer. I did not bring my laptop to work - so I could not get the log until now. A workaround would be great. Then I can get started. Tried to build sage devel at work and got a different error. Should I open a thread for that as well? (If it works

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
Dima Pasechnik wrote: > not sure whether it's worth the trouble fighting with outdated Singular > package refusing to work with > gcc 6.1.1. Perhaps it might be easier to use the bleeding edge > https://trac.sagemath.org/ticket/17635 and > https://trac.sagemath.org/ticket/17254 Well, he was

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread Dima Pasechnik
On Thursday, September 1, 2016 at 8:48:13 AM UTC, leif wrote: > > Simon Brandhorst wrote: > > So here are the logs. And a larger bit of the install.log > > Thanks, but we'd need the config.log files from Singular, not Sage's > top-level one, in your case: > >

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
leif wrote: > Simon Brandhorst wrote: >> So here are the logs. And a larger bit of the install.log > > Thanks, but we'd need the config.log files from Singular, not Sage's > top-level one, in your case: > > /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log > >

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread leif
Simon Brandhorst wrote: > So here are the logs. And a larger bit of the install.log Thanks, but we'd need the config.log files from Singular, not Sage's top-level one, in your case: /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log and since omalloc takes an

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread Simon Brandhorst
So here are the logs. And a larger bit of the install.log singular-3.1.7p1.p2] loading cache .././config.cache [singular-3.1.7p1.p2] checking whether make -j1 sets ${MAKE}... (cached) yes [singular-3.1.7p1.p2] checking for gcc... (cached) gcc [singular-3.1.7p1.p2] checking whether the C compiler

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-09-01 Thread Simon Brandhorst
Dear leif, dear Nils, Thank you for your replies. > That's obviously wrong. It should get 8 there. You might want to do a: > > $ grep "size of long" install.log > $grep "size of long" install.log [python2-2.7.10.p2] checking size of long... 8 [python2-2.7.10.p2] checking size of long long... 8

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-08-31 Thread leif
Simon Brandhorst wrote: > So far I am using precompiled binaries. They work. Now I am thinking on > writing my own branch/contributing to sage so I followed the instructions on > > http://doc.sagemath.org/html/en/developer/walk_through.html > > to get a developer version of sage. > Basically I

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-08-31 Thread Nils Bruin
On Wednesday, August 31, 2016 at 12:38:51 PM UTC-7, Simon Brandhorst wrote: > > So far I am using precompiled binaries. They work. Now I am thinking on > writing my own branch/contributing to sage so I followed the instructions on > > http://doc.sagemath.org/html/en/developer/walk_through.html >

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

2016-08-31 Thread Simon Brandhorst
Just in case some more hardware details: Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):8 On-line CPU(s) list: 0-7 Thread(s) per core:2 Core(s) per socket:4 Socket(s): 1 NUMA node(s): 1

[sage-devel] Re: Error Building Sage

2016-05-18 Thread Dima Pasechnik
typically, after a change that does not touch a library that is used a lot by Sage components, running make will take a couple of minutes, most of it spent on updating documentation. (sometimes, if documentation is messed up badly, you'd need to do 'make doc-clean', before make, then it's 5-10

[sage-devel] Re: Error Building Sage

2016-05-17 Thread saad khalid
So, I ran 'make distclean', and then I made sure that my develop branch was up to date, and then I did make build and it ran properly and I was able to do the doctest I had been trying to do before! Should I still run 'make'? I'm kind of afraid that it will mess up again, it takes like 8-12

[sage-devel] Re: Error Building Sage

2016-05-16 Thread John H Palmieri
Rather than deleting the entire Sage directory, you should be able to start from scratch by doing 'make distclean' and then 'make'. Is your 'develop' branch up to date? On Sunday, May 15, 2016 at 8:46:41 AM UTC-7, saad khalid wrote: > > Hey everyone: > > So, here's the issue. I was facing

[sage-devel] Re: error building sage

2015-12-27 Thread jhonrubia6
Hi. Everything worked fine after the second 'make'. now version is 7.0.beta1 thank you all El viernes, 25 de diciembre de 2015, 20:37:07 (UTC+1), jhonrubia6 escribió: > > Hi, > this is the first time I try to contribute. I began making a single change > in the comments, here is the diff >

[sage-devel] Re: error building sage

2015-12-26 Thread Volker Braun
Checking out a branch changes the entire source tree to that branch; Depending on which branch it is you need to re-run "make" as it is likely an entirely different Sage version. On Saturday, December 26, 2015 at 4:53:17 PM UTC+1, jhonrubia6 wrote: > > Hi, > I downloaded sage 6.10 source

[sage-devel] Re: error building sage

2015-12-26 Thread Volker Braun
On Saturday, December 26, 2015 at 9:17:35 AM UTC+1, Dima Pasechnik wrote: > > did you compile your Sage installation from source? > (probably noone tests Sage binary distributions for ability to compile > C/C++...) > No, that is tested and works for me. I'm guessing the OP changed his git

[sage-devel] Re: error building sage

2015-12-26 Thread Dima Pasechnik
On Friday, 25 December 2015 22:50:02 UTC, jhonrubia6 wrote: > > I did as you suggested (./sage -ba). Same result > /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:5020:165: > > error: no matching function for call to >

[sage-devel] Re: error building sage

2015-12-26 Thread jhonrubia6
Hi, I downloaded sage 6.10 source code, "make" it without problems (run sage ok), checked out a branch for a ticket I just opened. modified the /src/sage/plot/hyperbolic_arc.py adding only a comment with my name, and just for check I understood the procedure as describer in the web, I did sage

[sage-devel] Re: error building sage

2015-12-25 Thread Volker Braun
Can you try "sage -ba" On Friday, December 25, 2015 at 8:37:07 PM UTC+1, jhonrubia6 wrote: > > Hi, > this is the first time I try to contribute. I began making a single change > in the comments, here is the diff > MacBook-de-Javier:sage-6.10 t143730$ git diff > diff --git

[sage-devel] Re: error building sage

2015-12-25 Thread jhonrubia6
I did as you suggested (./sage -ba). Same result /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:5020:165: error: no matching function for call to 'bkzReduction(fplll::ZZ_mat<__mpz_struct [1]>*&, NULL, fplll::BKZParam&, fplll::FloatType, int&)' __pyx_v_r

[sage-devel] Re: Error building Sage

2015-08-21 Thread Volker Braun
You could try the cython upgrade #18927, might be fixed there A workaround is to build Sage in a directory whose name does not contain accents. On Friday, August 21, 2015 at 7:49:31 AM UTC-4, Anthony OLLB wrote: Hello, I attempted to compile SageMath 6.8-i686 from source on 32-bit

[sage-devel] Re: Error building Sage

2015-08-21 Thread Anthony OLLB
Thank tou for your help ! I installed cython on my computer because it wasn't on and I move the directory of SAGE in order to avoid accents and when I compiled 'make', there wasn't error anymore. So now I can play with SAGE ! Thanks :) -- You received this message because you are subscribed

[sage-devel] Re: Error building Sage (gcc-4.9.2.p1)

2015-05-04 Thread leif
François Bissey wrote: I am afraid you'll need to get 6.7.beta3 to get the needed fix to build gcc with xcode 6.3.1. That fix [1] is not even in Sage 6.7.beta3. The following /should/^TM work though: export GCC_CONFIGURE=--with-build-config=bootstrap-debug make No guarantees; you may

  1   2   >