Re: [sage-devel] Error Building Sage 10.4 on RHEL8 from Source

2024-07-31 Thread Dale Marshall

I've spent the last few days recompiling several versions of GCC and 
installing them in /usr/local/gccxx so I can try different versions of GCC 
against the different versions of Sage I have.

Yes, I'm building Sage as root (uid = 0).

I will report back as soon as my tests are complete.

Thanks for the suggestions.

- Dale



On Sunday, July 28, 2024 at 9:16:01 AM UTC-5 Volker Braun wrote:

> Pretty sure he means the "uid == 0" kind of root ;)
>
> If you have enough memory: try upgrading to gcc 14.1.1 or use our bundled 
> gcc 13 (./configure --with-system-gcc=no)
>
> On Sunday, July 28, 2024 at 4:10:32 PM UTC+2 Dima Pasechnik wrote:
>
>>
>>
>> On 24 July 2024 17:15:36 BST, Dale Marshall  wrote: 
>> > 
>> >I'm on a closed network so I cannot provide the log files. 
>> > 
>> >I'm building Sage 10.4 on a RHEL8.10 box using root and GCC 14.1.0. The 
>> >configure line was: 
>> > 
>> >./configure --prefix= --enable-build-as-root --enable-wheels 
>> >--with-python= 
>> > 
>> >The configure showed lots of packages to be compiled (even though I've 
>> >installed as many as I could). The make eventually fails on 
>> >giac-1.9.0.15p0. 
>> > 
>> >The last error messages are: 
>> >init2.c:52:MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t) 
>> >((mprf_uprec_t)(~(mpfr_uprec_t)0)>>1)) 
>> >during GIMPLE pass: fre 
>> >modpoly.cc: In function 'std::complex giac::horner_newton(const 
>> >vecteur&, conf std::complex&, const context*)'; 
>> >modpoly.cc:16083:1: internal compile error: Aborted 
>> >16083 | } // namespace giac 
>> > | ^ 
>> >0xf0873f crash signal 
>> >../../gcc-14.1.0/gcc/toplev.cc:319 
>> >0x7f624acd43c2 mpc_div_zero 
>>
>> this is usually a sign that the compiler ran out of memory. 
>>
>> C++ complilers are very memory-hungry. 
>> Can you make sure there is 4Gb or more of RAM 
>> available? 
>>
>> We should test Sage with root - presume you mean 
>>  ? 
>>
>> Dima 
>> > 
>> > 
>> >Oh... I'm getting the same error on my CentOS7.9 box using the same 
>> version 
>> >of GCC. 
>> > 
>> >Any suggestions on what I can do to resolve this issue would be welcome. 
>> > 
>> >- Dale 
>> > 
>>
>

-- 
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/bf490650-fd1f-4b31-8460-cf8ad76c455an%40googlegroups.com.


Re: [sage-devel] Error Building Sage 10.4 on RHEL8 from Source

2024-07-28 Thread Volker Braun
Pretty sure he means the "uid == 0" kind of root ;)

If you have enough memory: try upgrading to gcc 14.1.1 or use our bundled 
gcc 13 (./configure --with-system-gcc=no)

On Sunday, July 28, 2024 at 4:10:32 PM UTC+2 Dima Pasechnik wrote:

>
>
> On 24 July 2024 17:15:36 BST, Dale Marshall  wrote:
> >
> >I'm on a closed network so I cannot provide the log files.
> >
> >I'm building Sage 10.4 on a RHEL8.10 box using root and GCC 14.1.0. The 
> >configure line was:
> >
> >./configure --prefix= --enable-build-as-root --enable-wheels 
> >--with-python=
> >
> >The configure showed lots of packages to be compiled (even though I've 
> >installed as many as I could). The make eventually fails on 
> >giac-1.9.0.15p0.
> >
> >The last error messages are:
> >init2.c:52:MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t) 
> >((mprf_uprec_t)(~(mpfr_uprec_t)0)>>1))
> >during GIMPLE pass: fre
> >modpoly.cc: In function 'std::complex giac::horner_newton(const 
> >vecteur&, conf std::complex&, const context*)';
> >modpoly.cc:16083:1: internal compile error: Aborted
> >16083 | } // namespace giac
> > | ^
> >0xf0873f crash signal
> >../../gcc-14.1.0/gcc/toplev.cc:319
> >0x7f624acd43c2 mpc_div_zero
>
> this is usually a sign that the compiler ran out of memory.
>
> C++ complilers are very memory-hungry.
> Can you make sure there is 4Gb or more of RAM
> available?
>
> We should test Sage with root - presume you mean 
>  ?
>
> Dima
> >
> >
> >Oh... I'm getting the same error on my CentOS7.9 box using the same 
> version 
> >of GCC.
> >
> >Any suggestions on what I can do to resolve this issue would be welcome.
> >
> >- Dale
> >
>

-- 
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/6067172b-9624-4eb8-9587-1304713a26dcn%40googlegroups.com.


Re: [sage-devel] Error Building Sage 10.4 on RHEL8 from Source

2024-07-28 Thread Dima Pasechnik



On 24 July 2024 17:15:36 BST, Dale Marshall  wrote:
>
>I'm on a closed network so I cannot provide the log files.
>
>I'm building Sage 10.4 on a RHEL8.10 box using root and GCC 14.1.0.  The 
>configure line was:
>
>./configure --prefix= --enable-build-as-root --enable-wheels 
>--with-python=
>
>The configure showed lots of packages to be compiled (even though I've 
>installed as many as I could).  The make eventually fails on 
>giac-1.9.0.15p0.
>
>The last error messages are:
>init2.c:52:MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t) 
>((mprf_uprec_t)(~(mpfr_uprec_t)0)>>1))
>during GIMPLE pass: fre
>modpoly.cc: In function 'std::complex giac::horner_newton(const 
>vecteur&, conf std::complex&, const context*)';
>modpoly.cc:16083:1: internal compile error: Aborted
>16083 | } // namespace giac
>  | ^
>0xf0873f crash signal
>../../gcc-14.1.0/gcc/toplev.cc:319
>0x7f624acd43c2 mpc_div_zero

this is usually a sign that the compiler ran out of memory.

C++ complilers are very memory-hungry.
Can you make sure there is 4Gb or more of RAM
available?

We should test Sage with root - presume you mean 
 ?

Dima
>
>
>Oh... I'm getting the same error on my CentOS7.9 box using the same version 
>of GCC.
>
>Any suggestions on what I can do to resolve this issue would be welcome.
>
>- Dale
>

-- 
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/DC241D93-08DF-4D01-AA7C-7517F1714B54%40gmail.com.


[sage-devel] Error Building Sage 10.4 on RHEL8 from Source

2024-07-27 Thread Dale Marshall

I'm on a closed network so I cannot provide the log files.

I'm building Sage 10.4 on a RHEL8.10 box using root and GCC 14.1.0.  The 
configure line was:

./configure --prefix= --enable-build-as-root --enable-wheels 
--with-python=

The configure showed lots of packages to be compiled (even though I've 
installed as many as I could).  The make eventually fails on 
giac-1.9.0.15p0.

The last error messages are:
init2.c:52:MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t) 
((mprf_uprec_t)(~(mpfr_uprec_t)0)>>1))
during GIMPLE pass: fre
modpoly.cc: In function 'std::complex giac::horner_newton(const 
vecteur&, conf std::complex&, const context*)';
modpoly.cc:16083:1: internal compile error: Aborted
16083 | } // namespace giac
  | ^
0xf0873f crash signal
../../gcc-14.1.0/gcc/toplev.cc:319
0x7f624acd43c2 mpc_div_zero


Oh... I'm getting the same error on my CentOS7.9 box using the same version 
of GCC.

Any suggestions on what I can do to resolve this issue would be welcome.

- Dale

-- 
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/214dd1ba-b399-4c58-84a8-be855310ef57n%40googlegroups.com.


Re: [sage-devel] Error building Sage: lrcalc-2.1 and python3-3.11.1 failed to build successfully

2024-06-27 Thread Dima Pasechnik
On Thu, Jun 27, 2024 at 8:19 AM Ani J  wrote:

> ### Environment
>
> - **OS**:Ubuntu 22.04.4 LTS
> - **Sage Version**: sage-10.3
>
>
> ### Steps To Reproduce
>
> 1. I'm trying to install sage in an anaconda environment in Ubuntu 22.04
> 2. I have run the commands './bootstrap', './configure'
> 3. Then I installed some packages
> 4. Then I ran 'make reconfigure' followed by 'make'
>

If you just need Sage for computations, not for development, you should
follow
https://doc.sagemath.org/html/en/installation/conda.html#installing-all-of-sagemath-from-conda-not-for-development


Otherwise, please follow
https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-system-packages-for-the-sage-distribution
(slower)

or
https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-all-dependencies-for-the-sage-library
(quicker)


5. I get the following Error message:
> `***
> Error building Sage.
>
> merely mixing up system and conda packages whille building Sage is surely
going to break things.

HTH
Dima

-- 
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/CAAWYfq1hH0T1cSocPPpMPmE9W1THbJ2knyiemtQd1qkC8v10Dg%40mail.gmail.com.


[sage-devel] Error building Sage: lrcalc-2.1 and python3-3.11.1 failed to build successfully

2024-06-27 Thread Ani J
### Environment

- **OS**:Ubuntu 22.04.4 LTS
- **Sage Version**: sage-10.3


### Steps To Reproduce

1. I'm trying to install sage in an anaconda environment in Ubuntu 22.04 
2. I have run the commands './bootstrap', './configure'
3. Then I installed some packages
4. Then I ran 'make reconfigure' followed by 'make'
5. I get the following Error message:
`***
Error building Sage.

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

* package: lrcalc-2.1
  last build time: May 28 13:03
  log file:~/some_path/sage-10.3/logs/pkgs/lrcalc-2.1.log

* package: python3-3.11.1
  last build time: Jun 12 08:30
  log file:~/some_path/sage-10.3/logs/pkgs/python3-3.11.1.log

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 '~/some_path/sage-10.3'
make: *** [Makefile:13: all] Error 2
`

### Config log

[config.log](https://github.com/user-attachments/files/15798178/config.log)


### Package logs

[lrcalc-2.1.log](https://github.com/user-attachments/files/15798164/lrcalc-2.1.log)
[python3-3.11.1.log](https://github.com/user-attachments/files/15798165/python3-3.11.1.log)


### Additional Information

No specific references. I wasn't able to find any references for Sage-10.3 
with the same issue.


-- 
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/fecb54f9-9349-41dc-b7f9-eaec01e128d0n%40googlegroups.com.


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

2024-01-16 Thread John Cremona
Try not using the system's eclib.  I don't think that any Linux
distribution has an up to date eclib (but I don't keep track of this).
Sage does now have a very up to date eclib, and building it will not take
long.

John Cremona

On Mon, 15 Jan 2024 at 21:59, 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/940b1bab-04ec-44ff-bc38-e4b073baf5ban%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/CAD0p0K5z09T6tcJA1yOuYR4GevHR8AuPgUbKycyatppWq8dRjA%40mail.gmail.com.


Re: [sage-devel] Error building sage-9.7 in macOS Monterey with package giac-1.9.0.15p0

2022-09-29 Thread Sette Diop
./configure-with-system-pari=no solved my giac build error.

Thanks so much to Dima and Travis!


> On Sep 29, 2022, at 2:07 PM, dmo...@deductivepress.ca 
>  wrote:
> 
> To deal with this problem, I did:
> 
> ./configure --with-system-pari=no
> make
> 
> On Thursday, September 29, 2022 at 10:24:34 AM UTC-6 dim...@gmail.com wrote:
> On Thu, Sep 29, 2022 at 4:38 PM Sette Diop  > wrote: 
> > 
> > Hi: 
> > 
> > I am building sage-9.7 on macOS 12.6 (Monterey) and run through this error: 
> > 
> > Error building Sage. 
> > 
> > The following package(s) may have failed to build (not necessarily 
> > during this run of 'make all-start'): 
> 
> do you use pari from Homebrew? They now have 2.15, too new for Sage, 
> and we don't have a fix to reject it. 
> If so, try 
> 
> make -j8 pari 
> make -j8 build 
> 
> 
> > 
> > package: giac-1.9.0.15p0 
> > last build time: Sep 29 10:49 
> > log file: /Applications/sage/logs/pkgs/giac-1.9.0.15p0.log 
> > build directory: 
> > /Applications/sage/local/var/tmp/sage/build/giac-1.9.0.15p0 
> > 
> > The log file is attached. 
> > 
> > In the log it seems to me that the error comes from the installation of 
> > pari. But Homebrew says that pari 2.15.0 was previously successfully 
> > installed. 
> > 
> > Any help is welcome! 
> > 
> > Best, 
> > Diop 
> > 
> > -- 
> > 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 view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/D8B432C9-749F-4831-B96D-4536B6A7768F%40gmail.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/4e36d088-6064-4660-a758-a080900e3ae4n%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/2B6ADD3F-1569-48D2-B93B-182C17E93686%40gmail.com.


Re: [sage-devel] Error building sage-9.7 in macOS Monterey with package giac-1.9.0.15p0

2022-09-29 Thread dmo...@deductivepress.ca
To deal with this problem, I did:

./configure --with-system-pari=no
make

On Thursday, September 29, 2022 at 10:24:34 AM UTC-6 dim...@gmail.com wrote:

> On Thu, Sep 29, 2022 at 4:38 PM Sette Diop  wrote:
> >
> > Hi:
> >
> > I am building sage-9.7 on macOS 12.6 (Monterey) and run through this 
> error:
> >
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
>
> do you use pari from Homebrew? They now have 2.15, too new for Sage,
> and we don't have a fix to reject it.
> If so, try
>
> make -j8 pari
> make -j8 build
>
>
> >
> > package: giac-1.9.0.15p0
> > last build time: Sep 29 10:49
> > log file: /Applications/sage/logs/pkgs/giac-1.9.0.15p0.log
> > build directory: 
> /Applications/sage/local/var/tmp/sage/build/giac-1.9.0.15p0
> >
> > The log file is attached.
> >
> > In the log it seems to me that the error comes from the installation of 
> pari. But Homebrew says that pari 2.15.0 was previously successfully 
> installed.
> >
> > Any help is welcome!
> >
> > Best,
> > Diop
> >
> > --
> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/D8B432C9-749F-4831-B96D-4536B6A7768F%40gmail.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/4e36d088-6064-4660-a758-a080900e3ae4n%40googlegroups.com.


Re: [sage-devel] Error building sage-9.7 in macOS Monterey with package giac-1.9.0.15p0

2022-09-29 Thread Dima Pasechnik
On Thu, Sep 29, 2022 at 4:38 PM Sette Diop  wrote:
>
> Hi:
>
> I am building sage-9.7 on macOS 12.6 (Monterey) and run through this error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):

do you use pari from Homebrew? They now have 2.15, too new for Sage,
and we don't have a fix to reject it.
If so, try

make -j8 pari
make -j8 build


>
> package: giac-1.9.0.15p0
> last build time: Sep 29 10:49
> log file:/Applications/sage/logs/pkgs/giac-1.9.0.15p0.log
> build directory: /Applications/sage/local/var/tmp/sage/build/giac-1.9.0.15p0
>
> The log file is attached.
>
> In the log it seems to me that the error comes from the installation of pari. 
> But Homebrew says that pari 2.15.0 was previously successfully installed.
>
> Any help is welcome!
>
> Best,
> Diop
>
> --
> 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/D8B432C9-749F-4831-B96D-4536B6A7768F%40gmail.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/CAAWYfq1GeUoCKTQsSCd2wNv6s%3DEWw%3DkNitzRtLq_cen6VhCfVg%40mail.gmail.com.


Re: [sage-devel] Error building sage-9.7 in macOS Monterey with package giac-1.9.0.15p0

2022-09-29 Thread Jan Groenewald
Hi

On Thu, 29 Sept 2022 at 17:38, Sette Diop  wrote:

> Hi:
>
> I am building sage-9.7 on macOS 12.6 (Monterey) and run through this error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> package: giac-1.9.0.15p0
> last build time: Sep 29 10:49
> log file:/Applications/sage/logs/pkgs/giac-1.9.0.15p0.log
> build directory:
> /Applications/sage/local/var/tmp/sage/build/giac-1.9.0.15p0
>
> The log file is attached.
>
> In the log it seems to me that the error comes from the installation of
> pari. But Homebrew says that pari 2.15.0 was previously successfully
> installed.
>

I think you forgot the attachment?

Regards,
Jan

-- 
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/CAAg%3Dp_2hHg1O-k-r4qy%2BSjmHxebFW_ETqSyKO%2B_jNkE0kDGV%3DA%40mail.gmail.com.


[sage-devel] Error building sage-9.7 in macOS Monterey with package giac-1.9.0.15p0

2022-09-29 Thread Sette Diop
Hi:

I am building sage-9.7 on macOS 12.6 (Monterey) and run through this error:

Error building Sage.

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

package: giac-1.9.0.15p0
last build time: Sep 29 10:49
log file:/Applications/sage/logs/pkgs/giac-1.9.0.15p0.log
build directory: /Applications/sage/local/var/tmp/sage/build/giac-1.9.0.15p0

The log file is attached.

In the log it seems to me that the error comes from the installation of pari. 
But Homebrew says that pari 2.15.0 was previously successfully installed.

Any help is welcome!

Best,
Diop

-- 
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/D8B432C9-749F-4831-B96D-4536B6A7768F%40gmail.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-25 Thread Lucas Tan
Thanks all. I will simply leave the error unsolved. Thank you for your 
time. 

Sincerely, 
Lucas

On Monday, 25 July 2022 at 04:17:48 UTC+8 John H Palmieri wrote:

> I don't have any insights on how to fix this, but the error doesn't looks 
> particularly specific to the documentation:
>
> Traceback (most recent call last): File "sage/libs/singular/function.pyx", 
> line 1814
> ...
> NameError: Singular kernel function 'freeAlgebra' is not defined
>
>
> On Sunday, July 24, 2022 at 3:32:04 AM UTC-7 dim...@gmail.com wrote:
>
>>
>>
>> On Sun, 24 Jul 2022, 12:24 Lucas Tan,  wrote:
>>
>>> Hi Dima, 
>>>
>>> Thanks. Sage can be started. 
>>> Is there no way to resolve or complete the build? 
>>>
>>
>> not sure if it ever reliably worked on Cygwin, cf e.g. 
>> https://trac.sagemath.org/ticket/25089
>>
>> Given that Cygwin isn't really supported by CPython, it's hard to expect 
>> that sphinx (the tool behind doc building) is tested and debugged there.
>>
>> That's why I pointed you to WSL as a preferred solution.
>>
>>
>>> Sincerely, 
>>> Lucas
>>>
>>> On Sunday, 24 July 2022 at 17:49:08 UTC+8 dim...@gmail.com wrote:
>>>
 It could be something obscure, Cygwin only.
 Can you start Sage, can you run tests via
 ./sage -t ?

 On Sun, 24 Jul 2022, 11:40 Lucas Tan,  wrote:

>
> Yes,I tried a few times. Each time I tried, I always run "make 
> doc-clean doc-uninstall" first. 
> On Sunday, 24 July 2022 at 15:10:09 UTC+8 dim...@gmail.com wrote:
>
>> Did you try clearing the docs?
>>
>>make doc-clean
>>
>> as recommended by the builder,
>>
>> and re-running make ?
>>
>> On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:
>>
>>> Hi Dima and Matthias, 
>>>
>>> The build has failed again. I have attached the relevant logs. 
>>> Thank you. 
>>>
>>>
>>> On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:
>>>
 yes

 On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:

> There is both "singular" and "singular-devel", should I uninstall 
> both?
>
> Sincerely, 
> Lucas
>
> On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:
>
>>
>>
>> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  
>> wrote:
>>
>>> Do I run by "make singular-clean"?
>>>
>>
>> no, no, I am talking about Cygwin package Singular. You'd need to 
>> use apt-cyg or whatever the Cygwin package manager is called.
>>
>>
>>> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com 
>>> wrote:
>>>
 Could you uninstall Cygwin's Singular package (which is too old 
 to be used by Sage, but can still conflict with Sage's Singular)

 and run

  make

 again?

 On Fri, 22 Jul 2022, 02:11 Lucas Tan,  
 wrote:

> Sure, thanks Dima.
>
>
>
> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com 
> wrote:
>
>> your log appears to show that Singular was not built 
>> correctly.
>> Can you look at logs/pkg/singular*.log,
>> or just post it here?
>>
>>
>> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  
>> wrote:
>>
>>> Hi Matthias, 
>>>
>>> I restarted the installation from scratch and verified that 
>>> python3 has been accepted. This issue has been resolved, thank 
>>> you. 
>>> After running "make" for 10+  hours, a new error has 
>>> occurred. I apologize for troubling you once more. 
>>>
>>> The process [sagemath_doc_html-none] could not be completed. 
>>> I have attached the relevant logs files below. 
>>> As recommended by the error message, I ran the command "make 
>>> doc-clean doc-uninstall" before trying "make" again. After 3 
>>> tries, the 
>>> issue remains persistent. 
>>>
>>> Thank you very, very much for your assistance. 
>>>
>>> Sincerely, 
>>> Lucas
>>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe 
>>> wrote:
>>>
 By reading the configure messages

 On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 
 lucas@gmail.com wrote:

> How do I verify that Cygwin python3 is accepted?
>
> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias 
> Koeppe wrote:
>
>> 

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-24 Thread John H Palmieri
I don't have any insights on how to fix this, but the error doesn't looks 
particularly specific to the documentation:

Traceback (most recent call last): File "sage/libs/singular/function.pyx", 
line 1814
...
NameError: Singular kernel function 'freeAlgebra' is not defined


On Sunday, July 24, 2022 at 3:32:04 AM UTC-7 dim...@gmail.com wrote:

>
>
> On Sun, 24 Jul 2022, 12:24 Lucas Tan,  wrote:
>
>> Hi Dima, 
>>
>> Thanks. Sage can be started. 
>> Is there no way to resolve or complete the build? 
>>
>
> not sure if it ever reliably worked on Cygwin, cf e.g. 
> https://trac.sagemath.org/ticket/25089
>
> Given that Cygwin isn't really supported by CPython, it's hard to expect 
> that sphinx (the tool behind doc building) is tested and debugged there.
>
> That's why I pointed you to WSL as a preferred solution.
>
>
>> Sincerely, 
>> Lucas
>>
>> On Sunday, 24 July 2022 at 17:49:08 UTC+8 dim...@gmail.com wrote:
>>
>>> It could be something obscure, Cygwin only.
>>> Can you start Sage, can you run tests via
>>> ./sage -t ?
>>>
>>> On Sun, 24 Jul 2022, 11:40 Lucas Tan,  wrote:
>>>

 Yes,I tried a few times. Each time I tried, I always run "make 
 doc-clean doc-uninstall" first. 
 On Sunday, 24 July 2022 at 15:10:09 UTC+8 dim...@gmail.com wrote:

> Did you try clearing the docs?
>
>make doc-clean
>
> as recommended by the builder,
>
> and re-running make ?
>
> On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:
>
>> Hi Dima and Matthias, 
>>
>> The build has failed again. I have attached the relevant logs. 
>> Thank you. 
>>
>>
>> On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:
>>
>>> yes
>>>
>>> On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:
>>>
 There is both "singular" and "singular-devel", should I uninstall 
 both?

 Sincerely, 
 Lucas

 On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:

>
>
> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:
>
>> Do I run by "make singular-clean"?
>>
>
> no, no, I am talking about Cygwin package Singular. You'd need to 
> use apt-cyg or whatever the Cygwin package manager is called.
>
>
>> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>>
>>> Could you uninstall Cygwin's Singular package (which is too old 
>>> to be used by Sage, but can still conflict with Sage's Singular)
>>>
>>> and run
>>>
>>>  make
>>>
>>> again?
>>>
>>> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  
>>> wrote:
>>>
 Sure, thanks Dima.



 On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com 
 wrote:

> your log appears to show that Singular was not built correctly.
> Can you look at logs/pkg/singular*.log,
> or just post it here?
>
>
> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  
> wrote:
>
>> Hi Matthias, 
>>
>> I restarted the installation from scratch and verified that 
>> python3 has been accepted. This issue has been resolved, thank 
>> you. 
>> After running "make" for 10+  hours, a new error has 
>> occurred. I apologize for troubling you once more. 
>>
>> The process [sagemath_doc_html-none] could not be completed. 
>> I have attached the relevant logs files below. 
>> As recommended by the error message, I ran the command "make 
>> doc-clean doc-uninstall" before trying "make" again. After 3 
>> tries, the 
>> issue remains persistent. 
>>
>> Thank you very, very much for your assistance. 
>>
>> Sincerely, 
>> Lucas
>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe 
>> wrote:
>>
>>> By reading the configure messages
>>>
>>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 
>>> lucas@gmail.com wrote:
>>>
 How do I verify that Cygwin python3 is accepted?

 On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe 
 wrote:

> No, these system packages need to be installed. Otherwise 
> you won't get Cygwin's python package accepted.
>
> I recommend to start from scratch. Run configure, read 
> what it recommends to install via Cygwin, do this 
> installation, then run 
> configure again.

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-24 Thread Dima Pasechnik
On Sun, 24 Jul 2022, 12:24 Lucas Tan,  wrote:

> Hi Dima,
>
> Thanks. Sage can be started.
> Is there no way to resolve or complete the build?
>

not sure if it ever reliably worked on Cygwin, cf e.g.
https://trac.sagemath.org/ticket/25089

Given that Cygwin isn't really supported by CPython, it's hard to expect
that sphinx (the tool behind doc building) is tested and debugged there.

That's why I pointed you to WSL as a preferred solution.


> Sincerely,
> Lucas
>
> On Sunday, 24 July 2022 at 17:49:08 UTC+8 dim...@gmail.com wrote:
>
>> It could be something obscure, Cygwin only.
>> Can you start Sage, can you run tests via
>> ./sage -t ?
>>
>> On Sun, 24 Jul 2022, 11:40 Lucas Tan,  wrote:
>>
>>>
>>> Yes,I tried a few times. Each time I tried, I always run "make doc-clean
>>> doc-uninstall" first.
>>> On Sunday, 24 July 2022 at 15:10:09 UTC+8 dim...@gmail.com wrote:
>>>
 Did you try clearing the docs?

make doc-clean

 as recommended by the builder,

 and re-running make ?

 On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:

> Hi Dima and Matthias,
>
> The build has failed again. I have attached the relevant logs.
> Thank you.
>
>
> On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:
>
>> yes
>>
>> On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:
>>
>>> There is both "singular" and "singular-devel", should I uninstall
>>> both?
>>>
>>> Sincerely,
>>> Lucas
>>>
>>> On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:
>>>


 On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:

> Do I run by "make singular-clean"?
>

 no, no, I am talking about Cygwin package Singular. You'd need to
 use apt-cyg or whatever the Cygwin package manager is called.


> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>
>> Could you uninstall Cygwin's Singular package (which is too old
>> to be used by Sage, but can still conflict with Sage's Singular)
>>
>> and run
>>
>>  make
>>
>> again?
>>
>> On Fri, 22 Jul 2022, 02:11 Lucas Tan, 
>> wrote:
>>
>>> Sure, thanks Dima.
>>>
>>>
>>>
>>> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com
>>> wrote:
>>>
 your log appears to show that Singular was not built correctly.
 Can you look at logs/pkg/singular*.log,
 or just post it here?


 On Fri, 22 Jul 2022, 01:39 Lucas Tan, 
 wrote:

> Hi Matthias,
>
> I restarted the installation from scratch and verified that
> python3 has been accepted. This issue has been resolved, thank 
> you.
> After running "make" for 10+  hours, a new error has occurred.
> I apologize for troubling you once more.
>
> The process [sagemath_doc_html-none] could not be completed. I
> have attached the relevant logs files below.
> As recommended by the error message, I ran the command "make
> doc-clean doc-uninstall" before trying "make" again. After 3 
> tries, the
> issue remains persistent.
>
> Thank you very, very much for your assistance.
>
> Sincerely,
> Lucas
> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe
> wrote:
>
>> By reading the configure messages
>>
>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7
>> lucas@gmail.com wrote:
>>
>>> How do I verify that Cygwin python3 is accepted?
>>>
>>> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe
>>> wrote:
>>>
 No, these system packages need to be installed. Otherwise
 you won't get Cygwin's python package accepted.

 I recommend to start from scratch. Run configure, read what
 it recommends to install via Cygwin, do this installation, 
 then run
 configure again.
 Before running "make", verify that it accepts the Cygwin
 python3.


 On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7
 lucas@gmail.com wrote:

> Hi Matthias,
> Yes, they are. I have just uninstalled them via Cygwin
> setup. Should I uninstall libffi as well?
>
> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias
> Ko

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-24 Thread Lucas Tan
Hi Dima, 

Thanks. Sage can be started. 
Is there no way to resolve or complete the build? 

Sincerely, 
Lucas

On Sunday, 24 July 2022 at 17:49:08 UTC+8 dim...@gmail.com wrote:

> It could be something obscure, Cygwin only.
> Can you start Sage, can you run tests via
> ./sage -t ?
>
> On Sun, 24 Jul 2022, 11:40 Lucas Tan,  wrote:
>
>>
>> Yes,I tried a few times. Each time I tried, I always run "make doc-clean 
>> doc-uninstall" first. 
>> On Sunday, 24 July 2022 at 15:10:09 UTC+8 dim...@gmail.com wrote:
>>
>>> Did you try clearing the docs?
>>>
>>>make doc-clean
>>>
>>> as recommended by the builder,
>>>
>>> and re-running make ?
>>>
>>> On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:
>>>
 Hi Dima and Matthias, 

 The build has failed again. I have attached the relevant logs. 
 Thank you. 


 On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:

> yes
>
> On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:
>
>> There is both "singular" and "singular-devel", should I uninstall 
>> both?
>>
>> Sincerely, 
>> Lucas
>>
>> On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:
>>
>>>
>>>
>>> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:
>>>
 Do I run by "make singular-clean"?

>>>
>>> no, no, I am talking about Cygwin package Singular. You'd need to 
>>> use apt-cyg or whatever the Cygwin package manager is called.
>>>
>>>
 On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:

> Could you uninstall Cygwin's Singular package (which is too old to 
> be used by Sage, but can still conflict with Sage's Singular)
>
> and run
>
>  make
>
> again?
>
> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:
>
>> Sure, thanks Dima.
>>
>>
>>
>> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>>
>>> your log appears to show that Singular was not built correctly.
>>> Can you look at logs/pkg/singular*.log,
>>> or just post it here?
>>>
>>>
>>> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  
>>> wrote:
>>>
 Hi Matthias, 

 I restarted the installation from scratch and verified that 
 python3 has been accepted. This issue has been resolved, thank 
 you. 
 After running "make" for 10+  hours, a new error has occurred. 
 I apologize for troubling you once more. 

 The process [sagemath_doc_html-none] could not be completed. I 
 have attached the relevant logs files below. 
 As recommended by the error message, I ran the command "make 
 doc-clean doc-uninstall" before trying "make" again. After 3 
 tries, the 
 issue remains persistent. 

 Thank you very, very much for your assistance. 

 Sincerely, 
 Lucas
 On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe 
 wrote:

> By reading the configure messages
>
> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 
> lucas@gmail.com wrote:
>
>> How do I verify that Cygwin python3 is accepted?
>>
>> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe 
>> wrote:
>>
>>> No, these system packages need to be installed. Otherwise 
>>> you won't get Cygwin's python package accepted.
>>>
>>> I recommend to start from scratch. Run configure, read what 
>>> it recommends to install via Cygwin, do this installation, then 
>>> run 
>>> configure again.
>>> Before running "make", verify that it accepts the Cygwin 
>>> python3.
>>>
>>>
>>> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 
>>> lucas@gmail.com wrote:
>>>
 Hi Matthias, 
 Yes, they are. I have just uninstalled them via Cygwin 
 setup. Should I uninstall libffi as well?

 On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe 
 wrote:

> Are these cygwin packages installed?  bzip2 libbz2-devel 
> xz liblzma-devel 
>
> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 
> lucas@gmail.com wrote:
>
>> Apologies, my log files are here
>>
>>
>>
>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan 
>

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-24 Thread Dima Pasechnik
It could be something obscure, Cygwin only.
Can you start Sage, can you run tests via
./sage -t ?

On Sun, 24 Jul 2022, 11:40 Lucas Tan,  wrote:

>
> Yes,I tried a few times. Each time I tried, I always run "make doc-clean
> doc-uninstall" first.
> On Sunday, 24 July 2022 at 15:10:09 UTC+8 dim...@gmail.com wrote:
>
>> Did you try clearing the docs?
>>
>>make doc-clean
>>
>> as recommended by the builder,
>>
>> and re-running make ?
>>
>> On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:
>>
>>> Hi Dima and Matthias,
>>>
>>> The build has failed again. I have attached the relevant logs.
>>> Thank you.
>>>
>>>
>>> On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:
>>>
 yes

 On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:

> There is both "singular" and "singular-devel", should I uninstall both?
>
> Sincerely,
> Lucas
>
> On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:
>
>>
>>
>> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:
>>
>>> Do I run by "make singular-clean"?
>>>
>>
>> no, no, I am talking about Cygwin package Singular. You'd need to use
>> apt-cyg or whatever the Cygwin package manager is called.
>>
>>
>>> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>>>
 Could you uninstall Cygwin's Singular package (which is too old to
 be used by Sage, but can still conflict with Sage's Singular)

 and run

  make

 again?

 On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:

> Sure, thanks Dima.
>
>
>
> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>
>> your log appears to show that Singular was not built correctly.
>> Can you look at logs/pkg/singular*.log,
>> or just post it here?
>>
>>
>> On Fri, 22 Jul 2022, 01:39 Lucas Tan, 
>> wrote:
>>
>>> Hi Matthias,
>>>
>>> I restarted the installation from scratch and verified that
>>> python3 has been accepted. This issue has been resolved, thank you.
>>> After running "make" for 10+  hours, a new error has occurred. I
>>> apologize for troubling you once more.
>>>
>>> The process [sagemath_doc_html-none] could not be completed. I
>>> have attached the relevant logs files below.
>>> As recommended by the error message, I ran the command "make
>>> doc-clean doc-uninstall" before trying "make" again. After 3 tries, 
>>> the
>>> issue remains persistent.
>>>
>>> Thank you very, very much for your assistance.
>>>
>>> Sincerely,
>>> Lucas
>>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe
>>> wrote:
>>>
 By reading the configure messages

 On Thursday, July 21, 2022 at 12:37:08 AM UTC-7
 lucas@gmail.com wrote:

> How do I verify that Cygwin python3 is accepted?
>
> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe
> wrote:
>
>> No, these system packages need to be installed. Otherwise you
>> won't get Cygwin's python package accepted.
>>
>> I recommend to start from scratch. Run configure, read what
>> it recommends to install via Cygwin, do this installation, then 
>> run
>> configure again.
>> Before running "make", verify that it accepts the Cygwin
>> python3.
>>
>>
>> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7
>> lucas@gmail.com wrote:
>>
>>> Hi Matthias,
>>> Yes, they are. I have just uninstalled them via Cygwin
>>> setup. Should I uninstall libffi as well?
>>>
>>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe
>>> wrote:
>>>
 Are these cygwin packages installed?  bzip2 libbz2-devel xz
 liblzma-devel

 On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7
 lucas@gmail.com wrote:

> Apologies, my log files are here
>
>
>
> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan
> wrote:
>
>> Hi Matthias,
>>
>> I ran  "make bzip2-clean liblzma-clean libffi-clean
>> xz-clean" twice to ensure that the files are removed.
>> I check for the following message: "No legacy uninstaller
>> found for 'xz'; nothing to do", for all files.
>>

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-24 Thread Lucas Tan

Yes,I tried a few times. Each time I tried, I always run "make doc-clean 
doc-uninstall" first. 
On Sunday, 24 July 2022 at 15:10:09 UTC+8 dim...@gmail.com wrote:

> Did you try clearing the docs?
>
>make doc-clean
>
> as recommended by the builder,
>
> and re-running make ?
>
> On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:
>
>> Hi Dima and Matthias, 
>>
>> The build has failed again. I have attached the relevant logs. 
>> Thank you. 
>>
>>
>> On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:
>>
>>> yes
>>>
>>> On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:
>>>
 There is both "singular" and "singular-devel", should I uninstall both?

 Sincerely, 
 Lucas

 On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:

>
>
> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:
>
>> Do I run by "make singular-clean"?
>>
>
> no, no, I am talking about Cygwin package Singular. You'd need to use 
> apt-cyg or whatever the Cygwin package manager is called.
>
>
>> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>>
>>> Could you uninstall Cygwin's Singular package (which is too old to 
>>> be used by Sage, but can still conflict with Sage's Singular)
>>>
>>> and run
>>>
>>>  make
>>>
>>> again?
>>>
>>> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:
>>>
 Sure, thanks Dima.



 On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:

> your log appears to show that Singular was not built correctly.
> Can you look at logs/pkg/singular*.log,
> or just post it here?
>
>
> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:
>
>> Hi Matthias, 
>>
>> I restarted the installation from scratch and verified that 
>> python3 has been accepted. This issue has been resolved, thank you. 
>> After running "make" for 10+  hours, a new error has occurred. I 
>> apologize for troubling you once more. 
>>
>> The process [sagemath_doc_html-none] could not be completed. I 
>> have attached the relevant logs files below. 
>> As recommended by the error message, I ran the command "make 
>> doc-clean doc-uninstall" before trying "make" again. After 3 tries, 
>> the 
>> issue remains persistent. 
>>
>> Thank you very, very much for your assistance. 
>>
>> Sincerely, 
>> Lucas
>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>>
>>> By reading the configure messages
>>>
>>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 
>>> lucas@gmail.com wrote:
>>>
 How do I verify that Cygwin python3 is accepted?

 On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe 
 wrote:

> No, these system packages need to be installed. Otherwise you 
> won't get Cygwin's python package accepted.
>
> I recommend to start from scratch. Run configure, read what it 
> recommends to install via Cygwin, do this installation, then run 
> configure 
> again.
> Before running "make", verify that it accepts the Cygwin 
> python3.
>
>
> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 
> lucas@gmail.com wrote:
>
>> Hi Matthias, 
>> Yes, they are. I have just uninstalled them via Cygwin setup. 
>> Should I uninstall libffi as well?
>>
>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe 
>> wrote:
>>
>>> Are these cygwin packages installed?  bzip2 libbz2-devel xz 
>>> liblzma-devel 
>>>
>>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 
>>> lucas@gmail.com wrote:
>>>
 Apologies, my log files are here



 On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:

> Hi Matthias, 
>
> I ran  "make bzip2-clean liblzma-clean libffi-clean 
> xz-clean" twice to ensure that the files are removed. 
> I check for the following message: "No legacy uninstaller 
> found for 'xz'; nothing to do", for all files. 
> I have also ensured that I have python3.9 installed with 
> "python3 --version"
> After running the above, I run "./configure" once more as 
> suggested by John H Palmieri above. 
>
> I'm not sure if this

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-24 Thread Dima Pasechnik
Did you try clearing the docs?

   make doc-clean

as recommended by the builder,

and re-running make ?

On Sun, 24 Jul 2022, 03:09 Lucas Tan,  wrote:

> Hi Dima and Matthias,
>
> The build has failed again. I have attached the relevant logs.
> Thank you.
>
>
> On Friday, 22 July 2022 at 18:34:44 UTC+8 dim...@gmail.com wrote:
>
>> yes
>>
>> On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:
>>
>>> There is both "singular" and "singular-devel", should I uninstall both?
>>>
>>> Sincerely,
>>> Lucas
>>>
>>> On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:
>>>


 On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:

> Do I run by "make singular-clean"?
>

 no, no, I am talking about Cygwin package Singular. You'd need to use
 apt-cyg or whatever the Cygwin package manager is called.


> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>
>> Could you uninstall Cygwin's Singular package (which is too old to be
>> used by Sage, but can still conflict with Sage's Singular)
>>
>> and run
>>
>>  make
>>
>> again?
>>
>> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:
>>
>>> Sure, thanks Dima.
>>>
>>>
>>>
>>> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>>>
 your log appears to show that Singular was not built correctly.
 Can you look at logs/pkg/singular*.log,
 or just post it here?


 On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:

> Hi Matthias,
>
> I restarted the installation from scratch and verified that
> python3 has been accepted. This issue has been resolved, thank you.
> After running "make" for 10+  hours, a new error has occurred. I
> apologize for troubling you once more.
>
> The process [sagemath_doc_html-none] could not be completed. I
> have attached the relevant logs files below.
> As recommended by the error message, I ran the command "make
> doc-clean doc-uninstall" before trying "make" again. After 3 tries, 
> the
> issue remains persistent.
>
> Thank you very, very much for your assistance.
>
> Sincerely,
> Lucas
> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>
>> By reading the configure messages
>>
>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7
>> lucas@gmail.com wrote:
>>
>>> How do I verify that Cygwin python3 is accepted?
>>>
>>> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe
>>> wrote:
>>>
 No, these system packages need to be installed. Otherwise you
 won't get Cygwin's python package accepted.

 I recommend to start from scratch. Run configure, read what it
 recommends to install via Cygwin, do this installation, then run 
 configure
 again.
 Before running "make", verify that it accepts the Cygwin
 python3.


 On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7
 lucas@gmail.com wrote:

> Hi Matthias,
> Yes, they are. I have just uninstalled them via Cygwin setup.
> Should I uninstall libffi as well?
>
> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe
> wrote:
>
>> Are these cygwin packages installed?  bzip2 libbz2-devel xz
>> liblzma-devel
>>
>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7
>> lucas@gmail.com wrote:
>>
>>> Apologies, my log files are here
>>>
>>>
>>>
>>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>>>
 Hi Matthias,

 I ran  "make bzip2-clean liblzma-clean libffi-clean
 xz-clean" twice to ensure that the files are removed.
 I check for the following message: "No legacy uninstaller
 found for 'xz'; nothing to do", for all files.
 I have also ensured that I have python3.9 installed with
 "python3 --version"
 After running the above, I run "./configure" once more as
 suggested by John H Palmieri above.

 I'm not sure if this is relevant, but I noticed these
 messages when running "make":
 *(first line of xz)*
 [xz-5.2.5] Using cached file
 /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
 [xz-5.2.5] xz-5.2.5
 [xz-5.2.5]
 ===

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-22 Thread Dima Pasechnik
yes

On Fri, 22 Jul 2022, 11:32 Lucas Tan,  wrote:

> There is both "singular" and "singular-devel", should I uninstall both?
>
> Sincerely,
> Lucas
>
> On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:
>
>>
>>
>> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:
>>
>>> Do I run by "make singular-clean"?
>>>
>>
>> no, no, I am talking about Cygwin package Singular. You'd need to use
>> apt-cyg or whatever the Cygwin package manager is called.
>>
>>
>>> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>>>
 Could you uninstall Cygwin's Singular package (which is too old to be
 used by Sage, but can still conflict with Sage's Singular)

 and run

  make

 again?

 On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:

> Sure, thanks Dima.
>
>
>
> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>
>> your log appears to show that Singular was not built correctly.
>> Can you look at logs/pkg/singular*.log,
>> or just post it here?
>>
>>
>> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:
>>
>>> Hi Matthias,
>>>
>>> I restarted the installation from scratch and verified that python3
>>> has been accepted. This issue has been resolved, thank you.
>>> After running "make" for 10+  hours, a new error has occurred. I
>>> apologize for troubling you once more.
>>>
>>> The process [sagemath_doc_html-none] could not be completed. I have
>>> attached the relevant logs files below.
>>> As recommended by the error message, I ran the command "make
>>> doc-clean doc-uninstall" before trying "make" again. After 3 tries, the
>>> issue remains persistent.
>>>
>>> Thank you very, very much for your assistance.
>>>
>>> Sincerely,
>>> Lucas
>>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>>>
 By reading the configure messages

 On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com
 wrote:

> How do I verify that Cygwin python3 is accepted?
>
> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>
>> No, these system packages need to be installed. Otherwise you
>> won't get Cygwin's python package accepted.
>>
>> I recommend to start from scratch. Run configure, read what it
>> recommends to install via Cygwin, do this installation, then run 
>> configure
>> again.
>> Before running "make", verify that it accepts the Cygwin python3.
>>
>>
>> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7
>> lucas@gmail.com wrote:
>>
>>> Hi Matthias,
>>> Yes, they are. I have just uninstalled them via Cygwin setup.
>>> Should I uninstall libffi as well?
>>>
>>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe
>>> wrote:
>>>
 Are these cygwin packages installed?  bzip2 libbz2-devel xz
 liblzma-devel

 On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7
 lucas@gmail.com wrote:

> Apologies, my log files are here
>
>
>
> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>
>> Hi Matthias,
>>
>> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean"
>> twice to ensure that the files are removed.
>> I check for the following message: "No legacy uninstaller
>> found for 'xz'; nothing to do", for all files.
>> I have also ensured that I have python3.9 installed with
>> "python3 --version"
>> After running the above, I run "./configure" once more as
>> suggested by John H Palmieri above.
>>
>> I'm not sure if this is relevant, but I noticed these
>> messages when running "make":
>> *(first line of xz)*
>> [xz-5.2.5] Using cached file
>> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
>> [xz-5.2.5] xz-5.2.5
>> [xz-5.2.5]
>> 
>> [xz-5.2.5] Setting up build directory for xz-5.2.5
>> [xz-5.2.5] Finished extraction
>> *(similarly for libffi, the cached file is used)*
>>
>> *(first line of python3)*
>> [python3-3.10.3] Using cached file
>> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
>> [python3-3.10.3] python3-3.10.3
>> [python3-3.10.3]
>> 
>> [python3-3.10.3] Setting up build directory for python3-3.10.3
>> [python3-3.

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-22 Thread Lucas Tan
There is both "singular" and "singular-devel", should I uninstall both?

Sincerely, 
Lucas

On Friday, 22 July 2022 at 17:53:25 UTC+8 dim...@gmail.com wrote:

>
>
> On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:
>
>> Do I run by "make singular-clean"?
>>
>
> no, no, I am talking about Cygwin package Singular. You'd need to use 
> apt-cyg or whatever the Cygwin package manager is called.
>
>
>> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>>
>>> Could you uninstall Cygwin's Singular package (which is too old to be 
>>> used by Sage, but can still conflict with Sage's Singular)
>>>
>>> and run
>>>
>>>  make
>>>
>>> again?
>>>
>>> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:
>>>
 Sure, thanks Dima.



 On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:

> your log appears to show that Singular was not built correctly.
> Can you look at logs/pkg/singular*.log,
> or just post it here?
>
>
> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:
>
>> Hi Matthias, 
>>
>> I restarted the installation from scratch and verified that python3 
>> has been accepted. This issue has been resolved, thank you. 
>> After running "make" for 10+  hours, a new error has occurred. I 
>> apologize for troubling you once more. 
>>
>> The process [sagemath_doc_html-none] could not be completed. I have 
>> attached the relevant logs files below. 
>> As recommended by the error message, I ran the command "make 
>> doc-clean doc-uninstall" before trying "make" again. After 3 tries, the 
>> issue remains persistent. 
>>
>> Thank you very, very much for your assistance. 
>>
>> Sincerely, 
>> Lucas
>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>>
>>> By reading the configure messages
>>>
>>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com 
>>> wrote:
>>>
 How do I verify that Cygwin python3 is accepted?

 On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:

> No, these system packages need to be installed. Otherwise you 
> won't get Cygwin's python package accepted.
>
> I recommend to start from scratch. Run configure, read what it 
> recommends to install via Cygwin, do this installation, then run 
> configure 
> again.
> Before running "make", verify that it accepts the Cygwin python3.
>
>
> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 
> lucas@gmail.com wrote:
>
>> Hi Matthias, 
>> Yes, they are. I have just uninstalled them via Cygwin setup. 
>> Should I uninstall libffi as well?
>>
>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>>
>>> Are these cygwin packages installed?  bzip2 libbz2-devel xz 
>>> liblzma-devel 
>>>
>>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 
>>> lucas@gmail.com wrote:
>>>
 Apologies, my log files are here



 On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:

> Hi Matthias, 
>
> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" 
> twice to ensure that the files are removed. 
> I check for the following message: "No legacy uninstaller 
> found for 'xz'; nothing to do", for all files. 
> I have also ensured that I have python3.9 installed with 
> "python3 --version"
> After running the above, I run "./configure" once more as 
> suggested by John H Palmieri above. 
>
> I'm not sure if this is relevant, but I noticed these messages 
> when running "make": 
> *(first line of xz)* 
> [xz-5.2.5] Using cached file 
> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
> [xz-5.2.5] xz-5.2.5
> [xz-5.2.5] 
> [xz-5.2.5] Setting up build directory for xz-5.2.5
> [xz-5.2.5] Finished extraction
> *(similarly for libffi, the cached file is used)*
>
> *(first line of python3)*
> [python3-3.10.3] Using cached file 
> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
> [python3-3.10.3] python3-3.10.3
> [python3-3.10.3] 
> 
> [python3-3.10.3] Setting up build directory for python3-3.10.3
> [python3-3.10.3] Finished extraction
> *(shortly later...)*
> [python3-3.10.3] Thread model: posix
> [python3-3.10.3] Supported LTO compression algorith

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-22 Thread Dima Pasechnik
On Fri, 22 Jul 2022, 10:46 Lucas Tan,  wrote:

> Do I run by "make singular-clean"?
>

no, no, I am talking about Cygwin package Singular. You'd need to use
apt-cyg or whatever the Cygwin package manager is called.


> On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:
>
>> Could you uninstall Cygwin's Singular package (which is too old to be
>> used by Sage, but can still conflict with Sage's Singular)
>>
>> and run
>>
>>  make
>>
>> again?
>>
>> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:
>>
>>> Sure, thanks Dima.
>>>
>>>
>>>
>>> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>>>
 your log appears to show that Singular was not built correctly.
 Can you look at logs/pkg/singular*.log,
 or just post it here?


 On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:

> Hi Matthias,
>
> I restarted the installation from scratch and verified that python3
> has been accepted. This issue has been resolved, thank you.
> After running "make" for 10+  hours, a new error has occurred. I
> apologize for troubling you once more.
>
> The process [sagemath_doc_html-none] could not be completed. I have
> attached the relevant logs files below.
> As recommended by the error message, I ran the command "make doc-clean
> doc-uninstall" before trying "make" again. After 3 tries, the issue 
> remains
> persistent.
>
> Thank you very, very much for your assistance.
>
> Sincerely,
> Lucas
> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>
>> By reading the configure messages
>>
>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com
>> wrote:
>>
>>> How do I verify that Cygwin python3 is accepted?
>>>
>>> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>>>
 No, these system packages need to be installed. Otherwise you won't
 get Cygwin's python package accepted.

 I recommend to start from scratch. Run configure, read what it
 recommends to install via Cygwin, do this installation, then run 
 configure
 again.
 Before running "make", verify that it accepts the Cygwin python3.


 On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7
 lucas@gmail.com wrote:

> Hi Matthias,
> Yes, they are. I have just uninstalled them via Cygwin setup.
> Should I uninstall libffi as well?
>
> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>
>> Are these cygwin packages installed?  bzip2 libbz2-devel xz
>> liblzma-devel
>>
>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7
>> lucas@gmail.com wrote:
>>
>>> Apologies, my log files are here
>>>
>>>
>>>
>>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>>>
 Hi Matthias,

 I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean"
 twice to ensure that the files are removed.
 I check for the following message: "No legacy uninstaller found
 for 'xz'; nothing to do", for all files.
 I have also ensured that I have python3.9 installed with
 "python3 --version"
 After running the above, I run "./configure" once more as
 suggested by John H Palmieri above.

 I'm not sure if this is relevant, but I noticed these messages
 when running "make":
 *(first line of xz)*
 [xz-5.2.5] Using cached file
 /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
 [xz-5.2.5] xz-5.2.5
 [xz-5.2.5] 
 [xz-5.2.5] Setting up build directory for xz-5.2.5
 [xz-5.2.5] Finished extraction
 *(similarly for libffi, the cached file is used)*

 *(first line of python3)*
 [python3-3.10.3] Using cached file
 /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
 [python3-3.10.3] python3-3.10.3
 [python3-3.10.3]
 
 [python3-3.10.3] Setting up build directory for python3-3.10.3
 [python3-3.10.3] Finished extraction
 *(shortly later...)*
 [python3-3.10.3] Thread model: posix
 [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
 [python3-3.10.3] gcc version 11.3.0 (GCC)
 [python3-3.10.3]
 
 [python3-3.10.3] Package 'python3' is currently not installed
 [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
>>>

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-22 Thread Lucas Tan
Do I run by "make singular-clean"?

On Friday, 22 July 2022 at 17:19:34 UTC+8 dim...@gmail.com wrote:

> Could you uninstall Cygwin's Singular package (which is too old to be used 
> by Sage, but can still conflict with Sage's Singular)
>
> and run
>
>  make
>
> again?
>
> On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:
>
>> Sure, thanks Dima.
>>
>>
>>
>> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>>
>>> your log appears to show that Singular was not built correctly.
>>> Can you look at logs/pkg/singular*.log,
>>> or just post it here?
>>>
>>>
>>> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:
>>>
 Hi Matthias, 

 I restarted the installation from scratch and verified that python3 has 
 been accepted. This issue has been resolved, thank you. 
 After running "make" for 10+  hours, a new error has occurred. I 
 apologize for troubling you once more. 

 The process [sagemath_doc_html-none] could not be completed. I have 
 attached the relevant logs files below. 
 As recommended by the error message, I ran the command "make doc-clean 
 doc-uninstall" before trying "make" again. After 3 tries, the issue 
 remains 
 persistent. 

 Thank you very, very much for your assistance. 

 Sincerely, 
 Lucas
 On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:

> By reading the configure messages
>
> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com 
> wrote:
>
>> How do I verify that Cygwin python3 is accepted?
>>
>> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>>
>>> No, these system packages need to be installed. Otherwise you won't 
>>> get Cygwin's python package accepted.
>>>
>>> I recommend to start from scratch. Run configure, read what it 
>>> recommends to install via Cygwin, do this installation, then run 
>>> configure 
>>> again.
>>> Before running "make", verify that it accepts the Cygwin python3.
>>>
>>>
>>> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 lucas@gmail.com 
>>> wrote:
>>>
 Hi Matthias, 
 Yes, they are. I have just uninstalled them via Cygwin setup. 
 Should I uninstall libffi as well?

 On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:

> Are these cygwin packages installed?  bzip2 libbz2-devel xz 
> liblzma-devel 
>
> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 
> lucas@gmail.com wrote:
>
>> Apologies, my log files are here
>>
>>
>>
>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>>
>>> Hi Matthias, 
>>>
>>> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" 
>>> twice to ensure that the files are removed. 
>>> I check for the following message: "No legacy uninstaller found 
>>> for 'xz'; nothing to do", for all files. 
>>> I have also ensured that I have python3.9 installed with 
>>> "python3 --version"
>>> After running the above, I run "./configure" once more as 
>>> suggested by John H Palmieri above. 
>>>
>>> I'm not sure if this is relevant, but I noticed these messages 
>>> when running "make": 
>>> *(first line of xz)* 
>>> [xz-5.2.5] Using cached file 
>>> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
>>> [xz-5.2.5] xz-5.2.5
>>> [xz-5.2.5] 
>>> [xz-5.2.5] Setting up build directory for xz-5.2.5
>>> [xz-5.2.5] Finished extraction
>>> *(similarly for libffi, the cached file is used)*
>>>
>>> *(first line of python3)*
>>> [python3-3.10.3] Using cached file 
>>> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
>>> [python3-3.10.3] python3-3.10.3
>>> [python3-3.10.3] 
>>> 
>>> [python3-3.10.3] Setting up build directory for python3-3.10.3
>>> [python3-3.10.3] Finished extraction
>>> *(shortly later...)*
>>> [python3-3.10.3] Thread model: posix
>>> [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
>>> [python3-3.10.3] gcc version 11.3.0 (GCC)
>>> [python3-3.10.3] 
>>> 
>>> [python3-3.10.3] Package 'python3' is currently not installed
>>> [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
>>> [python3-3.10.3] Cleaning out old python / python3 / python3 
>>> venv binaries
>>> [python3-3.10.3] Configuring python3-3.10.3
>>>
>>> On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:
>>>
 Hi Matthi

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-22 Thread Dima Pasechnik
Could you uninstall Cygwin's Singular package (which is too old to be used
by Sage, but can still conflict with Sage's Singular)

and run

 make

again?

On Fri, 22 Jul 2022, 02:11 Lucas Tan,  wrote:

> Sure, thanks Dima.
>
>
>
> On Friday, 22 July 2022 at 09:09:56 UTC+8 dim...@gmail.com wrote:
>
>> your log appears to show that Singular was not built correctly.
>> Can you look at logs/pkg/singular*.log,
>> or just post it here?
>>
>>
>> On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:
>>
>>> Hi Matthias,
>>>
>>> I restarted the installation from scratch and verified that python3 has
>>> been accepted. This issue has been resolved, thank you.
>>> After running "make" for 10+  hours, a new error has occurred. I
>>> apologize for troubling you once more.
>>>
>>> The process [sagemath_doc_html-none] could not be completed. I have
>>> attached the relevant logs files below.
>>> As recommended by the error message, I ran the command "make doc-clean
>>> doc-uninstall" before trying "make" again. After 3 tries, the issue remains
>>> persistent.
>>>
>>> Thank you very, very much for your assistance.
>>>
>>> Sincerely,
>>> Lucas
>>> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>>>
 By reading the configure messages

 On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com
 wrote:

> How do I verify that Cygwin python3 is accepted?
>
> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>
>> No, these system packages need to be installed. Otherwise you won't
>> get Cygwin's python package accepted.
>>
>> I recommend to start from scratch. Run configure, read what it
>> recommends to install via Cygwin, do this installation, then run 
>> configure
>> again.
>> Before running "make", verify that it accepts the Cygwin python3.
>>
>>
>> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 lucas@gmail.com
>> wrote:
>>
>>> Hi Matthias,
>>> Yes, they are. I have just uninstalled them via Cygwin setup. Should
>>> I uninstall libffi as well?
>>>
>>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>>>
 Are these cygwin packages installed?  bzip2 libbz2-devel xz
 liblzma-devel

 On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7
 lucas@gmail.com wrote:

> Apologies, my log files are here
>
>
>
> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>
>> Hi Matthias,
>>
>> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean"
>> twice to ensure that the files are removed.
>> I check for the following message: "No legacy uninstaller found
>> for 'xz'; nothing to do", for all files.
>> I have also ensured that I have python3.9 installed with "python3
>> --version"
>> After running the above, I run "./configure" once more as
>> suggested by John H Palmieri above.
>>
>> I'm not sure if this is relevant, but I noticed these messages
>> when running "make":
>> *(first line of xz)*
>> [xz-5.2.5] Using cached file
>> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
>> [xz-5.2.5] xz-5.2.5
>> [xz-5.2.5] 
>> [xz-5.2.5] Setting up build directory for xz-5.2.5
>> [xz-5.2.5] Finished extraction
>> *(similarly for libffi, the cached file is used)*
>>
>> *(first line of python3)*
>> [python3-3.10.3] Using cached file
>> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
>> [python3-3.10.3] python3-3.10.3
>> [python3-3.10.3]
>> 
>> [python3-3.10.3] Setting up build directory for python3-3.10.3
>> [python3-3.10.3] Finished extraction
>> *(shortly later...)*
>> [python3-3.10.3] Thread model: posix
>> [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
>> [python3-3.10.3] gcc version 11.3.0 (GCC)
>> [python3-3.10.3]
>> 
>> [python3-3.10.3] Package 'python3' is currently not installed
>> [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
>> [python3-3.10.3] Cleaning out old python / python3 / python3 venv
>> binaries
>> [python3-3.10.3] Configuring python3-3.10.3
>>
>> On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:
>>
>>> Hi Matthias,
>>>
>>> I would believe so.
>>> ```
>>> $ apt-cyg install python39
>>> Package python39 is already installed, skipping
>>>
>>> $ apt-cyg install python3
>>> Package python3 is already installed, skipping
>>

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-21 Thread Dima Pasechnik
your log appears to show that Singular was not built correctly.
Can you look at logs/pkg/singular*.log,
or just post it here?


On Fri, 22 Jul 2022, 01:39 Lucas Tan,  wrote:

> Hi Matthias,
>
> I restarted the installation from scratch and verified that python3 has
> been accepted. This issue has been resolved, thank you.
> After running "make" for 10+  hours, a new error has occurred. I apologize
> for troubling you once more.
>
> The process [sagemath_doc_html-none] could not be completed. I have
> attached the relevant logs files below.
> As recommended by the error message, I ran the command "make doc-clean
> doc-uninstall" before trying "make" again. After 3 tries, the issue remains
> persistent.
>
> Thank you very, very much for your assistance.
>
> Sincerely,
> Lucas
> On Thursday, 21 July 2022 at 15:45:57 UTC+8 Matthias Koeppe wrote:
>
>> By reading the configure messages
>>
>> On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com
>> wrote:
>>
>>> How do I verify that Cygwin python3 is accepted?
>>>
>>> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>>>
 No, these system packages need to be installed. Otherwise you won't get
 Cygwin's python package accepted.

 I recommend to start from scratch. Run configure, read what it
 recommends to install via Cygwin, do this installation, then run configure
 again.
 Before running "make", verify that it accepts the Cygwin python3.


 On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 lucas@gmail.com
 wrote:

> Hi Matthias,
> Yes, they are. I have just uninstalled them via Cygwin setup. Should I
> uninstall libffi as well?
>
> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>
>> Are these cygwin packages installed?  bzip2 libbz2-devel xz
>> liblzma-devel
>>
>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 lucas@gmail.com
>> wrote:
>>
>>> Apologies, my log files are here
>>>
>>>
>>>
>>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>>>
 Hi Matthias,

 I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice
 to ensure that the files are removed.
 I check for the following message: "No legacy uninstaller found for
 'xz'; nothing to do", for all files.
 I have also ensured that I have python3.9 installed with "python3
 --version"
 After running the above, I run "./configure" once more as suggested
 by John H Palmieri above.

 I'm not sure if this is relevant, but I noticed these messages when
 running "make":
 *(first line of xz)*
 [xz-5.2.5] Using cached file
 /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
 [xz-5.2.5] xz-5.2.5
 [xz-5.2.5] 
 [xz-5.2.5] Setting up build directory for xz-5.2.5
 [xz-5.2.5] Finished extraction
 *(similarly for libffi, the cached file is used)*

 *(first line of python3)*
 [python3-3.10.3] Using cached file
 /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
 [python3-3.10.3] python3-3.10.3
 [python3-3.10.3]
 
 [python3-3.10.3] Setting up build directory for python3-3.10.3
 [python3-3.10.3] Finished extraction
 *(shortly later...)*
 [python3-3.10.3] Thread model: posix
 [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
 [python3-3.10.3] gcc version 11.3.0 (GCC)
 [python3-3.10.3]
 
 [python3-3.10.3] Package 'python3' is currently not installed
 [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
 [python3-3.10.3] Cleaning out old python / python3 / python3 venv
 binaries
 [python3-3.10.3] Configuring python3-3.10.3

 On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:

> Hi Matthias,
>
> I would believe so.
> ```
> $ apt-cyg install python39
> Package python39 is already installed, skipping
>
> $ apt-cyg install python3
> Package python3 is already installed, skipping
> ```
> On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:
>
>> Did you install the cygwin python3.9 packages?
>>
>> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7
>> lucas@gmail.com wrote:
>>
>>> Hi Matthias,
>>>
>>> I keep receiving the error: package: python3-3.10.3 failed to
>>> build.
>>> How do I restrict "make" to python 3.9?
>>>
>>> Sincerely,
>>> Lucas
>>>
>>> On Thursday, 21 July 20

Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-21 Thread Matthias Koeppe
By reading the configure messages

On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com wrote:

> How do I verify that Cygwin python3 is accepted?
>
> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>
>> No, these system packages need to be installed. Otherwise you won't get 
>> Cygwin's python package accepted.
>>
>> I recommend to start from scratch. Run configure, read what it recommends 
>> to install via Cygwin, do this installation, then run configure again.
>> Before running "make", verify that it accepts the Cygwin python3.
>>
>>
>> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 lucas@gmail.com 
>> wrote:
>>
>>> Hi Matthias, 
>>> Yes, they are. I have just uninstalled them via Cygwin setup. Should I 
>>> uninstall libffi as well?
>>>
>>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>>>
 Are these cygwin packages installed?  bzip2 libbz2-devel xz 
 liblzma-devel 

 On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 lucas@gmail.com 
 wrote:

> Apologies, my log files are here
>
>
>
> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>
>> Hi Matthias, 
>>
>> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice 
>> to ensure that the files are removed. 
>> I check for the following message: "No legacy uninstaller found for 
>> 'xz'; nothing to do", for all files. 
>> I have also ensured that I have python3.9 installed with "python3 
>> --version"
>> After running the above, I run "./configure" once more as suggested 
>> by John H Palmieri above. 
>>
>> I'm not sure if this is relevant, but I noticed these messages when 
>> running "make": 
>> *(first line of xz)* 
>> [xz-5.2.5] Using cached file 
>> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
>> [xz-5.2.5] xz-5.2.5
>> [xz-5.2.5] 
>> [xz-5.2.5] Setting up build directory for xz-5.2.5
>> [xz-5.2.5] Finished extraction
>> *(similarly for libffi, the cached file is used)*
>>
>> *(first line of python3)*
>> [python3-3.10.3] Using cached file 
>> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
>> [python3-3.10.3] python3-3.10.3
>> [python3-3.10.3] 
>> [python3-3.10.3] Setting up build directory for python3-3.10.3
>> [python3-3.10.3] Finished extraction
>> *(shortly later...)*
>> [python3-3.10.3] Thread model: posix
>> [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
>> [python3-3.10.3] gcc version 11.3.0 (GCC)
>> [python3-3.10.3] 
>> [python3-3.10.3] Package 'python3' is currently not installed
>> [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
>> [python3-3.10.3] Cleaning out old python / python3 / python3 venv 
>> binaries
>> [python3-3.10.3] Configuring python3-3.10.3
>>
>> On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:
>>
>>> Hi Matthias, 
>>>
>>> I would believe so. 
>>> ```
>>> $ apt-cyg install python39
>>> Package python39 is already installed, skipping
>>>
>>> $ apt-cyg install python3
>>> Package python3 is already installed, skipping
>>> ```
>>> On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:
>>>
 Did you install the cygwin python3.9 packages?

 On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com 
 wrote:

> Hi Matthias, 
>
> I keep receiving the error: package: python3-3.10.3 failed to 
> build. 
> How do I restrict "make" to python 3.9?
>
> Sincerely, 
> Lucas
>
> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>
>> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 
>> lucas@gmail.com wrote:
>>
>>>
>>> I could not install several packages using "apt-cyg". Some 
>>> packages could not be found, and some packages are not of the same 
>>> build or 
>>> version (e.g. apt-cyg install python3 -> python 3.9, not python 
>>> 3.10 as 
>>> used by "make"). 
>>>
>>
>> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's 
>> python 3.9 package.
>>
>>
>>
>>

-- 
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/0478d791-6169-4689-90a6-ddb60e00331an%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-21 Thread Lucas Tan
How do I verify that Cygwin python3 is accepted?

On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:

> No, these system packages need to be installed. Otherwise you won't get 
> Cygwin's python package accepted.
>
> I recommend to start from scratch. Run configure, read what it recommends 
> to install via Cygwin, do this installation, then run configure again.
> Before running "make", verify that it accepts the Cygwin python3.
>
>
> On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 lucas@gmail.com 
> wrote:
>
>> Hi Matthias, 
>> Yes, they are. I have just uninstalled them via Cygwin setup. Should I 
>> uninstall libffi as well?
>>
>> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>>
>>> Are these cygwin packages installed?  bzip2 libbz2-devel xz 
>>> liblzma-devel 
>>>
>>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 lucas@gmail.com 
>>> wrote:
>>>
 Apologies, my log files are here



 On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:

> Hi Matthias, 
>
> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice to 
> ensure that the files are removed. 
> I check for the following message: "No legacy uninstaller found for 
> 'xz'; nothing to do", for all files. 
> I have also ensured that I have python3.9 installed with "python3 
> --version"
> After running the above, I run "./configure" once more as suggested by 
> John H Palmieri above. 
>
> I'm not sure if this is relevant, but I noticed these messages when 
> running "make": 
> *(first line of xz)* 
> [xz-5.2.5] Using cached file 
> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
> [xz-5.2.5] xz-5.2.5
> [xz-5.2.5] 
> [xz-5.2.5] Setting up build directory for xz-5.2.5
> [xz-5.2.5] Finished extraction
> *(similarly for libffi, the cached file is used)*
>
> *(first line of python3)*
> [python3-3.10.3] Using cached file 
> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
> [python3-3.10.3] python3-3.10.3
> [python3-3.10.3] 
> [python3-3.10.3] Setting up build directory for python3-3.10.3
> [python3-3.10.3] Finished extraction
> *(shortly later...)*
> [python3-3.10.3] Thread model: posix
> [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
> [python3-3.10.3] gcc version 11.3.0 (GCC)
> [python3-3.10.3] 
> [python3-3.10.3] Package 'python3' is currently not installed
> [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
> [python3-3.10.3] Cleaning out old python / python3 / python3 venv 
> binaries
> [python3-3.10.3] Configuring python3-3.10.3
>
> On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:
>
>> Hi Matthias, 
>>
>> I would believe so. 
>> ```
>> $ apt-cyg install python39
>> Package python39 is already installed, skipping
>>
>> $ apt-cyg install python3
>> Package python3 is already installed, skipping
>> ```
>> On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:
>>
>>> Did you install the cygwin python3.9 packages?
>>>
>>> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com 
>>> wrote:
>>>
 Hi Matthias, 

 I keep receiving the error: package: python3-3.10.3 failed to 
 build. 
 How do I restrict "make" to python 3.9?

 Sincerely, 
 Lucas

 On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:

> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 
> lucas@gmail.com wrote:
>
>>
>> I could not install several packages using "apt-cyg". Some 
>> packages could not be found, and some packages are not of the same 
>> build or 
>> version (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 
>> as 
>> used by "make"). 
>>
>
> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's 
> python 3.9 package.
>
>
>
>

-- 
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/be42e98c-16fc-49f8-b879-526e5c42a0c5n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-21 Thread Matthias Koeppe
No, these system packages need to be installed. Otherwise you won't get 
Cygwin's python package accepted.

I recommend to start from scratch. Run configure, read what it recommends 
to install via Cygwin, do this installation, then run configure again.
Before running "make", verify that it accepts the Cygwin python3.


On Wednesday, July 20, 2022 at 11:47:41 PM UTC-7 lucas@gmail.com wrote:

> Hi Matthias, 
> Yes, they are. I have just uninstalled them via Cygwin setup. Should I 
> uninstall libffi as well?
>
> On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:
>
>> Are these cygwin packages installed?  bzip2 libbz2-devel xz liblzma-devel 
>>
>> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 lucas@gmail.com 
>> wrote:
>>
>>> Apologies, my log files are here
>>>
>>>
>>>
>>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>>>
 Hi Matthias, 

 I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice to 
 ensure that the files are removed. 
 I check for the following message: "No legacy uninstaller found for 
 'xz'; nothing to do", for all files. 
 I have also ensured that I have python3.9 installed with "python3 
 --version"
 After running the above, I run "./configure" once more as suggested by 
 John H Palmieri above. 

 I'm not sure if this is relevant, but I noticed these messages when 
 running "make": 
 *(first line of xz)* 
 [xz-5.2.5] Using cached file 
 /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
 [xz-5.2.5] xz-5.2.5
 [xz-5.2.5] 
 [xz-5.2.5] Setting up build directory for xz-5.2.5
 [xz-5.2.5] Finished extraction
 *(similarly for libffi, the cached file is used)*

 *(first line of python3)*
 [python3-3.10.3] Using cached file 
 /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
 [python3-3.10.3] python3-3.10.3
 [python3-3.10.3] 
 [python3-3.10.3] Setting up build directory for python3-3.10.3
 [python3-3.10.3] Finished extraction
 *(shortly later...)*
 [python3-3.10.3] Thread model: posix
 [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
 [python3-3.10.3] gcc version 11.3.0 (GCC)
 [python3-3.10.3] 
 [python3-3.10.3] Package 'python3' is currently not installed
 [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
 [python3-3.10.3] Cleaning out old python / python3 / python3 venv 
 binaries
 [python3-3.10.3] Configuring python3-3.10.3

 On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:

> Hi Matthias, 
>
> I would believe so. 
> ```
> $ apt-cyg install python39
> Package python39 is already installed, skipping
>
> $ apt-cyg install python3
> Package python3 is already installed, skipping
> ```
> On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:
>
>> Did you install the cygwin python3.9 packages?
>>
>> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com 
>> wrote:
>>
>>> Hi Matthias, 
>>>
>>> I keep receiving the error: package: python3-3.10.3 failed to build. 
>>> How do I restrict "make" to python 3.9?
>>>
>>> Sincerely, 
>>> Lucas
>>>
>>> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>>>
 On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
 wrote:

>
> I could not install several packages using "apt-cyg". Some 
> packages could not be found, and some packages are not of the same 
> build or 
> version (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 
> as 
> used by "make"). 
>

 That's normal. There's no python 3.10 for Cygwin. Use Cygwin's 
 python 3.9 package.





-- 
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/b306fc49-b06b-42ab-b5e4-2d19c690f748n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Lucas Tan
Hi Matthias, 
Yes, they are. I have just uninstalled them via Cygwin setup. Should I 
uninstall libffi as well?

On Thursday, 21 July 2022 at 13:22:48 UTC+8 Matthias Koeppe wrote:

> Are these cygwin packages installed?  bzip2 libbz2-devel xz liblzma-devel 
>
> On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 lucas@gmail.com 
> wrote:
>
>> Apologies, my log files are here
>>
>>
>>
>> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>>
>>> Hi Matthias, 
>>>
>>> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice to 
>>> ensure that the files are removed. 
>>> I check for the following message: "No legacy uninstaller found for 
>>> 'xz'; nothing to do", for all files. 
>>> I have also ensured that I have python3.9 installed with "python3 
>>> --version"
>>> After running the above, I run "./configure" once more as suggested by 
>>> John H Palmieri above. 
>>>
>>> I'm not sure if this is relevant, but I noticed these messages when 
>>> running "make": 
>>> *(first line of xz)* 
>>> [xz-5.2.5] Using cached file 
>>> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
>>> [xz-5.2.5] xz-5.2.5
>>> [xz-5.2.5] 
>>> [xz-5.2.5] Setting up build directory for xz-5.2.5
>>> [xz-5.2.5] Finished extraction
>>> *(similarly for libffi, the cached file is used)*
>>>
>>> *(first line of python3)*
>>> [python3-3.10.3] Using cached file 
>>> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
>>> [python3-3.10.3] python3-3.10.3
>>> [python3-3.10.3] 
>>> [python3-3.10.3] Setting up build directory for python3-3.10.3
>>> [python3-3.10.3] Finished extraction
>>> *(shortly later...)*
>>> [python3-3.10.3] Thread model: posix
>>> [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
>>> [python3-3.10.3] gcc version 11.3.0 (GCC)
>>> [python3-3.10.3] 
>>> [python3-3.10.3] Package 'python3' is currently not installed
>>> [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
>>> [python3-3.10.3] Cleaning out old python / python3 / python3 venv 
>>> binaries
>>> [python3-3.10.3] Configuring python3-3.10.3
>>>
>>> On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:
>>>
 Hi Matthias, 

 I would believe so. 
 ```
 $ apt-cyg install python39
 Package python39 is already installed, skipping

 $ apt-cyg install python3
 Package python3 is already installed, skipping
 ```
 On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:

> Did you install the cygwin python3.9 packages?
>
> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com 
> wrote:
>
>> Hi Matthias, 
>>
>> I keep receiving the error: package: python3-3.10.3 failed to build. 
>> How do I restrict "make" to python 3.9?
>>
>> Sincerely, 
>> Lucas
>>
>> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>>
>>> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
>>> wrote:
>>>

 I could not install several packages using "apt-cyg". Some packages 
 could not be found, and some packages are not of the same build or 
 version 
 (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 as used 
 by 
 "make"). 

>>>
>>> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's 
>>> python 3.9 package.
>>>
>>>
>>>
>>>

-- 
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/13bd3410-5098-4586-bbd0-445b16b17815n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Matthias Koeppe
Are these cygwin packages installed?  bzip2 libbz2-devel xz liblzma-devel 

On Wednesday, July 20, 2022 at 10:01:30 PM UTC-7 lucas@gmail.com wrote:

> Apologies, my log files are here
>
>
>
> On Thursday, 21 July 2022 at 12:47:16 UTC+8 Lucas Tan wrote:
>
>> Hi Matthias, 
>>
>> I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice to 
>> ensure that the files are removed. 
>> I check for the following message: "No legacy uninstaller found for 'xz'; 
>> nothing to do", for all files. 
>> I have also ensured that I have python3.9 installed with "python3 
>> --version"
>> After running the above, I run "./configure" once more as suggested by 
>> John H Palmieri above. 
>>
>> I'm not sure if this is relevant, but I noticed these messages when 
>> running "make": 
>> *(first line of xz)* 
>> [xz-5.2.5] Using cached file 
>> /home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
>> [xz-5.2.5] xz-5.2.5
>> [xz-5.2.5] 
>> [xz-5.2.5] Setting up build directory for xz-5.2.5
>> [xz-5.2.5] Finished extraction
>> *(similarly for libffi, the cached file is used)*
>>
>> *(first line of python3)*
>> [python3-3.10.3] Using cached file 
>> /home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
>> [python3-3.10.3] python3-3.10.3
>> [python3-3.10.3] 
>> [python3-3.10.3] Setting up build directory for python3-3.10.3
>> [python3-3.10.3] Finished extraction
>> *(shortly later...)*
>> [python3-3.10.3] Thread model: posix
>> [python3-3.10.3] Supported LTO compression algorithms: zlib zstd
>> [python3-3.10.3] gcc version 11.3.0 (GCC)
>> [python3-3.10.3] 
>> [python3-3.10.3] Package 'python3' is currently not installed
>> [python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
>> [python3-3.10.3] Cleaning out old python / python3 / python3 venv binaries
>> [python3-3.10.3] Configuring python3-3.10.3
>>
>> On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:
>>
>>> Hi Matthias, 
>>>
>>> I would believe so. 
>>> ```
>>> $ apt-cyg install python39
>>> Package python39 is already installed, skipping
>>>
>>> $ apt-cyg install python3
>>> Package python3 is already installed, skipping
>>> ```
>>> On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:
>>>
 Did you install the cygwin python3.9 packages?

 On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com 
 wrote:

> Hi Matthias, 
>
> I keep receiving the error: package: python3-3.10.3 failed to build. 
> How do I restrict "make" to python 3.9?
>
> Sincerely, 
> Lucas
>
> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>
>> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
>> wrote:
>>
>>>
>>> I could not install several packages using "apt-cyg". Some packages 
>>> could not be found, and some packages are not of the same build or 
>>> version 
>>> (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 as used by 
>>> "make"). 
>>>
>>
>> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 
>> 3.9 package.
>>
>>
>>
>>

-- 
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/83c9c121-dd6a-4105-a43f-eaeab8359f04n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Lucas Tan
Hi Matthias, 

I ran  "make bzip2-clean liblzma-clean libffi-clean xz-clean" twice to 
ensure that the files are removed. 
I check for the following message: "No legacy uninstaller found for 'xz'; 
nothing to do", for all files. 
I have also ensured that I have python3.9 installed with "python3 --version"
After running the above, I run "./configure" once more as suggested by John 
H Palmieri above. 

I'm not sure if this is relevant, but I noticed these messages when running 
"make": 
*(first line of xz)* 
[xz-5.2.5] Using cached file 
/home/Lucas/sage/sage-9.6/upstream/xz-5.2.5.tar.gz
[xz-5.2.5] xz-5.2.5
[xz-5.2.5] 
[xz-5.2.5] Setting up build directory for xz-5.2.5
[xz-5.2.5] Finished extraction
*(similarly for libffi, the cached file is used)*

*(first line of python3)*
[python3-3.10.3] Using cached file 
/home/Lucas/sage/sage-9.6/upstream/Python-3.10.3.tar.xz
[python3-3.10.3] python3-3.10.3
[python3-3.10.3] 
[python3-3.10.3] Setting up build directory for python3-3.10.3
[python3-3.10.3] Finished extraction
*(shortly later...)*
[python3-3.10.3] Thread model: posix
[python3-3.10.3] Supported LTO compression algorithms: zlib zstd
[python3-3.10.3] gcc version 11.3.0 (GCC)
[python3-3.10.3] 
[python3-3.10.3] Package 'python3' is currently not installed
[python3-3.10.3] Uninstalling 'python3' with legacy uninstaller
[python3-3.10.3] Cleaning out old python / python3 / python3 venv binaries
[python3-3.10.3] Configuring python3-3.10.3

On Thursday, 21 July 2022 at 11:11:42 UTC+8 Lucas Tan wrote:

> Hi Matthias, 
>
> I would believe so. 
> ```
> $ apt-cyg install python39
> Package python39 is already installed, skipping
>
> $ apt-cyg install python3
> Package python3 is already installed, skipping
> ```
> On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:
>
>> Did you install the cygwin python3.9 packages?
>>
>> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com 
>> wrote:
>>
>>> Hi Matthias, 
>>>
>>> I keep receiving the error: package: python3-3.10.3 failed to build. 
>>> How do I restrict "make" to python 3.9?
>>>
>>> Sincerely, 
>>> Lucas
>>>
>>> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>>>
 On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
 wrote:

>
> I could not install several packages using "apt-cyg". Some packages 
> could not be found, and some packages are not of the same build or 
> version 
> (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 as used by 
> "make"). 
>

 That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 
 3.9 package.





-- 
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/3b546cb7-8e74-4b6f-9e13-32539db0fddan%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Lucas Tan
Hi Matthias, 

I would believe so. 
```
$ apt-cyg install python39
Package python39 is already installed, skipping

$ apt-cyg install python3
Package python3 is already installed, skipping
```
On Thursday, 21 July 2022 at 11:08:50 UTC+8 Matthias Koeppe wrote:

> Did you install the cygwin python3.9 packages?
>
> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com wrote:
>
>> Hi Matthias, 
>>
>> I keep receiving the error: package: python3-3.10.3 failed to build. 
>> How do I restrict "make" to python 3.9?
>>
>> Sincerely, 
>> Lucas
>>
>> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>>
>>> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
>>> wrote:
>>>

 I could not install several packages using "apt-cyg". Some packages 
 could not be found, and some packages are not of the same build or version 
 (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 as used by 
 "make"). 

>>>
>>> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 
>>> 3.9 package.
>>>
>>>
>>>
>>>

-- 
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/82fb148a-5ce4-45f0-b9d5-b5925f10e059n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Matthias Koeppe
Your config.log is still saying:
##  ## #
# Checking whether SageMath should install SPKG python3... ## #
#  ## 
configure:32387: checking whether any of bzip2 liblzma libffi is installed 
as or will be installed as SPKG c
configure:32391: result: yes; install python3 as well


You need to uninstall these packages:
make bzip2-clean liblzma-clean libffi-clean xz-clean

 


On Wednesday, July 20, 2022 at 8:08:50 PM UTC-7 Matthias Koeppe wrote:

> Did you install the cygwin python3.9 packages?
>
> On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com wrote:
>
>> Hi Matthias, 
>>
>> I keep receiving the error: package: python3-3.10.3 failed to build. 
>> How do I restrict "make" to python 3.9?
>>
>> Sincerely, 
>> Lucas
>>
>> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>>
>>> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
>>> wrote:
>>>

 I could not install several packages using "apt-cyg". Some packages 
 could not be found, and some packages are not of the same build or version 
 (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 as used by 
 "make"). 

>>>
>>> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 
>>> 3.9 package.
>>>
>>>
>>>
>>>

-- 
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/13a4b4cc-c1c7-495b-904a-5ee18f6afff5n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Matthias Koeppe
Did you install the cygwin python3.9 packages?

On Wednesday, July 20, 2022 at 8:05:47 PM UTC-7 lucas@gmail.com wrote:

> Hi Matthias, 
>
> I keep receiving the error: package: python3-3.10.3 failed to build. 
> How do I restrict "make" to python 3.9?
>
> Sincerely, 
> Lucas
>
> On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:
>
>> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com 
>> wrote:
>>
>>>
>>> I could not install several packages using "apt-cyg". Some packages 
>>> could not be found, and some packages are not of the same build or version 
>>> (e.g. apt-cyg install python3 -> python 3.9, not python 3.10 as used by 
>>> "make"). 
>>>
>>
>> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 3.9 
>> package.
>>
>>
>>
>>

-- 
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/81eb2a94-3ae0-440f-8cd7-fe6e7e041842n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Lucas Tan
Hi Matthias, 

I keep receiving the error: package: python3-3.10.3 failed to build. 
How do I restrict "make" to python 3.9?

Sincerely, 
Lucas

On Thursday, 21 July 2022 at 10:34:41 UTC+8 Matthias Koeppe wrote:

> On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com wrote:
>
>>
>> I could not install several packages using "apt-cyg". Some packages could 
>> not be found, and some packages are not of the same build or version (e.g. 
>> apt-cyg install python3 -> python 3.9, not python 3.10 as used by "make"). 
>>
>
> That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 3.9 
> package.
>
>
>
>

-- 
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/2aebec3a-8cc7-4555-a3ed-6cf407eb8c90n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Matthias Koeppe
On Wednesday, July 20, 2022 at 7:26:06 PM UTC-7 lucas@gmail.com wrote:

>
> I could not install several packages using "apt-cyg". Some packages could 
> not be found, and some packages are not of the same build or version (e.g. 
> apt-cyg install python3 -> python 3.9, not python 3.10 as used by "make"). 
>

That's normal. There's no python 3.10 for Cygwin. Use Cygwin's python 3.9 
package.



-- 
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/6b80cdbf-df52-4317-bab9-25f0c78de273n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread John H Palmieri
I don't think anyone has said this explicitly: after installing the 
packages recommended by ./configure, then you need to run ./configure 
again. Then run make.

On Wednesday, July 20, 2022 at 9:25:07 AM UTC-7 dim...@gmail.com wrote:

> and once you have the needed python3 packages installed, you don't need to 
> build python3 from source anymore.
>
> On Wed, 20 Jul 2022, 16:59 Lucas Tan,  wrote:
>
>> Hi, 
>>
>> I have installed all the files that I could and ran "make". 
>> I could not install some files, the error returned was "Unable to locate 
>> package NAME", example NAME= openblas
>>
>> The Python package could still not be built, particularly 
>> python3-SAGE_VENV-no-deps
>>
>> I have attached the updated logs as well. 
>>
>> Thank you, 
>> Lucas
>>
>> On Wednesday, 20 July 2022 at 18:45:40 UTC+8 dim...@gmail.com wrote:
>>
>>> On Wed, 20 Jul 2022, 11:28 Lucas Tan,  wrote:
>>>
 Hi, 

 Thank you. 

 I have now installed all the packages recommended ./configure
 Do I run "make" again?

 (I have decided to use Cygwin as I hope to (1) add Sage to PATH, (2) 
 use as a kernel/interpreter in VSCode, and (3) to later upload some .sage 
 files from VSCode to Github)

>>>
>>> 2) VSCode on Windows has ability to use remote kernels, including ones 
>>> on its WSL.
>>>
>>> 1) Adding Sage to Windows PATH?
>>> Not sure this will fly.
>>>
>>> 3) can be done with WSL, sure
>>>
>>>
 Sincerely, 
 Lucas

 On Wednesday, 20 July 2022 at 17:40:29 UTC+8 dim...@gmail.com wrote:

> On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan  
> wrote: 
> > 
> > Good day, 
> > 
> > I have encountered an error when building Sage 9.6 on the Cygwin 
> Terminal. I am very new to Sage and am unfamiliar with debugging methods. 
> > 
> > It seems that Python3 could not be built, I suppose. I have attached 
> the relevant .log files. 
>
> please check out the list of Cygwin packages recommended for 
> installation, printed at the end of 
> ./configure 
> run, and follow it. 
>
> Cygwin is very tricky to support (we actually recommend that on 
> Windows people install/use Sage with WSL (WSL2, to be precise), not 
> Cygwin) 
>
> > My computer is running on "Windows 10 Home 64-bit (10.0, Build 
> 19044)", a Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7 
> 5800H with Radeon Graphics (16 CPUs), ~3.2GHz. 
> > 
> > Your assistance is greatly appreciated. Thank you. 
> > 
> > Yours sincerely, 
> > Lucas Tan 
> > 
> > -- 
> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/a8d5a159-9005-454f-83d8-aeb9798d0a65n%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/c44a67d4-913b-476e-b4a1-f15f2cf4d02en%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/24d7c360-9d80-4120-b8ab-f0437d165e07n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Dima Pasechnik
and once you have the needed python3 packages installed, you don't need to
build python3 from source anymore.

On Wed, 20 Jul 2022, 16:59 Lucas Tan,  wrote:

> Hi,
>
> I have installed all the files that I could and ran "make".
> I could not install some files, the error returned was "Unable to locate
> package NAME", example NAME= openblas
>
> The Python package could still not be built, particularly
> python3-SAGE_VENV-no-deps
>
> I have attached the updated logs as well.
>
> Thank you,
> Lucas
>
> On Wednesday, 20 July 2022 at 18:45:40 UTC+8 dim...@gmail.com wrote:
>
>> On Wed, 20 Jul 2022, 11:28 Lucas Tan,  wrote:
>>
>>> Hi,
>>>
>>> Thank you.
>>>
>>> I have now installed all the packages recommended ./configure
>>> Do I run "make" again?
>>>
>>> (I have decided to use Cygwin as I hope to (1) add Sage to PATH, (2) use
>>> as a kernel/interpreter in VSCode, and (3) to later upload some .sage files
>>> from VSCode to Github)
>>>
>>
>> 2) VSCode on Windows has ability to use remote kernels, including ones on
>> its WSL.
>>
>> 1) Adding Sage to Windows PATH?
>> Not sure this will fly.
>>
>> 3) can be done with WSL, sure
>>
>>
>>> Sincerely,
>>> Lucas
>>>
>>> On Wednesday, 20 July 2022 at 17:40:29 UTC+8 dim...@gmail.com wrote:
>>>
 On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan 
 wrote:
 >
 > Good day,
 >
 > I have encountered an error when building Sage 9.6 on the Cygwin
 Terminal. I am very new to Sage and am unfamiliar with debugging methods.
 >
 > It seems that Python3 could not be built, I suppose. I have attached
 the relevant .log files.

 please check out the list of Cygwin packages recommended for
 installation, printed at the end of
 ./configure
 run, and follow it.

 Cygwin is very tricky to support (we actually recommend that on
 Windows people install/use Sage with WSL (WSL2, to be precise), not
 Cygwin)

 > My computer is running on "Windows 10 Home 64-bit (10.0, Build
 19044)", a Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7
 5800H with Radeon Graphics (16 CPUs), ~3.2GHz.
 >
 > Your assistance is greatly appreciated. Thank you.
 >
 > Yours sincerely,
 > Lucas Tan
 >
 > --
 > 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 view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/a8d5a159-9005-454f-83d8-aeb9798d0a65n%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/c44a67d4-913b-476e-b4a1-f15f2cf4d02en%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/CAAWYfq3OjxAOSX%2B-9shWeoQ5E%3Dn_9eOdeRyoBY7aXjEWejW0UQ%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Dima Pasechnik
do you have the corr. Cygwin packages (e.g. openblas) installed?

Do you run make in a native shell, rather than a cygwin shell?

On Wed, 20 Jul 2022, 16:59 Lucas Tan,  wrote:

> Hi,
>
> I have installed all the files that I could and ran "make".
> I could not install some files, the error returned was "Unable to locate
> package NAME", example NAME= openblas
>
> The Python package could still not be built, particularly
> python3-SAGE_VENV-no-deps
>
> I have attached the updated logs as well.
>
> Thank you,
> Lucas
>
> On Wednesday, 20 July 2022 at 18:45:40 UTC+8 dim...@gmail.com wrote:
>
>> On Wed, 20 Jul 2022, 11:28 Lucas Tan,  wrote:
>>
>>> Hi,
>>>
>>> Thank you.
>>>
>>> I have now installed all the packages recommended ./configure
>>> Do I run "make" again?
>>>
>>> (I have decided to use Cygwin as I hope to (1) add Sage to PATH, (2) use
>>> as a kernel/interpreter in VSCode, and (3) to later upload some .sage files
>>> from VSCode to Github)
>>>
>>
>> 2) VSCode on Windows has ability to use remote kernels, including ones on
>> its WSL.
>>
>> 1) Adding Sage to Windows PATH?
>> Not sure this will fly.
>>
>> 3) can be done with WSL, sure
>>
>>
>>> Sincerely,
>>> Lucas
>>>
>>> On Wednesday, 20 July 2022 at 17:40:29 UTC+8 dim...@gmail.com wrote:
>>>
 On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan 
 wrote:
 >
 > Good day,
 >
 > I have encountered an error when building Sage 9.6 on the Cygwin
 Terminal. I am very new to Sage and am unfamiliar with debugging methods.
 >
 > It seems that Python3 could not be built, I suppose. I have attached
 the relevant .log files.

 please check out the list of Cygwin packages recommended for
 installation, printed at the end of
 ./configure
 run, and follow it.

 Cygwin is very tricky to support (we actually recommend that on
 Windows people install/use Sage with WSL (WSL2, to be precise), not
 Cygwin)

 > My computer is running on "Windows 10 Home 64-bit (10.0, Build
 19044)", a Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7
 5800H with Radeon Graphics (16 CPUs), ~3.2GHz.
 >
 > Your assistance is greatly appreciated. Thank you.
 >
 > Yours sincerely,
 > Lucas Tan
 >
 > --
 > 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 view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/a8d5a159-9005-454f-83d8-aeb9798d0a65n%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/c44a67d4-913b-476e-b4a1-f15f2cf4d02en%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/CAAWYfq0BmxD9cgHBUH-9_9hK7YZUm5Gve8Dse%3DO%2BWk9WdVXSaQ%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Matthias Koeppe
>From config.log:
##  ## 
## Checking whether SageMath should install SPKG python3... ## 
##  ## 
configure:32387: checking whether any of bzip2 liblzma libffi is installed 
as or will be installed as SPKG 
configure:32391: result: yes; install python3 as well 

This is from a prior run of "make" before you installed the system (Cygwin) 
packages.
To fix this, use "make bzip2-clean liblzma-clean libffi-clean"


On Wednesday, July 20, 2022 at 8:59:08 AM UTC-7 lucas@gmail.com wrote:

> Hi, 
>
> I have installed all the files that I could and ran "make". 
> I could not install some files, the error returned was "Unable to locate 
> package NAME", example NAME= openblas
>
> The Python package could still not be built, particularly 
> python3-SAGE_VENV-no-deps
>
> I have attached the updated logs as well. 
>
> Thank you, 
> Lucas
>
> On Wednesday, 20 July 2022 at 18:45:40 UTC+8 dim...@gmail.com wrote:
>
>> On Wed, 20 Jul 2022, 11:28 Lucas Tan,  wrote:
>>
>>> Hi, 
>>>
>>> Thank you. 
>>>
>>> I have now installed all the packages recommended ./configure
>>> Do I run "make" again?
>>>
>>> (I have decided to use Cygwin as I hope to (1) add Sage to PATH, (2) use 
>>> as a kernel/interpreter in VSCode, and (3) to later upload some .sage files 
>>> from VSCode to Github)
>>>
>>
>> 2) VSCode on Windows has ability to use remote kernels, including ones on 
>> its WSL.
>>
>> 1) Adding Sage to Windows PATH?
>> Not sure this will fly.
>>
>> 3) can be done with WSL, sure
>>
>>
>>> Sincerely, 
>>> Lucas
>>>
>>> On Wednesday, 20 July 2022 at 17:40:29 UTC+8 dim...@gmail.com wrote:
>>>
 On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan  
 wrote: 
 > 
 > Good day, 
 > 
 > I have encountered an error when building Sage 9.6 on the Cygwin 
 Terminal. I am very new to Sage and am unfamiliar with debugging methods. 
 > 
 > It seems that Python3 could not be built, I suppose. I have attached 
 the relevant .log files. 

 please check out the list of Cygwin packages recommended for 
 installation, printed at the end of 
 ./configure 
 run, and follow it. 

 Cygwin is very tricky to support (we actually recommend that on 
 Windows people install/use Sage with WSL (WSL2, to be precise), not 
 Cygwin) 

 > My computer is running on "Windows 10 Home 64-bit (10.0, Build 
 19044)", a Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7 
 5800H with Radeon Graphics (16 CPUs), ~3.2GHz. 
 > 
 > Your assistance is greatly appreciated. Thank you. 
 > 
 > Yours sincerely, 
 > Lucas Tan 
 > 
 > -- 
 > 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 view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/a8d5a159-9005-454f-83d8-aeb9798d0a65n%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/aacddd3c-3fb1-4a66-8818-5f565f5d97f8n%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Dima Pasechnik
On Wed, 20 Jul 2022, 11:28 Lucas Tan,  wrote:

> Hi,
>
> Thank you.
>
> I have now installed all the packages recommended ./configure
> Do I run "make" again?
>
> (I have decided to use Cygwin as I hope to (1) add Sage to PATH, (2) use
> as a kernel/interpreter in VSCode, and (3) to later upload some .sage files
> from VSCode to Github)
>

2) VSCode on Windows has ability to use remote kernels, including ones on
its WSL.

1) Adding Sage to Windows PATH?
Not sure this will fly.

3) can be done with WSL, sure


> Sincerely,
> Lucas
>
> On Wednesday, 20 July 2022 at 17:40:29 UTC+8 dim...@gmail.com wrote:
>
>> On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan  wrote:
>> >
>> > Good day,
>> >
>> > I have encountered an error when building Sage 9.6 on the Cygwin
>> Terminal. I am very new to Sage and am unfamiliar with debugging methods.
>> >
>> > It seems that Python3 could not be built, I suppose. I have attached
>> the relevant .log files.
>>
>> please check out the list of Cygwin packages recommended for
>> installation, printed at the end of
>> ./configure
>> run, and follow it.
>>
>> Cygwin is very tricky to support (we actually recommend that on
>> Windows people install/use Sage with WSL (WSL2, to be precise), not
>> Cygwin)
>>
>> > My computer is running on "Windows 10 Home 64-bit (10.0, Build 19044)",
>> a Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7 5800H with
>> Radeon Graphics (16 CPUs), ~3.2GHz.
>> >
>> > Your assistance is greatly appreciated. Thank you.
>> >
>> > Yours sincerely,
>> > Lucas Tan
>> >
>> > --
>> > 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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/a8d5a159-9005-454f-83d8-aeb9798d0a65n%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/CAAWYfq1D0QDuL%2BiOW63H%3DFLz-RuzFYVdLBsNo7vSKx0dDkJuqQ%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Dima Pasechnik
On Wed, 20 Jul 2022, 11:28 Lucas Tan,  wrote:

> Hi,
>
> Thank you.
>
> I have now installed all the packages recommended ./configure
> Do I run "make" again?
>

of course

>
> (I have decided to use Cygwin as I hope to (1) add Sage to PATH, (2) use
> as a kernel/interpreter in VSCode, and (3) to later upload some .sage files
> from VSCode to Github)
>
> Sincerely,
> Lucas
>
> On Wednesday, 20 July 2022 at 17:40:29 UTC+8 dim...@gmail.com wrote:
>
>> On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan  wrote:
>> >
>> > Good day,
>> >
>> > I have encountered an error when building Sage 9.6 on the Cygwin
>> Terminal. I am very new to Sage and am unfamiliar with debugging methods.
>> >
>> > It seems that Python3 could not be built, I suppose. I have attached
>> the relevant .log files.
>>
>> please check out the list of Cygwin packages recommended for
>> installation, printed at the end of
>> ./configure
>> run, and follow it.
>>
>> Cygwin is very tricky to support (we actually recommend that on
>> Windows people install/use Sage with WSL (WSL2, to be precise), not
>> Cygwin)
>>
>> > My computer is running on "Windows 10 Home 64-bit (10.0, Build 19044)",
>> a Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7 5800H with
>> Radeon Graphics (16 CPUs), ~3.2GHz.
>> >
>> > Your assistance is greatly appreciated. Thank you.
>> >
>> > Yours sincerely,
>> > Lucas Tan
>> >
>> > --
>> > 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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/a8d5a159-9005-454f-83d8-aeb9798d0a65n%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/CAAWYfq3Uy%3Dpt%2Bcte8bSGDUgjshA4iS-0Kq%2BW_Z%2B___eQdUM7mw%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.6 on Cygwin

2022-07-20 Thread Dima Pasechnik
On Wed, Jul 20, 2022 at 10:12 AM Lucas Tan  wrote:
>
> Good day,
>
> I have encountered an error when building Sage 9.6 on the Cygwin Terminal. I 
> am very new to Sage and am unfamiliar with debugging methods.
>
> It seems that Python3 could not be built, I suppose. I have attached the 
> relevant .log files.

please check out the list of Cygwin packages recommended for
installation, printed at the end of
./configure
run, and follow it.

Cygwin is very tricky to support (we actually recommend that on
Windows people install/use Sage with WSL (WSL2, to be precise), not
Cygwin)

> My computer is running on "Windows 10 Home 64-bit (10.0, Build 19044)", a 
> Lenovo Yoga Slim 7 Pro 14ACH5, with Processor: "AMD Ryzen 7 5800H with Radeon 
> Graphics (16 CPUs), ~3.2GHz.
>
> Your assistance is greatly appreciated. Thank you.
>
> Yours sincerely,
> Lucas Tan
>
> --
> 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/aa905e46-7e7b-491b-a89b-2e5fd17e5f17n%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/CAAWYfq2NNu6no4%2BkkL_z7ehwYegQnWz9kXkU84s4RO-9hiNXmw%40mail.gmail.com.


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

2022-07-19 Thread Max Kölbl
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/4b3e0fbc-9e95-470b-897c-1c1a59e29dcan%40googlegroups.com.
Attempting to download package openssl-3.0.4.tar.gz from mirrors
https://ftp.riken.jp/sagemath/spkg/upstream/openssl/openssl-3.0.4.tar.gz
[..]
openssl-3.0.4

Setting up build directory for openssl-3.0.4
Finished extraction
No patch files found in ../patches

Host system:
CYGWIN_NT-6.3-9600 MaxPC 3.3.5-341.x86_64 2022-05-13 12:27 UTC x86_64 Cygwin

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/11/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: /mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-11.3.0/configure 
--srcdir=/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-11.3.0 --prefix=/usr 
--exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc 
--docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C 
--build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin 
--without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib 
--with-gcc-major-version-only --enable-shared --enable-shared-libgcc 
--enable-static --enable-version-specific-runtime-libs --enable-bootstrap 
--enable-__cxa_atexit --with-dwarf2 --with-tune=generic 
--enable-languages=c,c++,fortran,lto,objc,obj-c++,jit --enable-graphite 
--enable-threads=posix --enable-libatomic --enable-libgomp --enable-libquadmath 
--enable-libquadmath-support --disable-libssp --enable-libada --disable-symvers 
--with-gnu-ld --with-gnu-as --with-cloog-include=/usr/include/cloog-isl 
--without-libiconv-prefix --without-libintl-prefix --with-system-zlib 
--enable-linker-build-id --with-default-libstdcxx-abi=gcc4-compatible 
--enable-libstdcxx-filesystem-ts
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.3.0 (GCC) 
***

Re: [sage-devel] error building sage-9.3 on catalina (gsl-2.6)

2021-05-25 Thread sal...@gmail.com

This worked! Thanks Dima!

On Tuesday, May 25, 2021 at 7:46:57 AM UTC-4 dim...@gmail.com wrote:

> On Tue, May 25, 2021 at 12:38 PM sal...@gmail.com  
> wrote:
> >
> >
> > Actually, I do have gsl installed via brew. I installed all the packages 
> suggested by homebrew and sourced the homebrew-build-env, but I still get 
> hints when I (re)run the configure scripts.
>
>
> The problem is that you have gfortran 11, as can be seen from your 
> config.log
>
> Thus, you need https://trac.sagemath.org/ticket/31838
>
>
>
>
> > On Tuesday, May 25, 2021 at 7:33:21 AM UTC-4 dim...@gmail.com wrote:
> >>
> >> Do you really have to build gsl yourself?
> >> https://formulae.brew.sh/formula/gsl
> >>
> >> also, note that ./configure tells you:
> >>
> >> hint: installing the following system packages, if not
> >> already present, is recommended and may avoid having to
> >> build them (though some may have to be built anyway):
> >>
> >> $ brew install gcc gsl openblas r suite-sparse
> >>
> >>
> >> On Tue, May 25, 2021 at 12:27 PM sal...@gmail.com  
> wrote:
> >> >
> >> >
> >> > Hello everyone.
> >> >
> >> > I've run into a problem while compiling sage-9.3 on macOS Catalina 
> 10.15.7. The installation hangs on compiling gsl-2.6. Some notes:
> >> >
> >> > - machine : 2020 macbook pro
> >> > - OS : macOS Catalina 10.15.7 with homebrew
> >> > - This occurs both after a "dist-clean" as well as with a new clone & 
> compile.
> >> >
> >> > See attached files. Any ideas on how to fix this?
> >> >
> >> > Best,
> >> > Franco
> >> >
> >> > --
> >> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/585d14fe-a68e-4ec8-a0dc-12e0e189b572n%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+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/9b7fb6f6-c584-4d67-bc2b-0f4087b4df05n%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/8a98baa1-1cfc-433e-acae-e429a74ecf2en%40googlegroups.com.


Re: [sage-devel] error building sage-9.3 on catalina (gsl-2.6)

2021-05-25 Thread Dima Pasechnik
On Tue, May 25, 2021 at 12:38 PM sal...@gmail.com  wrote:
>
>
> Actually, I do have gsl installed via brew. I installed all the packages 
> suggested by homebrew and sourced the homebrew-build-env, but I still get 
> hints when I (re)run the configure scripts.


The problem is that you have gfortran 11, as can be seen from your config.log

Thus, you need https://trac.sagemath.org/ticket/31838




> On Tuesday, May 25, 2021 at 7:33:21 AM UTC-4 dim...@gmail.com wrote:
>>
>> Do you really have to build gsl yourself?
>> https://formulae.brew.sh/formula/gsl
>>
>> also, note that ./configure tells you:
>>
>> hint: installing the following system packages, if not
>> already present, is recommended and may avoid having to
>> build them (though some may have to be built anyway):
>>
>> $ brew install gcc gsl openblas r suite-sparse
>>
>>
>> On Tue, May 25, 2021 at 12:27 PM sal...@gmail.com  wrote:
>> >
>> >
>> > Hello everyone.
>> >
>> > I've run into a problem while compiling sage-9.3 on macOS Catalina 
>> > 10.15.7. The installation hangs on compiling gsl-2.6. Some notes:
>> >
>> > - machine : 2020 macbook pro
>> > - OS : macOS Catalina 10.15.7 with homebrew
>> > - This occurs both after a "dist-clean" as well as with a new clone & 
>> > compile.
>> >
>> > See attached files. Any ideas on how to fix this?
>> >
>> > Best,
>> > Franco
>> >
>> > --
>> > 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 view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/585d14fe-a68e-4ec8-a0dc-12e0e189b572n%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/9b7fb6f6-c584-4d67-bc2b-0f4087b4df05n%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/CAAWYfq2Jjnf6TgeLZ-a-T9sXfJFHKtBbhXH26rnajKJniLggKw%40mail.gmail.com.


Re: [sage-devel] error building sage-9.3 on catalina (gsl-2.6)

2021-05-25 Thread sal...@gmail.com

Actually, I do have gsl installed via brew. I installed all the packages 
suggested by homebrew and sourced the homebrew-build-env, but I still get 
hints when I (re)run the configure scripts.

On Tuesday, May 25, 2021 at 7:33:21 AM UTC-4 dim...@gmail.com wrote:

> Do you really have to build gsl yourself?
> https://formulae.brew.sh/formula/gsl
>
> also, note that ./configure tells you:
>
> hint: installing the following system packages, if not
> already present, is recommended and may avoid having to
> build them (though some may have to be built anyway):
>
> $ brew install gcc gsl openblas r suite-sparse
>
>
> On Tue, May 25, 2021 at 12:27 PM sal...@gmail.com  
> wrote:
> >
> >
> > Hello everyone.
> >
> > I've run into a problem while compiling sage-9.3 on macOS Catalina 
> 10.15.7. The installation hangs on compiling gsl-2.6. Some notes:
> >
> > - machine : 2020 macbook pro
> > - OS : macOS Catalina 10.15.7 with homebrew
> > - This occurs both after a "dist-clean" as well as with a new clone & 
> compile.
> >
> > See attached files. Any ideas on how to fix this?
> >
> > Best,
> > Franco
> >
> > --
> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/585d14fe-a68e-4ec8-a0dc-12e0e189b572n%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/9b7fb6f6-c584-4d67-bc2b-0f4087b4df05n%40googlegroups.com.


Re: [sage-devel] error building sage-9.3 on catalina (gsl-2.6)

2021-05-25 Thread Dima Pasechnik
Do you really have to build gsl yourself?
https://formulae.brew.sh/formula/gsl

also, note that ./configure tells you:

hint: installing the following system packages, if not
already present, is recommended and may avoid having to
build them (though some may have to be built anyway):

  $ brew install gcc gsl openblas r suite-sparse


On Tue, May 25, 2021 at 12:27 PM sal...@gmail.com  wrote:
>
>
> Hello everyone.
>
> I've run into a problem while compiling sage-9.3 on macOS Catalina 10.15.7. 
> The installation hangs on compiling gsl-2.6. Some notes:
>
> - machine : 2020 macbook pro
> - OS : macOS Catalina 10.15.7 with homebrew
> - This occurs both after a "dist-clean" as well as with a new clone & compile.
>
> See attached files. Any ideas on how to fix this?
>
> Best,
> Franco
>
> --
> 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/585d14fe-a68e-4ec8-a0dc-12e0e189b572n%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/CAAWYfq0yUTDhi58mbhHNOxx6am3W0SSoosSH4bdFT_VnVM2naQ%40mail.gmail.com.


Re: [sage-devel] Error building sage

2020-03-12 Thread Dima Pasechnik
On Thu, Mar 12, 2020 at 6:36 PM DIVESH KUMAR
 wrote:
>
> I used git pull and then make worked fine.
> However upon starting this message is displayed
>
> SageMath version 9.1.beta7, Release Date: 2020-03-08   │
> │ Using Python 3.7.3. Type "help()" for help.│
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
>   ***   Warning: not enough memory, new PARI stack 1286025216
>
> what does  Warning: not enough memory, new PARI stack 1286025216 mean?

it probably is innocent, and tells you that you didn't have much free
memory as the moment you
started Sage.


>
>
>
>
>
> On Thursday, March 12, 2020 at 9:02:00 PM UTC+5:30, Dima Pasechnik wrote:
>>
>> the md5 in your checksum.ini does not match the (correct) md5 of the tar 
>> file.
>>
>> I gues that your git branch is
>> somehow inconsistent.
>> What is the output of
>>
>> git status
>>
>> ?
>>
>> if you wanted to build the development branch you needed to do
>>
>> git checkout develop
>>
>>
>>
>>
>> On Thu, 12 Mar 2020, 15:24 DIVESH KUMAR,  
>> wrote:
>>>
>>> First of all, I thank you for your prompt replies and please spare me for 
>>> my mistakes as I am a beginner.
>>>
>>> Contents of checksum.ini
>
> tarball=pyzmq-VERSION.tar.gz
>
> sha1=64799b73d6109fb6da5b7deb6101ba13cd7fe885
>
> md5=3c8039d007bbbd08a2275f52f5dc9a35
>
> cksum=1455168757
>>>
>>>
>>>  make command returns this

 configure: error: 
 "/home/diveshcode/Downloads/SageMath/build/pkgs/sage_conf/type" is missing.

 If you would like to try to build Sage anyway (to help porting),

 export the variable 'SAGE_PORT' to something non-empty.

 Makefile:39: recipe for target 'build/make/Makefile' failed

 make[1]: *** [build/make/Makefile] Error 1

 make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'

 Makefile:31: recipe for target 'base-toolchain' failed

 make: *** [base-toolchain] Error 2
>>>
>>>


>>>
>>> upon doing
>>> export SAGE_PORT=1
>>> make
>>> the error returned is
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: pyzmq-19.0.0
>
>   log file: /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>
>   build directory: 
> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>
> make[1]: *** [all-start] Error 1
>
> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>
> Makefile:13: recipe for target 'all' failed
>
> make: *** [all] e 2


>>>
>>>
>>> I have cloned the git repository from  git://git.sagemath.org//sage.git
>>>
>>> I am using Ubuntu 18.04.
>>>
>>> As I haven't done any signification modifications can I clone sage again 
>>> and link it with my trac account(which is already linked to the current 
>>> directory).
>>>
>>>
>>> Thank you for your time.
>>> Cheers.
>>>
>>> On Thursday, March 12, 2020 at 8:24:48 PM UTC+5:30, Dima Pasechnik wrote:

 On Thu, Mar 12, 2020 at 2:02 PM DIVESH KUMAR
  wrote:
 >
 > ~/Downloads/SageMath/upstream$ md5sum pyzmq-19.0.0.tar.gz
 > 4650e45ebcf8e08620211c0e720d6066  pyzmq-19.0.0.tar.gz
 >
 > ~/Downloads/SageMath/build/pkgs/pyzmq$ md5sum checksums.ini
 > eaae91b6017353df47f8f4f1415c07d7  checksums.ini

 I talked about the contents of  checksums.ini, i.e.

 tarball=pyzmq-VERSION.tar.gz
 sha1=b84077344ed67649f34d4af8f619d96acbd03e73
 md5=4650e45ebcf8e08620211c0e720d6066
 cksum=2135729608

 not its own md5sum. Anyhow, it appears that everything is OK, and the
 build should use the copy
 in ~/Downloads/SageMath/upstream/

 What happens if you just run

 make

 ?

 Are you able to build any other packages? Where have you go the source 
 from?
 via git? if yes, what tag and from where, if tarball, where from?
 What (Linux?) system are you using?



 >
 >
 >
 > On Thursday, March 12, 2020 at 6:24:43 PM UTC+5:30, Dima Pasechnik wrote:
 >>
 >> Have you placed
 >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
 >> (using wget, say)
 >> into  /home/diveshcode/Downlo

Re: [sage-devel] Error building sage

2020-03-12 Thread DIVESH KUMAR
I used git pull and then make worked fine.
However upon starting this message is displayed

SageMath version 9.1.beta7, Release Date: 2020-03-08   │
│ Using Python 3.7.3. Type "help()" for help.│
└┘
┏┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗┛
  ***   Warning: not enough memory, new PARI stack 1286025216

what does  Warning: not enough memory, new PARI stack 1286025216 mean?





On Thursday, March 12, 2020 at 9:02:00 PM UTC+5:30, Dima Pasechnik wrote:
>
> the md5 in your checksum.ini does not match the (correct) md5 of the tar 
> file.
>
> I gues that your git branch is 
> somehow inconsistent.
> What is the output of 
>
> git status
>
> ?
>
> if you wanted to build the development branch you needed to do
>
> git checkout develop
>
>
>
>
> On Thu, 12 Mar 2020, 15:24 DIVESH KUMAR,  > wrote:
>
>> First of all, I thank you for your prompt replies and please spare me for 
>> my mistakes as I am a beginner.
>>
>> *Contents of checksum.ini*
>>
>>> tarball=pyzmq-VERSION.tar.gz
>>>
>>> sha1=64799b73d6109fb6da5b7deb6101ba13cd7fe885
>>>
>>> md5=3c8039d007bbbd08a2275f52f5dc9a35
>>>
>>> cksum=1455168757
>>>
>>>
>> * make command returns this*
>>
>>> configure: error: 
>>> "/home/diveshcode/Downloads/SageMath/build/pkgs/sage_conf/type" is missing.
>>
>> If you would like to try to build Sage anyway (to help porting),
>>
>> export the variable 'SAGE_PORT' to something non-empty.
>>
>> Makefile:39: recipe for target 'build/make/Makefile' failed
>>
>> make[1]: *** [build/make/Makefile] Error 1
>>
>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>>
>> Makefile:31: recipe for target 'base-toolchain' failed
>>
>> make: *** [base-toolchain] Error 2
>>
>>  
>>
>>>  
>>
>> upon doing 
>> export SAGE_PORT=1
>> make
>> the error returned is 
>>
>>> Error building Sage.
>>>
>>>
 The following package(s) may have failed to build (not necessarily
>>>
>>> during this run of 'make all-start'):
>>>
>>>
 * package: pyzmq-19.0.0
>>>
>>>   log file: 
 /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>>>
>>>   build directory: 
 /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>>>
>>> make[1]: *** [all-start] Error 1
>>>
>>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>>>
>>> Makefile:13: recipe for target 'all' failed
>>>
>>> make: *** [all] e 2
>>>
>>>
>>>  
>>
>> I have cloned the git repository from  git://git.sagemath.org//sage.git
>>
>> I am using Ubuntu 18.04.
>>
>> As I haven't done any signification modifications can I clone sage again 
>> and link it with my trac account(which is already linked to the current 
>> directory).
>>
>>
>> Thank you for your time.
>> Cheers.
>>
>> On Thursday, March 12, 2020 at 8:24:48 PM UTC+5:30, Dima Pasechnik wrote:
>>>
>>> On Thu, Mar 12, 2020 at 2:02 PM DIVESH KUMAR 
>>>  wrote: 
>>> > 
>>> > ~/Downloads/SageMath/upstream$ md5sum pyzmq-19.0.0.tar.gz 
>>> > 4650e45ebcf8e08620211c0e720d6066  pyzmq-19.0.0.tar.gz 
>>> > 
>>> > ~/Downloads/SageMath/build/pkgs/pyzmq$ md5sum checksums.ini 
>>> > eaae91b6017353df47f8f4f1415c07d7  checksums.ini 
>>>
>>> I talked about the contents of  checksums.ini, i.e. 
>>>
>>> tarball=pyzmq-VERSION.tar.gz 
>>> sha1=b84077344ed67649f34d4af8f619d96acbd03e73 
>>> md5=4650e45ebcf8e08620211c0e720d6066 
>>> cksum=2135729608 
>>>
>>> not its own md5sum. Anyhow, it appears that everything is OK, and the 
>>> build should use the copy 
>>> in ~/Downloads/SageMath/upstream/ 
>>>
>>> What happens if you just run 
>>>
>>> make 
>>>
>>> ? 
>>>
>>> Are you able to build any other packages? Where have you go the source 
>>> from? 
>>> via git? if yes, what tag and from where, if tarball, where from? 
>>> What (Linux?) system are you using? 
>>>
>>>
>>>
>>> > 
>>> > 
>>> > 
>>> > On Thursday, March 12, 2020 at 6:24:43 PM UTC+5:30, Dima Pasechnik 
>>> wrote: 
>>> >> 
>>> >> Have you placed 
>>> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz 
>>> >> (using wget, say) 
>>> >> into  /home/diveshcode/Downloads/SageMath/upstream/ 
>>> >> ? 
>>> >> 
>>> >> As far as I can see from the attached log, you did not. 
>>> >> (What's strange that the 1st line of this file normally should say 
>>> >> Found local metadata for pyzmq-19.0.0) 
>>> >> 
>>> >> If it's there, please compute it's md5sum and compare it with one in 
>>> >> 
>>> >> /home/diveshcode/Dow

Re: [sage-devel] Error building sage

2020-03-12 Thread Dima Pasechnik
the md5 in your checksum.ini does not match the (correct) md5 of the tar
file.

I gues that your git branch is
somehow inconsistent.
What is the output of

git status

?

if you wanted to build the development branch you needed to do

git checkout develop




On Thu, 12 Mar 2020, 15:24 DIVESH KUMAR, 
wrote:

> First of all, I thank you for your prompt replies and please spare me for
> my mistakes as I am a beginner.
>
> *Contents of checksum.ini*
>
>> tarball=pyzmq-VERSION.tar.gz
>>
>> sha1=64799b73d6109fb6da5b7deb6101ba13cd7fe885
>>
>> md5=3c8039d007bbbd08a2275f52f5dc9a35
>>
>> cksum=1455168757
>>
>>
> * make command returns this*
>
>> configure: error:
>> "/home/diveshcode/Downloads/SageMath/build/pkgs/sage_conf/type" is missing.
>
> If you would like to try to build Sage anyway (to help porting),
>
> export the variable 'SAGE_PORT' to something non-empty.
>
> Makefile:39: recipe for target 'build/make/Makefile' failed
>
> make[1]: *** [build/make/Makefile] Error 1
>
> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>
> Makefile:31: recipe for target 'base-toolchain' failed
>
> make: *** [base-toolchain] Error 2
>
>
>
>>
>
> upon doing
> export SAGE_PORT=1
> make
> the error returned is
>
>> Error building Sage.
>>
>>
>>> The following package(s) may have failed to build (not necessarily
>>
>> during this run of 'make all-start'):
>>
>>
>>> * package: pyzmq-19.0.0
>>
>>   log file: /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>>
>>   build directory:
>>> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>>
>> make[1]: *** [all-start] Error 1
>>
>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>>
>> Makefile:13: recipe for target 'all' failed
>>
>> make: *** [all] e 2
>>
>>
>>
>
> I have cloned the git repository from  git://git.sagemath.org//sage.git
>
> I am using Ubuntu 18.04.
>
> As I haven't done any signification modifications can I clone sage again
> and link it with my trac account(which is already linked to the current
> directory).
>
>
> Thank you for your time.
> Cheers.
>
> On Thursday, March 12, 2020 at 8:24:48 PM UTC+5:30, Dima Pasechnik wrote:
>>
>> On Thu, Mar 12, 2020 at 2:02 PM DIVESH KUMAR
>>  wrote:
>> >
>> > ~/Downloads/SageMath/upstream$ md5sum pyzmq-19.0.0.tar.gz
>> > 4650e45ebcf8e08620211c0e720d6066  pyzmq-19.0.0.tar.gz
>> >
>> > ~/Downloads/SageMath/build/pkgs/pyzmq$ md5sum checksums.ini
>> > eaae91b6017353df47f8f4f1415c07d7  checksums.ini
>>
>> I talked about the contents of  checksums.ini, i.e.
>>
>> tarball=pyzmq-VERSION.tar.gz
>> sha1=b84077344ed67649f34d4af8f619d96acbd03e73
>> md5=4650e45ebcf8e08620211c0e720d6066
>> cksum=2135729608
>>
>> not its own md5sum. Anyhow, it appears that everything is OK, and the
>> build should use the copy
>> in ~/Downloads/SageMath/upstream/
>>
>> What happens if you just run
>>
>> make
>>
>> ?
>>
>> Are you able to build any other packages? Where have you go the source
>> from?
>> via git? if yes, what tag and from where, if tarball, where from?
>> What (Linux?) system are you using?
>>
>>
>>
>> >
>> >
>> >
>> > On Thursday, March 12, 2020 at 6:24:43 PM UTC+5:30, Dima Pasechnik
>> wrote:
>> >>
>> >> Have you placed
>> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
>> >> (using wget, say)
>> >> into  /home/diveshcode/Downloads/SageMath/upstream/
>> >> ?
>> >>
>> >> As far as I can see from the attached log, you did not.
>> >> (What's strange that the 1st line of this file normally should say
>> >> Found local metadata for pyzmq-19.0.0)
>> >>
>> >> If it's there, please compute it's md5sum and compare it with one in
>> >>
>> >> /home/diveshcode/Downloads/SageMath/build/pkgs/pyzmq/checksums.ini
>> >>
>> >>
>> >>
>> >> On Thu, Mar 12, 2020 at 12:32 PM DIVESH KUMAR
>> >>  wrote:
>> >> >
>> >> > Issue is still there any clue what to do ?
>> >> >
>> >> > On Thursday, March 12, 2020 at 2:09:46 PM UTC+5:30, Dima Pasechnik
>> wrote:
>> >> >>
>> >> >> You may try to copy the file
>> >> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
>> >> >> to upstream/ directory in your Sage directory, and try building
>> again.
>> >> >>
>> >> >> I guess it could be a firewall issue, preventing package downloads.
>> >> >>
>> >> >>
>> >> >> On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR
>> >> >>  wrote:
>> >> >> >
>> >> >> > On trying the make command this error is shown.
>> >> >> >>>
>> >> >> >>> ***
>> >> >> >>>
>> >> >> >>> Error building Sage.
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> The following package(s) may have failed to build (not
>> necessarily

Re: [sage-devel] Error building sage

2020-03-12 Thread DIVESH KUMAR
First of all, I thank you for your prompt replies and please spare me for 
my mistakes as I am a beginner.

*Contents of checksum.ini*

> tarball=pyzmq-VERSION.tar.gz
>
> sha1=64799b73d6109fb6da5b7deb6101ba13cd7fe885
>
> md5=3c8039d007bbbd08a2275f52f5dc9a35
>
> cksum=1455168757
>
>
* make command returns this*

> configure: error: 
> "/home/diveshcode/Downloads/SageMath/build/pkgs/sage_conf/type" is missing.

If you would like to try to build Sage anyway (to help porting),

export the variable 'SAGE_PORT' to something non-empty.

Makefile:39: recipe for target 'build/make/Makefile' failed

make[1]: *** [build/make/Makefile] Error 1

make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'

Makefile:31: recipe for target 'base-toolchain' failed

make: *** [base-toolchain] Error 2

 

>  

upon doing 
export SAGE_PORT=1
make
the error returned is 

> Error building Sage.
>
>
>> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
>> * package: pyzmq-19.0.0
>
>   log file: /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>
>   build directory: 
>> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>
> make[1]: *** [all-start] Error 1
>
> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>
> Makefile:13: recipe for target 'all' failed
>
> make: *** [all] e 2
>
>
>  

I have cloned the git repository from  git://git.sagemath.org//sage.git

I am using Ubuntu 18.04.

As I haven't done any signification modifications can I clone sage again 
and link it with my trac account(which is already linked to the current 
directory).


Thank you for your time.
Cheers.

On Thursday, March 12, 2020 at 8:24:48 PM UTC+5:30, Dima Pasechnik wrote:
>
> On Thu, Mar 12, 2020 at 2:02 PM DIVESH KUMAR 
> > wrote: 
> > 
> > ~/Downloads/SageMath/upstream$ md5sum pyzmq-19.0.0.tar.gz 
> > 4650e45ebcf8e08620211c0e720d6066  pyzmq-19.0.0.tar.gz 
> > 
> > ~/Downloads/SageMath/build/pkgs/pyzmq$ md5sum checksums.ini 
> > eaae91b6017353df47f8f4f1415c07d7  checksums.ini 
>
> I talked about the contents of  checksums.ini, i.e. 
>
> tarball=pyzmq-VERSION.tar.gz 
> sha1=b84077344ed67649f34d4af8f619d96acbd03e73 
> md5=4650e45ebcf8e08620211c0e720d6066 
> cksum=2135729608 
>
> not its own md5sum. Anyhow, it appears that everything is OK, and the 
> build should use the copy 
> in ~/Downloads/SageMath/upstream/ 
>
> What happens if you just run 
>
> make 
>
> ? 
>
> Are you able to build any other packages? Where have you go the source 
> from? 
> via git? if yes, what tag and from where, if tarball, where from? 
> What (Linux?) system are you using? 
>
>
>
> > 
> > 
> > 
> > On Thursday, March 12, 2020 at 6:24:43 PM UTC+5:30, Dima Pasechnik 
> wrote: 
> >> 
> >> Have you placed 
> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz 
> >> (using wget, say) 
> >> into  /home/diveshcode/Downloads/SageMath/upstream/ 
> >> ? 
> >> 
> >> As far as I can see from the attached log, you did not. 
> >> (What's strange that the 1st line of this file normally should say 
> >> Found local metadata for pyzmq-19.0.0) 
> >> 
> >> If it's there, please compute it's md5sum and compare it with one in 
> >> 
> >> /home/diveshcode/Downloads/SageMath/build/pkgs/pyzmq/checksums.ini 
> >> 
> >> 
> >> 
> >> On Thu, Mar 12, 2020 at 12:32 PM DIVESH KUMAR 
> >>  wrote: 
> >> > 
> >> > Issue is still there any clue what to do ? 
> >> > 
> >> > On Thursday, March 12, 2020 at 2:09:46 PM UTC+5:30, Dima Pasechnik 
> wrote: 
> >> >> 
> >> >> You may try to copy the file 
> >> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz 
> >> >> to upstream/ directory in your Sage directory, and try building 
> again. 
> >> >> 
> >> >> I guess it could be a firewall issue, preventing package downloads. 
> >> >> 
> >> >> 
> >> >> On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR 
> >> >>  wrote: 
> >> >> > 
> >> >> > On trying the make command this error is shown. 
> >> >> >>> 
> >> >> >>> *** 
> >> >> >>> 
> >> >> >>> Error building Sage. 
> >> >> >>> 
> >> >> >>> 
> >> >> >>> The following package(s) may have failed to build (not 
> necessarily 
> >> >> >>> 
> >> >> >>> during this run of 'make all-start'): 
> >> >> >>> 
> >> >> >>> 
> >> >> >>> * package: pyzmq-19.0.0 
> >> >> >>> 
> >> >> >>>   log file: 
> /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log 
> >> >> >>> 
> >> >> >>>   build directory: 
> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.0 
> >> >> >>> 
> >> >> >>> 
> >> >> >>> The build directory may contain 

Re: [sage-devel] Error building sage

2020-03-12 Thread Dima Pasechnik
On Thu, Mar 12, 2020 at 2:02 PM DIVESH KUMAR
 wrote:
>
> ~/Downloads/SageMath/upstream$ md5sum pyzmq-19.0.0.tar.gz
> 4650e45ebcf8e08620211c0e720d6066  pyzmq-19.0.0.tar.gz
>
> ~/Downloads/SageMath/build/pkgs/pyzmq$ md5sum checksums.ini
> eaae91b6017353df47f8f4f1415c07d7  checksums.ini

I talked about the contents of  checksums.ini, i.e.

tarball=pyzmq-VERSION.tar.gz
sha1=b84077344ed67649f34d4af8f619d96acbd03e73
md5=4650e45ebcf8e08620211c0e720d6066
cksum=2135729608

not its own md5sum. Anyhow, it appears that everything is OK, and the
build should use the copy
in ~/Downloads/SageMath/upstream/

What happens if you just run

make

?

Are you able to build any other packages? Where have you go the source from?
via git? if yes, what tag and from where, if tarball, where from?
What (Linux?) system are you using?



>
>
>
> On Thursday, March 12, 2020 at 6:24:43 PM UTC+5:30, Dima Pasechnik wrote:
>>
>> Have you placed
>> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
>> (using wget, say)
>> into  /home/diveshcode/Downloads/SageMath/upstream/
>> ?
>>
>> As far as I can see from the attached log, you did not.
>> (What's strange that the 1st line of this file normally should say
>> Found local metadata for pyzmq-19.0.0)
>>
>> If it's there, please compute it's md5sum and compare it with one in
>>
>> /home/diveshcode/Downloads/SageMath/build/pkgs/pyzmq/checksums.ini
>>
>>
>>
>> On Thu, Mar 12, 2020 at 12:32 PM DIVESH KUMAR
>>  wrote:
>> >
>> > Issue is still there any clue what to do ?
>> >
>> > On Thursday, March 12, 2020 at 2:09:46 PM UTC+5:30, Dima Pasechnik wrote:
>> >>
>> >> You may try to copy the file
>> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
>> >> to upstream/ directory in your Sage directory, and try building again.
>> >>
>> >> I guess it could be a firewall issue, preventing package downloads.
>> >>
>> >>
>> >> On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR
>> >>  wrote:
>> >> >
>> >> > On trying the make command this error is shown.
>> >> >>>
>> >> >>> ***
>> >> >>>
>> >> >>> Error building Sage.
>> >> >>>
>> >> >>>
>> >> >>> The following package(s) may have failed to build (not necessarily
>> >> >>>
>> >> >>> during this run of 'make all-start'):
>> >> >>>
>> >> >>>
>> >> >>> * package: pyzmq-19.0.0
>> >> >>>
>> >> >>>   log file: 
>> >> >>> /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>> >> >>>
>> >> >>>   build directory: 
>> >> >>> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>> >> >>>
>> >> >>> make[1]: *** [all-start] Error 1
>> >> >>>
>> >> >>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>> >> >>>
>> >> >>> Makefile:13: recipe for target 'all' failed
>> >> >>>
>> >> >>> make: *** [all] Error 2
>> >> >>
>> >> >>
>> >> >
>> >> > What should I do in this case?
>> >> > Thank you for your time. Cheers.
>> >> >
>> >> >
>> >> > --
>> >> > 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/a764f2ac-7ca5-46b5-981a-c4e71159c43b%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/75b20680-723f-4e17-9888-ab2e977478c9%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/9349a43d-479d-46e0-a92f-14553a2498a8%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/CAAWYfq1BAXitbNWrou8Ph4qzrwXdurHuWsFaMfEL4_DaWOjf5Q%40mail.gmail.com.


Re: [sage-devel] Error building sage

2020-03-12 Thread DIVESH KUMAR
~/Downloads/SageMath/upstream$ md5sum pyzmq-19.0.0.tar.gz 
*4650e45ebcf8e08620211c0e720d6066  pyzmq-19.0.0.tar.gz*

~/Downloads/SageMath/build/pkgs/pyzmq$ md5sum checksums.ini 
*eaae91b6017353df47f8f4f1415c07d7  checksums.ini*



On Thursday, March 12, 2020 at 6:24:43 PM UTC+5:30, Dima Pasechnik wrote:
>
> Have you placed 
> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz 
> (using wget, say) 
> into  /home/diveshcode/Downloads/SageMath/upstream/ 
> ? 
>
> As far as I can see from the attached log, you did not. 
> (What's strange that the 1st line of this file normally should say 
> Found local metadata for pyzmq-19.0.0) 
>
> If it's there, please compute it's md5sum and compare it with one in 
>
> /home/diveshcode/Downloads/SageMath/build/pkgs/pyzmq/checksums.ini 
>
>
>
> On Thu, Mar 12, 2020 at 12:32 PM DIVESH KUMAR 
> > wrote: 
> > 
> > Issue is still there any clue what to do ? 
> > 
> > On Thursday, March 12, 2020 at 2:09:46 PM UTC+5:30, Dima Pasechnik 
> wrote: 
> >> 
> >> You may try to copy the file 
> >> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz 
> >> to upstream/ directory in your Sage directory, and try building again. 
> >> 
> >> I guess it could be a firewall issue, preventing package downloads. 
> >> 
> >> 
> >> On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR 
> >>  wrote: 
> >> > 
> >> > On trying the make command this error is shown. 
> >> >>> 
> >> >>> *** 
> >> >>> 
> >> >>> Error building Sage. 
> >> >>> 
> >> >>> 
> >> >>> The following package(s) may have failed to build (not necessarily 
> >> >>> 
> >> >>> during this run of 'make all-start'): 
> >> >>> 
> >> >>> 
> >> >>> * package: pyzmq-19.0.0 
> >> >>> 
> >> >>>   log file: 
> /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log 
> >> >>> 
> >> >>>   build directory: 
> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed 
> >> >>> 
> >> >>> make[1]: *** [all-start] Error 1 
> >> >>> 
> >> >>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath' 
> >> >>> 
> >> >>> Makefile:13: recipe for target 'all' failed 
> >> >>> 
> >> >>> make: *** [all] Error 2 
> >> >> 
> >> >> 
> >> > 
> >> > What should I do in this case? 
> >> > Thank you for your time. Cheers. 
> >> > 
> >> > 
> >> > -- 
> >> > 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/a764f2ac-7ca5-46b5-981a-c4e71159c43b%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/75b20680-723f-4e17-9888-ab2e977478c9%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/9349a43d-479d-46e0-a92f-14553a2498a8%40googlegroups.com.


Re: [sage-devel] Error building sage

2020-03-12 Thread Dima Pasechnik
Have you placed
http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
(using wget, say)
into  /home/diveshcode/Downloads/SageMath/upstream/
?

As far as I can see from the attached log, you did not.
(What's strange that the 1st line of this file normally should say
Found local metadata for pyzmq-19.0.0)

If it's there, please compute it's md5sum and compare it with one in

/home/diveshcode/Downloads/SageMath/build/pkgs/pyzmq/checksums.ini



On Thu, Mar 12, 2020 at 12:32 PM DIVESH KUMAR
 wrote:
>
> Issue is still there any clue what to do ?
>
> On Thursday, March 12, 2020 at 2:09:46 PM UTC+5:30, Dima Pasechnik wrote:
>>
>> You may try to copy the file
>> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
>> to upstream/ directory in your Sage directory, and try building again.
>>
>> I guess it could be a firewall issue, preventing package downloads.
>>
>>
>> On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR
>>  wrote:
>> >
>> > On trying the make command this error is shown.
>> >>>
>> >>> ***
>> >>>
>> >>> Error building Sage.
>> >>>
>> >>>
>> >>> The following package(s) may have failed to build (not necessarily
>> >>>
>> >>> during this run of 'make all-start'):
>> >>>
>> >>>
>> >>> * package: pyzmq-19.0.0
>> >>>
>> >>>   log file: 
>> >>> /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>> >>>
>> >>>   build directory: 
>> >>> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>> >>>
>> >>> make[1]: *** [all-start] Error 1
>> >>>
>> >>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>> >>>
>> >>> Makefile:13: recipe for target 'all' failed
>> >>>
>> >>> make: *** [all] Error 2
>> >>
>> >>
>> >
>> > What should I do in this case?
>> > Thank you for your time. Cheers.
>> >
>> >
>> > --
>> > 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/a764f2ac-7ca5-46b5-981a-c4e71159c43b%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/75b20680-723f-4e17-9888-ab2e977478c9%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/CAAWYfq0ASWgW%3DT9EH3AXjT%2BC%3DXTF-%2BegwJrWXPy67pGQtd%2Bk9Q%40mail.gmail.com.


Re: [sage-devel] Error building sage

2020-03-12 Thread DIVESH KUMAR
Issue is still there any clue what to do ?

On Thursday, March 12, 2020 at 2:09:46 PM UTC+5:30, Dima Pasechnik wrote:
>
> You may try to copy the file 
> http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz 
> to upstream/ directory in your Sage directory, and try building again. 
>
> I guess it could be a firewall issue, preventing package downloads. 
>
>
> On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR 
> > wrote: 
> > 
> > On trying the make command this error is shown. 
> >>> 
> >>> *** 
> >>> 
> >>> Error building Sage. 
> >>> 
> >>> 
> >>> The following package(s) may have failed to build (not necessarily 
> >>> 
> >>> during this run of 'make all-start'): 
> >>> 
> >>> 
> >>> * package: pyzmq-19.0.0 
> >>> 
> >>>   log file: 
> /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log 
> >>> 
> >>>   build directory: 
> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed 
> >>> 
> >>> make[1]: *** [all-start] Error 1 
> >>> 
> >>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath' 
> >>> 
> >>> Makefile:13: recipe for target 'all' failed 
> >>> 
> >>> make: *** [all] Error 2 
> >> 
> >> 
> > 
> > What should I do in this case? 
> > Thank you for your time. Cheers. 
> > 
> > 
> > -- 
> > 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/a764f2ac-7ca5-46b5-981a-c4e71159c43b%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/75b20680-723f-4e17-9888-ab2e977478c9%40googlegroups.com.
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/
Attempting to download pa

Re: [sage-devel] Error building sage

2020-03-12 Thread Dima Pasechnik
You may try to copy the file
http://files.sagemath.org/spkg/upstream/pyzmq/pyzmq-19.0.0.tar.gz
to upstream/ directory in your Sage directory, and try building again.

I guess it could be a firewall issue, preventing package downloads.


On Thu, Mar 12, 2020 at 8:27 AM DIVESH KUMAR
 wrote:
>
> On trying the make command this error is shown.
>>>
>>> ***
>>>
>>> Error building Sage.
>>>
>>>
>>> The following package(s) may have failed to build (not necessarily
>>>
>>> during this run of 'make all-start'):
>>>
>>>
>>> * package: pyzmq-19.0.0
>>>
>>>   log file: /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>>>
>>>   build directory: 
>>> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>>>
>>> make[1]: *** [all-start] Error 1
>>>
>>> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>>>
>>> Makefile:13: recipe for target 'all' failed
>>>
>>> make: *** [all] Error 2
>>
>>
>
> What should I do in this case?
> Thank you for your time. Cheers.
>
>
> --
> 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/a764f2ac-7ca5-46b5-981a-c4e71159c43b%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/CAAWYfq2FiiAG-VOFPaXs14xTefvE9FLkpfZjQ%2BtfmgoALci_Lw%40mail.gmail.com.


[sage-devel] Error building sage

2020-03-12 Thread DIVESH KUMAR
On trying the make command this error is shown.
>
> ***
>
> Error building Sage.
>
>
>> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
>> * package: pyzmq-19.0.0
>
>   log file: /home/diveshcode/Downloads/SageMath/logs/pkgs/pyzmq-19.0.0.log
>
>   build directory: 
>> /home/diveshcode/Downloads/SageMath/local/var/tmp/sage/build/pyzmq-19.0.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-start' failed
>
> make[1]: *** [all-start] Error 1
>
> make[1]: Leaving directory '/home/diveshcode/Downloads/SageMath'
>
> Makefile:13: recipe for target 'all' failed
>
> make: *** [all] Error 2
>
>
>
What should I do in this case?
Thank you for your time. Cheers.
 

-- 
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/a764f2ac-7ca5-46b5-981a-c4e71159c43b%40googlegroups.com.
Attempting to download package pyzmq-19.0.0
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
Error: could not find a package matching pyzmq-19.0.0
   Try 'sage --package list' to see the available packages
   There is no package similar to pyzmq-19.0.0
You can find further packages at http://files.sagemath.org/spkg/


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

2020-03-05 Thread Arnald Dutta
I was facing issues while installing gfortran. I reinstalled all the 
packages and ran all the commands as instructed in the FAQ: building Sage 
on debian or ubuntu to build sage.
And now it is working fine.
Thank you, sir


On Thursday, 5 March 2020 13:20:57 UTC+5:30, Dima Pasechnik wrote:
>
> It looks as if you didn't have gfortran installed.
> Any reason for that?
>
> On Thu, 5 Mar 2020, 05:40 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/86632ba7-bc85-4e19-ad18-6a6dda5320f7%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/d6c19b2e-f80f-4005-b7cf-7081608eef29%40googlegroups.com.


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

2020-03-04 Thread Dima Pasechnik
It looks as if you didn't have gfortran installed.
Any reason for that?

On Thu, 5 Mar 2020, 05:40 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/86632ba7-bc85-4e19-ad18-6a6dda5320f7%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/CAAWYfq0w3Hk6Un4nAspQ%3DFLvtmKHsjOUn-SSWyttUWsn9VuaXQ%40mail.gmail.com.


Re: [sage-devel] Error Building Sage

2020-02-23 Thread Volker Braun
Python picks up the wrong readline, is there stuff in /usr/local?



On Sunday, February 23, 2020 at 8:23:42 AM UTC+1, Tanav Shah wrote:
>
> Hi
>
> I tried building the sage module in the internal wsl file system and it 
> seems to be working better than before, but still there are a couple of 
> errors. It says
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: gap-4.10.2.p1
>   log file: /home/tanav/sage-9.0/logs/pkgs/gap-4.10.2.p1.log
>   build directory: 
> /home/tanav/sage-9.0/SAGE_LOCAL/var/tmp/sage/build/gap-4.10.2.p1
>
> * package: python3-3.7.3.p1
>   log file: /home/tanav/sage-9.0/logs/pkgs/python3-3.7.3.p1.log
>   build directory: 
> /home/tanav/sage-9.0/SAGE_LOCAL/var/tmp/sage/build/python3-3.7.3.p1
>
> After this it terminates building. I have attached the log files here. Can 
> you please help me out with this?
>
> Thanks in advance.
>
> Tanav Shah
>
> On Sunday, February 23, 2020 at 4:50:33 AM UTC+5:30, Volker Braun wrote:
>>
>> I've built Sage in WSL before, its really a pretty standard Ubuntu.
>>
>> OP's problem is that he's building it on /mnt/c/, the mounted windows 
>> filesystem. That one is not POSIX so there is little chance. You have to 
>> build it on the internal WSL filesystem, which is fully POSIX compatible.
>>
>>
>>
>> On Saturday, February 22, 2020 at 8:17:26 PM UTC+1, Dima Pasechnik wrote:
>>>
>>> I don't think anyone managed to build Sage on WSL.
>>>
>>>
>>> On Sat, 22 Feb 2020, 19:47 Tanav Shah,  wrote:
>>>
 Hi

 I have downloaded the source code for SageMath from 
 https://www.sagemath.org/download-source.html and am willing to 
 contribute for the same. I have been following the steps provided in this 
 page 
 http://doc.sagemath.org/html/en/installation/source.html#prerequisites, 
 but am getting an error while building.

 When running the 'make' command, I get an error that "[arb-2.16.0.p0] 
 spkg-install should not be marked executable in the build/pkgs directory" 
 and it displays "Error building Sage". I have been trying to find a 
 solution to it but have not found one. I am working on HP-SPECTRE with 
 Windows-10 Home installed in it. I am using Windows Subsytem for 
 Linux(WSL) 
 Ubuntu 18.04 LTS for executing the commands. I have attached the error log 
 files.

 Can someone please help me solve this issue?

 Thanks in advance,
 Tanav Shah

 -- 
 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/cd9d5155-d82b-4e99-9b65-654d423c6671%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/50f75886-e7bb-4fe3-a50a-7ba0aa3f5c76%40googlegroups.com.


Re: [sage-devel] Error Building Sage

2020-02-22 Thread Volker Braun
I've built Sage in WSL before, its really a pretty standard Ubuntu.

OP's problem is that he's building it on /mnt/c/, the mounted windows 
filesystem. That one is not POSIX so there is little chance. You have to 
build it on the internal WSL filesystem, which is fully POSIX compatible.



On Saturday, February 22, 2020 at 8:17:26 PM UTC+1, Dima Pasechnik wrote:
>
> I don't think anyone managed to build Sage on WSL.
>
>
> On Sat, 22 Feb 2020, 19:47 Tanav Shah, > 
> wrote:
>
>> Hi
>>
>> I have downloaded the source code for SageMath from 
>> https://www.sagemath.org/download-source.html and am willing to 
>> contribute for the same. I have been following the steps provided in this 
>> page 
>> http://doc.sagemath.org/html/en/installation/source.html#prerequisites, 
>> but am getting an error while building.
>>
>> When running the 'make' command, I get an error that "[arb-2.16.0.p0] 
>> spkg-install should not be marked executable in the build/pkgs directory" 
>> and it displays "Error building Sage". I have been trying to find a 
>> solution to it but have not found one. I am working on HP-SPECTRE with 
>> Windows-10 Home installed in it. I am using Windows Subsytem for Linux(WSL) 
>> Ubuntu 18.04 LTS for executing the commands. I have attached the error log 
>> files.
>>
>> Can someone please help me solve this issue?
>>
>> Thanks in advance,
>> Tanav Shah
>>
>> -- 
>> 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/cd9d5155-d82b-4e99-9b65-654d423c6671%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/fbf2ef82-1e8d-4994-bfd4-d4e683f4f67d%40googlegroups.com.


Re: [sage-devel] Error Building Sage

2020-02-22 Thread Dima Pasechnik
I don't think anyone managed to build Sage on WSL.


On Sat, 22 Feb 2020, 19:47 Tanav Shah,  wrote:

> Hi
>
> I have downloaded the source code for SageMath from
> https://www.sagemath.org/download-source.html and am willing to
> contribute for the same. I have been following the steps provided in this
> page
> http://doc.sagemath.org/html/en/installation/source.html#prerequisites,
> but am getting an error while building.
>
> When running the 'make' command, I get an error that "[arb-2.16.0.p0]
> spkg-install should not be marked executable in the build/pkgs directory"
> and it displays "Error building Sage". I have been trying to find a
> solution to it but have not found one. I am working on HP-SPECTRE with
> Windows-10 Home installed in it. I am using Windows Subsytem for Linux(WSL)
> Ubuntu 18.04 LTS for executing the commands. I have attached the error log
> files.
>
> Can someone please help me solve this issue?
>
> Thanks in advance,
> Tanav Shah
>
> --
> 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/cd9d5155-d82b-4e99-9b65-654d423c6671%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/CAAWYfq3pH0ayUASL9zmKaxVrMYmKOtFdGR1a1KG4mbFh%3DqnmZA%40mail.gmail.com.


[sage-devel] Error Building Sage

2020-02-22 Thread Tanav Shah
Hi

I have downloaded the source code for SageMath from 
https://www.sagemath.org/download-source.html and am willing to contribute 
for the same. I have been following the steps provided in this page 
http://doc.sagemath.org/html/en/installation/source.html#prerequisites, but 
am getting an error while building.

When running the 'make' command, I get an error that "[arb-2.16.0.p0] 
spkg-install should not be marked executable in the build/pkgs directory" 
and it displays "Error building Sage". I have been trying to find a 
solution to it but have not found one. I am working on HP-SPECTRE with 
Windows-10 Home installed in it. I am using Windows Subsytem for Linux(WSL) 
Ubuntu 18.04 LTS for executing the commands. I have attached the error log 
files.

Can someone please help me solve this issue?

Thanks in advance,
Tanav Shah

-- 
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/cd9d5155-d82b-4e99-9b65-654d423c6671%40googlegroups.com.
Found local metadata for arb-2.16.0.p0
Using cached file 
/mnt/c/Tanav/GSoc2020/SageMath/sage-9.0/upstream/arb-2.16.0.tar.gz
arb-2.16.0.p0

Setting up build directory for arb-2.16.0.p0
Finished extraction
No patch files found in ../patches

spkg-install should not be marked executable in the build/pkgs directory

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /mnt/c/Tanav/GSoc2020/SageMath/sage-9.0/logs/pkgs/arb-2.16.0.p0.log
Describe your computer, operating system, etc.

Found local metadata for arb-2.16.0.p0
Using cached file 
/mnt/c/Tanav/GSoc2020/SageMath/sage-9.0/upstream/arb-2.16.0.tar.gz
arb-2.16.0.p0

Setting up build directory for arb-2.16.0.p0
Finished extraction
No patch files found in ../patches

spkg-install should not be marked executable in the build/pkgs directory

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /mnt/c/Tanav/GSoc2020/SageMath/sage-9.0/logs/pkgs/arb-2.16.0.p0.log
Describe your computer, operating system, etc.

Found local metadata for arb-2.16.0.p0
Using cached file 
/mnt/c/Tanav/GSoc2020/SageMath/sage-9.0/upstream/arb-2.16.0.tar.gz
arb-2.16.0.p0

Setting up build directory for arb-2.16.0.p0
Finished extraction
No patch files found in ../patches

spkg-install should not be marked executable in the build/pkgs directory

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /mnt/c/Tanav/GSoc2020/SageMath/sage-9.0/logs/pkgs/arb-2.16.0.p0.log
Describe your computer, operating system, etc.



Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-02-01 Thread Markus Wageringel
Rather than unsetting TERM, you could add set enable-meta-key off to your 
.inputrc file to solve this. I had the same problem here 
.


Am Freitag, 31. Januar 2020 23:26:17 UTC+1 schrieb Josh Bevan:
>
> I "unset TERM" and that worked, currently a hundred something tests deep 
> with no failures.
>
> Thanks again for your help!
> Josh
>

-- 
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/a19edb5b-9a1a-45e4-8373-eb812e5abdd9%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Josh Bevan
I "unset TERM" and that worked, currently a hundred something tests deep 
with no failures.

Thanks again for your help!
Josh

On Friday, January 31, 2020 at 5:11:50 PM UTC-5, Dima Pasechnik wrote:
>
> On Fri, Jan 31, 2020 at 10:04 PM Josh Bevan > 
> wrote: 
> > On Friday, January 31, 2020 at 4:00:34 PM UTC-5, Dima Pasechnik wrote: 
> >> 
> >> On Fri, Jan 31, 2020 at 8:47 PM Josh Bevan  wrote: 
> >> > I'm able to load up sage and do the simple suggested "2+2" and 
> "factor(2005)". 
> >> > However when I do 
> >> > [jbevan@scc-he1 sage-9.0]$ sage --testall 
> >> > 
> >> > I get: 
> >> > no stored timings available 
> >> > Running doctests with ID 2020-01-31-13-28-13-f917e3d0. 
> >> > Git branch: develop 
> >> > Using --optional=build,dochtml,memlimit,mpir,sage 
> >> > Doctesting entire Sage library. 
> >> > Doctesting 3796 files. 
> >> > sage -t src/sage/__init__.py 
> >> > [11 tests, 0.05 s] 
> >> > sage -t src/sage/env.py 
> >> > [44 tests, 0.36 s] 
> >> > sage -t src/sage/all.py 
> >> > [16 tests, 1.34 s] 
> >> > sage -t src/sage/version.py 
> >> > [0 tests, 0.00 s] 
> >> > sage -t src/sage/all_cmdline.py 
> >> > [0 tests, 0.00 s] 
> >> > sage -t src/sage/all_notebook.py 
> >> > [0 tests, 0.00 s] 
> >> > sage -t src/sage/monoids/automatic_semigroup.py 
> >> > 
> ** 
> >> > File "src/sage/monoids/automatic_semigroup.py", line 156, in 
> sage.monoids.automatic_semigroup.AutomaticSemigroup 
> >> > Failed example: 
> >> > N.cardinality() == G5.cardinality() 
> >> > Expected: 
> >> > True 
> >> > Got: 
> >> > True 
> >> 
> >> This must be something funny with locale, or terminal, or shell... 
> >> How exactly are you accessing the node? 
> > 
> > 
> > The cluster runs Sun Grid Engine (SGE). I ssh into the cluster to the 
> login node using MobaXterm v12.4 from Windows 10. Then I "qrsh" into a 
> compute node with an interactive shell and "module load sagemath"; this 
> uses Lmod to load a modulefile.lua which contains: 
> > local root = pathJoin("/share/pkg.7",myModuleName(),myModuleVersion()) 
> > local base = 
> pathJoin("/share/pkg.7",myModuleName(),myModuleVersion(),"install") 
> > 
> > setenv("SAGE_ROOT", pathJoin(root,"src/sage-9.0")) 
> > setenv("SAGE_LOCAL",base) 
> > setenv("SCC_SAGEMATH_DIR",  base) 
> > setenv("SCC_SAGEMATH_BIN",  pathJoin(base,"bin")) 
> > 
> > prepend_path("PATH",pathJoin(base,"bin")) 
> > 
> > Then I just execute "sage --testall" from the shell on the compute node. 
> > 
> > If you like I can log the tests to a file and upload it. The only other 
> salient fact I noticed is that on any given failure only 1 of the tests 
> fails with the extra "" garbage. 
>
> I found an old ticket where some CSI- garbage was mentioned: 
> https://trac.sagemath.org/ticket/14370 
> The solution there was to unset environment variable TERM 
>
> Perhaps that's the cause here too, in particular given that you ssh 
> from Windows... 
>

-- 
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/4f487090-1f8d-4119-ae94-ad19ddd01ff1%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Dima Pasechnik
On Fri, Jan 31, 2020 at 10:11 PM Dima Pasechnik  wrote:
>
> On Fri, Jan 31, 2020 at 10:04 PM Josh Bevan  wrote:
> >
> >
> >
> > On Friday, January 31, 2020 at 4:00:34 PM UTC-5, Dima Pasechnik wrote:
> >>
> >> On Fri, Jan 31, 2020 at 8:47 PM Josh Bevan  wrote:
> >> > I'm able to load up sage and do the simple suggested "2+2" and 
> >> > "factor(2005)".
> >> > However when I do
> >> > [jbevan@scc-he1 sage-9.0]$ sage --testall
> >> >
> >> > I get:
> >> > no stored timings available
> >> > Running doctests with ID 2020-01-31-13-28-13-f917e3d0.
> >> > Git branch: develop
> >> > Using --optional=build,dochtml,memlimit,mpir,sage
> >> > Doctesting entire Sage library.
> >> > Doctesting 3796 files.
> >> > sage -t src/sage/__init__.py
> >> > [11 tests, 0.05 s]
> >> > sage -t src/sage/env.py
> >> > [44 tests, 0.36 s]
> >> > sage -t src/sage/all.py
> >> > [16 tests, 1.34 s]
> >> > sage -t src/sage/version.py
> >> > [0 tests, 0.00 s]
> >> > sage -t src/sage/all_cmdline.py
> >> > [0 tests, 0.00 s]
> >> > sage -t src/sage/all_notebook.py
> >> > [0 tests, 0.00 s]
> >> > sage -t src/sage/monoids/automatic_semigroup.py
> >> > **
> >> > File "src/sage/monoids/automatic_semigroup.py", line 156, in 
> >> > sage.monoids.automatic_semigroup.AutomaticSemigroup
> >> > Failed example:
> >> > N.cardinality() == G5.cardinality()
> >> > Expected:
> >> > True
> >> > Got:
> >> > True
> >>
> >> This must be something funny with locale, or terminal, or shell...
> >> How exactly are you accessing the node?
> >
> >
> > The cluster runs Sun Grid Engine (SGE). I ssh into the cluster to the login 
> > node using MobaXterm v12.4 from Windows 10. Then I "qrsh" into a compute 
> > node with an interactive shell and "module load sagemath"; this uses Lmod 
> > to load a modulefile.lua which contains:
> > local root = pathJoin("/share/pkg.7",myModuleName(),myModuleVersion())
> > local base = 
> > pathJoin("/share/pkg.7",myModuleName(),myModuleVersion(),"install")
> >
> > setenv("SAGE_ROOT", pathJoin(root,"src/sage-9.0"))
> > setenv("SAGE_LOCAL",base)
> > setenv("SCC_SAGEMATH_DIR",  base)
> > setenv("SCC_SAGEMATH_BIN",  pathJoin(base,"bin"))
> >
> > prepend_path("PATH",pathJoin(base,"bin"))
> >
> > Then I just execute "sage --testall" from the shell on the compute node.
> >
> > If you like I can log the tests to a file and upload it. The only other 
> > salient fact I noticed is that on any given failure only 1 of the tests 
> > fails with the extra "" garbage.
>
> I found an old ticket where some CSI- garbage was mentioned:
> https://trac.sagemath.org/ticket/14370
> The solution there was to unset environment variable TERM
>
> Perhaps that's the cause here too, in particular given that you ssh
> from Windows...
>
once logged one, you might try setting TERM to "v100" or "xterm"


> >
> >
> > --
> > 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/097d0cdf-296f-4a0a-b007-d2c7cacf51e2%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/CAAWYfq3aqoZGx_u8nt10_vPVHstrUOLOJ%2BTcNajYZ-cWMdWRVA%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Dima Pasechnik
On Fri, Jan 31, 2020 at 10:04 PM Josh Bevan  wrote:
>
>
>
> On Friday, January 31, 2020 at 4:00:34 PM UTC-5, Dima Pasechnik wrote:
>>
>> On Fri, Jan 31, 2020 at 8:47 PM Josh Bevan  wrote:
>> > I'm able to load up sage and do the simple suggested "2+2" and 
>> > "factor(2005)".
>> > However when I do
>> > [jbevan@scc-he1 sage-9.0]$ sage --testall
>> >
>> > I get:
>> > no stored timings available
>> > Running doctests with ID 2020-01-31-13-28-13-f917e3d0.
>> > Git branch: develop
>> > Using --optional=build,dochtml,memlimit,mpir,sage
>> > Doctesting entire Sage library.
>> > Doctesting 3796 files.
>> > sage -t src/sage/__init__.py
>> > [11 tests, 0.05 s]
>> > sage -t src/sage/env.py
>> > [44 tests, 0.36 s]
>> > sage -t src/sage/all.py
>> > [16 tests, 1.34 s]
>> > sage -t src/sage/version.py
>> > [0 tests, 0.00 s]
>> > sage -t src/sage/all_cmdline.py
>> > [0 tests, 0.00 s]
>> > sage -t src/sage/all_notebook.py
>> > [0 tests, 0.00 s]
>> > sage -t src/sage/monoids/automatic_semigroup.py
>> > **
>> > File "src/sage/monoids/automatic_semigroup.py", line 156, in 
>> > sage.monoids.automatic_semigroup.AutomaticSemigroup
>> > Failed example:
>> > N.cardinality() == G5.cardinality()
>> > Expected:
>> > True
>> > Got:
>> > True
>>
>> This must be something funny with locale, or terminal, or shell...
>> How exactly are you accessing the node?
>
>
> The cluster runs Sun Grid Engine (SGE). I ssh into the cluster to the login 
> node using MobaXterm v12.4 from Windows 10. Then I "qrsh" into a compute node 
> with an interactive shell and "module load sagemath"; this uses Lmod to load 
> a modulefile.lua which contains:
> local root = pathJoin("/share/pkg.7",myModuleName(),myModuleVersion())
> local base = 
> pathJoin("/share/pkg.7",myModuleName(),myModuleVersion(),"install")
>
> setenv("SAGE_ROOT", pathJoin(root,"src/sage-9.0"))
> setenv("SAGE_LOCAL",base)
> setenv("SCC_SAGEMATH_DIR",  base)
> setenv("SCC_SAGEMATH_BIN",  pathJoin(base,"bin"))
>
> prepend_path("PATH",pathJoin(base,"bin"))
>
> Then I just execute "sage --testall" from the shell on the compute node.
>
> If you like I can log the tests to a file and upload it. The only other 
> salient fact I noticed is that on any given failure only 1 of the tests fails 
> with the extra "" garbage.

I found an old ticket where some CSI- garbage was mentioned:
https://trac.sagemath.org/ticket/14370
The solution there was to unset environment variable TERM

Perhaps that's the cause here too, in particular given that you ssh
from Windows...

>
>
> --
> 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/097d0cdf-296f-4a0a-b007-d2c7cacf51e2%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/CAAWYfq1EW2E1gLMYPT3ijP-GbjOE8oEEgiu-kzHF9KfgPyRkYA%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Josh Bevan


On Friday, January 31, 2020 at 4:00:34 PM UTC-5, Dima Pasechnik wrote:
>
> On Fri, Jan 31, 2020 at 8:47 PM Josh Bevan > 
> wrote: 
> > I'm able to load up sage and do the simple suggested "2+2" and 
> "factor(2005)". 
> > However when I do 
> > [jbevan@scc-he1 sage-9.0]$ sage --testall 
> > 
> > I get: 
> > no stored timings available 
> > Running doctests with ID 2020-01-31-13-28-13-f917e3d0. 
> > Git branch: develop 
> > Using --optional=build,dochtml,memlimit,mpir,sage 
> > Doctesting entire Sage library. 
> > Doctesting 3796 files. 
> > sage -t src/sage/__init__.py 
> > [11 tests, 0.05 s] 
> > sage -t src/sage/env.py 
> > [44 tests, 0.36 s] 
> > sage -t src/sage/all.py 
> > [16 tests, 1.34 s] 
> > sage -t src/sage/version.py 
> > [0 tests, 0.00 s] 
> > sage -t src/sage/all_cmdline.py 
> > [0 tests, 0.00 s] 
> > sage -t src/sage/all_notebook.py 
> > [0 tests, 0.00 s] 
> > sage -t src/sage/monoids/automatic_semigroup.py 
> > ** 
> > File "src/sage/monoids/automatic_semigroup.py", line 156, in 
> sage.monoids.automatic_semigroup.AutomaticSemigroup 
> > Failed example: 
> > N.cardinality() == G5.cardinality() 
> > Expected: 
> > True 
> > Got: 
> > True 
>
> This must be something funny with locale, or terminal, or shell... 
> How exactly are you accessing the node? 
>

The cluster runs Sun Grid Engine (SGE). I ssh into the cluster to the login 
node using MobaXterm v12.4 from Windows 10. Then I "qrsh" into a compute 
node with an interactive shell and "module load sagemath"; this uses Lmod 
to load a modulefile.lua which contains:
*local root = pathJoin("/share/pkg.7",myModuleName(),myModuleVersion())*
*local base = 
pathJoin("/share/pkg.7",myModuleName(),myModuleVersion(),"install")*

*setenv("SAGE_ROOT", pathJoin(root,"src/sage-9.0"))*
*setenv("SAGE_LOCAL",base)*
*setenv("SCC_SAGEMATH_DIR",  base)*
*setenv("SCC_SAGEMATH_BIN",  pathJoin(base,"bin"))*

*prepend_path("PATH",pathJoin(base,"bin"))*

Then I just execute "sage --testall" from the shell on the compute node.

If you like I can log the tests to a file and upload it. The only other 
salient fact I noticed is that on any given failure only 1 of the tests 
fails with the extra "" garbage.


-- 
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/097d0cdf-296f-4a0a-b007-d2c7cacf51e2%40googlegroups.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Dima Pasechnik
On Fri, Jan 31, 2020 at 8:47 PM Josh Bevan  wrote:
>
> Thanks for the help so far; a couple comments/questions:
> The "spkg-configure.m4" for sqlite worked and was able to use an installed 
> version, but I then got the same error with brial-1.2.5 which also does not 
> recognize the --disable-maintainer-mode option. I suspect continuing down 
> this route would just be playing whack-a-mole with packages that do not 
> recognize that option.
>
> The installation is indeed happening over a networked filesystem, so I get 
> how timestamps may not match. It *is* possible to build from a local disk 
> from a particular node (/scratch as noted). After reading more carefully 
> through the install instructions I noted:
> "Note that once you have built Sage (by running make, as described below), 
> you will not be able to move or rename its directory without likely breaking 
> Sage."
>
> Ok, so I can't actually have it put the built install on /scratch and move it 
> where I want after. Then I noted:
> "SAGE_BUILD_DIR - the default behavior is to build each spkg in a 
> subdirectory of $SAGE_ROOT/... If this variable is set, then build in 
> $SAGE_BUILD_DIR/... instead"
> "By default, `make install' will install all the files in ...  You can 
> specify an installation prefix other than ... using `--prefix', for instance 
> `--prefix=$HOME'."
>
> So I set the build dir on /scratch too and set "prefix" to be the correct 
> final install location.

Good!

> The install failed part-way through again with:
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: pari_seadata_small-20090618.p0
>   log file: 
> /scratch/sage/sage-9.0/logs/pkgs/pari_seadata_small-20090618.p0.log
>   build directory: /scratch/sageb/pari_seadata_small-20090618.p0
>
> The log file was empty, hmm. So I just simply ran make again on the hopes 
> that some transient issue popped up. This time it successfully installed.
>
> I'm able to load up sage and do the simple suggested "2+2" and "factor(2005)".
> However when I do
> [jbevan@scc-he1 sage-9.0]$ sage --testall
>
> I get:
> no stored timings available
> Running doctests with ID 2020-01-31-13-28-13-f917e3d0.
> Git branch: develop
> Using --optional=build,dochtml,memlimit,mpir,sage
> Doctesting entire Sage library.
> Doctesting 3796 files.
> sage -t src/sage/__init__.py
> [11 tests, 0.05 s]
> sage -t src/sage/env.py
> [44 tests, 0.36 s]
> sage -t src/sage/all.py
> [16 tests, 1.34 s]
> sage -t src/sage/version.py
> [0 tests, 0.00 s]
> sage -t src/sage/all_cmdline.py
> [0 tests, 0.00 s]
> sage -t src/sage/all_notebook.py
> [0 tests, 0.00 s]
> sage -t src/sage/monoids/automatic_semigroup.py
> **
> File "src/sage/monoids/automatic_semigroup.py", line 156, in 
> sage.monoids.automatic_semigroup.AutomaticSemigroup
> Failed example:
> N.cardinality() == G5.cardinality()
> Expected:
> True
> Got:
> True

This must be something funny with locale, or terminal, or shell...
How exactly are you accessing the node?


> **
> 1 item had failures:
>1 of  80 in sage.monoids.automatic_semigroup.AutomaticSemigroup
> [268 tests, 1 failure, 1.28 s]
>
> It continues on with more tests, most of which pass and maybe 1 in 10-20 have 
> a failure. They all look like:
> Expected:
> n^2*log(x)
> Got:
> n^2*log(x)
> and
> Expected:
>  pi*x
> e
> Got:
>  pi*x
> e
>
> It seems that these test actually are passing, but some garbage is 
> pre-pended. What's causing this, and should I care (i.e. will it affect 
> normal Sage usage)?
>
> Thanks!
> Josh
>
> On Friday, January 31, 2020 at 6:13:05 AM UTC-5, Dima Pasechnik wrote:
>>
>> On Fri, Jan 31, 2020 at 3:20 AM Isuru Fernando  wrote:
>> >
>> > > " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
>> > > unimportant since it's followed with the text "You only need it if..." 
>> > > with reasons that don't pertain to me.
>> >
>> > One possible reason is that somehow the timestamps for the files got 
>> > messed up. Easiest solution would be to install automake 1.15. You can 
>> > also do a make clean and try again.
>> >
>> if you have or can install sqlite development package on your system, then 
>> the current Sage beta (9.1.beta2) already has mechanisms to use it, instead 
>> of building its own. You can actually don't need to switch from your 9.0, 
>> just save
>> https://git.sagemath.org/sage.git/plain/build/pkgs/sqlite/spkg-configure.m4?id=3f9ef468a2a708f7c3607ed4200c912bba50f93d
>> to build/pkgs/sqlite/spkg-configure.m4
>> run
>> ./boostrap # needs autotools installed
>> ./configure
>>
>> and in the output of the latter you'd see
>>
>> sqlite-329 will not be installed (configure check)
>>
>> > Isuru
>> >
>> > On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan  wrote:

Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Josh Bevan
Thanks for the help so far; a couple comments/questions:
The "spkg-configure.m4" for sqlite worked and was able to use an installed 
version, but I then got the same error with brial-1.2.5 which also does not 
recognize the --disable-maintainer-mode option. I suspect continuing down 
this route would just be playing whack-a-mole with packages that do not 
recognize that option.

The installation is indeed happening over a networked filesystem, so I get 
how timestamps may not match. It *is* possible to build from a local disk 
from a particular node (/scratch as noted). After reading more carefully 
through the install instructions I noted:
"Note that once you have built Sage (by running make, as described below), 
you will not be able to move or rename its directory without likely 
breaking Sage."

Ok, so I can't actually have it put the built install on /scratch and move 
it where I want after. Then I noted:
"SAGE_BUILD_DIR - the default behavior is to build each spkg in a 
subdirectory of $SAGE_ROOT/... If this variable is set, then build in 
$SAGE_BUILD_DIR/... instead"
"By default, `make install' will install all the files in ...  You can 
specify an installation prefix other than ... using `--prefix', for 
instance `--prefix=$HOME'."

So I set the build dir on /scratch too and set "prefix" to be the correct 
final install location. The install failed part-way through again with:
*Error building Sage.*

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

** package: pari_seadata_small-20090618.p0*
*  log file: 
/scratch/sage/sage-9.0/logs/pkgs/pari_seadata_small-20090618.p0.log*
*  build directory: /scratch/sageb/pari_seadata_small-20090618.p0*

The log file was empty, hmm. So I just simply ran make again on the hopes 
that some transient issue popped up. This time it successfully installed.

I'm able to load up sage and do the simple suggested "2+2" and 
"factor(2005)".
However when I do 
*[jbevan@scc-he1 sage-9.0]$ sage --testall*

I get:
*no stored timings available*
*Running doctests with ID 2020-01-31-13-28-13-f917e3d0.*
*Git branch: develop*
*Using --optional=build,dochtml,memlimit,mpir,sage*
*Doctesting entire Sage library.*
*Doctesting 3796 files.*
*sage -t src/sage/__init__.py*
*[11 tests, 0.05 s]*
*sage -t src/sage/env.py*
*[44 tests, 0.36 s]*
*sage -t src/sage/all.py*
*[16 tests, 1.34 s]*
*sage -t src/sage/version.py*
*[0 tests, 0.00 s]*
*sage -t src/sage/all_cmdline.py*
*[0 tests, 0.00 s]*
*sage -t src/sage/all_notebook.py*
*[0 tests, 0.00 s]*
*sage -t src/sage/monoids/automatic_semigroup.py*

*File "src/sage/monoids/automatic_semigroup.py", line 156, in 
sage.monoids.automatic_semigroup.AutomaticSemigroup*
*Failed example:*
*N.cardinality() == G5.cardinality()*
*Expected:*
*True*
*Got:*
*True*

*1 item had failures:*
*   1 of  80 in sage.monoids.automatic_semigroup.AutomaticSemigroup*
*[268 tests, 1 failure, 1.28 s]*

It continues on with more tests, most of which pass and maybe 1 in 10-20 
have a failure. They all look like:
*Expected:*
*n^2*log(x)*
*Got:*
*n^2*log(x)*
and
*Expected:*
* pi*x*
*e*
*Got:*
* pi*x*
*e*

It seems that these test actually are passing, but some garbage is 
pre-pended. What's causing this, and should I care (i.e. will it affect 
normal Sage usage)?

Thanks!
Josh

On Friday, January 31, 2020 at 6:13:05 AM UTC-5, Dima Pasechnik wrote:
>
> On Fri, Jan 31, 2020 at 3:20 AM Isuru Fernando  > wrote: 
> > 
> > > " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
> unimportant since it's followed with the text "You only need it if..." with 
> reasons that don't pertain to me. 
> > 
> > One possible reason is that somehow the timestamps for the files got 
> messed up. Easiest solution would be to install automake 1.15. You can also 
> do a make clean and try again. 
> > 
> if you have or can install sqlite development package on your system, then 
> the current Sage beta (9.1.beta2) already has mechanisms to use it, instead 
> of building its own. You can actually don't need to switch from your 9.0, 
> just save 
>
> https://git.sagemath.org/sage.git/plain/build/pkgs/sqlite/spkg-configure.m4?id=3f9ef468a2a708f7c3607ed4200c912bba50f93d
>  
> to build/pkgs/sqlite/spkg-configure.m4 
> run 
> ./boostrap # needs autotools installed 
> ./configure 
>
> and in the output of the latter you'd see 
>
> sqlite-329 will not be installed (configure check) 
>
> > Isuru 
> > 
> > On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan > 
> wrote: 
> >> I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it 
> fails with: 
> >> "Error installing package sqlite-329" 
> >> Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that 
> the error message says to include: 
> >> https://pastebin.

Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Dima Pasechnik
On Fri, Jan 31, 2020 at 3:20 AM Isuru Fernando  wrote:
>
> > " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
> > unimportant since it's followed with the text "You only need it if..." with 
> > reasons that don't pertain to me.
>
> One possible reason is that somehow the timestamps for the files got messed 
> up. Easiest solution would be to install automake 1.15. You can also do a 
> make clean and try again.
>

if you have or can install sqlite development package on your system,
then the current Sage beta (9.1.beta2) already has mechanisms to use
it, instead of building its own.
You can actually don't need to switch from your 9.0, just save
https://git.sagemath.org/sage.git/plain/build/pkgs/sqlite/spkg-configure.m4?id=3f9ef468a2a708f7c3607ed4200c912bba50f93d
to build/pkgs/sqlite/spkg-configure.m4
run
./boostrap # needs autotools installed
./configure

and in the output of the latter you'd see

sqlite-329 will not be installed (configure check)




> Isuru
>
> On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan  wrote:
>>
>> Hello,
>>
>> I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails 
>> with:
>> "Error installing package sqlite-329"
>> Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the 
>> error message says to include:
>> https://pastebin.com/SCy98UXK
>>
>> The two main messages that jump out to me are:
>> "configure: WARNING: unrecognized options: --disable-maintainer-mode" I had 
>> seen that option listed in a post from a decade ago as a solution to a Sage 
>> Sqlite build error, although I doubt that is still relevant
>> and
>> " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
>> unimportant since it's followed with the text "You only need it if..." with 
>> reasons that don't pertain to me.
>>
>> For some additional context:
>> This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod 
>> for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0 
>> (OpenBLAS alternative with better performance) modules loaded, any other 
>> dependencies (e.g. Perl) I've left as the system defaults and they have not 
>> been overridden by the module system. I unpacked the zip and simply ran 
>> "make" with no additional messing with config or modifications.
>>
>> If there is any additional info I should supply that would prove helpful 
>> feel free to let me know.
>>
>> Thanks!
>> Josh
>>
>> --
>> 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/98041908-f9f6-47d6-9885-6126dffab1d9%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/CA%2B01voNFFxY7CzwPgbOUHQ6_m%2Bp-DCCECTy6hMDSZhZbrqywZQ%40mail.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3eeADPcH4OPA_ePPewTy-FfQA0JXONn%3DTWZMfQ-SrPfQ%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Dima Pasechnik
cf https://trac.sagemath.org/ticket/28511

On Fri, Jan 31, 2020 at 8:37 AM Dima Pasechnik  wrote:
>
> On Fri, Jan 31, 2020 at 3:20 AM Isuru Fernando  wrote:
> >
> > > " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
> > > unimportant since it's followed with the text "You only need it if..." 
> > > with reasons that don't pertain to me.
> >
> > One possible reason is that somehow the timestamps for the files got messed 
> > up. Easiest solution would be to install automake 1.15. You can also do a 
> > make clean and try again.
> >
> > Isuru
> >
> > On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan  wrote:
> >>
> >> Hello,
> >>
> >> I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails 
> >> with:
> >> "Error installing package sqlite-329"
> >> Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the 
> >> error message says to include:
> >> https://pastebin.com/SCy98UXK
> >>
> >> The two main messages that jump out to me are:
> >> "configure: WARNING: unrecognized options: --disable-maintainer-mode" I 
> >> had seen that option listed in a post from a decade ago as a solution to a 
> >> Sage Sqlite build error, although I doubt that is still relevant
> >> and
> >> " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
> >> unimportant since it's followed with the text "You only need it if..." 
> >> with reasons that don't pertain to me.
> >>
> >> For some additional context:
> >> This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod 
> >> for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0 
> >> (OpenBLAS alternative with better performance) modules loaded, any other 
> >> dependencies (e.g. Perl) I've left as the system defaults and they have 
> >> not been overridden by the module system. I unpacked the zip and simply 
> >> ran "make" with no additional messing with config or modifications.
>
> by default (without  --disable-maintainer-mode - which sadly is not
> understood by sqlite) autconf-generated config scripts are very
> sensitite to timestamps, and Lmod is not fast enough,
> apparently, to make it work.
>
> Can you do the build and work on a local disk?
> ("scratch partition", that's how cluster people call them, I gather)
>
>
>
> >>
> >> If there is any additional info I should supply that would prove helpful 
> >> feel free to let me know.
> >>
> >> Thanks!
> >> Josh
> >>
> >> --
> >> 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/98041908-f9f6-47d6-9885-6126dffab1d9%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/CA%2B01voNFFxY7CzwPgbOUHQ6_m%2Bp-DCCECTy6hMDSZhZbrqywZQ%40mail.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1MX7vohvw1%2BrMYWzo2BFTnNW4AhEQiFfTNSw1w34-MpQ%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-31 Thread Dima Pasechnik
On Fri, Jan 31, 2020 at 3:20 AM Isuru Fernando  wrote:
>
> > " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
> > unimportant since it's followed with the text "You only need it if..." with 
> > reasons that don't pertain to me.
>
> One possible reason is that somehow the timestamps for the files got messed 
> up. Easiest solution would be to install automake 1.15. You can also do a 
> make clean and try again.
>
> Isuru
>
> On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan  wrote:
>>
>> Hello,
>>
>> I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails 
>> with:
>> "Error installing package sqlite-329"
>> Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the 
>> error message says to include:
>> https://pastebin.com/SCy98UXK
>>
>> The two main messages that jump out to me are:
>> "configure: WARNING: unrecognized options: --disable-maintainer-mode" I had 
>> seen that option listed in a post from a decade ago as a solution to a Sage 
>> Sqlite build error, although I doubt that is still relevant
>> and
>> " WARNING: 'aclocal-1.15' is missing on your system." Which seems 
>> unimportant since it's followed with the text "You only need it if..." with 
>> reasons that don't pertain to me.
>>
>> For some additional context:
>> This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod 
>> for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0 
>> (OpenBLAS alternative with better performance) modules loaded, any other 
>> dependencies (e.g. Perl) I've left as the system defaults and they have not 
>> been overridden by the module system. I unpacked the zip and simply ran 
>> "make" with no additional messing with config or modifications.

by default (without  --disable-maintainer-mode - which sadly is not
understood by sqlite) autconf-generated config scripts are very
sensitite to timestamps, and Lmod is not fast enough,
apparently, to make it work.

Can you do the build and work on a local disk?
("scratch partition", that's how cluster people call them, I gather)



>>
>> If there is any additional info I should supply that would prove helpful 
>> feel free to let me know.
>>
>> Thanks!
>> Josh
>>
>> --
>> 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/98041908-f9f6-47d6-9885-6126dffab1d9%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/CA%2B01voNFFxY7CzwPgbOUHQ6_m%2Bp-DCCECTy6hMDSZhZbrqywZQ%40mail.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq10Y%2BPMbev0%2BZYcx2B-Ev5QZB8HUqKFzQ9UKcG8VMpbSw%40mail.gmail.com.


Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-30 Thread Isuru Fernando
> " WARNING: 'aclocal-1.15' is missing on your system." Which seems
unimportant since it's followed with the text "You only need it if..." with
reasons that don't pertain to me.

One possible reason is that somehow the timestamps for the files got messed
up. Easiest solution would be to install automake 1.15. You can also do a
make clean and try again.

Isuru

On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan  wrote:

> Hello,
>
> I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails
> with:
> "Error installing package sqlite-329"
> Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the
> error message says to include:
> https://pastebin.com/SCy98UXK
>
> The two main messages that jump out to me are:
> "configure: WARNING: unrecognized options: --disable-maintainer-mode" I
> had seen that option listed in a post from a decade ago as a solution to a
> Sage Sqlite build error, although I doubt that is still relevant
> and
> " WARNING: 'aclocal-1.15' is missing on your system." Which seems
> unimportant since it's followed with the text "You only need it if..." with
> reasons that don't pertain to me.
>
> For some additional context:
> This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod
> for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0
> (OpenBLAS alternative with better performance) modules loaded, any other
> dependencies (e.g. Perl) I've left as the system defaults and they have not
> been overridden by the module system. I unpacked the zip and simply ran
> "make" with no additional messing with config or modifications.
>
> If there is any additional info I should supply that would prove helpful
> feel free to let me know.
>
> Thanks!
> Josh
>
> --
> 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/98041908-f9f6-47d6-9885-6126dffab1d9%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/CA%2B01voNFFxY7CzwPgbOUHQ6_m%2Bp-DCCECTy6hMDSZhZbrqywZQ%40mail.gmail.com.


[sage-devel] Error building Sage 9.0 on CentOS 7.5

2020-01-30 Thread Josh Bevan
Hello,

I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails 
with:
"Error installing package sqlite-329"
Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the 
error message says to include:
https://pastebin.com/SCy98UXK

The two main messages that jump out to me are:
"configure: WARNING: unrecognized options: --disable-maintainer-mode" I had 
seen that option listed in a post from a decade ago as a solution to a Sage 
Sqlite build error, although I doubt that is still relevant
and
" WARNING: 'aclocal-1.15' is missing on your system." Which seems 
unimportant since it's followed with the text "You only need it if..." with 
reasons that don't pertain to me.

For some additional context:
This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod 
for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0 
(OpenBLAS alternative with better performance) modules loaded, any other 
dependencies (e.g. Perl) I've left as the system defaults and they have not 
been overridden by the module system. I unpacked the zip and simply ran 
"make" with no additional messing with config or modifications.

If there is any additional info I should supply that would prove helpful 
feel free to let me know.

Thanks!
Josh

-- 
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/98041908-f9f6-47d6-9885-6126dffab1d9%40googlegroups.com.


Re: [sage-devel] Error building sage while installing r-3.6.2

2020-01-29 Thread Dima Pasechnik
On Wed, Jan 29, 2020 at 7:55 AM 'Jonathan Kliem' via sage-devel
 wrote:
>
> Hello,
>
> I'm having trouble installing R with the newest beta on
>
> Ubuntu 18.04.3 LTS, using
> gcc 7.4.0
>
> The log file has a bunch of messages of this type
>
> 2301 ../../src/include/R_ext/BLAS.h:103:55: error: expected declaration 
> specifiers or '...' before ')' token
> 2302const double *beta, double *y, const int *incy FCLEN);
>
this is Fortran compiler problem.

There is no need to install R on ubuntu, you can use the system one.
See the list of packages to install:
https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation

there was a regression in this support in the latest beta, you actually need
https://trac.sagemath.org/ticket/29051 to fix it

HTH

> I attached the log file.
>
> Jonathan
>
> --
> 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/97b00f2d-cc09-47cf-8bd1-9a9c34094089%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/CAAWYfq3hx7_r4QD9S56DCjdGPRuPPLO-N96-eQ3-NRErPP-FAQ%40mail.gmail.com.


[sage-devel] Error building sage while installing r-3.6.2

2020-01-28 Thread 'Jonathan Kliem' via sage-devel
Hello,

I'm having trouble installing R with the newest beta on

Ubuntu 18.04.3 LTS, using
gcc 7.4.0

The log file has a bunch of messages of this type

2301 ../../src/include/R_ext/BLAS.h:103:55: error: expected declaration 
specifiers or '...' before ')' token
2302const double *beta, double *y, const int *incy FCLEN);

I attached the log file.

Jonathan

-- 
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/97b00f2d-cc09-47cf-8bd1-9a9c34094089%40googlegroups.com.
Found local metadata for r-3.6.2
Attempting to download package R-3.6.2.tar.gz from mirrors
https://mirror.koddos.net/sagemath/spkg/upstream/r/R-3.6.2.tar.gz
[..]
r-3.6.2

Setting up build directory for r-3.6.2
Finished extraction
Applying patches from ../patches...
Applying ../patches/autoconf_verb_dash.patch
patching file configure
Hunk #1 succeeded at 24966 with fuzz 2 (offset 129 lines).
Hunk #2 succeeded at 25323 (offset 130 lines).
Applying ../patches/cygwin_build_support.patch
patching file configure
Hunk #1 succeeded at 27637 (offset -86 lines).
Hunk #2 succeeded at 27879 (offset -117 lines).
Hunk #3 succeeded at 27892 (offset -117 lines).
Hunk #4 succeeded at 27905 (offset -117 lines).
patching file configure.ac
Hunk #1 succeeded at 1280 (offset -14 lines).
Hunk #2 succeeded at 1537 (offset -14 lines).
Hunk #3 succeeded at 1549 (offset -14 lines).
Hunk #4 succeeded at 1561 (offset -14 lines).
patching file src/library/tools/R/install.R
Hunk #1 succeeded at 1215 (offset 374 lines).
Applying ../patches/hardcoded_dirs.patch
patching file src/scripts/Makefile.in
Hunk #1 succeeded at 87 (offset -2 lines).
patching file src/scripts/R.sh.in
Applying ../patches/libcurl_https_support.patch
patching file configure
Hunk #1 succeeded at 42943 (offset 1874 lines).
Hunk #2 succeeded at 42952 (offset 1874 lines).
patching file m4/R.m4
Hunk #1 succeeded at 4181 (offset -24 lines).
Applying ../patches/link_all_shared_libs.patch
patching file etc/Makeconf.in
Hunk #1 succeeded at 159 with fuzz 2 (offset 9 lines).
Applying ../patches/m4_macro_bug.patch
patching file configure
Hunk #1 succeeded at 42543 (offset 1744 lines).
Hunk #2 succeeded at 42587 with fuzz 2 (offset 1744 lines).
patching file m4/R.m4
Hunk #1 succeeded at 3100 (offset -90 lines).
Hunk #2 succeeded at 3122 with fuzz 2 (offset -90 lines).
Applying ../patches/rcmd_exec.patch
patching file src/scripts/Rcmd.in

Host system:
Linux kliem-ThinkPad-L570 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 
UTC 2019 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/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) 

Warning: No files to uninstall for 'r'
Uninstalling existing 'r'
Removing stamp file 
'/home/jonathan/Applications/sage/local/var/lib/sage/installed/r-3.6.1'
R_CONFIGURE_BLAS=--with-blas=-L/home/jonathan/Applications/sage/local/lib 
-lopenblas
R_CONFIGURE_LAPACK=--with-lapack=-L/home/jonathan/Applications/sage/local/lib 
-lopenblas
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
loading site script './config.site'
loading build-specific script './config.site'
checking for pwd... /bin/pwd
checking whether builddir is srcdir... yes
checking whether ln -s wor

Re: [sage-devel] Error Building Sage

2019-06-16 Thread Alex S
Worked great. Thank you much!

On Sunday, June 16, 2019 at 7:03:59 PM UTC-4, Dima Pasechnik wrote:
>
> You are building in /Library - an unusual location. Perhaps you're 
> gotten into trouble with SIP. 
>
> Could you instead try in your home directory, or somewhere in /usr/local ? 
>
>
>
>
> On Sun, Jun 16, 2019 at 4:30 PM Alex S > 
> wrote: 
> > 
> > No unusual settings I'm aware of. Here is the new log file after running 
> that command. Thank you. 
> > 
> > On Sunday, June 16, 2019 at 4:46:43 AM UTC-4, Dima Pasechnik wrote: 
> >> 
> >> perhaps there is a race condition in the build? 
> >> Can you remove the log you have on python2 (rm logs/pkgs/python2*) and 
> >> try running 
> >> 
> >> MAKE="make -j1" ./sage -i python2 
> >> 
> >> And post the log you will get, if it still fails. 
> >> 
> >> 
> >> 
> >> On Sun, Jun 16, 2019 at 8:58 AM Dima Pasechnik  
> wrote: 
> >> > 
> >> > I don't think I even saw this - the Python build complains it cannot 
> >> > find _struct.c, _ctypes/_ctypes_test.c 
> >> > (and in fact most source files for modules) 
> >> > 
> >> > Do you have some unusual settins for the file system you are using 
> for 
> >> > the build? 
> >> > A non-standard tar program? 
> >> > 
> >> > 
> >> >  
> >> > clang -L. -L/Library/SageDev/local/lib 
> >> > -Wl,-rpath,/Library/SageDev/local/lib   -o python.exe \ 
> >> > Modules/python.o \ 
> >> > -L. -lpython2.7 -ldl  -framework CoreFoundation 
> >> > 
> DYLD_LIBRARY_PATH=/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src
>  
>
> >> > ./python.exe -E -S -m sysconfig --generate-posix-vars ;\ 
> >> > if test $? -ne 0 ; then \ 
> >> > echo "generate-posix-vars failed" ; \ 
> >> > rm -f ./pybuilddir.txt ; \ 
> >> > exit 1 ; \ 
> >> > fi 
> >> > running build 
> >> > running build_ext 
> >> > building dbm using ndbm 
> >> > building '_struct' extension 
> >> > clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
> >> > -Wno-unused -I/Library/SageDev/local/include -I. -IInclude 
> -I./Include 
> >> > -I/usr/local/include 
> >> > 
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include 
> >> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c 
> >> > _struct.c -o build/temp.macosx-10.9-x86_64-2.7/_struct.o 
> >> > clang: error: no such file or directory: '_struct.c' 
> >> > clang: error: no input files 
> >> > building '_ctypes_test' extension 
> >> > creating build/temp.macosx-10.9-x86_64-2.7/_ctypes 
> >> > clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
> >> > -Wno-unused -I/Library/SageDev/local/include -I. -IInclude 
> -I./Include 
> >> > -I/usr/local/include 
> >> > 
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include 
> >> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c 
> >> > _ctypes/_ctypes_test.c -o 
> >> > build/temp.macosx-10.9-x86_64-2.7/_ctypes/_ctypes_test.o 
> >> > clang: error: no such file or directory: '_ctypes/_ctypes_test.c' 
> >> > clang: error: no input files 
> >> > ... 
> >> > 
> >> > On Sun, Jun 16, 2019 at 7:00 AM Alex S  wrote: 
> >> > > 
> >> > > Hello, 
> >> > > 
> >> > > I am trying to build sage on my mac os 10.14.5, and am unable to 
> build the python2 and python3 packages. Running 'make' gives: 
> >> > > 
> >> > > *** 
> >> > > 
> >> > > Error building Sage. 
> >> > > 
> >> > > 
> >> > > The following package(s) may have failed to build (not necessarily 
> >> > > 
> >> > > during this run of 'make all-start'): 
> >> > > 
> >> > > 
> >> > > * package: python2-2.7.15.p1 
> >> > > 
> >> > >   log file: /Library/SageDev/logs/pkgs/python2-2.7.15.p1.log 
> >> > > 
> >> > >   build directory: 
> /Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1 
> >> > > 
> >> > > 
> >> > > * package: python3-3.7.3.p1 
> >> > > 
> >> > >   log file: /Library/SageDev/logs/pkgs/python3-3.7.3.p1.log 
> >> > > 
> >> > >   build directory: 
> /Library/SageDev/local/var/tmp/sage/build/python3-3.7.3.p1 
> >> > > 
> >> > > 
> >> > > 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[1]: *** [all-start] Error 1 
> >> > > 
> >> > > make: *** [all] Error 2 
> >> > > 
> >> > > 
> >> > > Thank you much, 
> >> > > 
> >> > > Alex 
> >> > > 
> >> > > -- 
> >> > > 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 post to this group, send email to sage-...@googlegroups.com. 
> >> > > Visit this group at https://groups.google.com/group/sage-devel. 
> >> > > To view this discu

Re: [sage-devel] Error Building Sage

2019-06-16 Thread Dima Pasechnik
You are building in /Library - an unusual location. Perhaps you're
gotten into trouble with SIP.

Could you instead try in your home directory, or somewhere in /usr/local ?




On Sun, Jun 16, 2019 at 4:30 PM Alex S  wrote:
>
> No unusual settings I'm aware of. Here is the new log file after running that 
> command. Thank you.
>
> On Sunday, June 16, 2019 at 4:46:43 AM UTC-4, Dima Pasechnik wrote:
>>
>> perhaps there is a race condition in the build?
>> Can you remove the log you have on python2 (rm logs/pkgs/python2*) and
>> try running
>>
>> MAKE="make -j1" ./sage -i python2
>>
>> And post the log you will get, if it still fails.
>>
>>
>>
>> On Sun, Jun 16, 2019 at 8:58 AM Dima Pasechnik  wrote:
>> >
>> > I don't think I even saw this - the Python build complains it cannot
>> > find _struct.c, _ctypes/_ctypes_test.c
>> > (and in fact most source files for modules)
>> >
>> > Do you have some unusual settins for the file system you are using for
>> > the build?
>> > A non-standard tar program?
>> >
>> >
>> > 
>> > clang -L. -L/Library/SageDev/local/lib
>> > -Wl,-rpath,/Library/SageDev/local/lib   -o python.exe \
>> > Modules/python.o \
>> > -L. -lpython2.7 -ldl  -framework CoreFoundation
>> > DYLD_LIBRARY_PATH=/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src
>> > ./python.exe -E -S -m sysconfig --generate-posix-vars ;\
>> > if test $? -ne 0 ; then \
>> > echo "generate-posix-vars failed" ; \
>> > rm -f ./pybuilddir.txt ; \
>> > exit 1 ; \
>> > fi
>> > running build
>> > running build_ext
>> > building dbm using ndbm
>> > building '_struct' extension
>> > clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
>> > -Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include
>> > -I/usr/local/include
>> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include
>> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c
>> > _struct.c -o build/temp.macosx-10.9-x86_64-2.7/_struct.o
>> > clang: error: no such file or directory: '_struct.c'
>> > clang: error: no input files
>> > building '_ctypes_test' extension
>> > creating build/temp.macosx-10.9-x86_64-2.7/_ctypes
>> > clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
>> > -Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include
>> > -I/usr/local/include
>> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include
>> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c
>> > _ctypes/_ctypes_test.c -o
>> > build/temp.macosx-10.9-x86_64-2.7/_ctypes/_ctypes_test.o
>> > clang: error: no such file or directory: '_ctypes/_ctypes_test.c'
>> > clang: error: no input files
>> > ...
>> >
>> > On Sun, Jun 16, 2019 at 7:00 AM Alex S  wrote:
>> > >
>> > > Hello,
>> > >
>> > > I am trying to build sage on my mac os 10.14.5, and am unable to build 
>> > > the python2 and python3 packages. Running 'make' gives:
>> > >
>> > > ***
>> > >
>> > > Error building Sage.
>> > >
>> > >
>> > > The following package(s) may have failed to build (not necessarily
>> > >
>> > > during this run of 'make all-start'):
>> > >
>> > >
>> > > * package: python2-2.7.15.p1
>> > >
>> > >   log file: /Library/SageDev/logs/pkgs/python2-2.7.15.p1.log
>> > >
>> > >   build directory: 
>> > > /Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1
>> > >
>> > >
>> > > * package: python3-3.7.3.p1
>> > >
>> > >   log file: /Library/SageDev/logs/pkgs/python3-3.7.3.p1.log
>> > >
>> > >   build directory: 
>> > > /Library/SageDev/local/var/tmp/sage/build/python3-3.7.3.p1
>> > >
>> > >
>> > > 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[1]: *** [all-start] Error 1
>> > >
>> > > make: *** [all] Error 2
>> > >
>> > >
>> > > Thank you much,
>> > >
>> > > Alex
>> > >
>> > > --
>> > > 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 post to this group, send email to sage-...@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/305e17da-b57d-4d86-bb5d-9690b86b6b6c%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-dev

Re: [sage-devel] Error Building Sage

2019-06-16 Thread Alex S
No unusual settings I'm aware of. Here is the new log file after running 
that command. Thank you.

On Sunday, June 16, 2019 at 4:46:43 AM UTC-4, Dima Pasechnik wrote:
>
> perhaps there is a race condition in the build? 
> Can you remove the log you have on python2 (rm logs/pkgs/python2*) and 
> try running 
>
> MAKE="make -j1" ./sage -i python2 
>
> And post the log you will get, if it still fails. 
>
>
>
> On Sun, Jun 16, 2019 at 8:58 AM Dima Pasechnik  > wrote: 
> > 
> > I don't think I even saw this - the Python build complains it cannot 
> > find _struct.c, _ctypes/_ctypes_test.c 
> > (and in fact most source files for modules) 
> > 
> > Do you have some unusual settins for the file system you are using for 
> > the build? 
> > A non-standard tar program? 
> > 
> > 
> >  
> > clang -L. -L/Library/SageDev/local/lib 
> > -Wl,-rpath,/Library/SageDev/local/lib   -o python.exe \ 
> > Modules/python.o \ 
> > -L. -lpython2.7 -ldl  -framework CoreFoundation 
> > 
> DYLD_LIBRARY_PATH=/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src
>  
>
> > ./python.exe -E -S -m sysconfig --generate-posix-vars ;\ 
> > if test $? -ne 0 ; then \ 
> > echo "generate-posix-vars failed" ; \ 
> > rm -f ./pybuilddir.txt ; \ 
> > exit 1 ; \ 
> > fi 
> > running build 
> > running build_ext 
> > building dbm using ndbm 
> > building '_struct' extension 
> > clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
> > -Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include 
> > -I/usr/local/include 
> > 
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include 
> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c 
> > _struct.c -o build/temp.macosx-10.9-x86_64-2.7/_struct.o 
> > clang: error: no such file or directory: '_struct.c' 
> > clang: error: no input files 
> > building '_ctypes_test' extension 
> > creating build/temp.macosx-10.9-x86_64-2.7/_ctypes 
> > clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
> > -Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include 
> > -I/usr/local/include 
> > 
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include 
> > -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c 
> > _ctypes/_ctypes_test.c -o 
> > build/temp.macosx-10.9-x86_64-2.7/_ctypes/_ctypes_test.o 
> > clang: error: no such file or directory: '_ctypes/_ctypes_test.c' 
> > clang: error: no input files 
> > ... 
> > 
> > On Sun, Jun 16, 2019 at 7:00 AM Alex S  > wrote: 
> > > 
> > > Hello, 
> > > 
> > > I am trying to build sage on my mac os 10.14.5, and am unable to build 
> the python2 and python3 packages. Running 'make' gives: 
> > > 
> > > *** 
> > > 
> > > Error building Sage. 
> > > 
> > > 
> > > The following package(s) may have failed to build (not necessarily 
> > > 
> > > during this run of 'make all-start'): 
> > > 
> > > 
> > > * package: python2-2.7.15.p1 
> > > 
> > >   log file: /Library/SageDev/logs/pkgs/python2-2.7.15.p1.log 
> > > 
> > >   build directory: 
> /Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1 
> > > 
> > > 
> > > * package: python3-3.7.3.p1 
> > > 
> > >   log file: /Library/SageDev/logs/pkgs/python3-3.7.3.p1.log 
> > > 
> > >   build directory: 
> /Library/SageDev/local/var/tmp/sage/build/python3-3.7.3.p1 
> > > 
> > > 
> > > 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[1]: *** [all-start] Error 1 
> > > 
> > > make: *** [all] Error 2 
> > > 
> > > 
> > > Thank you much, 
> > > 
> > > Alex 
> > > 
> > > -- 
> > > 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 post to this group, send email to sage-...@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/305e17da-b57d-4d86-bb5d-9690b86b6b6c%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/e3afa88e-5d62-49ca-adc3-cef8e15cf252%40googlegroups.com.
For more options, v

Re: [sage-devel] Error Building Sage

2019-06-16 Thread Dima Pasechnik
perhaps there is a race condition in the build?
Can you remove the log you have on python2 (rm logs/pkgs/python2*) and
try running

MAKE="make -j1" ./sage -i python2

And post the log you will get, if it still fails.



On Sun, Jun 16, 2019 at 8:58 AM Dima Pasechnik  wrote:
>
> I don't think I even saw this - the Python build complains it cannot
> find _struct.c, _ctypes/_ctypes_test.c
> (and in fact most source files for modules)
>
> Do you have some unusual settins for the file system you are using for
> the build?
> A non-standard tar program?
>
>
> 
> clang -L. -L/Library/SageDev/local/lib
> -Wl,-rpath,/Library/SageDev/local/lib   -o python.exe \
> Modules/python.o \
> -L. -lpython2.7 -ldl  -framework CoreFoundation
> DYLD_LIBRARY_PATH=/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src
> ./python.exe -E -S -m sysconfig --generate-posix-vars ;\
> if test $? -ne 0 ; then \
> echo "generate-posix-vars failed" ; \
> rm -f ./pybuilddir.txt ; \
> exit 1 ; \
> fi
> running build
> running build_ext
> building dbm using ndbm
> building '_struct' extension
> clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
> -Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include
> -I/usr/local/include
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c
> _struct.c -o build/temp.macosx-10.9-x86_64-2.7/_struct.o
> clang: error: no such file or directory: '_struct.c'
> clang: error: no input files
> building '_ctypes_test' extension
> creating build/temp.macosx-10.9-x86_64-2.7/_ctypes
> clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
> -Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include
> -I/usr/local/include
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include
> -I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c
> _ctypes/_ctypes_test.c -o
> build/temp.macosx-10.9-x86_64-2.7/_ctypes/_ctypes_test.o
> clang: error: no such file or directory: '_ctypes/_ctypes_test.c'
> clang: error: no input files
> ...
>
> On Sun, Jun 16, 2019 at 7:00 AM Alex S  wrote:
> >
> > Hello,
> >
> > I am trying to build sage on my mac os 10.14.5, and am unable to build the 
> > python2 and python3 packages. Running 'make' gives:
> >
> > ***
> >
> > Error building Sage.
> >
> >
> > The following package(s) may have failed to build (not necessarily
> >
> > during this run of 'make all-start'):
> >
> >
> > * package: python2-2.7.15.p1
> >
> >   log file: /Library/SageDev/logs/pkgs/python2-2.7.15.p1.log
> >
> >   build directory: 
> > /Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1
> >
> >
> > * package: python3-3.7.3.p1
> >
> >   log file: /Library/SageDev/logs/pkgs/python3-3.7.3.p1.log
> >
> >   build directory: 
> > /Library/SageDev/local/var/tmp/sage/build/python3-3.7.3.p1
> >
> >
> > 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[1]: *** [all-start] Error 1
> >
> > make: *** [all] Error 2
> >
> >
> > Thank you much,
> >
> > Alex
> >
> > --
> > 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/305e17da-b57d-4d86-bb5d-9690b86b6b6c%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/CAAWYfq2R9CkZdwfhruoANNka4ood5khA-fnX2W-FO%2ByUxOhBXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Error Building Sage

2019-06-16 Thread Dima Pasechnik
I don't think I even saw this - the Python build complains it cannot
find _struct.c, _ctypes/_ctypes_test.c
(and in fact most source files for modules)

Do you have some unusual settins for the file system you are using for
the build?
A non-standard tar program?



clang -L. -L/Library/SageDev/local/lib
-Wl,-rpath,/Library/SageDev/local/lib   -o python.exe \
Modules/python.o \
-L. -lpython2.7 -ldl  -framework CoreFoundation
DYLD_LIBRARY_PATH=/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src
./python.exe -E -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
echo "generate-posix-vars failed" ; \
rm -f ./pybuilddir.txt ; \
exit 1 ; \
fi
running build
running build_ext
building dbm using ndbm
building '_struct' extension
clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include
-I/usr/local/include
-I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include
-I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c
_struct.c -o build/temp.macosx-10.9-x86_64-2.7/_struct.o
clang: error: no such file or directory: '_struct.c'
clang: error: no input files
building '_ctypes_test' extension
creating build/temp.macosx-10.9-x86_64-2.7/_ctypes
clang -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-Wno-unused -I/Library/SageDev/local/include -I. -IInclude -I./Include
-I/usr/local/include
-I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src/Include
-I/Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1/src -c
_ctypes/_ctypes_test.c -o
build/temp.macosx-10.9-x86_64-2.7/_ctypes/_ctypes_test.o
clang: error: no such file or directory: '_ctypes/_ctypes_test.c'
clang: error: no input files
...

On Sun, Jun 16, 2019 at 7:00 AM Alex S  wrote:
>
> Hello,
>
> I am trying to build sage on my mac os 10.14.5, and am unable to build the 
> python2 and python3 packages. Running 'make' gives:
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-start'):
>
>
> * package: python2-2.7.15.p1
>
>   log file: /Library/SageDev/logs/pkgs/python2-2.7.15.p1.log
>
>   build directory: /Library/SageDev/local/var/tmp/sage/build/python2-2.7.15.p1
>
>
> * package: python3-3.7.3.p1
>
>   log file: /Library/SageDev/logs/pkgs/python3-3.7.3.p1.log
>
>   build directory: /Library/SageDev/local/var/tmp/sage/build/python3-3.7.3.p1
>
>
> 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[1]: *** [all-start] Error 1
>
> make: *** [all] Error 2
>
>
> Thank you much,
>
> Alex
>
> --
> 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/305e17da-b57d-4d86-bb5d-9690b86b6b6c%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/CAAWYfq1sn8KA2mrTieXPprAfaRmO7-eayWsxwOoo8xiQsme51A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Error Building Sage

2019-06-13 Thread Dima Pasechnik
On Thu, Jun 13, 2019 at 1:16 PM 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/

somewhere towards the end of the log file you can see

   virtual memory exhausted: Cannot allocate memory

error message by the compiler. That is, give your VirtualBox more RAM,
then it will hopefully work.

HTH
Dima


>
> 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/0d56f5f0-7696-48c8-9198-a9dfd718a2bb%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/CAAWYfq0L5Rzu4NhcL4wt0TLp95JSAdACx%2BT_QorDOitMX6YfOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Error Building Sage

2019-06-13 Thread Brandon Gontmacher
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/0d56f5f0-7696-48c8-9198-a9dfd718a2bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-05-31 Thread E. Madison Bray
Are you trying to upgrade from some old, partial build?  Or is this a
fresh build from scratch?  If the former, I would just run `make
distclean` and start again.

On Thu, May 30, 2019 at 9:51 PM 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/f087424b-b8a3-4f86-854c-fd2372695f81%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/CAOTD34bp19BOZGUDNnxu6%2BA9iU2kEVZdOn%2BSYkae3QxUvamwUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-05-30 Thread Dima Pasechnik
On Thu, May 30, 2019 at 8:51 PM 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;

pari comes from Sage as well; there is a package called pari, of which
pari_seadata_small
is a part. So it's perfectly normal that directory
'/home/cecbkup/SW/SAGE/sage-8.7/local/./share/pari' already exists.

Do you have `cp` aliased to something (perhaps at the system level)
that produces this weird error in your log?

 >Copying package files from temporary location
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0/inst
to > /home/cecbkup/SW/SAGE/sage-8.7/local
> cp: cannot create directory 
> '/home/cecbkup/SW/SAGE/sage-8.7/local/./share/pari': File exists




> 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/f087424b-b8a3-4f86-854c-fd2372695f81%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/CAAWYfq0N1m6Df5t_Jqh5D%3Dfijq-m_eVAM%2BpONWXkrex5GtC9QA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-05-30 Thread Charles Campbell
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.el7
epel 
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/f087424b-b8a3-4f86-854c-fd2372695f81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for pari_seadata_small-20090618.p0
Using cached file 
/home/cecbkup/SW/SAGE/sage-8.7/upstream/pari_seadata_small-20090618.tar.bz2
pari_seadata_small-20090618.p0

Setting up build directory for pari_seadata_small-20090618.p0
Finished extraction
No patch files found in ../patches

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 'pari_seadata_small' is currently not installed
No legacy uninstaller found for 'pari_seadata_small'; nothing to do
src/seadata -> 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0/inst/home/cecbkup/SW/SAGE/sage-8.7/local/share/pari

real0m0.014s
user0m0.003s
sys 0m0.010s
Copying package files from temporary location 
/home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0/inst
 to /home/cecbkup/SW/SAGE/sage-8.7/local
cp: cannot create directory 
'/home/cecbkup/SW/SAGE/sage-8.7/local/./share/pari': File exists

Error copying files for pari_seadata_small-20090618.p0.

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/pari_seadata_small-20090618.p0.log
Describe your computer, operating system, etc.



[sage-devel] Error building sage

2019-05-24 Thread Satyanarayana Vusirikala
I am tried to build sage. I ran   ./configure   followed by   make. Here's 
the output. Could not figure out why. 

[sagelib-8.7] Removing 
/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage-8.7-py2.7.egg-info

[sagelib-8.7] Writing 
/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage-8.7-py2.7.egg-info

[sagelib-8.7] Cleaning up stale installed files

[sagelib-8.7] - cleaning 
/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages

[sagelib-8.7] - cleaning build/lib.macosx-10.9-x86_64-2.7

[sagelib-8.7] Finished cleaning, time: 0.40 seconds.

[sagelib-8.7] if [ "$UNAME" = "CYGWIN" ]; then \

[sagelib-8.7] sage-rebase.sh "$SAGE_LOCAL" 2>/dev/null;\

[sagelib-8.7] fi

[sagelib-8.7] 

[sagelib-8.7] real 19m37.851s

[sagelib-8.7] user 59m16.416s

[sagelib-8.7] sys 2m58.759s

cp /Users/satya/Downloads/SageMath/src/bin/sage-env-config 
/Users/satya/Downloads/SageMath/local/bin/sage-env-config

cd ../.. && sage-logger -p './sage --docbuild --no-pdf-links all html ' 
logs/dochtml.log

[dochtml] Traceback (most recent call last):

[dochtml]   File 
"/Users/satya/Downloads/SageMath/local/lib/python2.7/runpy.py", line 163, 
in _run_module_as_main

[dochtml] mod_name, _Error)

[dochtml]   File 
"/Users/satya/Downloads/SageMath/local/lib/python2.7/runpy.py", line 111, 
in _get_module_details

[dochtml] __import__(mod_name)  # Do not catch exceptions initializing 
package

[dochtml]   File 
"/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
 
line 60, in 

[dochtml] import sage.all

[dochtml]   File 
"/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage/all.py",
 
line 98, in 

[dochtml] from sage.symbolic.all   import *

[dochtml]   File 
"/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage/symbolic/all.py",
 
line 3, in 

[dochtml] from sage.libs.pynac.pynac import I

[dochtml]   File "sage/symbolic/expression.pxd", line 4, in init 
sage.libs.pynac.pynac (build/cythonized/sage/libs/pynac/pynac.cpp:30147)

[dochtml]   File "sage/symbolic/expression.pyx", line 161, in init 
sage.symbolic.expression 
(build/cythonized/sage/symbolic/expression.cpp:74075)

[dochtml] ImportError: 
dlopen(/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so,
 
2): Symbol not found: 
__ZNSt3__16vectorIN5GiNaC2exENS_9allocatorIS2_EEE11__vallocateEm

[dochtml]   Referenced from: 
/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so

[dochtml]   Expected in: flat namespace

[dochtml]  in 
/Users/satya/Downloads/SageMath/local/lib/python2.7/site-packages/sage/symbolic/ring.so

make[3]: *** [doc-html] Error 1

make[2]: *** [all-start] Error 2


real 19m41.468s

user 59m18.862s

sys 3m0.256s

***

Error building Sage.


The following package(s) may have failed to build (not necessarily

during this run of 'make all-start'):


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[1]: *** [all-start] Error 1

make: *** [all] Error 2

-- 
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/325f80e1-c2e9-4dfb-8203-6d44fed60d4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Error building sage documentation

2019-03-10 Thread Dima Pasechnik
On Sun, Mar 10, 2019 at 7:12 AM rajat.mittal.mat15 via sage-devel
 wrote:
>
> I have succesfully installed sage from git on my ubuntu 16.04 OS.
> When I made some changes to a file and wanted to build the documetnation I 
> tried :
> command given in the documentation which threw some errors

the first thing is to make your changes available, otherwise we'd need
to guess what are the changes you actually
made that caused this error.
(e.g. push your changes to github and post here a link to the branch
in question, or
attach a diff here...)

> Then I tried
> make doc-clean
> make doc
>
> It seems to build two folders in sage/local/share/doc/sage
> namely doctrees and inventory
> but it gets stuck and doesn't move forward after that
>
> [dochtml] Build finished. The built documents can be found in 
> /home/rajat/sage/local/share/doc/sage/inventory/en/reference/structure
> [dochtml] [valuation] loading pickled environment... not yet created
> [dochtml] [valuation] building [inventory]: targets for 14 source files that 
> are out of date
> [dochtml] [valuation] updating environment: 14 added, 0 changed, 0 removed
> [dochtml] [valuation] The inventory files are in 
> local/share/doc/sage/inventory/en/reference/valuations.
> [dochtml] Build finished. The built documents can be found in 
> /home/rajat/sage/local/share/doc/sage/inventory/en/reference/valuations
>
>
>
> in between I do get following:
> [dochtml] Cython backtrace
> [dochtml] 
> [dochtml]
> [dochtml] 29../sysdeps/unix/sysv/linux/waitpid.c: No such file or 
> directory.
> [dochtml] Traceback (most recent call last):
> [dochtml]   File "", line 56, in 
> [dochtml]   File 
> "/usr/lib/python3/dist-packages/Cython/Debugger/libcython.py", line 689, in 
> invoke
> [dochtml] for arg in string_to_argv(args):
> [dochtml] TypeError: argument 1 must be str, not bytes
> [dochtml] Saved trace to /home/rajat/.sage/crash_logs/crash_kzbB4q.log
> [dochtml] 
> 
> [dochtml] Unhandled SIGSEGV: A segmentation fault occurred.
> [dochtml] This probably occurred because a *compiled* module has a bug
> [dochtml] in it and is not properly wrapped with sig_on(), sig_off().
> [dochtml] Python will now terminate.
> [dochtml] 
> 
>
>
> following is the crash log report I got attached:
>
> Can somebody please tell what should I do?
>
>
>
> Thanks
> Rajat
>
> --
> 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] Error building Sage

2019-02-27 Thread Quentin Hillebrand
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.
Found local metadata for pip-18.0
Using cached file 
/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/upstream/pip-18.0.tar.gz
pip-18.0

Setting up build directory for pip-18.0
Finished extraction
No patch files found in ../patches

Host system:
Darwin MacBook-Pro-de-Quentin.local 18.2.0 Darwin Kernel Version 18.2.0: Thu 
Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64

C compiler: gcc
C compiler version:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

No record that 'pip' was ever installed; skipping uninstall
Traceback (most recent call last):
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/lib/python3.6/runpy.py",
 line 193, in _run_module_as_main
"__main__", mod_spec)
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/lib/python3.6/runpy.py",
 line 85, in _run_code
exec(code, run_globals)
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0/src/src/pip/__main__.py",
 line 16, in 
from pip._internal import main as _main  # isort:skip # noqa
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0/src/src/pip/_internal/__init__.py",
 line 20, in 
from pip._vendor.urllib3.exceptions import DependencyWarning
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0/src/src/pip/_vendor/urllib3/__init__.py",
 line 8, in 
from .connectionpool import (
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0/src/src/pip/_vendor/urllib3/connectionpool.py",
 line 36, in 
from .response import HTTPResponse
  File 
"/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0/src/src/pip/_vendor/urllib3/response.py",
 line 3, in 
import zlib
ModuleNotFoundError: No module named 'zlib'

Error building / installing pip3


real0m0.218s
user0m0.152s
sys 0m0.054s

Error installing package pip-18.0

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /Users/quentin/Documents/M1/Projet_Integre/sage-8.6/logs/pkgs/pip-18.0.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0
 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 
'/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/local/var/tmp/sage/build/pip-18.0'
 && '/Users/quentin/Documents/M1/Projet_Integre/sage-8.6/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.



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

2019-01-02 Thread Dima Pasechnik
The first thing to try would be to install gfortran on the system  -
most probably you don't need to build a copy of gfortran from source
(this is a measure of last resort...):
That is, do (perhaps with sudo?)

pacman -S gcc-fortran

and try again

On Wed, Jan 2, 2019 at 6:41 PM Sverre Lunøe-Nielsen  wrote:
>
> Hello,
>
> I just cloned the GIT repository and tried to build version 8.5 on a fresh 
> Manjaro 18.0 installation.  I got the following error:
>
>>
>> [...]
>>
>> 66509-real  31m50.729s
>>
>> 66510-user  28m47.266s
>> 66511-sys   2m43.839s
>> 66512-Copying package files from temporary location 
>> /home/sverre/sage/local/var/tmp/sage/build/gfortran-7.2.0/inst to 
>> /home/sverre/sage/local
>> 66513-cp: cannot overwrite non-directory '/home/sverre/sage/local/./lib64' 
>> with directory 
>> '/home/sverre/sage/local/var/tmp/sage/build/gfortran-7.2.0/inst/home/sverre/sage/local/./lib64'
>> 66514-
>> 66515:Error copying files for gfortran-7.2.0.
>> 66516-
>> 66517-Please email sage-devel (http://groups.google.com/group/sage-devel)
>> 66518-explaining the problem and including the log file
>> 66519-  /home/sverre/sage/logs/pkgs/gfortran-7.2.0.log
>> 66520-Describe your computer, operating system, etc.
>> 66521-
>
>
> The full log file is available here: http://virtex.no/temp/gfortran-7.2.0.log 
>   (It exceeds the size limit of this forum, so I had to put it on my own FTP 
> server.)
>
> Any help moving forward will be very much appreciated.
>
>
> - 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.

-- 
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] Error building Sage 8.5 on Manjaro 18.0

2019-01-02 Thread Sverre Lunøe-Nielsen
Hello,

I just cloned the GIT repository and tried to build version 8.5 on a fresh 
Manjaro 18.0 installation.  I got the following error:
 

> [...]
>
66509-real  31m50.729s 
>
66510-user  28m47.266s
> 66511-sys   2m43.839s
> 66512-Copying package files from temporary location 
> /home/sverre/sage/local/var/tmp/sage/build/gfortran-7.2.0/inst to 
> /home/sverre/sage/local
> 66513-cp: cannot overwrite non-directory '/home/sverre/sage/local/./lib64' 
> with directory 
> '/home/sverre/sage/local/var/tmp/sage/build/gfortran-7.2.0/inst/home/sverre/sage/local/./lib64'
>
> 66514-
> 66515:Error copying files for gfortran-7.2.0.
>
> 66516-
> 66517-Please email sage-devel (http://groups.google.com/group/sage-devel)
> 66518-explaining the problem and including the log file
> 66519-  /home/sverre/sage/logs/pkgs/gfortran-7.2.0.log
> 66520-Describe your computer, operating system, etc.
>
> 66521-
>

The full log file is available here: 
http://virtex.no/temp/gfortran-7.2.0.log   (It exceeds the size limit of 
this forum, so I had to put it on my own FTP server.)

Any help moving forward will be very much appreciated.


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


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

2018-10-29 Thread 'Paul Mercat' via sage-devel
The compilation is successful now !
It was enough to set SAGE_INSTALL_GCC='yes'.

Le lundi 29 octobre 2018 18:08:41 UTC+1, Paul Mercat a écrit :
>
>
> I tried to recompile with SAGE_INSTALL_GCC='yes', and now openblas compile 
> (but the compilation of sage is not terminated).
>
> Le lundi 29 octobre 2018 17:04:30 UTC+1, Dima Pasechnik a écrit :
>>
>> So this must mean that you actually failed to gfortran package, no? 
>> (cause if you don't have gfortran installed it would be built --- of 
>> course it's madness to do on Linux, where 
>> you can just install gfortran). 
>> On Mon, Oct 29, 2018 at 4:49 PM 'Paul Mercat' via sage-devel 
>>  wrote: 
>> > 
>> > No, gfortran was not installed, nor anaconda. I tried to compile sage 
>> on a fresh new installation of Ubuntu. 
>> > 
>> > Le lundi 29 octobre 2018 16:18:41 UTC+1, Dima Pasechnik a écrit : 
>> >> 
>> >> This looks like you have several versions of gfortran guts lying 
>> >> around. A leftover from (ana)conda? 
>> >> 
>> >> On Mon, Oct 29, 2018 at 3:02 PM 'Paul Mercat' via sage-devel 
>> >>  wrote: 
>> >> > 
>> >> > Hi ! 
>> >> > 
>> >> > I tried to compile sage-8.4, and I have the following error. 
>> >> > 
>> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
>> or directory 
>> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
>> or directory 
>> >> > [openblas-0.2.20.p2] Makefile:7: recipe for target 'testlsame' 
>> failed 
>> >> > [openblas-0.2.20.p2] make[6]: *** [testlsame] Error 1 
>> >> > [openblas-0.2.20.p2] make[6]: *** Waiting for unfinished jobs 
>> >> > [openblas-0.2.20.p2] Makefile:10: recipe for target 'testslamch' 
>> failed 
>> >> > [openblas-0.2.20.p2] make[6]: *** [testslamch] Error 1 
>> >> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by 
>> make.inc) 
>> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
>> or directory 
>> >> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm 
>> -lpthread -lgfortran -o testsecond second_INT_ETIME.o secondtst.o 
>> >> > [openblas-0.2.20.p2] Makefile:13: recipe for target 'testdlamch' 
>> failed 
>> >> > [openblas-0.2.20.p2] make[6]: *** [testdlamch] Error 1 
>> >> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by 
>> make.inc) 
>> >> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm 
>> -lpthread -lgfortran -o testdsecnd dsecnd_INT_ETIME.o dsecndtst.o 
>> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
>> or directory 
>> >> > [openblas-0.2.20.p2] Makefile:16: recipe for target 'testsecond' 
>> failed 
>> >> > [openblas-0.2.20.p2] make[6]: *** [testsecond] Error 1 
>> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
>> or directory 
>> >> > [openblas-0.2.20.p2] Makefile:20: recipe for target 'testdsecnd' 
>> failed 
>> >> > [openblas-0.2.20.p2] make[6]: *** [testdsecnd] Error 1 
>> >> > [openblas-0.2.20.p2] make[6]: Leaving directory 
>> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib/INSTALL'
>>  
>>
>> >> > [openblas-0.2.20.p2] Makefile:17: recipe for target 'lapack_install' 
>> failed 
>> >> > [openblas-0.2.20.p2] make[5]: *** [lapack_install] Error 2 
>> >> > [openblas-0.2.20.p2] make[5]: Leaving directory 
>> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib'
>>  
>>
>> >> > [openblas-0.2.20.p2] Makefile:215: recipe for target 'netlib' failed 
>> >> > [openblas-0.2.20.p2] make[4]: *** [netlib] Error 2 
>> >> > [openblas-0.2.20.p2] make[4]: Leaving directory 
>> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src' 
>> >> > [openblas-0.2.20.p2] 
>> 
>>  
>>
>> >> > [openblas-0.2.20.p2] Error building openblas-0.2.20.p2 
>> >> > [openblas-0.2.20.p2] 
>> 
>>  
>>
>> >> > [openblas-0.2.20.p2] 
>> >> > [openblas-0.2.20.p2] real1m13.703s 
>> >> > [openblas-0.2.20.p2] user7m9.646s 
>> >> > [openblas-0.2.20.p2] sys0m58.397s 
>> >> > [openblas-0.2.20.p2] 
>>  
>> >> > [openblas-0.2.20.p2] Error installing package openblas-0.2.20.p2 
>> >> > [openblas-0.2.20.p2] 
>>  
>> >> > [openblas-0.2.20.p2] Please email sage-devel (
>> http://groups.google.com/group/sage-devel) 
>> >> > [openblas-0.2.20.p2] explaining the problem and including the log 
>> file 
>> >> > [openblas-0.2.20.p2]   
>> /home/mercatpaul/sage/logs/pkgs/openblas-0.2.20.p2.log 
>> >> > [openblas-0.2.20.p2] Describe your computer, operating system, etc. 
>> >> > [openblas-0.2.20.p2] If you want to try to fix the problem yourself, 
>> *don't* just cd to 
>> >> > [openblas-0.2.20.p2] 
>> /home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2 an

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

2018-10-29 Thread 'Paul Mercat' via sage-devel

I tried to recompile with SAGE_INSTALL_GCC='yes', and now openblas compile 
(but the compilation of sage is not terminated).

Le lundi 29 octobre 2018 17:04:30 UTC+1, Dima Pasechnik a écrit :
>
> So this must mean that you actually failed to gfortran package, no? 
> (cause if you don't have gfortran installed it would be built --- of 
> course it's madness to do on Linux, where 
> you can just install gfortran). 
> On Mon, Oct 29, 2018 at 4:49 PM 'Paul Mercat' via sage-devel 
> > wrote: 
> > 
> > No, gfortran was not installed, nor anaconda. I tried to compile sage on 
> a fresh new installation of Ubuntu. 
> > 
> > Le lundi 29 octobre 2018 16:18:41 UTC+1, Dima Pasechnik a écrit : 
> >> 
> >> This looks like you have several versions of gfortran guts lying 
> >> around. A leftover from (ana)conda? 
> >> 
> >> On Mon, Oct 29, 2018 at 3:02 PM 'Paul Mercat' via sage-devel 
> >>  wrote: 
> >> > 
> >> > Hi ! 
> >> > 
> >> > I tried to compile sage-8.4, and I have the following error. 
> >> > 
> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
> or directory 
> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
> or directory 
> >> > [openblas-0.2.20.p2] Makefile:7: recipe for target 'testlsame' failed 
> >> > [openblas-0.2.20.p2] make[6]: *** [testlsame] Error 1 
> >> > [openblas-0.2.20.p2] make[6]: *** Waiting for unfinished jobs 
> >> > [openblas-0.2.20.p2] Makefile:10: recipe for target 'testslamch' 
> failed 
> >> > [openblas-0.2.20.p2] make[6]: *** [testslamch] Error 1 
> >> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by 
> make.inc) 
> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
> or directory 
> >> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm 
> -lpthread -lgfortran -o testsecond second_INT_ETIME.o secondtst.o 
> >> > [openblas-0.2.20.p2] Makefile:13: recipe for target 'testdlamch' 
> failed 
> >> > [openblas-0.2.20.p2] make[6]: *** [testdlamch] Error 1 
> >> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by 
> make.inc) 
> >> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm 
> -lpthread -lgfortran -o testdsecnd dsecnd_INT_ETIME.o dsecndtst.o 
> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
> or directory 
> >> > [openblas-0.2.20.p2] Makefile:16: recipe for target 'testsecond' 
> failed 
> >> > [openblas-0.2.20.p2] make[6]: *** [testsecond] Error 1 
> >> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file 
> or directory 
> >> > [openblas-0.2.20.p2] Makefile:20: recipe for target 'testdsecnd' 
> failed 
> >> > [openblas-0.2.20.p2] make[6]: *** [testdsecnd] Error 1 
> >> > [openblas-0.2.20.p2] make[6]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib/INSTALL'
>  
>
> >> > [openblas-0.2.20.p2] Makefile:17: recipe for target 'lapack_install' 
> failed 
> >> > [openblas-0.2.20.p2] make[5]: *** [lapack_install] Error 2 
> >> > [openblas-0.2.20.p2] make[5]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib'
>  
>
> >> > [openblas-0.2.20.p2] Makefile:215: recipe for target 'netlib' failed 
> >> > [openblas-0.2.20.p2] make[4]: *** [netlib] Error 2 
> >> > [openblas-0.2.20.p2] make[4]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src' 
> >> > [openblas-0.2.20.p2] 
> 
>  
>
> >> > [openblas-0.2.20.p2] Error building openblas-0.2.20.p2 
> >> > [openblas-0.2.20.p2] 
> 
>  
>
> >> > [openblas-0.2.20.p2] 
> >> > [openblas-0.2.20.p2] real1m13.703s 
> >> > [openblas-0.2.20.p2] user7m9.646s 
> >> > [openblas-0.2.20.p2] sys0m58.397s 
> >> > [openblas-0.2.20.p2] 
>  
> >> > [openblas-0.2.20.p2] Error installing package openblas-0.2.20.p2 
> >> > [openblas-0.2.20.p2] 
>  
> >> > [openblas-0.2.20.p2] Please email sage-devel (
> http://groups.google.com/group/sage-devel) 
> >> > [openblas-0.2.20.p2] explaining the problem and including the log 
> file 
> >> > [openblas-0.2.20.p2]   
> /home/mercatpaul/sage/logs/pkgs/openblas-0.2.20.p2.log 
> >> > [openblas-0.2.20.p2] Describe your computer, operating system, etc. 
> >> > [openblas-0.2.20.p2] If you want to try to fix the problem yourself, 
> *don't* just cd to 
> >> > [openblas-0.2.20.p2] 
> /home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2 and type 
> 'make' or whatever is appropriate. 
> >> > [openblas-0.2.20.p2] Instead, the following commands setup all 
> environment variables 
> >> > [openblas-0.2.20.p2] correctly and load a subshell for you to debug 
> the error: 
> >> > [openblas-0.2.20.p2

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

2018-10-29 Thread Dima Pasechnik
So this must mean that you actually failed to gfortran package, no?
(cause if you don't have gfortran installed it would be built --- of
course it's madness to do on Linux, where
you can just install gfortran).
On Mon, Oct 29, 2018 at 4:49 PM 'Paul Mercat' via sage-devel
 wrote:
>
> No, gfortran was not installed, nor anaconda. I tried to compile sage on a 
> fresh new installation of Ubuntu.
>
> Le lundi 29 octobre 2018 16:18:41 UTC+1, Dima Pasechnik a écrit :
>>
>> This looks like you have several versions of gfortran guts lying
>> around. A leftover from (ana)conda?
>>
>> On Mon, Oct 29, 2018 at 3:02 PM 'Paul Mercat' via sage-devel
>>  wrote:
>> >
>> > Hi !
>> >
>> > I tried to compile sage-8.4, and I have the following error.
>> >
>> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
>> > directory
>> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
>> > directory
>> > [openblas-0.2.20.p2] Makefile:7: recipe for target 'testlsame' failed
>> > [openblas-0.2.20.p2] make[6]: *** [testlsame] Error 1
>> > [openblas-0.2.20.p2] make[6]: *** Waiting for unfinished jobs
>> > [openblas-0.2.20.p2] Makefile:10: recipe for target 'testslamch' failed
>> > [openblas-0.2.20.p2] make[6]: *** [testslamch] Error 1
>> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by make.inc)
>> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
>> > directory
>> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm -lpthread 
>> > -lgfortran -o testsecond second_INT_ETIME.o secondtst.o
>> > [openblas-0.2.20.p2] Makefile:13: recipe for target 'testdlamch' failed
>> > [openblas-0.2.20.p2] make[6]: *** [testdlamch] Error 1
>> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by make.inc)
>> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm -lpthread 
>> > -lgfortran -o testdsecnd dsecnd_INT_ETIME.o dsecndtst.o
>> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
>> > directory
>> > [openblas-0.2.20.p2] Makefile:16: recipe for target 'testsecond' failed
>> > [openblas-0.2.20.p2] make[6]: *** [testsecond] Error 1
>> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
>> > directory
>> > [openblas-0.2.20.p2] Makefile:20: recipe for target 'testdsecnd' failed
>> > [openblas-0.2.20.p2] make[6]: *** [testdsecnd] Error 1
>> > [openblas-0.2.20.p2] make[6]: Leaving directory 
>> > '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib/INSTALL'
>> > [openblas-0.2.20.p2] Makefile:17: recipe for target 'lapack_install' failed
>> > [openblas-0.2.20.p2] make[5]: *** [lapack_install] Error 2
>> > [openblas-0.2.20.p2] make[5]: Leaving directory 
>> > '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib'
>> > [openblas-0.2.20.p2] Makefile:215: recipe for target 'netlib' failed
>> > [openblas-0.2.20.p2] make[4]: *** [netlib] Error 2
>> > [openblas-0.2.20.p2] make[4]: Leaving directory 
>> > '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src'
>> > [openblas-0.2.20.p2] 
>> > 
>> > [openblas-0.2.20.p2] Error building openblas-0.2.20.p2
>> > [openblas-0.2.20.p2] 
>> > 
>> > [openblas-0.2.20.p2]
>> > [openblas-0.2.20.p2] real1m13.703s
>> > [openblas-0.2.20.p2] user7m9.646s
>> > [openblas-0.2.20.p2] sys0m58.397s
>> > [openblas-0.2.20.p2] 
>> > 
>> > [openblas-0.2.20.p2] Error installing package openblas-0.2.20.p2
>> > [openblas-0.2.20.p2] 
>> > 
>> > [openblas-0.2.20.p2] Please email sage-devel 
>> > (http://groups.google.com/group/sage-devel)
>> > [openblas-0.2.20.p2] explaining the problem and including the log file
>> > [openblas-0.2.20.p2]   
>> > /home/mercatpaul/sage/logs/pkgs/openblas-0.2.20.p2.log
>> > [openblas-0.2.20.p2] Describe your computer, operating system, etc.
>> > [openblas-0.2.20.p2] If you want to try to fix the problem yourself, 
>> > *don't* just cd to
>> > [openblas-0.2.20.p2] 
>> > /home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2 and type 
>> > 'make' or whatever is appropriate.
>> > [openblas-0.2.20.p2] Instead, the following commands setup all environment 
>> > variables
>> > [openblas-0.2.20.p2] correctly and load a subshell for you to debug the 
>> > error:
>> > [openblas-0.2.20.p2]   (cd 
>> > '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2' && 
>> > '/home/mercatpaul/sage/sage' --sh)
>> > [openblas-0.2.20.p2] When you are done debugging, you can type "exit" to 
>> > leave the subshell.
>> > [openblas-0.2.20.p2] 
>> > 
>> > Makefile:2107: recipe for target 
>> 

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

2018-10-29 Thread 'Paul Mercat' via sage-devel
No, gfortran was not installed, nor anaconda. I tried to compile sage on a 
fresh new installation of Ubuntu.

Le lundi 29 octobre 2018 16:18:41 UTC+1, Dima Pasechnik a écrit :
>
> This looks like you have several versions of gfortran guts lying 
> around. A leftover from (ana)conda? 
>
> On Mon, Oct 29, 2018 at 3:02 PM 'Paul Mercat' via sage-devel 
> > wrote: 
> > 
> > Hi ! 
> > 
> > I tried to compile sage-8.4, and I have the following error. 
> > 
> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory 
> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory 
> > [openblas-0.2.20.p2] Makefile:7: recipe for target 'testlsame' failed 
> > [openblas-0.2.20.p2] make[6]: *** [testlsame] Error 1 
> > [openblas-0.2.20.p2] make[6]: *** Waiting for unfinished jobs 
> > [openblas-0.2.20.p2] Makefile:10: recipe for target 'testslamch' failed 
> > [openblas-0.2.20.p2] make[6]: *** [testslamch] Error 1 
> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by make.inc) 
> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory 
> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm 
> -lpthread -lgfortran -o testsecond second_INT_ETIME.o secondtst.o 
> > [openblas-0.2.20.p2] Makefile:13: recipe for target 'testdlamch' failed 
> > [openblas-0.2.20.p2] make[6]: *** [testdlamch] Error 1 
> > [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by make.inc) 
> > [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm 
> -lpthread -lgfortran -o testdsecnd dsecnd_INT_ETIME.o dsecndtst.o 
> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory 
> > [openblas-0.2.20.p2] Makefile:16: recipe for target 'testsecond' failed 
> > [openblas-0.2.20.p2] make[6]: *** [testsecond] Error 1 
> > [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory 
> > [openblas-0.2.20.p2] Makefile:20: recipe for target 'testdsecnd' failed 
> > [openblas-0.2.20.p2] make[6]: *** [testdsecnd] Error 1 
> > [openblas-0.2.20.p2] make[6]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib/INSTALL'
>  
>
> > [openblas-0.2.20.p2] Makefile:17: recipe for target 'lapack_install' 
> failed 
> > [openblas-0.2.20.p2] make[5]: *** [lapack_install] Error 2 
> > [openblas-0.2.20.p2] make[5]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib'
>  
>
> > [openblas-0.2.20.p2] Makefile:215: recipe for target 'netlib' failed 
> > [openblas-0.2.20.p2] make[4]: *** [netlib] Error 2 
> > [openblas-0.2.20.p2] make[4]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src' 
> > [openblas-0.2.20.p2] 
> 
>  
>
> > [openblas-0.2.20.p2] Error building openblas-0.2.20.p2 
> > [openblas-0.2.20.p2] 
> 
>  
>
> > [openblas-0.2.20.p2] 
> > [openblas-0.2.20.p2] real1m13.703s 
> > [openblas-0.2.20.p2] user7m9.646s 
> > [openblas-0.2.20.p2] sys0m58.397s 
> > [openblas-0.2.20.p2] 
>  
> > [openblas-0.2.20.p2] Error installing package openblas-0.2.20.p2 
> > [openblas-0.2.20.p2] 
>  
> > [openblas-0.2.20.p2] Please email sage-devel (
> http://groups.google.com/group/sage-devel) 
> > [openblas-0.2.20.p2] explaining the problem and including the log file 
> > [openblas-0.2.20.p2]   
> /home/mercatpaul/sage/logs/pkgs/openblas-0.2.20.p2.log 
> > [openblas-0.2.20.p2] Describe your computer, operating system, etc. 
> > [openblas-0.2.20.p2] If you want to try to fix the problem yourself, 
> *don't* just cd to 
> > [openblas-0.2.20.p2] 
> /home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2 and type 
> 'make' or whatever is appropriate. 
> > [openblas-0.2.20.p2] Instead, the following commands setup all 
> environment variables 
> > [openblas-0.2.20.p2] correctly and load a subshell for you to debug the 
> error: 
> > [openblas-0.2.20.p2]   (cd 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2' && 
> '/home/mercatpaul/sage/sage' --sh) 
> > [openblas-0.2.20.p2] When you are done debugging, you can type "exit" to 
> leave the subshell. 
> > [openblas-0.2.20.p2] 
>  
> > Makefile:2107: recipe for target 
> '/home/mercatpaul/sage/local/var/lib/sage/installed/openblas-0.2.20.p2' 
> failed 
> > make[3]: *** 
> [/home/mercatpaul/sage/local/var/lib/sage/installed/openblas-0.2.20.p2] 
> Error 1 
> > make[3] : on quitte le répertoire « /home/mercatpaul/sage/build/make » 
> > Makefile:1795: recipe for target 'all-start' failed 
> > make[2]: *** [all-st

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

2018-10-29 Thread Dima Pasechnik
This looks like you have several versions of gfortran guts lying
around. A leftover from (ana)conda?

On Mon, Oct 29, 2018 at 3:02 PM 'Paul Mercat' via sage-devel
 wrote:
>
> Hi !
>
> I tried to compile sage-8.4, and I have the following error.
>
> [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory
> [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory
> [openblas-0.2.20.p2] Makefile:7: recipe for target 'testlsame' failed
> [openblas-0.2.20.p2] make[6]: *** [testlsame] Error 1
> [openblas-0.2.20.p2] make[6]: *** Waiting for unfinished jobs
> [openblas-0.2.20.p2] Makefile:10: recipe for target 'testslamch' failed
> [openblas-0.2.20.p2] make[6]: *** [testslamch] Error 1
> [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by make.inc)
> [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory
> [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm -lpthread 
> -lgfortran -o testsecond second_INT_ETIME.o secondtst.o
> [openblas-0.2.20.p2] Makefile:13: recipe for target 'testdlamch' failed
> [openblas-0.2.20.p2] make[6]: *** [testdlamch] Error 1
> [openblas-0.2.20.p2] [INFO] : TIMER value: INT_ETIME (given by make.inc)
> [openblas-0.2.20.p2] gfortran -pthread -O2 -Wall -m64 -fPIC -lm -lpthread 
> -lgfortran -o testdsecnd dsecnd_INT_ETIME.o dsecndtst.o
> [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory
> [openblas-0.2.20.p2] Makefile:16: recipe for target 'testsecond' failed
> [openblas-0.2.20.p2] make[6]: *** [testsecond] Error 1
> [openblas-0.2.20.p2] gfortran: error: libgfortran.spec: No such file or 
> directory
> [openblas-0.2.20.p2] Makefile:20: recipe for target 'testdsecnd' failed
> [openblas-0.2.20.p2] make[6]: *** [testdsecnd] Error 1
> [openblas-0.2.20.p2] make[6]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib/INSTALL'
> [openblas-0.2.20.p2] Makefile:17: recipe for target 'lapack_install' failed
> [openblas-0.2.20.p2] make[5]: *** [lapack_install] Error 2
> [openblas-0.2.20.p2] make[5]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src/lapack-netlib'
> [openblas-0.2.20.p2] Makefile:215: recipe for target 'netlib' failed
> [openblas-0.2.20.p2] make[4]: *** [netlib] Error 2
> [openblas-0.2.20.p2] make[4]: Leaving directory 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2/src'
> [openblas-0.2.20.p2] 
> 
> [openblas-0.2.20.p2] Error building openblas-0.2.20.p2
> [openblas-0.2.20.p2] 
> 
> [openblas-0.2.20.p2]
> [openblas-0.2.20.p2] real1m13.703s
> [openblas-0.2.20.p2] user7m9.646s
> [openblas-0.2.20.p2] sys0m58.397s
> [openblas-0.2.20.p2] 
> 
> [openblas-0.2.20.p2] Error installing package openblas-0.2.20.p2
> [openblas-0.2.20.p2] 
> 
> [openblas-0.2.20.p2] Please email sage-devel 
> (http://groups.google.com/group/sage-devel)
> [openblas-0.2.20.p2] explaining the problem and including the log file
> [openblas-0.2.20.p2]   /home/mercatpaul/sage/logs/pkgs/openblas-0.2.20.p2.log
> [openblas-0.2.20.p2] Describe your computer, operating system, etc.
> [openblas-0.2.20.p2] If you want to try to fix the problem yourself, *don't* 
> just cd to
> [openblas-0.2.20.p2] 
> /home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2 and type 
> 'make' or whatever is appropriate.
> [openblas-0.2.20.p2] Instead, the following commands setup all environment 
> variables
> [openblas-0.2.20.p2] correctly and load a subshell for you to debug the error:
> [openblas-0.2.20.p2]   (cd 
> '/home/mercatpaul/sage/local/var/tmp/sage/build/openblas-0.2.20.p2' && 
> '/home/mercatpaul/sage/sage' --sh)
> [openblas-0.2.20.p2] When you are done debugging, you can type "exit" to 
> leave the subshell.
> [openblas-0.2.20.p2] 
> 
> Makefile:2107: recipe for target 
> '/home/mercatpaul/sage/local/var/lib/sage/installed/openblas-0.2.20.p2' failed
> make[3]: *** 
> [/home/mercatpaul/sage/local/var/lib/sage/installed/openblas-0.2.20.p2] Error 
> 1
> make[3] : on quitte le répertoire « /home/mercatpaul/sage/build/make »
> Makefile:1795: recipe for target 'all-start' failed
> make[2]: *** [all-start] Error 2
> make[2] : on quitte le répertoire « /home/mercatpaul/sage/build/make »
>
> real1m15,665s
> user7m11,527s
> sys0m59,385s
> ***
> Error building Sage.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emai

[sage-devel] Error building Sage

2018-09-17 Thread Kathryn Burton
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.


Terminal Saved Output
Description: Binary data


[sage-devel] error building sage

2017-09-16 Thread Maarten Derickx
Also did you install all the prerequisites for building sage in your system? 
The webpage 

http://doc.sagemath.org/html/en/installation/source.html

Shows more detailed instructions how to build sage

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


  1   2   >