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

[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.
I uninstalled the old gmp in /usr/local too.


A more lightweight approach is to use gmp from  your OS. On most Linux 
systems supported by Sage the OS-provided
gmp version is good enough.
(you'd do  "sudo apt install libgmp-dev" to install it)
Once you don't use gmp from OS, you cannot use any OS-provided package 
which depends on gmp, and make
building Sage much slower.



 


Thanks for your help!

Aurore.

Le mardi 16 janvier 2024 à 20:59:07 UTC+1, Matthias Koeppe a écrit :

>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 Monday, January 15, 2024 at 1:59:28 PM UTC-8 Aurore Guillevic wrote:

Dear Sagemath developers,, 

I am trying to install sagemath from git. 
I am following the instructions at 
https://doc.sagemath.org/html/en/installation/source.html 

First I did a tentative without anything special when configuring, but 
there were errors building singular and eclib. Then I tried to force 
sagemath to use the packages of the system (ubuntu) instead of installing 
them again so I tried: 

git clean -x -f -d # clean the previous tentative of installation 

export MAKE="make -j4" # exploit the 4 processors 
make configure 
./configure --help 
./configure --with-system-singular=yes --with-system-eclib=yes 
--config-cache --enable-ccache 

First there is this repeated warning: 

[flint-3.0.1] ./src/ulong_extras.h:92:36: warning: implicit declaration of 
function 'mpn_gcd_11'; did you mean 'mpn_gcd_1'? 
[-Wimplicit-function-declaration] 
[flint-3.0.1]92 | res = (x != 1 && y != 1) ? mpn_gcd_11(x, y) : 
1; 

Then 
[singular-4.3.2p8] Error installing package singular-4.3.2p8 
The two log files are attached to this email. 

I suspect the problem is some incompatibility of versions of packages? 
(very common with a ubuntu LTS). Here are the installed packages: 

apt list **eclib** **singular** 
En train de lister... Fait 
eclib-tools/jammy,now 20210625-1build1 amd64  [installé] 
libsingular4-dev-common/jammy,jammy,now 1:4.2.1-p3+ds-1 all [installé, 
automatique] 
libsingular4-dev/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé] 
libsingular4m2n1/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
singular-data/jammy,jammy,now 1:4.2.1-p3+ds-1 all  [installé, automatique] 
singular-doc/jammy,jammy,now 1:4.2.1-p3+ds-1 all  [installé] 
singular-modules/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
singular-ui/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
singular/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé] 


Many thanks for your help, 

Aurore. 

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/814e7a90-874f-471c-8769-421ef9bab400n%40googlegroups.com.

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

[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!

Aurore.

Le mardi 16 janvier 2024 à 20:59:07 UTC+1, Matthias Koeppe a écrit :

> 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 Monday, January 15, 2024 at 1:59:28 PM UTC-8 Aurore Guillevic wrote:
>
>> Dear Sagemath developers,, 
>>
>> I am trying to install sagemath from git. 
>> I am following the instructions at 
>> https://doc.sagemath.org/html/en/installation/source.html 
>>
>> First I did a tentative without anything special when configuring, but 
>> there were errors building singular and eclib. Then I tried to force 
>> sagemath to use the packages of the system (ubuntu) instead of installing 
>> them again so I tried: 
>>
>> git clean -x -f -d # clean the previous tentative of installation 
>>
>> export MAKE="make -j4" # exploit the 4 processors 
>> make configure 
>> ./configure --help 
>> ./configure --with-system-singular=yes --with-system-eclib=yes 
>> --config-cache --enable-ccache 
>>
>> First there is this repeated warning: 
>>
>> [flint-3.0.1] ./src/ulong_extras.h:92:36: warning: implicit declaration 
>> of function 'mpn_gcd_11'; did you mean 'mpn_gcd_1'? 
>> [-Wimplicit-function-declaration] 
>> [flint-3.0.1]92 | res = (x != 1 && y != 1) ? mpn_gcd_11(x, y) 
>> : 1; 
>>
>> Then 
>> [singular-4.3.2p8] Error installing package singular-4.3.2p8 
>> The two log files are attached to this email. 
>>
>> I suspect the problem is some incompatibility of versions of packages? 
>> (very common with a ubuntu LTS). Here are the installed packages: 
>>
>> apt list **eclib** **singular** 
>> En train de lister... Fait 
>> eclib-tools/jammy,now 20210625-1build1 amd64  [installé] 
>> libsingular4-dev-common/jammy,jammy,now 1:4.2.1-p3+ds-1 all [installé, 
>> automatique] 
>> libsingular4-dev/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé] 
>> libsingular4m2n1/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
>> singular-data/jammy,jammy,now 1:4.2.1-p3+ds-1 all  [installé, 
>> automatique] 
>> singular-doc/jammy,jammy,now 1:4.2.1-p3+ds-1 all  [installé] 
>> singular-modules/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
>> singular-ui/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
>> singular/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé] 
>>
>>
>> Many thanks for your help, 
>>
>> Aurore. 
>
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/508f2763-7515-4b62-ac28-63d1cf30cdb8n%40googlegroups.com.

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

[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 Monday, January 15, 2024 at 1:59:28 PM UTC-8 Aurore Guillevic wrote:

> Dear Sagemath developers,, 
>
> I am trying to install sagemath from git. 
> I am following the instructions at 
> https://doc.sagemath.org/html/en/installation/source.html 
>
> First I did a tentative without anything special when configuring, but 
> there were errors building singular and eclib. Then I tried to force 
> sagemath to use the packages of the system (ubuntu) instead of installing 
> them again so I tried: 
>
> git clean -x -f -d # clean the previous tentative of installation 
>
> export MAKE="make -j4" # exploit the 4 processors 
> make configure 
> ./configure --help 
> ./configure --with-system-singular=yes --with-system-eclib=yes 
> --config-cache --enable-ccache 
>
> First there is this repeated warning: 
>
> [flint-3.0.1] ./src/ulong_extras.h:92:36: warning: implicit declaration of 
> function 'mpn_gcd_11'; did you mean 'mpn_gcd_1'? 
> [-Wimplicit-function-declaration] 
> [flint-3.0.1]92 | res = (x != 1 && y != 1) ? mpn_gcd_11(x, y) 
> : 1; 
>
> Then 
> [singular-4.3.2p8] Error installing package singular-4.3.2p8 
> The two log files are attached to this email. 
>
> I suspect the problem is some incompatibility of versions of packages? 
> (very common with a ubuntu LTS). Here are the installed packages: 
>
> apt list **eclib** **singular** 
> En train de lister... Fait 
> eclib-tools/jammy,now 20210625-1build1 amd64  [installé] 
> libsingular4-dev-common/jammy,jammy,now 1:4.2.1-p3+ds-1 all [installé, 
> automatique] 
> libsingular4-dev/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé] 
> libsingular4m2n1/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
> singular-data/jammy,jammy,now 1:4.2.1-p3+ds-1 all  [installé, automatique] 
> singular-doc/jammy,jammy,now 1:4.2.1-p3+ds-1 all  [installé] 
> singular-modules/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
> singular-ui/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé, automatique] 
> singular/jammy,now 1:4.2.1-p3+ds-1 amd64  [installé] 
>
>
> Many thanks for your help, 
>
> Aurore. 

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/18586ae2-4824-464a-b30c-b9a30e12c4bfn%40googlegroups.com.

[sage-devel] Re: Error building sage

[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: 
dlopen(/Users/allisonfitisone/sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-darwin.so,
 
0x0002): Library not loaded: 
/usr/local/opt/gcc/lib/gcc/11/libgfortran.5.dylib
Referenced from: 
/Users/allisonfitisone/sage/local/lib/libopenblas_haswellp-r0.3.20.dylib
Reason: tried: '/usr/local/opt/gcc/lib/gcc/11/libgfortran.5.dylib' (no 
such file), '/usr/local/lib/libgfortran.5.dylib' (no such file), 
'/usr/lib/libgfortran.5.dylib' (no such file)
===

This is likely caused by an update of homebrew.
You can fix this by rebuilding from scratch (for example, using "make 
distclean").

To save time of a complete rebuild, you can try to use the branch of this 
ticket: https://trac.sagemath.org/ticket/34203:

git fetch trac 
u/mkoeppe/find_and_uninstall_broken_installed_spkgs_and_wheels && git merge 
FETCH_HEAD && make -j list-broken-packages

This command will give more specific cleaning instructions.

 


On Thursday, September 8, 2022 at 6:50:56 AM UTC-7 allison...@gmail.com 
wrote:

> Hi all,
>
> I'm having trouble building sage. I'm using a MacBook Pro with macOS 
> Monterey. I've attached a screenshot of the error I get and the relevant 
> logs. Please advise.
>
> Thanks,
> Alli
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/886009a8-c0ed-4035-ba9e-d77cd9507562n%40googlegroups.com.

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

[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:

> 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:
>> >```
>> >$ 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 recommendations at end of configure output.
>> >
>> >Finally decide number of parallel jobs
>> >```
>> >$ export MAKE='make -j8'
>> >```
>> >and run make again:
>> >```
>> >$ make -s V=0
>>
>> That helped. Sage is now *almost* completely installed.
>> However, now a different problem appeared. 
>> While installing the docs, the following error occured:
>>
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:34: 
>> WARNING: unknown document: categories/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:76: 
>> WARNING: unknown document: groups/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:79: 
>> WARNING: unknown document: algebras/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:84: 
>> WARNING: unknown document: combinat/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:85: 
>> WARNING: unknown document: graphs/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:89: 
>> WARNING: unknown document: coding/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:105: 
>> WARNING: unknown document: knots/index
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:157: 
>> WARNING: unknown document: libs/index
>> >[reference] The inventory files are in 
>> ../../local/share/doc/sage/inventory/en/reference.
>> >Error building the documentation.
>> >Traceback (most recent call last):
>> >  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
>> >return _run_code(code, main_globals, None,
>> >  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
>> >exec(code, run_globals)
>> >  File 
>> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
>>  
>> line 500, in 
>> >sys.exit(main())
>> >  File 
>> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
>>  
>> line 497, in main
>> >builder()
>> >  File 
>> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/builders.py",
>>  
>> line 167, in f
>> >runsphinx()
>> >  File 
>> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
>>  
>> line 327, in runsphinx
>> >sys.stderr.raise_errors()
>> >  File 
>> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
>>  
>> line 263, in raise_errors
>> >raise OSError(self._error)
>> >OSError: /home/Ray/sage/sage/src/doc/en/reference/index.rst:34: WARNING: 
>> unknown document: categories/index
>> >
>> >Note: incremental documentation builds sometimes cause spurious
>> >error messages. To be certain that these are real errors, run
>> >"make doc-clean doc-uninstall" first and try again.
>> >make[6]: *** [Makefile:27: doc-inventory--reference_top] Error 1
>> >make[5]: *** [Makefile:45: doc-inventory-reference] Error 2
>>
>> I tried
>> ```
>> $make doc-clean doc-uninstall
>> $make configure
>> $./configure
>> $make -s V=0
>> ```
>> and it raised the same error (log file is attached).
>> It appears that some of the docs are not building completely; this is a 
>> part of the log:
>> >[knots] building [inventory]: targets for 4 source files that are 
>> out of date
>> >[knots] updating environment: [new config] 4 added, 0 changed, 0 
>> removed
>> >[lfunction] building [inventory]: targets for 5 source files that are 
>> out of date
>> >[lfunction] updating environment: [new config] 5 added, 0 changed, 0 
>> removed
>> >[lfunction] The inventory files are in 
>> ../../local/share/doc/sage/inventory/en/reference/lfunctions.
>> >Build finished. The built documents can be found in 
>> /home/Ray/sage/sage/local/share/doc/sage/inventory/en/reference/lfunctions
>> And later I get this:
>> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:105: 
>> WARNING: unknown document: knots/index 
>>
>> What is the best thing to do 

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

[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:
> >```
> >$ 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 recommendations at end of configure output.
> >
> >Finally decide number of parallel jobs
> >```
> >$ export MAKE='make -j8'
> >```
> >and run make again:
> >```
> >$ make -s V=0
>
> That helped. Sage is now *almost* completely installed.
> However, now a different problem appeared.
> While installing the docs, the following error occured:
>
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:34:
> WARNING: unknown document: categories/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:76:
> WARNING: unknown document: groups/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:79:
> WARNING: unknown document: algebras/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:84:
> WARNING: unknown document: combinat/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:85:
> WARNING: unknown document: graphs/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:89:
> WARNING: unknown document: coding/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:105:
> WARNING: unknown document: knots/index
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:157:
> WARNING: unknown document: libs/index
> >[reference] The inventory files are in
> ../../local/share/doc/sage/inventory/en/reference.
> >Error building the documentation.
> >Traceback (most recent call last):
> >  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
> >return _run_code(code, main_globals, None,
> >  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
> >exec(code, run_globals)
> >  File
> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
> line 500, in 
> >sys.exit(main())
> >  File
> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
> line 497, in main
> >builder()
> >  File
> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/builders.py",
> line 167, in f
> >runsphinx()
> >  File
> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
> line 327, in runsphinx
> >sys.stderr.raise_errors()
> >  File
> "/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
> line 263, in raise_errors
> >raise OSError(self._error)
> >OSError: /home/Ray/sage/sage/src/doc/en/reference/index.rst:34: WARNING:
> unknown document: categories/index
> >
> >Note: incremental documentation builds sometimes cause spurious
> >error messages. To be certain that these are real errors, run
> >"make doc-clean doc-uninstall" first and try again.
> >make[6]: *** [Makefile:27: doc-inventory--reference_top] Error 1
> >make[5]: *** [Makefile:45: doc-inventory-reference] Error 2
>
> I tried
> ```
> $make doc-clean doc-uninstall
> $make configure
> $./configure
> $make -s V=0
> ```
> and it raised the same error (log file is attached).
> It appears that some of the docs are not building completely; this is a
> part of the log:
> >[knots] building [inventory]: targets for 4 source files that are out
> of date
> >[knots] updating environment: [new config] 4 added, 0 changed, 0
> removed
> >[lfunction] building [inventory]: targets for 5 source files that are out
> of date
> >[lfunction] updating environment: [new config] 5 added, 0 changed, 0
> removed
> >[lfunction] The inventory files are in
> ../../local/share/doc/sage/inventory/en/reference/lfunctions.
> >Build finished. The built documents can be found in
> /home/Ray/sage/sage/local/share/doc/sage/inventory/en/reference/lfunctions
> And later I get this:
> >[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:105:
> WARNING: unknown document: knots/index
>
> What is the best thing to do there?
> It's the same packages that cause the trouble in both runs.
>
> Thank you very much in advance!
>
> Max
>
> Samuel Lelievre schrieb am Montag, 25. Juli 2022 um 09:17:47 UTC+9:
>
>> 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

[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 configure
>$ ./configure
>```
>
>Follow any recommendations at end of configure output.
>
>Finally decide number of parallel jobs
>```
>$ export MAKE='make -j8'
>```
>and run make again:
>```
>$ make -s V=0

That helped. Sage is now *almost* completely installed.
However, now a different problem appeared. 
While installing the docs, the following error occured:

>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:34: 
WARNING: unknown document: categories/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:76: 
WARNING: unknown document: groups/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:79: 
WARNING: unknown document: algebras/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:84: 
WARNING: unknown document: combinat/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:85: 
WARNING: unknown document: graphs/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:89: 
WARNING: unknown document: coding/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:105: 
WARNING: unknown document: knots/index
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:157: 
WARNING: unknown document: libs/index
>[reference] The inventory files are in 
../../local/share/doc/sage/inventory/en/reference.
>Error building the documentation.
>Traceback (most recent call last):
>  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
>return _run_code(code, main_globals, None,
>  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
>exec(code, run_globals)
>  File 
"/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
 
line 500, in 
>sys.exit(main())
>  File 
"/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
 
line 497, in main
>builder()
>  File 
"/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/builders.py",
 
line 167, in f
>runsphinx()
>  File 
"/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
 
line 327, in runsphinx
>sys.stderr.raise_errors()
>  File 
"/home/Ray/sage/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
 
line 263, in raise_errors
>raise OSError(self._error)
>OSError: /home/Ray/sage/sage/src/doc/en/reference/index.rst:34: WARNING: 
unknown document: categories/index
>
>Note: incremental documentation builds sometimes cause spurious
>error messages. To be certain that these are real errors, run
>"make doc-clean doc-uninstall" first and try again.
>make[6]: *** [Makefile:27: doc-inventory--reference_top] Error 1
>make[5]: *** [Makefile:45: doc-inventory-reference] Error 2

I tried
```
$make doc-clean doc-uninstall
$make configure
$./configure
$make -s V=0
```
and it raised the same error (log file is attached).
It appears that some of the docs are not building completely; this is a 
part of the log:
>[knots] building [inventory]: targets for 4 source files that are out 
of date
>[knots] updating environment: [new config] 4 added, 0 changed, 0 
removed
>[lfunction] building [inventory]: targets for 5 source files that are out 
of date
>[lfunction] updating environment: [new config] 5 added, 0 changed, 0 
removed
>[lfunction] The inventory files are in 
../../local/share/doc/sage/inventory/en/reference/lfunctions.
>Build finished. The built documents can be found in 
/home/Ray/sage/sage/local/share/doc/sage/inventory/en/reference/lfunctions
And later I get this:
>[reference] /home/Ray/sage/sage/src/doc/en/reference/index.rst:105: 
WARNING: unknown document: knots/index 

What is the best thing to do there?
It's the same packages that cause the trouble in both runs.

Thank you very much in advance!

Max

Samuel Lelievre schrieb am Montag, 25. Juli 2022 um 09:17:47 UTC+9:

> 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 recommendations at end of configure output.
>
> Finally decide number of parallel jobs
> ```
> $ export MAKE='make -j8'
> ```
> and run make again:
> ```
> $ make -s V=0
> ```
>
>

-- 
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 

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

[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 recommendations at end of configure output.

Finally decide number of parallel jobs
```
$ export MAKE='make -j8'
```
and run make again:
```
$ make -s V=0
```

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/eec6cc12-e02c-4ad0-8e68-d1998235cd19n%40googlegroups.com.

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

[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:
> > ##  ##
> > ## Checking whether SageMath should install SPKG python3... ##
> > ##  ##
> > configure:34869: checking whether any of bzip2 liblzma libffi is installed 
> > as or will be installed as SPKG
> > configure:34874: result: yes; install python3 as well
> > configure:36263: no suitable system package found for SPKG python3
>
> I see. Does that mean that the install script can't find my python3?

no, read what it says:
configure:34869: checking whether any of bzip2 liblzma libffi is
installed as or will be installed as SPKG
configure:34874: result: yes; install python3 as well

it says that one of the the Cygwin packages: bzip2, or  liblzma, or
libffi is not installed, and
this is the reason that the system Python3 cannot be used.

You need to install bzip2 liblzma libffi
and try running ./configure again

> Is there any path variable that I should change? If not, how do I find out 
> what's broken?
> I apologise in advance if these questions are naive; I'm quite new new all 
> this.
>
> Thanks very much in advance!
>
> Matthias Koeppe schrieb am Montag, 25. Juli 2022 um 02:34:53 UTC+9:
>>
>> 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 'make' 
>>> is not trying to build openssl anymore.
>>> Perhaps also relevant: python3 is installed on my machine, but it's Python 
>>> 3.9.10 whereas Sage seems to require Python 3.10.5.
>>
>>
>> No, Sage accepts any system Python >= 3.8.
>>
>>>
>>> But cygwin doesn't seem to have it: 
>>> https://cygwin.com/packages/summary/python3.html
>>>
>>> I attached the config log and the python log.
>>
>>
>> In your config.log one can see that system python3 is not rejected because 
>> of a version check:
>> ##  ##
>> ## Checking whether SageMath should install SPKG python3... ##
>> ##  ##
>> configure:34869: checking whether any of bzip2 liblzma libffi is installed 
>> as or will be installed as SPKG
>> configure:34874: result: yes; install python3 as well
>> configure:36263: no suitable system package found for SPKG python3
>>
>>
>>
> --
> 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 this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/fdfbc9c7-4a45-48f1-8b61-931eeca8b5b4n%40googlegroups.com.

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3C0x6HK3gcDxFasybc9ig%3D%2BJ%3Dmogb%2B_q1CTk15vNJFBQ%40mail.gmail.com.

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

[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 SageMath should install SPKG python3... ## 
> ##  ## 
> configure:34869: checking whether any of bzip2 liblzma libffi is 
installed as or will be installed as SPKG 
> configure:34874: result: yes; install python3 as well 
> configure:36263: no suitable system package found for SPKG python3

I see. Does that mean that the install script can't find my python3?
Is there any path variable that I should change? If not, how do I find out 
what's broken?
I apologise in advance if these questions are naive; I'm quite new new all 
this.

Thanks very much in advance!

Matthias Koeppe schrieb am Montag, 25. Juli 2022 um 02:34:53 UTC+9:

> 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 
>> 'make' is not trying to build openssl anymore.
>> Perhaps also relevant: python3 is installed on my machine, but it's 
>> Python 3.9.10 whereas Sage seems to require Python 3.10.5. 
>>
>
> No, Sage accepts any system Python >= 3.8. 
>  
>
>> But cygwin doesn't seem to have it: 
>> https://cygwin.com/packages/summary/python3.html
>>
>> I attached the config log and the python log.
>>
>
> In your config.log one can see that system python3 is not rejected because 
> of a version check:
> ##  ## 
> ## Checking whether SageMath should install SPKG python3... ## 
> ##  ## 
> configure:34869: checking whether any of bzip2 liblzma libffi is installed 
> as or will be installed as SPKG 
> configure:34874: result: yes; install python3 as well 
> configure:36263: no suitable system package found for SPKG python3
>
>
>
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fdfbc9c7-4a45-48f1-8b61-931eeca8b5b4n%40googlegroups.com.

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

[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 'make' 
> is not trying to build openssl anymore.
> Perhaps also relevant: python3 is installed on my machine, but it's Python 
> 3.9.10 whereas Sage seems to require Python 3.10.5. 
>

No, Sage accepts any system Python >= 3.8. 
 

> But cygwin doesn't seem to have it: 
> https://cygwin.com/packages/summary/python3.html
>
> I attached the config log and the python log.
>

In your config.log one can see that system python3 is not rejected because 
of a version check:
##  ## 
## Checking whether SageMath should install SPKG python3... ## 
##  ## 
configure:34869: checking whether any of bzip2 liblzma libffi is installed 
as or will be installed as SPKG 
configure:34874: result: yes; install python3 as well 
configure:36263: no suitable system package found for SPKG python3



-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cedea39b-559d-47db-8bce-6be38c2df262n%40googlegroups.com.

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

[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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/22793c53-53db-4611-8a99-e326c6ac3258n%40googlegroups.com.

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

[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.
>
> [openssl-3.0.4] 
> 
> [openssl-3.0.4] Error installing package openssl-3.0.4
> [openssl-3.0.4] 
> 
> [openssl-3.0.4] Please email sage-devel (
> http://groups.google.com/group/sage-devel)
> [openssl-3.0.4] explaining the problem and including the log files
> [openssl-3.0.4]   /home/Ray/sage/sage/logs/pkgs/openssl-3.0.4.log
> [openssl-3.0.4] and
> [openssl-3.0.4]   /home/Ray/sage/sage/config.log
> [openssl-3.0.4] Describe your computer, operating system, etc.
> [openssl-3.0.4] If you want to try to fix the problem yourself, *don't* 
> just cd to
> [openssl-3.0.4] /home/Ray/sage/sage/local/var/tmp/sage/build/openssl-3.0.4 
> and type 'make' or whatever is appropriate.
> [openssl-3.0.4] Instead, the following commands setup all environment 
> variables
> [openssl-3.0.4] correctly and load a subshell for you to debug the error:
> [openssl-3.0.4]   (cd 
> '/home/Ray/sage/sage/local/var/tmp/sage/build/openssl-3.0.4' && 
> '/home/Ray/sage/sage/sage' --buildsh)
> [openssl-3.0.4] When you are done debugging, you can type "exit" to leave 
> the subshell.
> [openssl-3.0.4] 
> 
> make[4]: *** [Makefile:2858: openssl-SAGE_LOCAL-no-deps] Error 1
> make[3]: *** [Makefile:2858: 
> /home/Ray/sage/sage/local/var/lib/sage/installed/openssl-3.0.4] Error 2
> make[2]: *** [Makefile:2562: all-start] Error 2
> make[2]: Leaving directory '/home/Ray/sage/sage/build/make'
>
> real346m50.600s
> user35m57.071s
> sys 30m16.874s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: openssl-3.0.4
>   last build time: Jul 19 17:04
>   log file:/home/Ray/sage/sage/logs/pkgs/openssl-3.0.4.log
>   build directory: 
> /home/Ray/sage/sage/local/var/tmp/sage/build/openssl-3.0.4
>
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> WARNING: If you now run 'make' again, the build directory of the
> same version of the package will, by default, be deleted. Set the
> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
>
> make[1]: *** [Makefile:40: all-start] Error 1
> make[1]: Leaving directory '/home/Ray/sage/sage'
> make: *** [Makefile:13: all] Error 2
>
> Attached, you will find the logfile.
>
> Thank you very much in advance!
>
> Max 
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2d2a3fdd-7f22-48da-933e-0edf65cafc8en%40googlegroups.com.

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

[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 $SAGE_ROOT/logs/pkgs).

Furthermore, config printed :

configure:83400:

notice: the following SPKGs did not find equivalent system packages:
appdirs arb boost_cropped brial cddlib cliquer curl distlib ecl eclib ecm 
fflas_ffpack filelock flint flintqs fplll freetype gc gengetopt
gf2x gfan giac givaro glpk gsl iml lcalc libatomic_ops libbraiding libgd 
libhomfly liblzma libpng linbox lrcalc m4ri m4rie mpc mpfi
ncurses ntl openblas openssl palp pari pari_galdata pari_seadata_small 
planarity ppl primecount primesieve python3 qhull r readline
rw singular sqlite suitesparse symmetrica sympow tachyon toml tox virtualenv 
zeromq zn_poly   4ti2 cbc coxeter3 gp2c igraph isl
libsemigroups lrslib pari_elldata pari_galpol pari_nftables pari_seadata 
polymake _recommended

Did you try to follow this hint ?

HTH,
​
Le lundi 18 avril 2022 à 22:41:31 UTC+2, tristanp...@gmail.com a écrit :

> Hello,
>
> A little while ago I downloaded sage 9.5 from source without issue. But 
> recently, when trying to build via git, I am getting an "Error installing 
> package r-3.6.3." Attached are the relevant log files. Any help resolving 
> this issue would be greatly appreciated.
>
> Thank you,
> Tristan
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/32472b5e-52fd-45d6-b8bd-18d162cb8c12n%40googlegroups.com.

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

[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 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 with readline) and try again? 
>
> (but, indeed, also please look at the hints at the end of 
> ./configure's output, and follow them) 
>
> > 
> > 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: 
> >> > 
> >> > 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, March 30, 2020 at 5:42:09 PM UTC-6, Matthias Koeppe wrote: 
> >> >> 
> >> >> 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 for 
> the module "readline".  Any ideas what might be the issue? 
> >> >>> 
> >> >>> As a little more info, I've successfully built older versions of 
> Sage on this operating system (earlier in the 18.X timeframe) but haven't 
> needed to build from source since 19.X.  I've attached the log file for the 
> python3 build; let me know if any other information would be helpful. 
> >> >> 
> >> >> 
> >> >> The top-level config.log would be helpful. 
> >> >> 
> >> >> 
> >> >> 
> >> >> 
> >> > 
> >> > -- 
> >> > 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-...@googlegroups.com. 
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/aad88984-0d68-4bfe-828c-a9e58f2db95a%40googlegroups.com.
>  
>
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/7c952869-610a-4f4c-82c0-878e980f2966%40googlegroups.com.
>  
>
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/46cb568c-01a2-4856-b2bd-c9045d13a88b%40googlegroups.com.

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

[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 with readline) and try again?

(but, indeed, also please look at the hints at the end of
./configure's output, and follow them)

>
> 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:
>> >
>> > 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, March 30, 2020 at 5:42:09 PM UTC-6, Matthias Koeppe wrote:
>> >>
>> >> 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 for 
>> >>> the module "readline".  Any ideas what might be the issue?
>> >>>
>> >>> As a little more info, I've successfully built older versions of Sage on 
>> >>> this operating system (earlier in the 18.X timeframe) but haven't needed 
>> >>> to build from source since 19.X.  I've attached the log file for the 
>> >>> python3 build; let me know if any other information would be helpful.
>> >>
>> >>
>> >> The top-level config.log would be helpful.
>> >>
>> >>
>> >>
>> >>
>> >
>> > --
>> > 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-...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/aad88984-0d68-4bfe-828c-a9e58f2db95a%40googlegroups.com.
>
> --
> 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 this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/7c952869-610a-4f4c-82c0-878e980f2966%40googlegroups.com.

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2_ENHVOQJkCSw8y1ih6aUDSDrcbShc%2BU-O5XQY%3Dm57fw%40mail.gmail.com.

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

[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, March 30, 2020 at 8:36:50 PM UTC-6, Dima Pasechnik wrote:
>
> 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. 
> > 
> > Do you have  libreadline-dev installed? 
>
> By the way, do you see at the end of the ./confugure run a list of 
> packages recommended to be installed? 
> E.g. on Fedora one would see something like 
>
> configure: Hint: Installing the following system packages is 
> recommended and may avoid building some of the above SPKGs from 
> source: 
> configure:   $ sudo yum install arb arb-devel coin-or-Cbc 
> coin-or-Cbc-devel eclib eclib-devel gmp-ecm gmp-ecm-devel 
> fflas-ffpack-devel flint flint-devel libfplll libfplll-devel givaro 
> givaro-devel isl-devel L-function-devel L-function libatomic_ops 
> libatomic_ops-devel libmpc libmpc-devel mpfr-devel 
> configure: After installation, re-run configure using: 
> configure:   $ ./config.status --recheck && ./config.status 
>
>
> > 
> > > 
> > > Best, 
> > > Bryan 
> > > 
> > > On Monday, March 30, 2020 at 5:42:09 PM UTC-6, Matthias Koeppe wrote: 
> > >> 
> > >> 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 for 
> the module "readline".  Any ideas what might be the issue? 
> > >>> 
> > >>> As a little more info, I've successfully built older versions of 
> Sage on this operating system (earlier in the 18.X timeframe) but haven't 
> needed to build from source since 19.X.  I've attached the log file for the 
> python3 build; let me know if any other information would be helpful. 
> > >> 
> > >> 
> > >> The top-level config.log would be helpful. 
> > >> 
> > >> 
> > >> 
> > >> 
> > > 
> > > -- 
> > > 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-...@googlegroups.com . 
> > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/aad88984-0d68-4bfe-828c-a9e58f2db95a%40googlegroups.com.
>  
>
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/823dc4f6-fe73-4f45-8394-1f30f275d0c7%40googlegroups.com.

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

[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: 
> > 
> > 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, March 30, 2020 at 5:42:09 PM UTC-6, Matthias Koeppe wrote: 
> >> 
> >> 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 for the 
> module "readline".  Any ideas what might be the issue? 
> >>> 
> >>> As a little more info, I've successfully built older versions of Sage 
> on this operating system (earlier in the 18.X timeframe) but haven't needed 
> to build from source since 19.X.  I've attached the log file for the 
> python3 build; let me know if any other information would be helpful. 
> >> 
> >> 
> >> The top-level config.log would be helpful. 
> >> 
> >> 
> >> 
> >> 
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/aad88984-0d68-4bfe-828c-a9e58f2db95a%40googlegroups.com.
>  
>
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7c952869-610a-4f4c-82c0-878e980f2966%40googlegroups.com.

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

[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.
>
> Do you have  libreadline-dev installed?

By the way, do you see at the end of the ./confugure run a list of
packages recommended to be installed?
E.g. on Fedora one would see something like

configure: Hint: Installing the following system packages is
recommended and may avoid building some of the above SPKGs from
source:
configure:   $ sudo yum install arb arb-devel coin-or-Cbc
coin-or-Cbc-devel eclib eclib-devel gmp-ecm gmp-ecm-devel
fflas-ffpack-devel flint flint-devel libfplll libfplll-devel givaro
givaro-devel isl-devel L-function-devel L-function libatomic_ops
libatomic_ops-devel libmpc libmpc-devel mpfr-devel
configure: After installation, re-run configure using:
configure:   $ ./config.status --recheck && ./config.status


>
> >
> > Best,
> > Bryan
> >
> > On Monday, March 30, 2020 at 5:42:09 PM UTC-6, Matthias Koeppe wrote:
> >>
> >> 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 for 
> >>> the module "readline".  Any ideas what might be the issue?
> >>>
> >>> As a little more info, I've successfully built older versions of Sage on 
> >>> this operating system (earlier in the 18.X timeframe) but haven't needed 
> >>> to build from source since 19.X.  I've attached the log file for the 
> >>> python3 build; let me know if any other information would be helpful.
> >>
> >>
> >> The top-level config.log would be helpful.
> >>
> >>
> >>
> >>
> >
> > --
> > 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 this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/aad88984-0d68-4bfe-828c-a9e58f2db95a%40googlegroups.com.

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0chwo0NKFFc5s87%3DdMT320xV2R8StVAp53go4E5w6BJw%40mail.gmail.com.

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

[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, March 30, 2020 at 5:42:09 PM UTC-6, Matthias Koeppe wrote:
>>
>> 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 for the module 
>>> "readline".  Any ideas what might be the issue?
>>>
>>> As a little more info, I've successfully built older versions of Sage on 
>>> this operating system (earlier in the 18.X timeframe) but haven't needed to 
>>> build from source since 19.X.  I've attached the log file for the python3 
>>> build; let me know if any other information would be helpful.
>>
>>
>> The top-level config.log would be helpful.
>>
>>
>>
>>
>
> --
> 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 this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/aad88984-0d68-4bfe-828c-a9e58f2db95a%40googlegroups.com.

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0DGjQZ3pLRyTXMtgC%3DZH%2B13-rw-p2vhf%2B1pka%3DLVOxmA%40mail.gmail.com.

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

[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 for the module 
> "readline".  Any ideas what might be the issue?
>
> As a little more info, I've successfully built older versions of Sage on 
> this operating system (earlier in the 18.X timeframe) but haven't needed to 
> build from source since 19.X.  I've attached the log file for the python3 
> build; let me know if any other information would be helpful.
>

The top-level config.log would be helpful.



 

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/83176b69-3bdf-45d0-8158-60b9e0b95b6e%40googlegroups.com.

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

[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 wrote:
>>
>> Hi,
>>
>> I am trying to build Sage from source, but get the following error:
>>
>> "
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: r-3.6.2.p0
>>   last build time: Mar 11 19:11
>>   log file:/home/gsol/sage-9.0/logs/pkgs/r-3.6.2.p0.log
>>   build directory: /home/gsol/sage-9.0/local/var/tmp/sage/build/r-3.6.2.p0
>> "
>>
>> The error in r-3.6.2.p0.log is
>>
>> "
>> make[7]: Entering directory
>> '/home/gsol/sage-9.0/local/var/tmp/sage/build/r-3.6.2.p0/src/src/main'
>> gcc -I../../src/extra  -I. -I../../src/include -I../../src/include
>> -I/home/gsol/Instalations/anaconda3/include  -I../../src/nmath
>> -DHAVE_CONFIG_H   -fopenmp -fpic  -g -O2   -c Rmain.c -o Rmain.o
>> gcc -Wl,--export-dynamic -fopenmp  -L"../../lib"
>> -L/home/gsol/sage-9.0/local/lib -Wl,-rpath,/home/gsol/sage-9.0/local/lib
>> -o R.bin Rmain.o  -lR
>> ../../lib/libR.so: undefined reference to `ucol_strcollIter_58'
>> ../../lib/libR.so: undefined reference to `u_getVersion_58'
>> ../../lib/libR.so: undefined reference to `uloc_setDefault_58'
>> ../../lib/libR.so: undefined reference to `ucol_close_58'
>> ../../lib/libR.so: undefined reference to `ucol_getLocaleByType_58'
>> ../../lib/libR.so: undefined reference to `ucol_setAttribute_58'
>> ../../lib/libR.so: undefined reference to `u_versionToString_58'
>> ../../lib/libR.so: undefined reference to `ucol_open_58'
>> ../../lib/libR.so: undefined reference to `uiter_setUTF8_58'
>> ../../lib/libR.so: undefined reference to `ucol_setStrength_58'
>> collect2: error: ld returned 1 exit status
>> Makefile:145: recipe for target 'R.bin' failed
>> "
>>
>> My setup is:
>>
>> Computer : HP EliteBook 840 G5 (2FA64AV)
>> Os: Pop!_OS 18.04 LTS
>>
>> Is there something that I can do to fix this?
>>
>> Thanks in advance!
>>
> --
> 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 this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/83bbbf32-875d-4d17-b5f7-477ce3e098f0%40googlegroups.com
> 
> .
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CANyEw9onONouyUis2QE7G6mbsMrh_wYTjyLp6LnXhZVMO_DzQg%40mail.gmail.com.

[sage-devel] Re: Error building Sage

[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.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: r-3.6.2.p0
>   last build time: Mar 11 19:11
>   log file:/home/gsol/sage-9.0/logs/pkgs/r-3.6.2.p0.log
>   build directory: /home/gsol/sage-9.0/local/var/tmp/sage/build/r-3.6.2.p0
> "
>
> The error in r-3.6.2.p0.log is
>
> "
> make[7]: Entering directory 
> '/home/gsol/sage-9.0/local/var/tmp/sage/build/r-3.6.2.p0/src/src/main'
> gcc -I../../src/extra  -I. -I../../src/include -I../../src/include 
> -I/home/gsol/Instalations/anaconda3/include  -I../../src/nmath 
> -DHAVE_CONFIG_H   -fopenmp -fpic  -g -O2   -c Rmain.c -o Rmain.o
> gcc -Wl,--export-dynamic -fopenmp  -L"../../lib" 
> -L/home/gsol/sage-9.0/local/lib -Wl,-rpath,/home/gsol/sage-9.0/local/lib  
> -o R.bin Rmain.o  -lR 
> ../../lib/libR.so: undefined reference to `ucol_strcollIter_58'
> ../../lib/libR.so: undefined reference to `u_getVersion_58'
> ../../lib/libR.so: undefined reference to `uloc_setDefault_58'
> ../../lib/libR.so: undefined reference to `ucol_close_58'
> ../../lib/libR.so: undefined reference to `ucol_getLocaleByType_58'
> ../../lib/libR.so: undefined reference to `ucol_setAttribute_58'
> ../../lib/libR.so: undefined reference to `u_versionToString_58'
> ../../lib/libR.so: undefined reference to `ucol_open_58'
> ../../lib/libR.so: undefined reference to `uiter_setUTF8_58'
> ../../lib/libR.so: undefined reference to `ucol_setStrength_58'
> collect2: error: ld returned 1 exit status
> Makefile:145: recipe for target 'R.bin' failed
> "
>
> My setup is:
>
> Computer : HP EliteBook 840 G5 (2FA64AV)
> Os: Pop!_OS 18.04 LTS
>
> Is there something that I can do to fix this?
>
> Thanks in advance!
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/83bbbf32-875d-4d17-b5f7-477ce3e098f0%40googlegroups.com.

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

[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.
>
> Error prompted on the terminal after trying to build sage :
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-build'):
>
> * package: gfortran-9.2.0
>   log file: /home/arnald/sage-9.0/logs/pkgs/gfortran-9.2.0.log
>   build directory: 
> /home/arnald/sage-9.0/local/var/tmp/sage/build/gfortran-9.2.0
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> Makefile:31: recipe for target 'all-build' failed
> make[1]: *** [all-build] Error 1
> make[1]: Leaving directory '/home/arnald/sage-9.0'
> Makefile:16: recipe for target 'build' failed
> make: *** [build] Error 2
>
> I have attached gfortran-9.2.0.log and config.log.
> Thanks in advance.
>

-- 
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 this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4f0ba051-a897-4362-b535-81c15c07fcf0%40googlegroups.com.

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

[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 
>> but in particular it has been on the following screen with no progress for a 
>> while now
>>
>>
>> I know there is still a process running since I cannot use any commands. Is 
>> there anything you recommend? I do not believe it is done, but I'm not sure 
>> what to do.
>
>
> well, you don't really need to build HTML documentation (which you can 
> consult online); just hit Ctrl-C (perhaps a number of times) to kill this 
> process,
> and run
>
> make build
>
> to make sure Sage is built (without docs in HTML)
>
> 
>
> building docs is known to be a bit iffy, in particular on Cygwin. You make 
> try to restart the build as

Not sure why Cygwin is relevant on this thread, but for a note I've
actually had it working pretty well lately.  Roughly 8 times out of 10
the only problem with building the docs on Cygwin has been due to bugs
in openblas that only occurred in the context of forked processes (of
which there are many when building the docs), or more recently due to
a bug in Cygwin 3.0.0 that interacted badly with Python's
multiprocessing module (which is used in the docbuild).  The remaining
10% of the time is due to rebase issues but those are rare anymore on
a clean build.


>> On Thursday, June 13, 2019 at 8:16:27 AM UTC-4, Brandon Gontmacher wrote:
>>>
>>> Hi,
>>>
>>> I'm running Ubuntu 18.04 on a Windows 7 (32-bit) laptop through VirtualBox. 
>>> Every time I try to make Sage I get an error when it tries to install Scipy 
>>> 1.2 (Google drive link to log file at the end of the post). It appears to 
>>> me that the issue is
>>>
>>> failed with error code 1 in /tmp/pip-req-build-OJsJeE/
>>>
>>> I have looked this problem up - it appears to be an easy fix with something 
>>> along the lines of
>>>
>>> pip install --upgrade setuptools
>>>
>>> but this has not been working for me (in addition to having unrelated 
>>> problems with pip itself).
>>>
>>> Any help is appreciated!
>>>
>>>
>>> https://drive.google.com/open?id=1B7p1SKuRXnun1eiYN1gnylGhlvxpzPL0
>>
>> --
>> 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, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/bb072e6b-7b1a-44a0-b558-c14796819308%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0%3D1zz_wSYzpcX7-C4gJcy42Wi4%3DjCbQPomBJo4fKuLHw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAOTD34ZRKfeEUoYnjp2XnXL9mCpWc8LWafa_iJhAS-aN5LzNQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[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
> a while now
>
> [image: Selection_001.png]
>
>
> I know there is still a process running since I cannot use any commands.
> Is there anything you recommend? I do not believe it is done, but I'm not
> sure what to do.
>

well, you don't really need to build HTML documentation (which you can
consult online); just hit Ctrl-C (perhaps a number of times) to kill this
process,
and run

make build

to make sure Sage is built (without docs in HTML)



building docs is known to be a bit iffy, in particular on Cygwin. You make
try to restart the build as

make -j1

perhaps it won't get stuck.




>
> Thanks.
>
> On Thursday, June 13, 2019 at 8:16:27 AM UTC-4, Brandon Gontmacher wrote:
>>
>> Hi,
>>
>> I'm running Ubuntu 18.04 on a Windows 7 (32-bit) laptop through
>> VirtualBox. Every time I try to make Sage I get an error when it tries
>> to install Scipy 1.2 (Google drive link to log file at the end of the
>> post). It appears to me that the issue is
>>
>> failed with error code 1 in /tmp/pip-req-build-OJsJeE/
>>
>> I have looked this problem up - it appears to be an easy fix with
>> something along the lines of
>>
>> pip install --upgrade setuptools
>>
>> but this has not been working for me (in addition to having unrelated
>> problems with pip itself).
>>
>> Any help is appreciated!
>>
>>
>> https://drive.google.com/open?id=1B7p1SKuRXnun1eiYN1gnylGhlvxpzPL0
>>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/bb072e6b-7b1a-44a0-b558-c14796819308%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0%3D1zz_wSYzpcX7-C4gJcy42Wi4%3DjCbQPomBJo4fKuLHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Building Sage

[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 process running since I cannot use any commands. Is 
there anything you recommend? I do not believe it is done, but I'm not sure 
what to do.

Thanks.

On Thursday, June 13, 2019 at 8:16:27 AM UTC-4, Brandon Gontmacher wrote:
>
> Hi,
>
> I'm running Ubuntu 18.04 on a Windows 7 (32-bit) laptop through 
> VirtualBox. Every time I try to make Sage I get an error when it tries to 
> install Scipy 1.2 (Google drive link to log file at the end of the post). 
> It appears to me that the issue is
>
> failed with error code 1 in /tmp/pip-req-build-OJsJeE/
>
> I have looked this problem up - it appears to be an easy fix with 
> something along the lines of 
>
> pip install --upgrade setuptools
>
> but this has not been working for me (in addition to having unrelated 
> problems with pip itself). 
>
> Any help is appreciated!
>
>
> https://drive.google.com/open?id=1B7p1SKuRXnun1eiYN1gnylGhlvxpzPL0
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bb072e6b-7b1a-44a0-b558-c14796819308%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 (released in 2017).
https://en.wikichip.org/wiki/intel/core_i9/i9-7900x
I suppose openblas tries to use all the available features of this
CPU, but it fails due to old assembler.
An upgrade seem to be overdue.




> 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, actually)
>
> mesg from compiler:
> * package: gsl-2.5
>   log file: /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/gsl-2.5.log
>
> The logged message that "C compiler cannot create executables" seems a bit 
> odd -- I create executables with the c compiler all the time.  Does it need 
> root privileges?
>   build directory: 
> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/gsl-2.5
>
>
> The f
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/62b6129f-cc43-4ef4-9e85-02e7395b0216%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq165xL132%2BSxP4ariJBb%2BHw5%3D22j0fjsGQ5UaJMvohY2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[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, 
actually)

mesg from compiler:
* package: gsl-2.5
  log file: /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/gsl-2.5.log

The logged message that "C compiler cannot create executables" seems a bit 
odd -- I create executables with the c compiler all the time.  Does it need 
root privileges?
  build directory: 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/gsl-2.5


The f

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/62b6129f-cc43-4ef4-9e85-02e7395b0216%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for gsl-2.5
Using cached file /home/cecbkup/SW/SAGE/sage-8.7/upstream/gsl-2.5.tar.gz
gsl-2.5

Setting up build directory for gsl-2.5
Finished extraction
Applying patches from ../patches...
Applying ../patches/gsl-2.1-gslcblas.patch
patching file gsl.pc.in

Host system:
Linux sphinx.campbellfamily.biz 3.10.0-957.el7.x86_64 #1 SMP Tue Oct 30 
14:13:26 CDT 2018 x86_64 x86_64 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla 
--enable-bootstrap --enable-shared --enable-threads=posix 
--enable-checking=release --with-system-zlib --enable-__cxa_atexit 
--disable-libunwind-exceptions --enable-gnu-unique-object 
--enable-linker-build-id --with-linker-hash-style=gnu 
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin 
--enable-initfini-array --disable-libgcj 
--with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install
 
--with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install
 --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) 

Package 'gsl' is currently not installed
Uninstalling 'gsl' with legacy uninstaller
Configuring gsl-2.5
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a sed that does not truncate output... /usr/bin/sed
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in 
`/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/gsl-2.5/src':
configure: error: C compiler cannot create executables
See `config.log' for more details

Error configuring gsl-2.5
See the file

/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/gsl-2.5/src/config.log
for details.


real0m0.559s
user0m0.272s
sys 0m0.342s

Error installing package gsl-2.5

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/gsl-2.5.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/gsl-2.5 and type 'make' 
or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/gsl-2.5' && 

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

[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 that mentions
> cross-compiling to a 32-bit architecture.  You're clearly not doing
> that, and you do have the NO_AVX512 macro defined.


it is first trying to build openblas for skylake architecture,
and errors out. This could indicate an old as, a.k.a. gas (GNU assembler),
which usually comes from binutils.
Do you really have a skylake CPU, so it is not a misconfiguration by
openblas?

What is your as version?

Then it tries to build for some dumb architecture, and errors out, perhaps
as this option is not tested much, and so it broken in some way.



>
> I think the race condition issue seems more likely.  I've also had
> problems in the past with OpenBLAS's build system and running in
> parallel.  Try running just `make -j1 openblas` to build openblas by
> itself first.
>
> Failing that, you can try using an existing system BLAS by running
> `./configure --with-blas=atlas` and also setting SAGE_ATLAS_LIB to the
> correct path (typically just SAGE_ATLAS_LIB=/usr/lib).  It's
> unfortunate that both steps are required; something we're working to
> fix.
>
> Despite the spelling "--with-blas=atlas" this doesn't necessarily have
> to use ATLAS BLAS, as it can detect other generic BLAS libs in many
> cases.
>
> On Mon, Jun 3, 2019 at 1:20 AM Charles Campbell  wrote:
> >
> > Hello:
> >
> > Dima: good catch; I have cp aliased to: /bin/cp -i.  I've now unaliased
> it and commented the alias command out of the file that normally sets it
> (the latter step as a "paranoia" step)
> >
> > E.M.Bray: I've never had any success building sage, so no old stuff was
> lying around.  I simply got the tarball for sage 8.7 and extracted the
> contents.
> >
> > I did a make distclean, then make -j10 which resulted in the log file
> I've provided.
> > Next try: make distclean; configure; make -j10 .  Didn't work, either,
> although there are some differences between the two log files.  I've
> attached it, too.
> >
> > Hope you can help!
> > Charles Campbell
> > The latest problem now appears to be with openblas; I've attached the
> associated log.
> >
> >
> > On Thursday, May 30, 2019 at 3:51:57 PM UTC-4, Charles Campbell wrote:
> >
> >> Been trying to build sage 8.7 under Scientific Linux (a redhat
> derivative); actually, I've tried to do so on and off for several years
> with no success ever.  I've installed openblas.x86_64 already.
> >>
> >> From make:
> >>
> >> The following package(s) may have failed to build (not necessarily
> >> during this run of 'make all-start'):
> >>
> >> * package: openblas-0.3.5.p0
> >>   log file:
> /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log
> >>   build directory:
> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.p0
> >>
> >> * package: pari_seadata_small-20090618.p0
> >>   log file:
> /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/pari_seadata_small-20090618.p0.log
> >>   build directory:
> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0
> >>
> >> I have no idea where pari... comes from; yum -y list shows
> >>
> >> opari2.x86_64   1.1.2-3.el7epel
> >> paris-traceroute.x86_64 0.92-6.el7 epel
> >>
> >> Neither of which are "pari", although perhaps "opari..." is close.
> >>
> >> Regards,
> >> Charles Campbell
> >
> > --
> > 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, send email to sage-devel@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-devel.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/b609243e-4f7e-45c9-8665-1757825ebfb0%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAOTD34Ysh1y6-9u%2BXpqKqfBTCnNu7KhUn7AnvBZm93OhrmewWw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 

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

[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 clearly not doing
that, and you do have the NO_AVX512 macro defined.

I think the race condition issue seems more likely.  I've also had
problems in the past with OpenBLAS's build system and running in
parallel.  Try running just `make -j1 openblas` to build openblas by
itself first.

Failing that, you can try using an existing system BLAS by running
`./configure --with-blas=atlas` and also setting SAGE_ATLAS_LIB to the
correct path (typically just SAGE_ATLAS_LIB=/usr/lib).  It's
unfortunate that both steps are required; something we're working to
fix.

Despite the spelling "--with-blas=atlas" this doesn't necessarily have
to use ATLAS BLAS, as it can detect other generic BLAS libs in many
cases.

On Mon, Jun 3, 2019 at 1:20 AM Charles Campbell  wrote:
>
> Hello:
>
> Dima: good catch; I have cp aliased to: /bin/cp -i.  I've now unaliased it 
> and commented the alias command out of the file that normally sets it (the 
> latter step as a "paranoia" step)
>
> E.M.Bray: I've never had any success building sage, so no old stuff was lying 
> around.  I simply got the tarball for sage 8.7 and extracted the contents.
>
> I did a make distclean, then make -j10 which resulted in the log file I've 
> provided.
> Next try: make distclean; configure; make -j10 .  Didn't work, either, 
> although there are some differences between the two log files.  I've attached 
> it, too.
>
> Hope you can help!
> Charles Campbell
> The latest problem now appears to be with openblas; I've attached the 
> associated log.
>
>
> On Thursday, May 30, 2019 at 3:51:57 PM UTC-4, Charles Campbell wrote:
>
>> Been trying to build sage 8.7 under Scientific Linux (a redhat derivative); 
>> actually, I've tried to do so on and off for several years with no success 
>> ever.  I've installed openblas.x86_64 already.
>>
>> From make:
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: openblas-0.3.5.p0
>>   log file: /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log
>>   build directory: 
>> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.p0
>>
>> * package: pari_seadata_small-20090618.p0
>>   log file: 
>> /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/pari_seadata_small-20090618.p0.log
>>   build directory: 
>> /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0
>>
>> I have no idea where pari... comes from; yum -y list shows
>>
>> opari2.x86_64   1.1.2-3.el7epel
>> paris-traceroute.x86_64 0.92-6.el7 epel
>>
>> Neither of which are "pari", although perhaps "opari..." is close.
>>
>> Regards,
>> Charles Campbell
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/b609243e-4f7e-45c9-8665-1757825ebfb0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAOTD34Ysh1y6-9u%2BXpqKqfBTCnNu7KhUn7AnvBZm93OhrmewWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage

[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 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 
>> construction de pip-18.0.
>>
>> Je suis sur un MacBook Pro avec macOS Mojave Version 10.14.3.
>>
>> Merci d'avance de votre attention
>>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage

[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 
> construction de pip-18.0.
>
> Je suis sur un MacBook Pro avec macOS Mojave Version 10.14.3.
>
> Merci d'avance de votre attention
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 wrote:
>
> This is now https://trac.sagemath.org/ticket/26996
>

Great!


- Sverre



-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 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 reason...)
>
> On Tue, Oct 30, 2018 at 4:39 PM Timo Kaufmann  wrote:
> >
> > 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 before, I'm not sure if it stopped working because of a sage
> change or a gfortran update. I vaguely remembered reading something similar
> on the mailing list, so I thought I'd ask you what you think is causing
> this before spending more time debugging.
> >
> > [0] https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
> > [1] https://nixos.org/nixpkgs/manual/#sec-fhs-environments
> >
> > Am Dienstag, 30. Oktober 2018 16:34:47 UTC+1 schrieb 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 build sage-the-distribution when testing because that won't
> build natively on nixos.
> >>
> >> Hmm, do you mean to say you cannot have "native" nixos's gfortran, you
> >> must build Sage's one?
> >>
> >> >
> >> > Am Dienstag, 30. Oktober 2018 16:08:24 UTC+1 schrieb 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 with (Ana)conda...
> >> >>
> >> >> > --
> >> >> > 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+...@googlegroups.com.
> >> >> > To post to this group, send email to sage-...@googlegroups.com.
> >> >> > Visit this group at https://groups.google.com/group/sage-devel.
> >> >> > For more options, visit https://groups.google.com/d/optout.
> >> >
> >> > --
> >> > 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+...@googlegroups.com.
> >> > To post to this group, send email to sage-...@googlegroups.com.
> >> > Visit this group at https://groups.google.com/group/sage-devel.
> >> > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > 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, send email to sage-devel@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/rLQLLSzHlNk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 reason...)

On Tue, Oct 30, 2018 at 4:39 PM Timo Kaufmann  wrote:
>
> 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 
> before, I'm not sure if it stopped working because of a sage change or a 
> gfortran update. I vaguely remembered reading something similar on the 
> mailing list, so I thought I'd ask you what you think is causing this before 
> spending more time debugging.
>
> [0] https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
> [1] https://nixos.org/nixpkgs/manual/#sec-fhs-environments
>
> Am Dienstag, 30. Oktober 2018 16:34:47 UTC+1 schrieb 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 build sage-the-distribution when testing because that won't build 
>> > natively on nixos.
>>
>> Hmm, do you mean to say you cannot have "native" nixos's gfortran, you
>> must build Sage's one?
>>
>> >
>> > Am Dienstag, 30. Oktober 2018 16:08:24 UTC+1 schrieb 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 with (Ana)conda...
>> >>
>> >> > --
>> >> > 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+...@googlegroups.com.
>> >> > To post to this group, send email to sage-...@googlegroups.com.
>> >> > Visit this group at https://groups.google.com/group/sage-devel.
>> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/sage-devel.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 
before, I'm not sure if it stopped working because of a sage change or a 
gfortran update. I vaguely remembered reading something similar on the 
mailing list, so I thought I'd ask you what you think is causing this 
before spending more time debugging.

[0] https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
[1] https://nixos.org/nixpkgs/manual/#sec-fhs-environments

Am Dienstag, 30. Oktober 2018 16:34:47 UTC+1 schrieb 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 build sage-the-distribution when testing because that won't build 
> natively on nixos. 
>
> Hmm, do you mean to say you cannot have "native" nixos's gfortran, you 
> must build Sage's one? 
>
> > 
> > Am Dienstag, 30. Oktober 2018 16:08:24 UTC+1 schrieb 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 with (Ana)conda... 
> >> 
> >> > -- 
> >> > 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+...@googlegroups.com. 
> >> > To post to this group, send email to sage-...@googlegroups.com. 
> >> > Visit this group at https://groups.google.com/group/sage-devel. 
> >> > For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 
> build sage-the-distribution when testing because that won't build natively on 
> nixos.

Hmm, do you mean to say you cannot have "native" nixos's gfortran, you
must build Sage's one?

>
> Am Dienstag, 30. Oktober 2018 16:08:24 UTC+1 schrieb 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 with (Ana)conda...
>>
>> > --
>> > 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+...@googlegroups.com.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/sage-devel.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 
natively on nixos.

Am Dienstag, 30. Oktober 2018 16:08:24 UTC+1 schrieb 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 with (Ana)conda... 
>
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 with (Ana)conda...

> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 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 some 2 year old version of Sage will work
> cleanly, and it's probably better if you start from a clean
> repository.
>
> That said, even if you did a `git pull` to update to the latest
> develop branch I don't know why those files would have incorrect
> permissions.  But try running `chmod -R a-X build/pkgs/*/spkg-*`.
> On Tue, Sep 18, 2018 at 6:30 PM Kathryn Burton 
> wrote:
> >
> > 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
> /Users/knburton12/Downloads/sage-master/upstream/patch-2.7.5.tar.gz
> >>> [patch-2.7.5] patch-2.7.5
> >>> [patch-2.7.5] 
> >>> [patch-2.7.5] Setting up build directory for patch-2.7.5
> >>> [patch-2.7.5] Finished extraction
> >>> [patch-2.7.5] No patch files found in ../patches
> >>> [patch-2.7.5]
> 
> >>> [patch-2.7.5] spkg-install should not be marked executable in the
> build/pkgs directory
> >>> [patch-2.7.5]
> 
> >>> [patch-2.7.5] Please email sage-devel (
> http://groups.google.com/group/sage-devel)
> >>> [patch-2.7.5] explaining the problem and including the log file
> >>> [patch-2.7.5]
>  /Users/knburton12/Downloads/sage-master/logs/pkgs/patch-2.7.5.log
> >>> [patch-2.7.5] Describe your computer, operating system, etc.
> >>> [patch-2.7.5]
> 
> >>> make[1]: ***
> [/Users/knburton12/Downloads/sage-master/local/var/lib/sage/installed/patch-2.7.5]
> Error 1
> >>
> >>
> >>
> >>
> >>
> >> On Monday, September 17, 2018 at 2:50:20 PM UTC-7, Travis Scrimshaw
> wrote:
> >>>
> >>> 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 same
> make error. I have a MacBook Pro running High Sierra version 10.13.3.
> >>
> >> --
> >> 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, send email to sage-devel@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/sage-devel.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > Kathryn Burton
> > knburto...@gmail.com
> >
> > --
> > 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, send email to sage-devel@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Kathryn Burton
knburto...@gmail.com

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 some 2 year old version of Sage will work
cleanly, and it's probably better if you start from a clean
repository.

That said, even if you did a `git pull` to update to the latest
develop branch I don't know why those files would have incorrect
permissions.  But try running `chmod -R a-X build/pkgs/*/spkg-*`.
On Tue, Sep 18, 2018 at 6:30 PM Kathryn Burton  wrote:
>
> 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 
>>> /Users/knburton12/Downloads/sage-master/upstream/patch-2.7.5.tar.gz
>>> [patch-2.7.5] patch-2.7.5
>>> [patch-2.7.5] 
>>> [patch-2.7.5] Setting up build directory for patch-2.7.5
>>> [patch-2.7.5] Finished extraction
>>> [patch-2.7.5] No patch files found in ../patches
>>> [patch-2.7.5] 
>>> 
>>> [patch-2.7.5] spkg-install should not be marked executable in the 
>>> build/pkgs directory
>>> [patch-2.7.5] 
>>> 
>>> [patch-2.7.5] Please email sage-devel 
>>> (http://groups.google.com/group/sage-devel)
>>> [patch-2.7.5] explaining the problem and including the log file
>>> [patch-2.7.5]   
>>> /Users/knburton12/Downloads/sage-master/logs/pkgs/patch-2.7.5.log
>>> [patch-2.7.5] Describe your computer, operating system, etc.
>>> [patch-2.7.5] 
>>> 
>>> make[1]: *** 
>>> [/Users/knburton12/Downloads/sage-master/local/var/lib/sage/installed/patch-2.7.5]
>>>  Error 1
>>
>>
>>
>>
>>
>> On Monday, September 17, 2018 at 2:50:20 PM UTC-7, Travis Scrimshaw wrote:
>>>
>>> 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 same 
 make error. I have a MacBook Pro running High Sierra version 10.13.3.
>>
>> --
>> 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, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Kathryn Burton
> knburto...@gmail.com
>
> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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
>> /Users/knburton12/Downloads/sage-master/upstream/patch-2.7.5.tar.gz
>> [patch-2.7.5] patch-2.7.5
>> [patch-2.7.5] 
>> [patch-2.7.5] Setting up build directory for patch-2.7.5
>> [patch-2.7.5] Finished extraction
>> [patch-2.7.5] No patch files found in ../patches
>> [patch-2.7.5]
>> 
>> [patch-2.7.5] spkg-install should not be marked executable in the
>> build/pkgs directory
>> [patch-2.7.5]
>> 
>> [patch-2.7.5] Please email sage-devel (
>> http://groups.google.com/group/sage-devel)
>> [patch-2.7.5] explaining the problem and including the log file
>> [patch-2.7.5]
>> /Users/knburton12/Downloads/sage-master/logs/pkgs/patch-2.7.5.log
>> [patch-2.7.5] Describe your computer, operating system, etc.
>> [patch-2.7.5]
>> 
>> make[1]: ***
>> [/Users/knburton12/Downloads/sage-master/local/var/lib/sage/installed/patch-2.7.5]
>> Error 1
>>
>
>
>
>
> On Monday, September 17, 2018 at 2:50:20 PM UTC-7, Travis Scrimshaw wrote:
>>
>> 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 same make
>>> error. I have a MacBook Pro running High Sierra version 10.13.3.
>>>
>> --
> 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, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Kathryn Burton
knburto...@gmail.com

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


patch-2.7.5.log
Description: Binary data

[sage-devel] Re: Error building Sage

[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] 
> [patch-2.7.5] Setting up build directory for patch-2.7.5
> [patch-2.7.5] Finished extraction
> [patch-2.7.5] No patch files found in ../patches
> [patch-2.7.5] 
> 
> [patch-2.7.5] spkg-install should not be marked executable in the 
> build/pkgs directory
> [patch-2.7.5] 
> 
> [patch-2.7.5] Please email sage-devel 
> (http://groups.google.com/group/sage-devel)
> [patch-2.7.5] explaining the problem and including the log file
> [patch-2.7.5]   
> /Users/knburton12/Downloads/sage-master/logs/pkgs/patch-2.7.5.log
> [patch-2.7.5] Describe your computer, operating system, etc.
> [patch-2.7.5] 
> 
> make[1]: *** 
> [/Users/knburton12/Downloads/sage-master/local/var/lib/sage/installed/patch-2.7.5]
>  
> Error 1
>


 

On Monday, September 17, 2018 at 2:50:20 PM UTC-7, Travis Scrimshaw wrote:
>
> 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 same make 
>> error. I have a MacBook Pro running High Sierra version 10.13.3.
>>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage

[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 same make 
> error. I have a MacBook Pro running High Sierra version 10.13.3.
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 strange to me, some kind of
> race condition?
> Could you try re-running with just one CPU, that is
>
> MAKE="make -j1" make
>
>
>  
>
>>
>> On Sunday, September 17, 2017 at 1:38:33 PM UTC+5:30, Dima Pasechnik 
>> wrote:
>>>
>>> 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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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


 

>
> On Sunday, September 17, 2017 at 1:38:33 PM UTC+5:30, Dima Pasechnik wrote:
>>
>> 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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 have failed to build (not necessarily
> during this run of 'make all'):
>
> * package: openblas-0.2.19.p0
>   log file: /home/shivam/sage/logs/pkgs/openblas-0.2.19.p0.log
>   build directory: 
> /home/shivam/sage/local/var/tmp/sage/build/openblas-0.2.19.p0
>
> what should be done??
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 Saturday, September 16, 2017 at 12:29:28 PM UTC+5:30, shivam gor wrote:
>
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
>
> * package: openblas-0.2.19.p0
>   log file: /home/shivam/sage/logs/pkgs/openblas-0.2.19.p0.log
>   build directory: 
> /home/shivam/sage/local/var/tmp/sage/build/openblas-0.2.19.p0
>
> what should be done??
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-devel/O7KqK2AQQz4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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
>   description: System memory
>   physical id: 0
>   size: 7880MiB
>  *-cpu
>   product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
>   vendor: Intel Corp.
>   physical id: 1
>   bus info: cpu@0
>   size: 2020MHz
>   capacity: 3100MHz
>   width: 64 bits
>   capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce 
> cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
> ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon 
> pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf tsc_known_freq pni 
> pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm 
> pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx 
> f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi 
> flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid 
> mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida 
> arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
>  *-pci
>   description: Host bridge
>   product: Intel Corporation
>   vendor: Intel Corporation
>   physical id: 100
>   bus info: pci@:00:00.0
>   version: 02
>   width: 32 bits
>   clock: 33MHz
> *-display
>  description: VGA compatible controller
>  product: Intel Corporation
>  vendor: Intel Corporation
>  physical id: 2
>  bus info: pci@:00:02.0
>  version: 02
>  width: 64 bits
>  clock: 33MHz
>  capabilities: vga_controller bus_master cap_list rom
>  configuration: driver=i915 latency=0
>  resources: irq:280 memory:d100-d1ff 
> memory:b000-bfff ioport:f000(size=64) memory:c-d
> *-generic:0
>  description: Signal processing controller
>  product: Skylake Processor Thermal Subsystem
>  vendor: Intel Corporation
>  physical id: 4
>  bus info: pci@:00:04.0
>  version: 02
>  width: 64 bits
>  clock: 33MHz
>  capabilities: cap_list
>  configuration: driver=proc_thermal latency=0
>  resources: irq:16 memory:d222-d2227fff
> *-usb
>  description: USB controller
>  product: Sunrise Point-LP USB 3.0 xHCI Controller
>  vendor: Intel Corporation
>  physical id: 14
>  bus info: pci@:00:14.0
>  version: 21
>  width: 64 bits
>  clock: 33MHz
>  capabilities: xhci bus_master cap_list
>  configuration: driver=xhci_hcd latency=0
>  resources: irq:125 memory:d221-d221
> *-generic:1
>  description: Signal processing controller
>  product: Sunrise Point-LP Thermal subsystem
>  vendor: Intel Corporation
>  physical id: 14.2
>  bus info: pci@:00:14.2
>  version: 21
>  width: 64 bits
>  clock: 33MHz
>  capabilities: cap_list
>  configuration: driver=intel_pch_thermal latency=0
>  resources: irq:18 memory:d2238000-d2238fff
> *-generic:2
>  description: Signal processing controller
>  product: Sunrise Point-LP Serial IO I2C Controller #0
>  vendor: Intel Corporation
>  physical id: 15
>  bus info: pci@:00:15.0
>  version: 21
>  width: 64 bits
>  clock: 33MHz
>  capabilities: bus_master cap_list
>  configuration: driver=intel-lpss latency=0
>  resources: irq:16 memory:d2237000-d2237fff
> *-generic:3
>  description: Signal processing controller
>  product: Sunrise Point-LP Serial IO I2C Controller #1
>  vendor: Intel Corporation
>  physical id: 15.1
>  bus info: pci@:00:15.1
>  version: 21
>  width: 64 bits
>  clock: 33MHz
>  capabilities: bus_master cap_list
>  configuration: driver=intel-lpss latency=0
>  resources: irq:17 memory:d2236000-d2236fff
> *-communication
>  description: Communication controller
>  product: Sunrise Point-LP CSME HECI #1
>  vendor: Intel Corporation
>  physical id: 16
>  bus info: pci@:00:16.0
>  version: 21
> 

[sage-devel] Re: error building sage

[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 @ 2.50GHz
  vendor: Intel Corp.
  physical id: 1
  bus info: cpu@0
  size: 2020MHz
  capacity: 3100MHz
  width: 64 bits
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon 
pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm 
pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx 
f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi 
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid 
mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida 
arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
 *-pci
  description: Host bridge
  product: Intel Corporation
  vendor: Intel Corporation
  physical id: 100
  bus info: pci@:00:00.0
  version: 02
  width: 32 bits
  clock: 33MHz
*-display
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 64 bits
 clock: 33MHz
 capabilities: vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:280 memory:d100-d1ff 
memory:b000-bfff ioport:f000(size=64) memory:c-d
*-generic:0
 description: Signal processing controller
 product: Skylake Processor Thermal Subsystem
 vendor: Intel Corporation
 physical id: 4
 bus info: pci@:00:04.0
 version: 02
 width: 64 bits
 clock: 33MHz
 capabilities: cap_list
 configuration: driver=proc_thermal latency=0
 resources: irq:16 memory:d222-d2227fff
*-usb
 description: USB controller
 product: Sunrise Point-LP USB 3.0 xHCI Controller
 vendor: Intel Corporation
 physical id: 14
 bus info: pci@:00:14.0
 version: 21
 width: 64 bits
 clock: 33MHz
 capabilities: xhci bus_master cap_list
 configuration: driver=xhci_hcd latency=0
 resources: irq:125 memory:d221-d221
*-generic:1
 description: Signal processing controller
 product: Sunrise Point-LP Thermal subsystem
 vendor: Intel Corporation
 physical id: 14.2
 bus info: pci@:00:14.2
 version: 21
 width: 64 bits
 clock: 33MHz
 capabilities: cap_list
 configuration: driver=intel_pch_thermal latency=0
 resources: irq:18 memory:d2238000-d2238fff
*-generic:2
 description: Signal processing controller
 product: Sunrise Point-LP Serial IO I2C Controller #0
 vendor: Intel Corporation
 physical id: 15
 bus info: pci@:00:15.0
 version: 21
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=intel-lpss latency=0
 resources: irq:16 memory:d2237000-d2237fff
*-generic:3
 description: Signal processing controller
 product: Sunrise Point-LP Serial IO I2C Controller #1
 vendor: Intel Corporation
 physical id: 15.1
 bus info: pci@:00:15.1
 version: 21
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=intel-lpss latency=0
 resources: irq:17 memory:d2236000-d2236fff
*-communication
 description: Communication controller
 product: Sunrise Point-LP CSME HECI #1
 vendor: Intel Corporation
 physical id: 16
 bus info: pci@:00:16.0
 version: 21
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=mei_me latency=0
 resources: irq:282 memory:d2235000-d2235fff
*-storage
 description: SATA controller
 product: Sunrise Point-LP SATA Controller [AHCI mode]
 vendor: Intel 

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

[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 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 
> had a 32-bit system (Atom refers to X86_64 cpus). And while I don't even 
> know what MIPS or SPARC arch is, someone is probably building OpenBLAS on 
> it. There's just too many possible hardware configurations for OpenBLAS to 
> make assumptions about what you are running!
>
> On Friday, July 21, 2017 at 10:28:00 AM UTC-7, John H Palmieri wrote:
>>
>> 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 wrote:
>>>
>>> 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 7.6 on my laptop, and there was an error making 
 openblas that directed me to the log files for that package. The log file 
 said that detecting CPU failed, and to set TARGET explicitly. It also 
 suggested I email this google group to explain the problem, with the 
 relevant part of the log files. So I've attached it below. 

 OS: Ubuntu Mate 16.04 LTS
 Sage Version: 7.6
 HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
 cpu cores

 Before the build, I made sure that I had all the listed dependencies 
 and suggested packages already installed. Then I cloned the Git repo, set 
 MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more 
 before 
 it stopped and reported the error. I asked about this issue on 
 sage-support 
 earlier (
 https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ).

 Someone had the same issue on very similar hardware (another 11e) here: 
 https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ 
 The log files look almost exactly the same. They reported that setting 
 OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
 going to try setting this and building Sage again later today. I was a 
 little confused since a Celeron is not an Atom afaik, I'm guessing this is 
 a catch-all setting for lower-end processors?

 Any advice will be greatly appreciated!

>>>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 
had a 32-bit system (Atom refers to X86_64 cpus). And while I don't even 
know what MIPS or SPARC arch is, someone is probably building OpenBLAS on 
it. There's just too many possible hardware configurations for OpenBLAS to 
make assumptions about what you are running!

On Friday, July 21, 2017 at 10:28:00 AM UTC-7, John H Palmieri wrote:
>
> 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 wrote:
>>
>> 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 7.6 on my laptop, and there was an error making 
>>> openblas that directed me to the log files for that package. The log file 
>>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>>> suggested I email this google group to explain the problem, with the 
>>> relevant part of the log files. So I've attached it below. 
>>>
>>> OS: Ubuntu Mate 16.04 LTS
>>> Sage Version: 7.6
>>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>>> cpu cores
>>>
>>> Before the build, I made sure that I had all the listed dependencies and 
>>> suggested packages already installed. Then I cloned the Git repo, set 
>>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>>> it stopped and reported the error. I asked about this issue on sage-support 
>>> earlier (
>>> https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ).
>>>
>>> Someone had the same issue on very similar hardware (another 11e) here: 
>>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>>> log files look almost exactly the same. They reported that setting 
>>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>>> going to try setting this and building Sage again later today. I was a 
>>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>>> a catch-all setting for lower-end processors?
>>>
>>> Any advice will be greatly appreciated!
>>>
>>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 
choice for all. People on this help topic suggested using TARGET=HASWELL 
for Kaby Lake: https://github.com/xianyi/OpenBLAS/issues/1006

I believe there are some specific optimizations applied to each setting 
that help it run faster on particular CPUs. If OpenBLAS fails to detect 
your cpu, its probably better that make simply stops the process and asks 
for the user to apply the right setting instead of just falling on a 
default that may or may not be appropriate for your situation. Fixing it 
just requires setting a single env variable before the build, after all. 

On Friday, July 21, 2017 at 10:28:00 AM UTC-7, John H Palmieri wrote:
>
> 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 wrote:
>>
>> 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 7.6 on my laptop, and there was an error making 
>>> openblas that directed me to the log files for that package. The log file 
>>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>>> suggested I email this google group to explain the problem, with the 
>>> relevant part of the log files. So I've attached it below. 
>>>
>>> OS: Ubuntu Mate 16.04 LTS
>>> Sage Version: 7.6
>>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>>> cpu cores
>>>
>>> Before the build, I made sure that I had all the listed dependencies and 
>>> suggested packages already installed. Then I cloned the Git repo, set 
>>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>>> it stopped and reported the error. I asked about this issue on sage-support 
>>> earlier (
>>> https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ).
>>>
>>> Someone had the same issue on very similar hardware (another 11e) here: 
>>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>>> log files look almost exactly the same. They reported that setting 
>>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>>> going to try setting this and building Sage again later today. I was a 
>>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>>> a catch-all setting for lower-end processors?
>>>
>>> Any advice will be greatly appreciated!
>>>
>>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 wrote:
>
> 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 7.6 on my laptop, and there was an error making 
>> openblas that directed me to the log files for that package. The log file 
>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>> suggested I email this google group to explain the problem, with the 
>> relevant part of the log files. So I've attached it below. 
>>
>> OS: Ubuntu Mate 16.04 LTS
>> Sage Version: 7.6
>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>> cpu cores
>>
>> Before the build, I made sure that I had all the listed dependencies and 
>> suggested packages already installed. Then I cloned the Git repo, set 
>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>> it stopped and reported the error. I asked about this issue on sage-support 
>> earlier (https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ
>> ).
>>
>> Someone had the same issue on very similar hardware (another 11e) here: 
>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>> log files look almost exactly the same. They reported that setting 
>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>> going to try setting this and building Sage again later today. I was a 
>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>> a catch-all setting for lower-end processors?
>>
>> Any advice will be greatly appreciated!
>>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 this hardware later, 
but I'm not really sure what to do to test it once it does build. This was 
my first time building a big program from source, so I'm still getting used 
to it all. It would be interesting to see if this detection issue with 
lower-end x86-64 cpus continues in the dev version. 

On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik wrote:
>
> 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 7.6 on my laptop, and there was an error making 
>> openblas that directed me to the log files for that package. The log file 
>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>> suggested I email this google group to explain the problem, with the 
>> relevant part of the log files. So I've attached it below. 
>>
>> OS: Ubuntu Mate 16.04 LTS
>> Sage Version: 7.6
>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>> cpu cores
>>
>> Before the build, I made sure that I had all the listed dependencies and 
>> suggested packages already installed. Then I cloned the Git repo, set 
>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>> it stopped and reported the error. I asked about this issue on sage-support 
>> earlier (https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ
>> ).
>>
>> Someone had the same issue on very similar hardware (another 11e) here: 
>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>> log files look almost exactly the same. They reported that setting 
>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>> going to try setting this and building Sage again later today. I was a 
>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>> a catch-all setting for lower-end processors?
>>
>> Any advice will be greatly appreciated!
>>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 7.6 on my laptop, and there was an error making openblas 
> that directed me to the log files for that package. The log file said that 
> detecting CPU failed, and to set TARGET explicitly. It also suggested I 
> email this google group to explain the problem, with the relevant part of 
> the log files. So I've attached it below. 
>
> OS: Ubuntu Mate 16.04 LTS
> Sage Version: 7.6
> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
> cpu cores
>
> Before the build, I made sure that I had all the listed dependencies and 
> suggested packages already installed. Then I cloned the Git repo, set 
> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
> it stopped and reported the error. I asked about this issue on sage-support 
> earlier (https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ
> ).
>
> Someone had the same issue on very similar hardware (another 11e) here: 
> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
> log files look almost exactly the same. They reported that setting 
> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
> going to try setting this and building Sage again later today. I was a 
> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
> a catch-all setting for lower-end processors?
>
> Any advice will be greatly appreciated!
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 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,
>>
>> I'm attempting to build sage on Fedora 24 as a first step toward 
>> contributing to the project. The build fails at gcc however, and I'm 
>> uncertain about how to proceed. I attached the relevant log.
>> Any advice appreciated!
>>
>> Lennart
>>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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,
>
> I'm attempting to build sage on Fedora 24 as a first step toward 
> contributing to the project. The build fails at gcc however, and I'm 
> uncertain about how to proceed. I attached the relevant log.
> Any advice appreciated!
>
> Lennart
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 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: 
>> >> 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 picks 
>> > up.)  sizeof(long) should be set to 8 now though. 
>> > 
>> > So where does the build fail now? 
>> > 
>> > Could you move your libomalloc.so out of the way such that Singular 
>> > won't find and try to use that?  (It's supposed to build its own.) 
>>
>> /In principle/ it should be sufficient to explicitly configure Singular 
>> with '--enable-omalloc' (in build/pkgs/singular/spkg-install), but 
>> AFAICS it still insists on (at least temporarily) picking up an existing 
>> library, in your case in addition an apparently broken one. 
>>
>> If you still have trouble building Singular (and if that's related to 
>> the above), you can put another dumb patch (attached) into 
>> build/pkgs/singular/patches/, then either running 'make' or doing 
>> './sage -i -s singular', later continuing with 'make'. 
>>
>>
>> By the way, Sage 7.4.beta3 has just been released, still with the old 
>> Singular though. 
>>
>>
>> -leif 
>>
>>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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: 
> >> 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 picks 
> > up.)  sizeof(long) should be set to 8 now though. 
> > 
> > So where does the build fail now? 
> > 
> > Could you move your libomalloc.so out of the way such that Singular 
> > won't find and try to use that?  (It's supposed to build its own.) 
>
> /In principle/ it should be sufficient to explicitly configure Singular 
> with '--enable-omalloc' (in build/pkgs/singular/spkg-install), but 
> AFAICS it still insists on (at least temporarily) picking up an existing 
> library, in your case in addition an apparently broken one. 
>
> If you still have trouble building Singular (and if that's related to 
> the above), you can put another dumb patch (attached) into 
> build/pkgs/singular/patches/, then either running 'make' or doing 
> './sage -i -s singular', later continuing with 'make'. 
>
>
> By the way, Sage 7.4.beta3 has just been released, still with the old 
> Singular though. 
>
>
> -leif 
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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:
 
undefined reference to `fmpz_get_mpz'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`convertFmpq_poly_t2FacCF(fmpq_poly_struct*, Variable const&)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:223:
 
undefined reference to `fmpq_poly_get_coeff_fmpq'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`_fmpz_demote':
[singular-3.1.7p1.p2] /home/simon/sage/local/include/flint/fmpz.h:99: 
undefined reference to `_fmpz_clear_mpz'
[singular-3.1.7p1.p2] /home/simon/sage/local/include/flint/fmpz.h:99: 
undefined reference to `_fmpz_clear_mpz'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`convertFacCF2Fmpq_poly_t(fmpq_poly_struct*, CanonicalForm const&)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:247:
 
undefined reference to `fmpq_poly_init2'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:248:
 
undefined reference to `_fmpq_poly_set_length'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`convertFacCF2Fmpz_mod_poly_t(fmpz_mod_poly_struct*, CanonicalForm const&, 
long const*)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:284:
 
undefined reference to `fmpz_mod_poly_init2'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:287:
 
undefined reference to `fmpz_mod_poly_set_fmpz_poly'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:288:
 
undefined reference to `fmpz_poly_clear'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`convertFmpz_mod_poly_t2FacCF(fmpz_mod_poly_struct*, Variable const&, modpk 
const&)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:296:
 
undefined reference to `fmpz_poly_init'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:297:
 
undefined reference to `fmpz_mod_poly_get_fmpz_poly'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:299:
 
undefined reference to `fmpz_poly_clear'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`convertFacCFMatrix2Fmpz_mat_t(fmpz_mat_struct*, Matrix&)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:305:
 
undefined reference to `fmpz_mat_init'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(FLINTconvert.o): In function 
`convertFacCFMatrix2nmod_mat_t(nmod_mat_struct*, Matrix&)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:332:
 
undefined reference to `nmod_mat_init'
[singular-3.1.7p1.p2] /home/simon/sage/local/lib/libsingcf.a(algext.o): In 
function `myicontent(CanonicalForm const&, CanonicalForm const&)':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/algext.cc:689:
 
undefined reference to `fmpz_poly_gcd'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/algext.cc:695:
 
undefined reference to `fmpz_poly_clear'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/algext.cc:696:
 
undefined reference to `fmpz_poly_clear'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(cfModResultant.o): In function 
`nmod_poly_resultant':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/include/flint/nmod_poly.h:1121: undefined reference 
to `nmod_poly_resultant_hgcd'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(cfModResultant.o): In function 
`uniResultant':
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/cfModResultant.cc:256:
 
undefined reference to `nmod_poly_clear'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/cfModResultant.cc:257:
 
undefined reference to `nmod_poly_clear'
[singular-3.1.7p1.p2] 
/home/simon/sage/local/lib/libsingcf.a(cfModResultant.o): In function 
`nmod_poly_resultant':
[singular-3.1.7p1.p2] 

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

[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 system-wide which it picks
> up.)  sizeof(long) should be set to 8 now though.
> 
> So where does the build fail now?
> 
> Could you move your libomalloc.so out of the way such that Singular
> won't find and try to use that?  (It's supposed to build its own.)

/In principle/ it should be sufficient to explicitly configure Singular
with '--enable-omalloc' (in build/pkgs/singular/spkg-install), but
AFAICS it still insists on (at least temporarily) picking up an existing
library, in your case in addition an apparently broken one.

If you still have trouble building Singular (and if that's related to
the above), you can put another dumb patch (attached) into
build/pkgs/singular/patches/, then either running 'make' or doing
'./sage -i -s singular', later continuing with 'make'.


By the way, Sage 7.4.beta3 has just been released, still with the old
Singular though.


-leif

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--- a/latest/configure
+++ b/latest/configure
@@ -1981,7 +1981,7 @@ int main() {
 omTestAddr()
 ; return 0; }
 EOF
-if { (eval echo configure:1985: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
+if { (eval echo configure:1985: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && false; then
   rm -rf conftest*
   eval "ac_cv_lib_$ac_lib_var=yes"
 else

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

[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 picks
up.)  sizeof(long) should be set to 8 now though.

So where does the build fail now?

Could you move your libomalloc.so out of the way such that Singular
won't find and try to use that?  (It's supposed to build its own.)


-leif

> 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 - 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
> 
> >
> > Ok, that doesn't tell much, but at least a bit...
> >
> > Compilation seems to work, but running the conftest supposed to print
> > sizeof(long) presumably fails, I guess due to a runtime linker error.
> > (You seem to have libomalloc installed system-wide; unfortunately
> stderr
> > is redirected to /dev/null.)
> >
> > Looking closer at Singular's top-level 'configure', it's quite
> > surprising that test (and others) didn't fail before, AFAIK.
> >
> >
> >>> A workaround would be great. Then I can get started.
> >>
> >> I can't tell before I've seen the log above, but I guess it won't be
> >> hard to at least get you past /that/ error... ;-)
> >
> > I made a patch that may enlighten us regarding the error, and should
> > bring you past the error with sizeof(long)!=sizeof(void*) at least.
> >
> > Copy the attached patch into build/pkgs/singular/patches/, then do
> >
> > ../sage -i -s singular
> 
> P.S.:  If you want to go triple-safe, delete the old build directory
> (or
> at least config.cache there) before running './sage -i ...':
> 
> rm -rf /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2
> 
> 
> -leif
> 
> 
> > Even if that succeeded, please first again make a copy of the newly
> > generated config.log from the temporary Singular build directory as
> > before (and post it) before proceeding.
> >
> > In case installing the Singular package now worked, you can continue
> > building Sage by simply typing 'make' again (or 'make -jN` with N
> being
> > the number of threads/jobs, but you'll presumably know).
> >
> >
> > Good luck!
> >
> >
> > -leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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
>> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
> 
> Ok, that doesn't tell much, but at least a bit...
> 
> Compilation seems to work, but running the conftest supposed to print
> sizeof(long) presumably fails, I guess due to a runtime linker error.
> (You seem to have libomalloc installed system-wide; unfortunately stderr
> is redirected to /dev/null.)

Yep.  From the new config.log:

configure:2313: checking size of long
configure:2332: gcc -o conftest -O2 -g  -fPIC
-I/home/simon/sage/local/include -I/home/simon/sage/local/include
-L/home/simon/sage/local/lib -L/home/simon/sage/local/lib
-Wl,-rpath,/home/simon/sage/local/lib  conftest.c -lomalloc -lgmp -lnsl
-lm  1>&5
configure:2323:1: warning: return type defaults to 'int' [-Wimplicit-int]
 main()
 ^~~~
configure: In function 'main':
configure:2326:11: warning: implicit declaration of function 'exit'
[-Wimplicit-function-declaration]
   if (!f) exit(1);
   ^~~~
configure:2326:11: warning: incompatible implicit declaration of
built-in function 'exit'
configure:2326:11: note: include '' or provide a declaration
of 'exit'
configure:2328:3: warning: incompatible implicit declaration of built-in
function 'exit'
   exit(0);
   ^~~~
configure:2328:3: note: include '' or provide a declaration of
'exit'
./conftest: error while loading shared libraries: libomalloc-0.9.6.so:
cannot open shared object file: No such file or directory


-leif

> Looking closer at Singular's top-level 'configure', it's quite
> surprising that test (and others) didn't fail before, AFAIK.
> 
> 
>>> A workaround would be great. Then I can get started.
>>
>> I can't tell before I've seen the log above, but I guess it won't be
>> hard to at least get you past /that/ error... ;-)
> 
> I made a patch that may enlighten us regarding the error, and should
> bring you past the error with sizeof(long)!=sizeof(void*) at least.
> 
> Copy the attached patch into build/pkgs/singular/patches/, then do
> 
> ../sage -i -s singular
> 
> Even if that succeeded, please first again make a copy of the newly
> generated config.log from the temporary Singular build directory as
> before (and post it) before proceeding.
> 
> In case installing the Singular package now worked, you can continue
> building Sage by simply typing 'make' again (or 'make -jN` with N being
> the number of threads/jobs, but you'll presumably know).
> 
> 
> Good luck!
> 
> 
> -leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 - 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
>  
>
> > 
> > Ok, that doesn't tell much, but at least a bit... 
> > 
> > Compilation seems to work, but running the conftest supposed to print 
> > sizeof(long) presumably fails, I guess due to a runtime linker error. 
> > (You seem to have libomalloc installed system-wide; unfortunately stderr 
> > is redirected to /dev/null.) 
> > 
> > Looking closer at Singular's top-level 'configure', it's quite 
> > surprising that test (and others) didn't fail before, AFAIK. 
> > 
> > 
> >>> A workaround would be great. Then I can get started. 
> >> 
> >> I can't tell before I've seen the log above, but I guess it won't be 
> >> hard to at least get you past /that/ error... ;-) 
> > 
> > I made a patch that may enlighten us regarding the error, and should 
> > bring you past the error with sizeof(long)!=sizeof(void*) at least. 
> > 
> > Copy the attached patch into build/pkgs/singular/patches/, then do 
> > 
> > ../sage -i -s singular 
>
> P.S.:  If you want to go triple-safe, delete the old build directory (or 
> at least config.cache there) before running './sage -i ...': 
>
> rm -rf /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2 
>
>
> -leif 
>
>
> > Even if that succeeded, please first again make a copy of the newly 
> > generated config.log from the temporary Singular build directory as 
> > before (and post it) before proceeding. 
> > 
> > In case installing the Singular package now worked, you can continue 
> > building Sage by simply typing 'make' again (or 'make -jN` with N being 
> > the number of threads/jobs, but you'll presumably know). 
> > 
> > 
> > Good luck! 
> > 
> > 
> > -leif 
> > 
>
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:649: checking uname for singular
configure:685: checking for gcc
configure:798: checking whether the C compiler (gcc -O2 -g  -fPIC 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) works
configure:814: gcc -o conftest -O2 -g  -fPIC -I/home/simon/sage/local/include  
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  conftest.c  
1>&5
configure:811:1: warning: return type defaults to 'int' [-Wimplicit-int]
 main(){return(0);}
 ^~~~
configure:840: checking whether the C compiler (gcc -O2 -g  -fPIC 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) is a 
cross-compiler
configure:845: checking whether we are using GNU C
configure:854: gcc -E conftest.c
configure:873: checking whether gcc accepts -g
configure:905: checking how to run the C preprocessor
configure:926: gcc -E -I/home/simon/sage/local/include  conftest.c >/dev/null 
2>conftest.out
configure:1015: checking for a BSD compatible install
configure:1068: checking for AIX
configure:1096: checking for c++
configure:1128: checking whether the C++ compiler (g++ 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  -O2 -g  
-fPIC -fno-delete-null-pointer-checks -fno-strict-overflow 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) works
configure:1144: g++ -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  -o conftest -O2 -g  -fPIC 
-fno-delete-null-pointer-checks -fno-strict-overflow 
-I/home/simon/sage/local/include  -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  conftest.C  1>&5
configure:1170: checking whether the C++ compiler (g++ 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  -O2 -g  
-fPIC -fno-delete-null-pointer-checks -fno-strict-overflow 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) is a 
cross-compiler
configure:1175: checking whether we are using GNU C++
configure:1184: g++ -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  -E conftest.C
configure:1203: checking whether g++ -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  accepts -g
configure:1240: checking whether compiler accepts -pipe
configure:1254: gcc -c -O2 -g  -fPIC -pipe -I/home/simon/sage/local/include  
conftest.c 1>&5
configure:1281: checking for perl5

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

[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
>> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
> 
> Ok, that doesn't tell much, but at least a bit...
> 
> Compilation seems to work, but running the conftest supposed to print
> sizeof(long) presumably fails, I guess due to a runtime linker error.
> (You seem to have libomalloc installed system-wide; unfortunately stderr
> is redirected to /dev/null.)
> 
> Looking closer at Singular's top-level 'configure', it's quite
> surprising that test (and others) didn't fail before, AFAIK.
> 
> 
>>> A workaround would be great. Then I can get started.
>>
>> I can't tell before I've seen the log above, but I guess it won't be
>> hard to at least get you past /that/ error... ;-)
> 
> I made a patch that may enlighten us regarding the error, and should
> bring you past the error with sizeof(long)!=sizeof(void*) at least.
> 
> Copy the attached patch into build/pkgs/singular/patches/, then do
> 
> ../sage -i -s singular

P.S.:  If you want to go triple-safe, delete the old build directory (or
at least config.cache there) before running './sage -i ...':

rm -rf /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2


-leif


> Even if that succeeded, please first again make a copy of the newly
> generated config.log from the temporary Singular build directory as
> before (and post it) before proceeding.
> 
> In case installing the Singular package now worked, you can continue
> building Sage by simply typing 'make' again (or 'make -jN` with N being
> the number of threads/jobs, but you'll presumably know).
> 
> 
> Good luck!
> 
> 
> -leif
> 


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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

Ok, that doesn't tell much, but at least a bit...

Compilation seems to work, but running the conftest supposed to print
sizeof(long) presumably fails, I guess due to a runtime linker error.
(You seem to have libomalloc installed system-wide; unfortunately stderr
is redirected to /dev/null.)

Looking closer at Singular's top-level 'configure', it's quite
surprising that test (and others) didn't fail before, AFAIK.


>> A workaround would be great. Then I can get started.
> 
> I can't tell before I've seen the log above, but I guess it won't be
> hard to at least get you past /that/ error... ;-)

I made a patch that may enlighten us regarding the error, and should
bring you past the error with sizeof(long)!=sizeof(void*) at least.

Copy the attached patch into build/pkgs/singular/patches/, then do

./sage -i -s singular

Even if that succeeded, please first again make a copy of the newly
generated config.log from the temporary Singular build directory as
before (and post it) before proceeding.

In case installing the Singular package now worked, you can continue
building Sage by simply typing 'make' again (or 'make -jN` with N being
the number of threads/jobs, but you'll presumably know).


Good luck!


-leif

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--- a/latest/configure
+++ b/latest/configure
@@ -2328,14 +2328,14 @@ main()
   exit(0);
 }
 EOF
-if { (eval echo configure:2332: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
+if { (eval echo configure:2332: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>&5
 then
   ac_cv_sizeof_long=`cat conftestval`
 else
   echo "configure: failed program was:" >&5
   cat conftest.$ac_ext >&5
   rm -fr conftest*
-  ac_cv_sizeof_long=0
+  ac_cv_sizeof_long=8 # crude hack just to get you past the later error
 fi
 rm -fr conftest*
 fi

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

[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

Oooops, there hadn't been attachments when I replied -- I could swear!

Right now noticed them, will take a look...


-leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 be great. Then I can get started.

I can't tell before I've seen the log above, but I guess it won't be
hard to at least get you past /that/ error... ;-)


> Tried to build sage devel at work and got a different error. Should I
> open a thread for that as well?

In case it's a quite different error (or the system is different anyway,
w.r.t. the distribution / compilers), yes.


-leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 on my laptop, I am happy enough)

On Thursday, September 1, 2016 at 12:28:23 PM UTC+2, leif wrote:
>
> 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 just *starting* developing Sage. 
>
> Of course we want to get rid of Singular 3.x asap, but I'm not saying we 
> should further fix it, and he's currently stuck in an early stage. 
>
> It will IMHO be worth to at least *know* why it failed for him, since 
> I've never seen that test failing, and similar may happen elsewhere, 
> too.  There's possibly some simple fix or work-around such that at least 
> he personally can continue building his first development version... 
>
>
> FWIW, Volker on Fedora had less issues with its GCC 6.1.1 and Singular 
> than I had with vanilla GCC 6.1, but we fixed them before 7.3 was 
> released. 
>
>
> -leif 
>
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


config.cache
Description: Binary data
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:649: checking uname for singular
configure:685: checking for gcc
configure:798: checking whether the C compiler (gcc -O2 -g  -fPIC 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) works
configure:814: gcc -o conftest -O2 -g  -fPIC -I/home/simon/sage/local/include  
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  conftest.c  
1>&5
configure:811:1: warning: return type defaults to 'int' [-Wimplicit-int]
 main(){return(0);}
 ^~~~
configure:840: checking whether the C compiler (gcc -O2 -g  -fPIC 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) is a 
cross-compiler
configure:845: checking whether we are using GNU C
configure:854: gcc -E conftest.c
configure:873: checking whether gcc accepts -g
configure:905: checking how to run the C preprocessor
configure:926: gcc -E -I/home/simon/sage/local/include  conftest.c >/dev/null 
2>conftest.out
configure:1015: checking for a BSD compatible install
configure:1068: checking for AIX
configure:1096: checking for c++
configure:1128: checking whether the C++ compiler (g++ 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  -O2 -g  
-fPIC -fno-delete-null-pointer-checks -fno-strict-overflow 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) works
configure:1144: g++ -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  -o conftest -O2 -g  -fPIC 
-fno-delete-null-pointer-checks -fno-strict-overflow 
-I/home/simon/sage/local/include  -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  conftest.C  1>&5
configure:1170: checking whether the C++ compiler (g++ 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  -O2 -g  
-fPIC -fno-delete-null-pointer-checks -fno-strict-overflow 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib ) is a 
cross-compiler
configure:1175: checking whether we are using GNU C++
configure:1184: g++ -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  -E conftest.C
configure:1203: checking whether g++ -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib  accepts -g
configure:1240: checking whether compiler accepts -pipe
configure:1254: gcc -c -O2 -g  -fPIC -pipe -I/home/simon/sage/local/include  
conftest.c 1>&5
configure:1281: checking for perl5
configure:1281: checking for perl
configure:1315: checking for uudecode
configure:1315: checking for uudeview
configure:1350: checking for gunzip
configure:1386: checking for gzip
configure:1419: checking for latex2html
configure:1446: checking whether ln -s works
configure:1516: checking whether _AIX is defined
configure:1547: checking for atof in -lm
configure:1566: gcc -o conftest -O2 -g  -fPIC -I/home/simon/sage/local/include 
-I/home/simon/sage/local/include  -L/home/simon/sage/local/lib 
-L/home/simon/sage/local/lib -Wl,-rpath,/home/simon/sage/local/lib  conftest.c 
-lm   1>&5
configure:1594: checking for socket in -lbsd
configure:1613: gcc -o conftest -O2 -g  -fPIC 

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

[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 just *starting* developing Sage.

Of course we want to get rid of Singular 3.x asap, but I'm not saying we
should further fix it, and he's currently stuck in an early stage.

It will IMHO be worth to at least *know* why it failed for him, since
I've never seen that test failing, and similar may happen elsewhere,
too.  There's possibly some simple fix or work-around such that at least
he personally can continue building his first development version...


FWIW, Volker on Fedora had less issues with its GCC 6.1.1 and Singular
than I had with vanilla GCC 6.1, but we fixed them before 7.3 was released.


-leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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: 
>
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
>  
>
>
> and since omalloc takes an allegedly cached value for sizeof(long) from 
> Singular's top-level 'configure', where the value indeed appears to be 
> already wrong, probably also: 
>
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.cache
>  
>
>

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

 

>
>
> -leif 
>
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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
> 
> and since omalloc takes an allegedly cached value for sizeof(long) from
> Singular's top-level 'configure', where the value indeed appears to be
> already wrong, probably also:
> 
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.cache

Hmmm, I'd say there's a slight bug in Singular's top-level 'configure',
as it doesn't really check for sizeof(long), but only cares whether it
is 4 or not.

If the test altogether fails, it doesn't bail out, but instead really
sets the value (which is used later on) to 0.


Simon, to figure out *why* the conftest failed, we still need the first
file I mentioned above.


-leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 allegedly cached value for sizeof(long) from
Singular's top-level 'configure', where the value indeed appears to be
already wrong, probably also:

/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.cache


-leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 (gcc -O2 -g  -fPIC 
-L/home/simon/sage/local/lib -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib ) works... yes
[singular-3.1.7p1.p2] checking whether the C compiler (gcc -O2 -g  -fPIC 
-L/home/simon/sage/local/lib -L/home/simon/sage/local/lib 
-Wl,-rpath,/home/simon/sage/local/lib ) is a cross-compiler... no
[singular-3.1.7p1.p2] checking whether we are using GNU C... (cached) yes
[singular-3.1.7p1.p2] checking whether gcc accepts -g... (cached) yes
[singular-3.1.7p1.p2] checking how to run the C preprocessor... (cached) 
gcc -E
[singular-3.1.7p1.p2] checking for ranlib... ranlib
[singular-3.1.7p1.p2] checking whether ln -s works... (cached) yes
[singular-3.1.7p1.p2] checking for a BSD compatible install... (cached) 
/usr/bin/install -c
[singular-3.1.7p1.p2] checking for working const... yes
[singular-3.1.7p1.p2] checking for inline... inline
[singular-3.1.7p1.p2] checking for ar... ar
[singular-3.1.7p1.p2] checking for perl... (cached) perl
[singular-3.1.7p1.p2] checking for addr2line... addr2line
[singular-3.1.7p1.p2] checking for ANSI C header files... yes
[singular-3.1.7p1.p2] checking for limits.h... yes
[singular-3.1.7p1.p2] checking for unistd.h... yes
[singular-3.1.7p1.p2] checking for sys/mman.h... yes
[singular-3.1.7p1.p2] checking for fcntl.h... yes
[singular-3.1.7p1.p2] checking for /usr/include/malloc.h... yes
[singular-3.1.7p1.p2] checking for popen... yes
[singular-3.1.7p1.p2] checking for readlink... yes
[singular-3.1.7p1.p2] checking for getcwd... yes
[singular-3.1.7p1.p2] checking for getwd... yes
[singular-3.1.7p1.p2] checking for mmap... yes
[singular-3.1.7p1.p2] checking for sbrk... yes
[singular-3.1.7p1.p2] checking for random... yes
[singular-3.1.7p1.p2] checking size of long... (cached) 0
[singular-3.1.7p1.p2] checking size of void*... 8
[singular-3.1.7p1.p2] checking size of double... 8
[singular-3.1.7p1.p2] checking size of size_t... 8
[singular-3.1.7p1.p2] configure: error: need equal sizes for long and void*
[singular-3.1.7p1.p2] configure: error: ./configure failed for omalloc
[singular-3.1.7p1.p2] Unable to configure Singular.
[singular-3.1.7p1.p2] Error building Singular (error in config).
[singular-3.1.7p1.p2] 
[singular-3.1.7p1.p2] real0m1.515s
[singular-3.1.7p1.p2] user0m0.781s
[singular-3.1.7p1.p2] sys0m0.835s
[singular-3.1.7p1.p2] 

[singular-3.1.7p1.p2] Error installing package singular-3.1.7p1.p2
[singular-3.1.7p1.p2] 

[singular-3.1.7p1.p2] Please email sage-devel 
(http://groups.google.com/group/sage-devel)
[singular-3.1.7p1.p2] explaining the problem and including the relevant 
part of the log file
[singular-3.1.7p1.p2]   /home/simon/sage/logs/pkgs/singular-3.1.7p1.p2.log
[singular-3.1.7p1.p2] Describe your computer, operating system, etc.
[singular-3.1.7p1.p2] If you want to try to fix the problem yourself, 
*don't* just cd to
[singular-3.1.7p1.p2] 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2 and type 
'make' or whatever is appropriate.
[singular-3.1.7p1.p2] Instead, the following commands setup all environment 
variables
[singular-3.1.7p1.p2] correctly and load a subshell for you to debug the 
error:
[singular-3.1.7p1.p2]   (cd 
'/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2' && 
'/home/simon/sage/sage' --sh)
[singular-3.1.7p1.p2] When you are done debugging, you can type "exit" to 
leave the subshell.
[singular-3.1.7p1.p2] 

Makefile:2746: die Regel für Ziel 
„/home/simon/sage/local/var/lib/sage/installed/singular-3.1.7p1.p2“ 
scheiterte
make[2]: *** 
[/home/simon/sage/local/var/lib/sage/installed/singular-3.1.7p1.p2] Fehler 1
make[2]: Verzeichnis „/home/simon/sage/build/make“ wird verlassen
Makefile:862: die Regel für Ziel „all“ scheiterte
make[1]: *** [all] Fehler 2
make[1]: Verzeichnis „/home/simon/sage/build/make“ wird verlassen

real71m30.858s
user63m41.418s
sys6m58.234s
***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):

* package: singular-3.1.7p1.p2
  log file: /home/simon/sage/logs/pkgs/singular-3.1.7p1.p2.log
  build directory: 
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent 

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

[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
[python2-2.7.10.p2] checking size of long double... 16
[python2-2.7.10.p2] checking size of long double... 16
[brial-0.8.5] checking size of long... 8
[ecl-16.1.2.p2] checking size of long long... 64
[freetype-2.6.3] checking size of long... 8
[givaro-3.7.1] checking size of long... 8
[givaro-3.7.1] checking size of long long... 8
[fflas_ffpack-1.6.0.p2] checking size of long... 8
[fflas_ffpack-1.6.0.p2] checking size of long long... 8
[linbox-1.3.2.p1] checking size of long... 8
[linbox-1.3.2.p1] checking size of long long... 8
[ppl-1.2] checking size of long... 8
[ppl-1.2] checking size of long long... 8
[ppl-1.2] checking size of long double... 16
[pynac-0.6.8] checking size of long... 8
[pynac-0.6.8] checking size of long long... 8
[pynac-0.6.8] checking size of long double... 16
[singular-3.1.7p1.p2] checking size of long... 0
[singular-3.1.7p1.p2] checking size of long... (cached) 0
 

>
> to see if on other occasions the system was able to figure out a more 
> sensible value.
>
> In any case, the first thing to try would be to figure out how to wipe the 
> configure cache and hope that on a fresh run it will be able to figure out 
> the right value.
>
Please tell me if you figure it out. I have no clue what to do here. 


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 just typed
> 
> git clone git://github.com/sagemath/sage.git
> cd sage
> git checkout develop
> make
> 
> And get an error Message:
> [singular-3.1.7p1.p2] checking size of long... (cached) 0
> [singular-3.1.7p1.p2] checking size of void*... 8
> [singular-3.1.7p1.p2] checking size of double... 8
> [singular-3.1.7p1.p2] checking size of size_t... 8
> [singular-3.1.7p1.p2] configure: error: need equal sizes for long and void*
> [singular-3.1.7p1.p2] configure: error: ./configure failed for omalloc
> [singular-3.1.7p1.p2] Unable to configure Singular.
> [singular-3.1.7p1.p2] Error building Singular (error in config).

sizeof(long) is zero...  Nice.


> (the log is too big to attach)

Well, the last lines should contain "The following packages may have
failed to build:" along with paths to the temporary build directory of
Singular and the log file created for that package.

Since Singular's 'configure' already failed, we'd need the config.log
file(s) from subfolders of the build directory mentioned.

Also logs/pkgs/singular-3.1.7p1.p2.log shouldn't be that long; from that
we could see /which/ 'configure' failed (presumably indeed that of
omalloc), as Singular consists of a couple of components with their own
'configure' scripts.


-leif


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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
>
> to get a developer version of sage.
> Basically I just typed
>
> git clone git://github.com/sagemath/sage.git
> cd sage
> git checkout develop
> make
>
> And get an error Message:
> [singular-3.1.7p1.p2] checking size of long... (cached) 0
>
>
That's obviously wrong. It should get 8 there. You might want to do a:

$ grep "size of long" install.log

to see if on other occasions the system was able to figure out a more 
sensible value.

In any case, the first thing to try would be to figure out how to wipe the 
configure cache and hope that on a fresh run it will be able to figure out 
the right value.


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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
Vendor ID: GenuineIntel
CPU family:6
Model: 60
Model name:Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Stepping:  3
CPU MHz:   2399.906
CPU max MHz:   3400.
CPU min MHz:   800.
BogoMIPS:  4789.26
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  256K
L3 cache:  6144K
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor 
ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt dtherm ida arat pln pts




H/W path   Device Class  Description

  system X761X (To be filled by O.E.M.)
/0busX761X
/0/0  memory 64KiB BIOS
/0/3e processor  Intel(R) Core(TM) i7-4700HQ CPU @ 
2.40GHz
/0/3e/3f  memory 1MiB L2 cache
/0/3e/40  memory 256KiB L1 cache
/0/3e/41  memory 6MiB L3 cache
/0/42 memory 16GiB System Memory
/0/42/0   memory 8GiB SODIMM DDR3 Synchronous 1600 
MHz (0.6 ns)
/0/42/1   memory 8GiB SODIMM DDR3 Synchronous 1600 
MHz (0.6 ns)
/0/100bridge Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller
/0/100/1  bridge Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controlle
/0/100/1/0displayGK106M [GeForce GTX 765M]
/0/100/1/0.1  multimedia GK106 HDMI Audio Controller
/0/100/2  display4th Gen Core Processor Integrated 
Graphics Controller
/0/100/14 bus8 Series/C220 Series Chipset 
Family USB xHCI
/0/100/14/0usb3   busxHCI Host Controller
/0/100/14/0/5 input  Razer Orochi
/0/100/14/0/7 communication  Bluetooth wireless interface
/0/100/14/0/8 multimedia USB 2.0 Webcam Device
/0/100/14/0/e input  MSI EPF USB
/0/100/14/1usb4   busxHCI Host Controller
/0/100/16 communication  8 Series/C220 Series Chipset 
Family MEI Controller #1
/0/100/1a bus8 Series/C220 Series Chipset 
Family USB EHCI #2
/0/100/1a/1usb1   busEHCI Host Controller
/0/100/1a/1/1 busUSB hub
/0/100/1b multimedia 8 Series/C220 Series Chipset High 
Definition Audio Controller
/0/100/1c bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #1
/0/100/1c.2   bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #3
/0/100/1c.3   bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #4
/0/100/1c.3/0  enp4s0 networkKiller E220x Gigabit Ethernet 
Controller
/0/100/1c.4   bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #5
/0/100/1c.4/0  wlp5s0 networkWireless 7260
/0/100/1d bus8 Series/C220 Series Chipset 
Family USB EHCI #1
/0/100/1d/1usb2   busEHCI Host Controller
/0/100/1d/1/1 busUSB hub
/0/100/1f bridge HM87 Express LPC Controller
/0/100/1f.2   storage8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AH
/0/100/1f.3   bus8 Series/C220 Series Chipset 
Family SMBus Controller
/0/1   scsi0  storage
/0/1/0.0.0 /dev/sda   disk   128GB SanDisk SD6SF1M1
/0/1/0.0.0/1   /dev/sda1  volume 498MiB Windows NTFS volume
/0/1/0.0.0/2   /dev/sda2  volume 99MiB Windows FAT volume
/0/1/0.0.0/3   /dev/sda3  volume 127MiB reserved partition
/0/1/0.0.0/4   /dev/sda4  volume 1023MiB Windows FAT volume
/0/1/0.0.0/5   /dev/sda5  volume 117GiB Windows NTFS volume
/0/2   scsi4  storage
/0/2/0.0.0 /dev/sdb   disk   1TB ST1000LM024 HN-M
/0/2/0.0.0/1   /dev/sdb1  

[sage-devel] Re: Error Building Sage

[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 minutes more)

On Wednesday, May 18, 2016 at 12:29:30 AM UTC+1, saad khalid wrote:
>
> 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 
> hours total to run 'make distclean' and 'make build' if it messes up 
> again... However, I do want to know why it wasn't working. 
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Building Sage

[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 hours 
total to run 'make distclean' and 'make build' if it messes up again... 
However, I do want to know why it wasn't working. 

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Building Sage

[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 this same issue before, so I decided to 
> delete my git folder in home and then install it again. So, I ran 
>
> git clone git://github.com/sagemath/sage.git
>
> and it remade the sage directory. Then, I did "cd sage", and ran "git 
> checkout develop". After this, I checked and I was on the develop branch. 
> This should have been a fresh copy, straight from 
> the Sage mirror. 
> However, when I ran make, I got the following error: 
> Error building the documentation.
> Traceback (most recent call last):
>   File "/home/saad/sage/local/lib/python/runpy.py", line 162, in 
> _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/home/saad/sage/local/lib/python/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__main__.py",
>  line 2, in 
> main()
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
>  line 1629, in main
> builder()
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
>  line 284, in _wrapper
> getattr(get_builder(document), 'inventory')(*args, **kwds)
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
>  line 495, in _wrapper
> x.get(9)
>   File "/home/saad/sage/local/lib/python/multiprocessing/pool.py", line 567, 
> in get
> raise self._value
> OSError: [plot3d   ] 
> /home/saad/sage/local/lib/python2.7/site-packages/sage/plot/plot3d/platonic.py:docstring
>  of sage.plot.plot3d.platonic:10: WARNING: Exception occurred in plotting 
> platonic-1
>
> make[2]: *** [doc-html] Error 1
> make[2]: Leaving directory `/home/saad/sage/build/make'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/saad/sage/build/make'
>
> real193m34.862s
> user182m33.248s
> sys 4m55.540s
> ***
> 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/saad/sage/logs/pkgs/../dochtml.log
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> make: *** [all] Error 1
>
>
> I'm not exactly sure what to do here. Now, when I try running a doctest like 
> the following:
> ./sage -t /src/sage/interface/maxima_lib.py
>
> I get the following error:
> no stored timings available
> Running doctests with ID 2016-05-15-10-38-26-bc8799da.
> Git branch: develop
> Using --optional=mpir,python2,sage
> Doctesting 1 file.
> Traceback (most recent call last):
>   File "/home/saad/sage/src/bin/sage-runtests", line 89, in 
> err = DC.run()
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", 
> line 1044, in run
> self.run_doctests()
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", 
> line 761, in run_doctests
> self.dispatcher = DocTestDispatcher(self)
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
> line 1376, in __init__
> init_sage()
>   File 
> "/home/saad/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
> line 125, in init_sage
> from sympy.printing.pretty.stringpict import stringPict
> ImportError: No module named sympy.printing.pretty.stringpict
>
>
> Now, I got this error in the last thread as well(see here 
> https://groups.google.com/forum/#!topic/sage-devel/ayb4qJ6_sM4 ) and when I 
> tried the suggestion of reinstalling sympy within the
>  sage directory, it gave me  errors with mpmath, the same ones that are in 
> these tickets(and were obviously fixed a while ago)
>
> http://trac.sagemath.org/ticket/16624
> https://github.com/sympy/sympy/issues/8022
>
> I'm certain I'm running the most recent version of Sage. When I run it, it 
> says that I'm running 7.2.rc2. Obviously, something is happening incorrectly 
> with my install of sympy(it's not automatically
>  installed in my sage directory, and simply installing the .7.6.1 copy from 
> sympy just gives me the mpmath based errors). What exactly is 
> happening? 
> To do a full reinstall from scratch, do I need to do more than delete the 
> sage directory? 
>
>

-- 
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

[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
> MacBook-de-Javier:sage-6.10 t143730$ git diff
> diff --git a/src/sage/plot/hyperbolic_arc.py 
> b/src/sage/plot/hyperbolic_arc.py
> index 5b1ac5d..17f88f5 100644
> --- a/src/sage/plot/hyperbolic_arc.py
> +++ b/src/sage/plot/hyperbolic_arc.py
> @@ -8,6 +8,7 @@ AUTHORS:
>
>  
> #*
>  #   Copyright (C) 2011 Hartmut Monien ,
>  # 2015 Stefan Kraemer  >
> +# 2016 Javier Honrubia 
>  #
>  #  Distributed under the terms of the GNU General Public License (GPL)
>  #
>
> then I used ./sage -br as instructed to rebuild my local copy of sage and 
> got 1 error where there should be none . Could somebody give me a clue on 
> this?
>
> Executing 146 commands (using 1 thread)
> [  1/146] gcc -fno-strict-aliasing 
> -I/Users/t143730/Applications/sage-6.10/local/var/tmp/sage/build/python2-2.7.10.p0/include
>  
> -DNDEBUG -g -fwrapv -O3 -Wall 
> -I/Users/t143730/Applications/sage-6.10/local/include 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 
> -I/Users/t143730/Applications/sage-6.10/local/lib/python2.7/site-packages/numpy/core/include
>  
> -I/Users/t143730/Applications/sage-6.10/src 
> -I/Users/t143730/Applications/sage-6.10/src/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 -c 
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp
>  
> -o 
> build/temp.macosx-10.7-x86_64-2.7/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.o
>  
> -DFPLLL_V3_COMPAT -fno-strict-aliasing -w
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:
>  
> In function 'PyObject* 
> __pyx_pf_4sage_4libs_5fplll_5fplll_6FP_LLL_10BKZ(__pyx_obj_4sage_4libs_5fplll_5fplll_FP_LLL*,
>  
> int, double, PyObject*, int, int, int, PyObject*, PyObject*, PyObject*, 
> PyObject*)':
> /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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
> __pyx_v_o, 
> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
> __pyx_v_precision);
>   
> 
>^
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 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 -br getting the error I showed before. All during the same two days 
> interval. Tried sage -ba unsuccessfully I'm trying 'make' again. I will 
> return the result when it finishes. Is there a thumb rule as to when it is 
> mandatory to go through 'make' all the source or when simple sage -b will 
> suffice?
>
>
> 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
>> MacBook-de-Javier:sage-6.10 t143730$ git diff
>> diff --git a/src/sage/plot/hyperbolic_arc.py 
>> b/src/sage/plot/hyperbolic_arc.py
>> index 5b1ac5d..17f88f5 100644
>> --- a/src/sage/plot/hyperbolic_arc.py
>> +++ b/src/sage/plot/hyperbolic_arc.py
>> @@ -8,6 +8,7 @@ AUTHORS:
>>
>>  
>> #*
>>  #   Copyright (C) 2011 Hartmut Monien > >,
>>  # 2015 Stefan Kraemer > >
>> +# 2016 Javier Honrubia > >
>>  #
>>  #  Distributed under the terms of the GNU General Public License (GPL)
>>  #
>>
>> then I used ./sage -br as instructed to rebuild my local copy of sage and 
>> got 1 error where there should be none . Could somebody give me a clue on 
>> this?
>>
>> Executing 146 commands (using 1 thread)
>> [  1/146] gcc -fno-strict-aliasing 
>> -I/Users/t143730/Applications/sage-6.10/local/var/tmp/sage/build/python2-2.7.10.p0/include
>>  
>> -DNDEBUG -g -fwrapv -O3 -Wall 
>> -I/Users/t143730/Applications/sage-6.10/local/include 
>> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 
>> -I/Users/t143730/Applications/sage-6.10/local/lib/python2.7/site-packages/numpy/core/include
>>  
>> -I/Users/t143730/Applications/sage-6.10/src 
>> -I/Users/t143730/Applications/sage-6.10/src/sage/ext 
>> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized 
>> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/ext 
>> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 -c 
>> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp
>>  
>> -o 
>> build/temp.macosx-10.7-x86_64-2.7/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.o
>>  
>> -DFPLLL_V3_COMPAT -fno-strict-aliasing -w
>> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:
>>  
>> In function 'PyObject* 
>> __pyx_pf_4sage_4libs_5fplll_5fplll_6FP_LLL_10BKZ(__pyx_obj_4sage_4libs_5fplll_5fplll_FP_LLL*,
>>  
>> int, double, PyObject*, int, int, int, PyObject*, PyObject*, PyObject*, 
>> PyObject*)':
>> /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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
>> __pyx_v_o, 
>> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
>> __pyx_v_precision);
>>   
>> 
>>^
>>
>>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 branch, there was a recent fplll 
update. You probably need to run "make" or "make distclean && 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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 
> 'bkzReduction(fplll::ZZ_mat<__mpz_struct [1]>*&, NULL, fplll::BKZParam&, 
> fplll::FloatType, int&)'
>__pyx_v_r = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
> __pyx_v_o, 
> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
> __pyx_v_precision);
>   
> 
>^
>
> 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
>> MacBook-de-Javier:sage-6.10 t143730$ git diff
>> diff --git a/src/sage/plot/hyperbolic_arc.py 
>> b/src/sage/plot/hyperbolic_arc.py
>> index 5b1ac5d..17f88f5 100644
>> --- a/src/sage/plot/hyperbolic_arc.py
>> +++ b/src/sage/plot/hyperbolic_arc.py
>> @@ -8,6 +8,7 @@ AUTHORS:
>>
>>  
>> #*
>>  #   Copyright (C) 2011 Hartmut Monien > >,
>>  # 2015 Stefan Kraemer > >
>> +# 2016 Javier Honrubia > >
>>  #
>>  #  Distributed under the terms of the GNU General Public License (GPL)
>>  #
>>
>> then I used ./sage -br as instructed to rebuild my local copy of sage and 
>> got 1 error where there should be none . Could somebody give me a clue on 
>> this?
>>
>> Executing 146 commands (using 1 thread)
>> [  1/146] gcc -fno-strict-aliasing 
>> -I/Users/t143730/Applications/sage-6.10/local/var/tmp/sage/build/python2-2.7.10.p0/include
>>  
>> -DNDEBUG -g -fwrapv -O3 -Wall 
>> -I/Users/t143730/Applications/sage-6.10/local/include 
>> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 
>> -I/Users/t143730/Applications/sage-6.10/local/lib/python2.7/site-packages/numpy/core/include
>>  
>> -I/Users/t143730/Applications/sage-6.10/src 
>> -I/Users/t143730/Applications/sage-6.10/src/sage/ext 
>> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized 
>> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/ext 
>> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 -c 
>> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp
>>  
>> -o 
>> build/temp.macosx-10.7-x86_64-2.7/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.o
>>  
>> -DFPLLL_V3_COMPAT -fno-strict-aliasing -w
>> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:
>>  
>> In function 'PyObject* 
>> __pyx_pf_4sage_4libs_5fplll_5fplll_6FP_LLL_10BKZ(__pyx_obj_4sage_4libs_5fplll_5fplll_FP_LLL*,
>>  
>> int, double, PyObject*, int, int, int, PyObject*, PyObject*, PyObject*, 
>> PyObject*)':
>> /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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
>> __pyx_v_o, 
>> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
>> __pyx_v_precision);
>>   
>> 
>>^
>>
>  
did you compile your Sage installation from source?
(probably noone tests Sage binary distributions for ability to compile 
C/C++...)
 

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 -br getting the error I showed before. All during the same two days 
interval. Tried sage -ba unsuccessfully I'm trying 'make' again. I will 
return the result when it finishes. Is there a thumb rule as to when it is 
mandatory to go through 'make' all the source or when simple sage -b will 
suffice?


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
> MacBook-de-Javier:sage-6.10 t143730$ git diff
> diff --git a/src/sage/plot/hyperbolic_arc.py 
> b/src/sage/plot/hyperbolic_arc.py
> index 5b1ac5d..17f88f5 100644
> --- a/src/sage/plot/hyperbolic_arc.py
> +++ b/src/sage/plot/hyperbolic_arc.py
> @@ -8,6 +8,7 @@ AUTHORS:
>
>  
> #*
>  #   Copyright (C) 2011 Hartmut Monien ,
>  # 2015 Stefan Kraemer  >
> +# 2016 Javier Honrubia 
>  #
>  #  Distributed under the terms of the GNU General Public License (GPL)
>  #
>
> then I used ./sage -br as instructed to rebuild my local copy of sage and 
> got 1 error where there should be none . Could somebody give me a clue on 
> this?
>
> Executing 146 commands (using 1 thread)
> [  1/146] gcc -fno-strict-aliasing 
> -I/Users/t143730/Applications/sage-6.10/local/var/tmp/sage/build/python2-2.7.10.p0/include
>  
> -DNDEBUG -g -fwrapv -O3 -Wall 
> -I/Users/t143730/Applications/sage-6.10/local/include 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 
> -I/Users/t143730/Applications/sage-6.10/local/lib/python2.7/site-packages/numpy/core/include
>  
> -I/Users/t143730/Applications/sage-6.10/src 
> -I/Users/t143730/Applications/sage-6.10/src/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 -c 
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp
>  
> -o 
> build/temp.macosx-10.7-x86_64-2.7/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.o
>  
> -DFPLLL_V3_COMPAT -fno-strict-aliasing -w
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:
>  
> In function 'PyObject* 
> __pyx_pf_4sage_4libs_5fplll_5fplll_6FP_LLL_10BKZ(__pyx_obj_4sage_4libs_5fplll_5fplll_FP_LLL*,
>  
> int, double, PyObject*, int, int, int, PyObject*, PyObject*, PyObject*, 
> PyObject*)':
> /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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
> __pyx_v_o, 
> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
> __pyx_v_precision);
>   
> 
>^
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 a/src/sage/plot/hyperbolic_arc.py 
> b/src/sage/plot/hyperbolic_arc.py
> index 5b1ac5d..17f88f5 100644
> --- a/src/sage/plot/hyperbolic_arc.py
> +++ b/src/sage/plot/hyperbolic_arc.py
> @@ -8,6 +8,7 @@ AUTHORS:
>
>  
> #*
>  #   Copyright (C) 2011 Hartmut Monien  >,
>  # 2015 Stefan Kraemer  >
> +# 2016 Javier Honrubia  >
>  #
>  #  Distributed under the terms of the GNU General Public License (GPL)
>  #
>
> then I used ./sage -br as instructed to rebuild my local copy of sage and 
> got 1 error where there should be none . Could somebody give me a clue on 
> this?
>
> Executing 146 commands (using 1 thread)
> [  1/146] gcc -fno-strict-aliasing 
> -I/Users/t143730/Applications/sage-6.10/local/var/tmp/sage/build/python2-2.7.10.p0/include
>  
> -DNDEBUG -g -fwrapv -O3 -Wall 
> -I/Users/t143730/Applications/sage-6.10/local/include 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 
> -I/Users/t143730/Applications/sage-6.10/local/lib/python2.7/site-packages/numpy/core/include
>  
> -I/Users/t143730/Applications/sage-6.10/src 
> -I/Users/t143730/Applications/sage-6.10/src/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 -c 
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp
>  
> -o 
> build/temp.macosx-10.7-x86_64-2.7/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.o
>  
> -DFPLLL_V3_COMPAT -fno-strict-aliasing -w
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:
>  
> In function 'PyObject* 
> __pyx_pf_4sage_4libs_5fplll_5fplll_6FP_LLL_10BKZ(__pyx_obj_4sage_4libs_5fplll_5fplll_FP_LLL*,
>  
> int, double, PyObject*, int, int, int, PyObject*, PyObject*, PyObject*, 
> PyObject*)':
> /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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
> __pyx_v_o, 
> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
> __pyx_v_precision);
>   
> 
>^
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: error building sage

[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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, __pyx_v_o, 
__pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
__pyx_v_precision);


 ^

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
> MacBook-de-Javier:sage-6.10 t143730$ git diff
> diff --git a/src/sage/plot/hyperbolic_arc.py 
> b/src/sage/plot/hyperbolic_arc.py
> index 5b1ac5d..17f88f5 100644
> --- a/src/sage/plot/hyperbolic_arc.py
> +++ b/src/sage/plot/hyperbolic_arc.py
> @@ -8,6 +8,7 @@ AUTHORS:
>
>  
> #*
>  #   Copyright (C) 2011 Hartmut Monien ,
>  # 2015 Stefan Kraemer  >
> +# 2016 Javier Honrubia 
>  #
>  #  Distributed under the terms of the GNU General Public License (GPL)
>  #
>
> then I used ./sage -br as instructed to rebuild my local copy of sage and 
> got 1 error where there should be none . Could somebody give me a clue on 
> this?
>
> Executing 146 commands (using 1 thread)
> [  1/146] gcc -fno-strict-aliasing 
> -I/Users/t143730/Applications/sage-6.10/local/var/tmp/sage/build/python2-2.7.10.p0/include
>  
> -DNDEBUG -g -fwrapv -O3 -Wall 
> -I/Users/t143730/Applications/sage-6.10/local/include 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 
> -I/Users/t143730/Applications/sage-6.10/local/lib/python2.7/site-packages/numpy/core/include
>  
> -I/Users/t143730/Applications/sage-6.10/src 
> -I/Users/t143730/Applications/sage-6.10/src/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized 
> -I/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/ext 
> -I/Users/t143730/Applications/sage-6.10/local/include/python2.7 -c 
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp
>  
> -o 
> build/temp.macosx-10.7-x86_64-2.7/Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.o
>  
> -DFPLLL_V3_COMPAT -fno-strict-aliasing -w
> /Users/t143730/Applications/sage-6.10/src/build/cythonized/sage/libs/fplll/fplll.cpp:
>  
> In function 'PyObject* 
> __pyx_pf_4sage_4libs_5fplll_5fplll_6FP_LLL_10BKZ(__pyx_obj_4sage_4libs_5fplll_5fplll_FP_LLL*,
>  
> int, double, PyObject*, int, int, int, PyObject*, PyObject*, PyObject*, 
> PyObject*)':
> /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 = fplll::bkzReduction(__pyx_v_self->_lattice, NULL, 
> __pyx_v_o, 
> __pyx_f_4sage_4libs_5fplll_5fplll_check_float_type(__pyx_v_float_type), 
> __pyx_v_precision);
>   
> 
>^
>
>

-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage

[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 
 *Ubuntu_14.04_LTS* 
 http://www-ftp.lip6.fr/pub/math/sagemath/linux/32bit/Ubuntu_14.04_LTS_sage-6.8-i686-Linux.tar.lrz
  
 and when I compile make I received this error message:


 ***
 Error building Sage.

 The following package(s) may have failed to build (not necessarily
 during this run of 'make all'):

 * package: sage-6.8
   log file: 
 /home/anthony/Téléchargements/sage-6.8-i686-Linux/logs/pkgs/sage-6.8.log
   build directory: 
 /home/anthony/Téléchargements/sage-6.8-i686-Linux/local/var/tmp/sage/build/sage-6.8

 The build directory may contain configuration files and other potentially
 helpful information. WARNING: if you now run 'make' again, the build
 directory will, by default, be deleted. Set the environment variable
 SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

 make: *** [all] Erreur 1

 My log file is attached.

 Could you please help me ? Thanks


-- 
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, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage

[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 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, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[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 run into further problems...


-leif

[1] http://trac.sagemath.org/ticket/18156


 On 05/05/15 12:53, Tynan Kelly wrote:
 Comparing stages 2 and 3

 warning: gcc/cc1-checksum.o differs

 warning: gcc/cc1plus-checksum.o differs

 Bootstrap comparison 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 from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.