pip-21.1.2 compile fails on MacOS

[harald....@gmail.com]

Hi,

I'm trying to build Sagemath from source (within miniconda) on an Intel-based Mac Mini running MacOS Monterrey. I get:

[pip-21.1.2] Error building a wheel for pip-21.1.2

...

[pip-21.1.2] Error installing package pip-21.1.2

See the log files.

Best

Harald

[harald....@gmail.com]

I run into the same issue without miniconda, and thus cannot build Sage at all.

[Dima Pasechnik]

Hi Harald,

We don't have Sage ported to macos 12 yet, I am afraid.

We have been fighting macos 11 until April, see

https://trac.sagemath.org/ticket/30651

I've just opened https://trac.sagemath.org/ticket/32855

Binaries built on macOS 10 or 11 might run on 12, but building is another story.

Can one install Sage on macOS 12 using (mini)Conda at all ?

I think building might be easier with Homebrew rather than Conda, too.

Cheers,

Dima

[Isuru Fernando]

> Can one install Sage on macOS 12 using (mini)Conda at all ?

Sure. It should work fine. Bug reports are welcome.

Isuru

--
You received this message because you are 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/c95cfc0d-c1ea-41b9-8038-c360479af7efn%40googlegroups.com.

[Isuru Fernando]

For this issue, you need setuptools 58 or higher.

Or remove the line https://github.com/sagemath/sage/blob/f5efe4883f348e01ca3069ed82bf517a4de337f6/build/bin/sage-build-env#L174

Isuru

[Dima Pasechnik]

On Thu, Nov 11, 2021 at 9:56 PM Isuru Fernando <isu...@gmail.com> wrote:

> Can one install Sage on macOS 12 using (mini)Conda at all ?

Sure. It should work fine. Bug reports are welcome.

Am I right that it's possible to change Sage's Cython files in such an installation, and  update Sage this way?

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2B01voOYmV5hZAnoRjN-zw6v8A6qvLHHYhZ75firWG%2BGg6a6Lg%40mail.gmail.com.

[Isuru Fernando]

> Am I right that it's possible to change Sage's Cython files in such an installation, and  update Sage this way?

No, it's binary only. See https://wiki.sagemath.org/Conda section "Conda for sage developers" if you want to do that.

(Btw, that hasn't been updated in a while and might not work due to a recent restructure of sage build system)

Isuru

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2%3DwZiAyvdq4RNR10CnririEx_1E7jKjpJ9c0LxH2iKOA%40mail.gmail.com.

[Dima Pasechnik]

On Thu, Nov 11, 2021 at 10:10 PM Isuru Fernando <isu...@gmail.com> wrote:

> Am I right that it's possible to change Sage's Cython files in such an installation, and  update Sage this way?

No, it's binary only. See https://wiki.sagemath.org/Conda section "Conda for sage developers" if you want to do that.

(Btw, that hasn't been updated in a while and might not work due to a recent restructure of sage build system)

I'm checking it now on macOS 11, did few changes already.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2B01voOKdCFNvKUgn%3D9BWSDcVuEMA9uLyAbDUQUhSDP86UaOjA%40mail.gmail.com.

[Dima Pasechnik]

Conda's pari packages are a bit broken (they are per env, but not
quite), and this test fails:

configure:21400: result: libpari's datadir does not match GP's datadir. Not good
configure:21449: no suitable system package found for SPKG pari

namely, GP's datadir is
/Users/dima/opt/miniconda3/envs/sage-build/share/pari
but libpari's datadir is
/Users/dima/opt/miniconda3/envs/sage/share/pari

and if I try "mamba install pari" I just get

All requested packages already installed.

I suppose I don't understand conda's environments well - how does one tell
conda to install pari (and libpari) into sage-build?

On Thu, Nov 11, 2021 at 9:56 PM Isuru Fernando <isu...@gmail.com> wrote:
>

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2B01voOYmV5hZAnoRjN-zw6v8A6qvLHHYhZ75firWG%2BGg6a6Lg%40mail.gmail.com.

[Isuru Fernando]

It's not good to have two conda environments. I'm not sure how you got them both involved in the build.

`mamba install pari -n sage-build` will install sage in `sage-build` env.

Isuru

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1XCMmjs2FGj7%2B6AZXoAg4rXb9CYzndodfjWXtO7%2B_w%2Bg%40mail.gmail.com.

[Dima Pasechnik]

On Thu, Nov 11, 2021 at 11:49 PM Isuru Fernando <isu...@gmail.com> wrote:
>
> It's not good to have two conda environments. I'm not sure how you got them both involved in the build.

hmm. First I just installed Sage 9.4 as a conda package, (getting sage
env), and then
tried your sage-build env. instructions.

> You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/xYQXZKVMYfM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2B01voP8%2BR%2BjtbWJieM4Nsn7Af3QmhUMTYvySN%3DK%2B-3VX314Dg%40mail.gmail.com.

[Isuru Fernando]

I suggest running `conda activate sage-build` and then doing a `make dist-clean`.

[Dima Pasechnik]

anyhow, Conda for Sage Developers needs updates.
Before doing

cd src/
python setup.py install

one needs to do the same for a number of packages in
pkgs/

cd pkgs/sage-conf
python setup.py install
cd ../sage-setup
python setup.py install

and I also did

pip install memory-allocator

because some of these was failing with an error there


Perhaps Matthias can tell us more about the precise order and need.

On Thu, Nov 11, 2021 at 11:56 PM Isuru Fernando <isu...@gmail.com> wrote:
>
> I suggest running `conda activate sage-build` and then doing a `make dist-clean`.
>

> --
> You received this message because you are 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/CA%2B01voMXPYnm3FmYZYq-4fRWkB7ttBpABBbJ%3D6p_Yaw9mNAZKw%40mail.gmail.com.

[Matthias Koeppe]

Invoking "setup.py install" is always wrong, it should not be used directly anymore.

Try "pip install ." instead

[Matthias Koeppe]

I have updated the instructions.

[Dima Pasechnik]

On Friday, November 12, 2021 at 6:36:00 AM UTC Matthias Koeppe wrote:

I have updated the instructions.

Thanks - are these tested?

I've changed the release version at the bottom, so that it does not look like something untouched since Sage 9.2

[Matthias Koeppe]

On Friday, November 12, 2021 at 2:42:09 AM UTC-8 Dima Pasechnik wrote:

On Friday, November 12, 2021 at 6:36:00 AM UTC Matthias Koeppe wrote:

I have updated the instructions.

Thanks - are these tested?

Yes, I tested them on macOS Big Sur.

 

[Dima Pasechnik]

hmm, by design, or in error, "make ptest" starts building all the
dependencies, e.g. maxima.
So that's not a usual environment - perhaps it should be mentioned.

>
>
>
> --
> You received this message because you are 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/7cffbfcd-ef4c-48a4-a2ae-126677315662n%40googlegroups.com.

[Matthias Koeppe]

Yes, if one is not using the Sage distribution for build, one should also not use it for testing.

Use "sage -t".

[Dima Pasechnik]

On Friday, November 12, 2021 at 8:20:24 PM UTC Matthias Koeppe wrote:

Yes, if one is not using the Sage distribution for build, one should also not use it for testing.

Use "sage -t".

that's not nice. Should we have a ./configure option that just blesses all deps as "coming from the system"?

[Matthias Koeppe]

No, we should revise the documentation so that it does not advertise "make ....test" any more.

[Matthias Koeppe]

I have added this as a task to https://trac.sagemath.org/ticket/30453

[Dima Pasechnik]

On Fri, Nov 12, 2021 at 10:17 PM Matthias Koeppe
<matthia...@gmail.com> wrote:
>
> No, we should revise the documentation so that it does not advertise "make ....test" any more.

No, if we use autotools/make to build a project, there should be
meaningful make targets for testing too, force
people to learn peculiarities of tox or whatever the latest Python
testing rage is, is wrong.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/b316b9ed-c5d9-4ac6-9717-ffb275ea267fn%40googlegroups.com.

[Dima Pasechnik]

On Fri, Nov 12, 2021 at 10:46 PM Dima Pasechnik <dim...@gmail.com> wrote:
>
> On Fri, Nov 12, 2021 at 10:17 PM Matthias Koeppe
> <matthia...@gmail.com> wrote:
> >
> > No, we should revise the documentation so that it does not advertise "make ....test" any more.
>
> No, if we use autotools/make to build a project, there should be
> meaningful make targets for testing too, force
> people to learn peculiarities of tox or whatever the latest Python
> testing rage is, is wrong.

Besides, in the use case we're taking about, ./configure produces
results which are
wrong for the purposes of the further use, which is not to build any
packages, but only sagelib.
Let's stop this confusion - I suppose then the ugly pip commands can
be replaces by "make build", no?