On Wednesday, February 10, 2021 at 6:18:24 AM UTC-8 Dima Pasechnik wrote:
> It would make sense if bootstrap also printed platform-specific system
> packages
> (as listed in build/pkgs/_bootstrap/distros/.txt) it needs,
> in case it fails and tells them to try "./bootstrap -d", - see the lines
On Wed, Feb 10, 2021 at 1:27 PM Trevor Karn wrote:
>
> I would be willing to help make improvements to the manual, my only
> hesitation is that I'm not 100% sure what is going on with the bootstrapping.
> Is there anything particular to bootstrapping in Sage that wouldn't show up
> in googling
I would be willing to help make improvements to the manual, my only
hesitation is that I'm not 100% sure what is going on with the
bootstrapping. Is there anything particular to bootstrapping in Sage that
wouldn't show up in googling around about it?
Best Regards,
Trevor Karn
On Tue, Feb 9, 202
On Tuesday, February 9, 2021 at 9:09:32 AM UTC-8 zsc...@gmail.com wrote:
> I see that the link I posted to the installation from source documentation
> doesn't mention autoconf/automake, but I would have thought some other
> package would have already installed them. Probably since homebrew is
I see that the link I posted to the installation from source documentation
doesn't mention autoconf/automake, but I would have thought some other
package would have already installed them. Probably since homebrew is all
bottles now they don't automatically get installed anymore if you are not
On Tue, Feb 9, 2021 at 3:32 PM Trevor Karn wrote:
>
> I uninstalled and reinstalled homebrew and that got rid of the brew doctor
> warnings. I then brewed the suggested packages from the Sage link Zachary
> provided and the packages listed at the end of the output of configure.
>
> Then from SAG
I uninstalled and reinstalled homebrew and that got rid of the brew doctor
warnings. I then brewed the suggested packages from the Sage link Zachary
provided and the packages listed at the end of the output of configure.
Then from SAGE_ROOT I ran
make distclean
source .homebrew-build-env
./bootst
On Tue, Feb 9, 2021 at 4:07 AM Zachary Scherr wrote:
>
> I need to sign off for the night, but the numpy error is definitely related
> to gfortran. If you have gcc installed via homebrew then it should come with
> the latest version of gfortran. You can see from your config.log file that
> gf
I need to sign off for the night, but the numpy error is definitely related
to gfortran. If you have gcc installed via homebrew then it should come
with the latest version of gfortran. You can see from your config.log file
that gfortran is not found:
configure:7281: checking for gfortran
conf
At some point you should deal with those warnings, but I don't think that
is what is causing your problems (although they are probably symptomatic of
other possible issues).
The config.log file you posted earlier is picking up a lot of packages that
were built by sage and not from homebrew.
brew doctor is giving lots of errors about unbrewed files:
trevorkarn@Trevors-MacBook-Air sage % brew doctor
*Please note that these warnings are just used to help the Homebrew
maintainers*
*with debugging if you file an issue. If everything you use Homebrew for is*
*working fine: please don't
In your original config.log, it looked like sage was picking up its own
fortran:
configure:11991: gfortran has already been installed by SageMath
configure:39396: result: gfortran-9.2.0:
already installed as an SPKG
The current version of gfortran from homebrew is 1
Unfortunately, that did not seem to work.
Here are the last few lines of the terminal output and I've attached the
numpy log.
[singular-4.1.1p2.p0] real 28m38.843s
[singular-4.1.1p2.p0] user 24m18.545s
[singular-4.1.1p2.p0] sys 3m53.423s
[singular-4.1.1p2.p0] Copying package files from tempora
yea, something seems messed up. For example, the numpy problem was fixed
on beta 6 and should still be fixed in beta 7. It looks like somehow you
have old files hanging around which are causing problems. Hopefully make
distclean will clean everything and let you start fresh.
On Monday, Febru
I must have typed it wrong. The second option you gave failed on numpy, but
I tried the first option again, and it is compiling.
Best Regards,
Trevor Karn
On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr wrote:
> Are you sure you typed it correctly? Maybe try running
>
> ./bootstrap
>
> to make
Are you sure you typed it correctly? Maybe try running
./bootstrap
to make sure that the make targets are in order.
On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:
> I tried make distclean and got an error “make: *** No rule to make target
> ‘distclean’. Stop.”
>
> So I tri
I tried make distclean and got an error “make: *** No rule to make target
‘distclean’. Stop.”
So I tried your second suggestion and it seems to be working so far, but it
is still compiling.
On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr wrote:
> Probably the thing to try would be:
>
> make dist
Probably the thing to try would be:
make distclean
and then you can build from scratch via:
./bootstrap
source .homebrew-build-env
./configure
make -j4 build
But if you want to try cleaning wheel first before starting from scratch,
you could just try
make wheel-clean
make -j4 build
but it mi
I do not see pep425tags.py in that directory.
trevorkarn@Trevors-MacBook-Air sage % cd
/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
trevorkarn@Trevors-MacBook-Air wheel % ls
__init__.py __pycache__ cli metadata.py util.py wheelfile.py
__main__.py bdist_wheel.py m
the only explanation for pep425tags.py would be an unclean build
environment - e.g. weird env vars set, or strange stuff in PATH.
On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr wrote:
>
> and do you see that pep425tags.py file in that directory?
>
> On Monday, February 8, 2021 at 10:21:09 AM UTC-5
and do you see that pep425tags.py file in that directory?
On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
> The only contents of the file you pointed me towards are
>
> __version__ = '0.36.2'
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr
The only contents of the file you pointed me towards are
__version__ = '0.36.2'
Best Regards,
Trevor Karn
On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr wrote:
> I really don't understand. The Cython log file shows that the problem is
> in
>
>
> /Users/trevorkarn/Applications/sage/local/lib/
I really don't understand. The Cython log file shows that the problem is in
/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
I could be mistaken, but I don't think pep425tags.py has been a part of the
wheel package for a while now. Certainly when I look
I also have this. Is there any reason it might be calling python instead of
python3?
trevorkarn@Trevors-MacBook-Air sage % python3 --version
Python 3.9.1
trevorkarn@Trevors-MacBook-Air sage % python --version
Python 2.7.16
Best Regards,
Trevor Karn
On Mon, Feb 8, 2021 at 8:28 AM Trevor Karn
Here is what I get. It seems like it is the same as yours?
trevorkarn@Trevors-MacBook-Air sage % brew info python3
python@3.9: stable 3.9.1
Interpreted, interactive, object-oriented programming language
https://www.python.org/
/usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
B
Could it be that you need to update your Homebrew (?) python3 package?
What version do you have now?
E.g. on a box where the latest Sage builds I have
% brew info python3
python@3.9: stable 3.9.1 (bottled)
Interpreted, interactive, object-oriented programming language
https://www.python.org/
/usr
On Mon, 8 Feb 2021, 13:02 Trevor Karn, wrote:
> Thanks for sending that link. I am confused though, because it says a fix
> was issued. Does that mean it should work now?
>
sorry, I was not clear. What I meant to say that it appears to be a
well-known issue in the Python@macOS universe,
and late
Thanks for sending that link. I am confused though, because it says a fix
was issued. Does that mean it should work now?
And yes, I am on the most recent develop branch
On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik wrote:
> This seems to be well-known issue, see e.g
> https://github.com/pypa/vi
This seems to be well-known issue, see e.g
https://github.com/pypa/virtualenv/issues/2027
Are you on the most recent develop branch (9.3.beta7)?
On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn wrote:
>
> Hi,
>
> I'm trying to build Sage from the source code. I cloned it from git, and
> tried to buil
29 matches
Mail list logo
