Thank you, it seems to have found it now! (I did make clean, bootstrap,
this told me to install gettext, then I ran configure, which told me again
to install some more things, but already picked up the right python)
Matthias Koeppe schrieb am Dienstag, 8. September 2020 um 19:36:29 UTC+2:
>
This is not the latest beta, or you forgot to run "./bootstrap".
On Tuesday, September 8, 2020 at 10:29:09 AM UTC-7, Martin R wrote:
>
> The reason is interesting. What should I do now?
>
> ## Checking whether SageMath should install SPKG python3... ##
> ##
The reason is interesting. What should I do now?
## Checking whether SageMath should install SPKG python3... ##
## ##
configure:29618: checking whether any of sqlite libpng bzip2 xz libffi is
installed as or will be installed as SPKG
On Tue, Sep 8, 2020 at 5:02 PM 'Martin R' via sage-devel
wrote:
>
> My config.log says, after having done make clean and configure
> --enable-openssl
>
> ## ##
> ## Checking whether SageMath should install SPKG python3... ##
> ##
My config.log says, after having done make clean and configure
--enable-openssl
## ##
## Checking whether SageMath should install SPKG python3... ##
## ##
configure:29580: python3
On Tuesday, September 8, 2020 at 4:00:33 PM UTC+1 axio...@yahoo.de wrote:
> I'd be very grateful for all detail, because I'm not all that good at
> performing rites.
>
oops, sorry, I thought you're on macOS :-)
As that's a typical macOS trouble.
>
> Actually, my system python says:
>
>
see also this page:
https://ask.sagemath.org/question/51130/ssl-error-using-sage-pip-install-to-download-a-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
I'd be very grateful for all detail, because I'm not all that good at
performing rites.
Actually, my system python says:
martin@toolbox:~/sage-develop$ python
Python 3.8.2 (default, Jul 16 2020, 14:00:26)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more
install python 3.8 from python.org, perform the necessary rite to bless the
certs, and then let Sage use it rather than build its own Python.
On Tue, 8 Sep 2020, 15:05 'Martin R' via sage-devel, <
sage-devel@googlegroups.com> wrote:
> I did make clean, configure --enable-openssl, make and it
I did make clean, configure --enable-openssl, make and it still fails :-(
Martin R schrieb am Montag, 7. September 2020 um 21:23:20 UTC+2:
> yes (I did this) and no (it didn't work).
> John H Palmieri schrieb am Montag, 7. September 2020 um 20:54:37 UTC+2:
>
>> Did you do what Dima said, rebuild
yes (I did this) and no (it didn't work).
John H Palmieri schrieb am Montag, 7. September 2020 um 20:54:37 UTC+2:
> Did you do what Dima said, rebuild Python 3?
>
> 1. make
> 2. realize you need to install openssl
> 3. make openssl
> 4. sage -f python3 (to force a rebuild Python 3)
> 5. make
>
>
Did you do what Dima said, rebuild Python 3?
1. make
2. realize you need to install openssl
3. make openssl
4. sage -f python3 (to force a rebuild Python 3)
5. make
should work.
On Monday, September 7, 2020 at 11:48:19 AM UTC-7, Martin R wrote:
>
> Unfortunately, it seems that make clean is
Unfortunately, it seems that make clean is necessary. I tried both to no
avail. Thank you anyway!
John H Palmieri schrieb am Montag, 7. September 2020 um 20:29:07 UTC+2:
>
>
> On Monday, September 7, 2020 at 11:27:15 AM UTC-7, John H Palmieri wrote:
>>
>> You could do
>>
>> ./configure
On Monday, September 7, 2020 at 11:27:15 AM UTC-7, John H Palmieri wrote:
>
> You could do
>
> ./configure --enable-openssl=yes
> make
>
> or atlernatively
>
> make openssl
> make
>
And the second of these (make openssl; make) might be better because it
should ensure that openssl is built
You could do
./configure --enable-openssl=yes
make
or atlernatively
make openssl
make
On Monday, September 7, 2020 at 11:09:07 AM UTC-7, Martin R wrote:
>
> unfortunately, no.
>
> What I don't quite understand: I can do sage -i openssl only *after* I
> built sage, but python3 is built at the
unfortunately, no.
What I don't quite understand: I can do sage -i openssl only *after* I
built sage, but python3 is built at the very beginning. So what am I
supposed to do?
dim...@gmail.com schrieb am Montag, 7. September 2020 um 16:01:59 UTC+2:
> after you rebuild python3,
> simply
>
>
after you rebuild python3,
simply
make build
should work, no need to clean, IMHO
On Mon, 7 Sep 2020, 13:11 'Martin R' via sage-devel, <
sage-devel@googlegroups.com> wrote:
> I am getting an ssl error when using my fresh sage build.
>
> I admit that I first build sage without thinking about
I am getting an ssl error when using my fresh sage build.
I admit that I first build sage without thinking about ssl, and then did
sage -i openssl and sage -f python3.
Should I rebuild from scratch? If so, what should I do exactly?
Martin
sage: oeis([sum(1 for la in Partitions(n)) for n in
18 matches
Mail list logo
