I am not able to build beta5 after running make distclean using my standard
build script that includes no external libraries. I am seeing errors about
missing autoconf commands:
make: `configure' is up to date.
./configure: line 4932: AC_LIB_RPATH: command not found
./configure: line 24924: AC_
After working around the issues with the bootstrap script and symengine_py
I have managed to build 9.7.beta5 on an arm mac mini. This was an
incremental build from beta4. When the build finished I noticed that both
sage/local/var/lib/sage/venv-python3.10.3 and
sage/local/var/lib/sage/venv-pyt
Yes, you can delete the old venv. We do not uninstall other venvs that may
have been built previously.
On Wednesday, July 13, 2022 at 1:08:57 PM UTC-7 marc@gmail.com wrote:
> After working around the issues with the bootstrap script and symengine_py
> I have managed to build 9.7.beta5 on a
I don't want to have to remember to do this by hand. If I delete all of
the venvs before starting an incremental build will the build still work,
and will it create a new venv that is appropriate for its python, even if
the python version has not changed?
- Marc
On Wednesday, July 13, 2022 at
That statement is actually false. I think this issue needs to be
addressed. I think the old venvs should be removed when doing an
incremental build, since I cannot think of any use for them.
Here is the problem. When I did an incremental build with the
venv-python3.10.3 in place, a new venv
I used sed to fix the 16 files with bad shebangs in
sage/venv-python3.10.5/bin and that appeared to produce a working copy of
sage. So perhaps the bad shebangs are the only reason that
venv-python3.10.5 depends on venv-python3.10.3.
- Marc
On Thursday, July 14, 2022 at 7:30:47 AM UTC-5 Marc C
On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote:
> When I did an incremental build with the venv-python3.10.3 in place, a new
> venv named python3.10.5 was created. But that new venv depends on the old
> 3.10.3 venv. In fact, there are at least 16 executable files in
>
On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote:
> If I delete all of the venvs before starting an incremental build will the
> build still work, and will it create a new venv that is appropriate for its
> python, even if the python version has not changed?
>
Yes.
--
Y
I've opened https://trac.sagemath.org/ticket/34181 for this.
On Thursday, July 14, 2022 at 7:36:15 AM UTC-7 Matthias Köppe wrote:
> On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote:
>
>> When I did an incremental build with the venv-python3.10.3 in place, a
>> new venv nam
FWIW, a recent routine update of Debian testing removed part of the flint
libraries used by Sage ; I tried to re/.configure to re-specify the use of
the (new) system flint, but then make failed due to the snag already
reported on documentation building ; I then resorted to make distclean ;
re
did you run
./bootstrap
?
On Mon, 11 Jul 2022, 13:08 Marc Culler, wrote:
> I am not able to build beta5 after running make distclean using my
> standard build script that includes no external libraries. I am seeing
> errors about missing autoconf commands:
>
> make: `configure' is up to date.
>
Yes, I tried that but there was no change.
However when I deleted the calls to the undefined autoconf commands from
the configure script (which meant changing about 5 lines in the script) I
was able to run configure and the make build appears to be running normally
after that. Incidentally, th
On my Mac OS 12.4 with Intel Core i5, with homebrew and Xcode 13.4.1, it
compiled from the first build.
2022年7月11日(月) 15:21 Marc Culler :
> Yes, I tried that but there was no change.
>
> However when I deleted the calls to the undefined autoconf commands from
> the configure script (which meant
On Mon, Jul 11, 2022 at 2:21 PM Marc Culler wrote:
>
> Yes, I tried that but there was no change.
Was it succesfully run?
Do you have autotools and gettext installed?
>
> However when I deleted the calls to the undefined autoconf commands from the
> configure script (which meant changing about
As I said, I am not using any homebrew packages or any other external
libraries for this build. Sage should be able to build without homebrew,.
The binary macOS app needs to be self-contained and relocatable.
The configure file for previous betas did not use the AC_LIB_RPATH command,
although
On Mon, Jul 11, 2022 at 3:54 PM Marc Culler wrote:
>
> As I said, I am not using any homebrew packages or any other external
> libraries for this build. Sage should be able to build without homebrew,.
You need autotools if you want to modify ./configure
They can come from Homebrew, conda, doesn
I do not install anything on my build system (except I am forced to install
the homebrew gfortran on the arm64 build system). Everything needed to
build sage must be included in the sage repo, and until 9.7.beta5 that was
the case.
I do not think it would be wise to require people to install gett
On Mon, Jul 11, 2022 at 10:01 AM Dima Pasechnik wrote:
>
> One way to fix it is to re-create ./configure from ./bootstrap
>
The problem with this is that the bootstrap script in beta5 generates
warnings about the exact same commands, but then it still goes ahead and
produces a configure script t
On Mon, Jul 11, 2022 at 4:02 PM Marc Culler wrote:
>
> I do not install anything on my build system (except I am forced to install
> the homebrew gfortran on the arm64 build system). Everything needed to build
> sage must be included in the sage repo, and until 9.7.beta5 that was the case.
>
>
On Mon, Jul 11, 2022 at 4:06 PM Marc Culler wrote:
>
> On Mon, Jul 11, 2022 at 10:01 AM Dima Pasechnik wrote:
>>
>>
>> One way to fix it is to re-create ./configure from ./bootstrap
>
>
> The problem with this is that the bootstrap script in beta5 generates
> warnings about the exact same comman
On Monday, July 11, 2022 at 8:11:38 AM UTC-7 Dima Pasechnik wrote:
> that's a bug in ./bootstrap then.
>
Yes, see https://trac.sagemath.org/ticket/34152 for a proposed fix
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from
21 matches
Mail list logo
