On Fri, Nov 12, 2021 at 10:46 PM Dima Pasechnik wrote:
>
> On Fri, Nov 12, 2021 at 10:17 PM Matthias Koeppe
> 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
>
On Fri, Nov 12, 2021 at 10:17 PM Matthias Koeppe
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 peculiarit
I have added this as a task to https://trac.sagemath.org/ticket/30453
On Friday, November 12, 2021 at 2:17:05 PM UTC-8 Matthias Koeppe wrote:
> No, we should revise the documentation so that it does not advertise "make
> test" any more.
>
> On Friday, November 12, 2021 at 2:09:12 PM UTC-8 Di
No, we should revise the documentation so that it does not advertise "make
test" any more.
On Friday, November 12, 2021 at 2:09:12 PM UTC-8 Dima Pasechnik wrote:
> On Friday, November 12, 2021 at 8:20:24 PM UTC Matthias Koeppe wrote:
>
>> Yes, if one is not using the Sage distribution for bu
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 sy
Yes, if one is not using the Sage distribution for build, one should also
not use it for testing.
Use "sage -t".
On Friday, November 12, 2021 at 10:39:47 AM UTC-8 Dima Pasechnik wrote:
> On Fri, Nov 12, 2021 at 5:01 PM Matthias Koeppe
> wrote:
> >
> > On Friday, November 12, 2021 at 2:42:09 AM
On Fri, Nov 12, 2021 at 5:01 PM Matthias Koeppe
wrote:
>
> 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 te
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.
--
You received this message because yo
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
>
> On Thursday, November 11, 2021 at 4:27:3
I have updated the instructions.
On Thursday, November 11, 2021 at 4:27:38 PM UTC-8 Matthias Koeppe wrote:
> Invoking "setup.py install" is always wrong, it should not be used
> directly anymore.
>
> Try "pip install ." instead
>
> On Thursday, November 11, 2021 at 4:24:47 PM UTC-8 Dima Pasechn
Invoking "setup.py install" is always wrong, it should not be used directly
anymore.
Try "pip install ." instead
On Thursday, November 11, 2021 at 4:24:47 PM UTC-8 Dima Pasechnik wrote:
> anyhow, Conda for Sage Developers needs updates.
> Before doing
>
> cd src/
> python setup.py install
>
> o
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
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+unsubscr...@googlegrou
On Thu, Nov 11, 2021 at 11:49 PM Isuru Fernando 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.
>
>
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
On Thu, Nov 11, 2021 at 5:15 PM Dima Pasechnik wrote:
> Conda's pari packages are a bit broken (they are per e
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/s
On Thu, Nov 11, 2021 at 10:10 PM Isuru Fernando 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.
> 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 t
On Thu, Nov 11, 2021 at 9:56 PM Isuru Fernando 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?
Isuru
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
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
> Can one install Sage on macOS 12 using (mini)Conda at all ?
Sure. It should work fine. Bug reports are welcome.
Isuru
On Thu, Nov 11, 2021 at 3:38 PM Dima Pasechnik wrote:
> Hi Harald,
>
> We don't have Sage ported to macos 12 yet, I am afraid.
> We have been fighting macos 11 until April, s
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
I run into the same issue without miniconda, and thus cannot build Sage at
all.
Le jeudi 11 novembre 2021 à 20:00:06 UTC+1, harald@gmail.com a écrit :
> Hi,
>
> I'm trying to build Sagemath from source (within miniconda) on an
> Intel-based Mac Mini running MacOS Monterrey. I get:
>
> [pip-
On Saturday, 1 February 2014 20:38:03 UTC-7, jason wrote:
>
> On 2/1/14 9:33 PM, William Stein wrote:
> > Hi,
> >
> > I think we should include pip with Sage. It's now the standard Python
> > package manager, and anybody using Sage now should always do this with
> > their new Sage install, so
On 2/1/14 9:33 PM, William Stein wrote:
Hi,
I think we should include pip with Sage. It's now the standard Python
package manager, and anybody using Sage now should always do this with
their new Sage install, so they can install/upgrade/remove(!)/etc.,
packages.
wget https://raw.github.co
25 matches
Mail list logo
