Hi,
> I just stumbled on the website
http://www.catb.org/~esr/writings/taoup/html/ch10s05.html, which describes
some of the history of command line options in Unix and related systems.
Thank you so much for sharing a bit of the history and tradition of Unix.
Regards,
phiho
On Tue, Jun
Hi,
> When SAGE_ROOT is not available, "sage --advanced" will not show the
commands for rebuilding Sage, which need SAGE_ROOT.
and any other options like "sage --coverageall", :sage --testall", ... and
what else?
Not only that "sage --advanced" will not show the options but also 'sage'
should
Hi,
> "It is not supported to move the SAGE_ROOT or SAGE_LOCAL directory after
building Sage. If you do move the directories, you will have to run make
distclean and build Sage again from scratch."
So, practically speaking, BOTH "$SAGE_ROOT" and "$SAGE_LOCAL" are part of
the 'sage' installation?
Dear All,
A plain vanilla Sage 9.7 Beta1 was built from "~/sage-9.7$/beta1" which
then is renamed to "~/sage-9.7$/beta1_"
"root.beta1" is a symlink to "$SAGE_ROOT/sage" and "local.beta1" is a
symlink to "$SAGE_LOCAL/bin/sage".
Please find appended below the scenario when some of the 'sage'
Hi,
Thank you for the information, both of these work:
https://trac.sagemath.org/wiki/patchbot
https://wiki.sagemath.org/buildbot?action=info
Regards,
phiho
On Mon, May 30, 2022 at 2:53 PM Samuel Lelievre
wrote:
> phiho wrote:
> >
> > Is this link correct:
Dear All,
Is this link correct: https://wiki.sagemath.org/buildbot ?
*This page does not exist yet. You can create a new empty page, or use one
of the page templates.*
Thank you for your help.
phiho
~/sage-9.7/b1.3$ root.beta1 -patchbot
Traceback (most recent call last):
File "", line 1, in
Hi,
> https://researchseminars.org/seminar/SageDays112358
Thank you for organizing the seminar.
Please broadcast the recordings at the event.
Best regards,
phiho
On Thursday, May 26, 2022 at 2:57:13 AM UTC-4 Matthias Koeppe wrote:
> Preliminary program:
>
Hi,
Thanks for the link but it is way above her head right now.
Thanks for your support, anyway.
Regards,
phiho
On Fri, May 27, 2022 at 5:39 PM John H Palmieri
wrote:
> The development process and the trac server are documented at
>
;>>>
>>>> # Check that we are not building in a directory containing spaces
>>>> if echo "$SAGE_ROOT" | grep " " > /dev/null ; then
>>>> echo "The path to the Sage root directory ($SAGE_ROOT) contains a
>>
Hi,
> Please open a ticket for it.
Thank you for the encouragement but this hitchhiker has admitted her
weakness with the ticket system.
It is just a copy and paste snippet, maybe those who are in charge of '
configure.ac' could help with the ticket issue?
All the best,
phiho
On Fri, May
the Sage root directory ($SAGE_ROOT) contains a
>> space. Sage will not build correctly in this case."
>> exit 1
>> fi
>>
>>
>>
>>
>> On Fri, May 27, 2022 at 7:33 AM ph h wrote:
>>
>>> Hi,
>>>
>>> M
ST=1
sage-spkg-info "$PKG_BASE") | sed -e "s|
https://trac.sagemath.org/ticket/\([0-9]*\)|:trac:\`\1\`|g" -e "s|
https://arxiv.org/abs/cs/\([0-9]*\)|:arxiv:\`cs/\1\`|g" >
"$OUTPUT_DIR"/$PKG_BASE.rst
echo >> "$OUTPUT_INDEX" "
ho "$SAGE_ROOT" | grep " " > /dev/null ; then
echo "The path to the Sage root directory ($SAGE_ROOT) contains a
space. Sage will not build correctly in this case."
exit 1
fi
On Fri, May 27, 2022 at 7:33 AM ph h wrote:
> Hi,
>
> Maybe the tests with
Hi,
Maybe the tests with "contains_spaces()" in 'src/bin/sage-env' can be
replaced with the followings in 'configure.ac' (after line 75,
SAGE_LOCAL="$prefix"):
*http://configure.ac>>*
# Check that we are not building in a directory containing spaces
AS_IF([echo "$ac_pwd" |grep " " >/dev/null],
>>
>> *# at validating time.*
>>
>>
>> On Tue, May 24, 2022 at 10:14 PM ph h wrote:
>>
>>> Dear All,
>>>
>>> Is this feasible [ 1 = 1+0i ] <=> [ 1 = 1 ] ?
>>>
>>> Regards,
>>>
>>> phiho
&
he src/doc/bootstrap can be
>> completely independent of SAGE_ROOT/sage:
>>
>> # ./sage -advanced> "$OUTPUT"
>>
>> SAGE_ROOT="$(pwd)"
>> . "src/bin/sage-version"
>> . "src/bin/sage-usage_advanced" > "$OUTPUT"
oc/bootstrap can be completely
independent of SAGE_ROOT/sage:
# ./sage -advanced> "$OUTPUT"
SAGE_ROOT="$(pwd)"
. "src/bin/sage-version"
. "src/bin/sage-usage_advanced" > "$OUTPUT"
Is there a better way to achieve this?
Thank you for your hel
P.S: Sorry, there was a typo here:
*# at configuration time.*
should read
*# at validating time.*
On Tue, May 24, 2022 at 10:14 PM ph h wrote:
> Dear All,
>
> Is this feasible [ 1 = 1+0i ] <=> [ 1 = 1 ] ?
>
> Regards,
>
> phiho
>
> **
> if [ 1 = 1+0i
Dear All,
Is this feasible [ 1 = 1+0i ] <=> [ 1 = 1 ] ?
Regards,
phiho
**
if [ 1 = 1+0i ]; then
# Make sure that SAGE_ROOT is either an absolute physical directory name
# or empty.
*# An absolute physical directory name has already been embedded and
exported*
*# at configuration
Dear All,
Does this apply only to "$SAGE_ROOT"?
Can sub-directories of "$SAGE_ROOT" (like "lo space cal") contain spaces?
Is it OK for $SAGE_LOCAL to contain spaces? If it is so, why the
differences?
Thank you for your help.
Regards,
phiho
**
if contains_spaces X${SAGE_ROOT}X ; then
Hi,
> > What does it mean for 'MANIFEST.in' to 'include' 'MANIFEST.in'?
> See https://packaging.python.org/en/latest/guides/using-manifest-in/
> This is not specific to Sage.
This is very interesting.
Thanks so much.
phiho
On Tue, May 24, 2022 at 2:11 PM ph h wrote:
> Dear
Dear All,
How do these 'include' statements in 'MANIFEST.in' work?
What does it mean for 'MANIFEST.in' to 'include' 'MANIFEST.in'?
Is there a corresponding 'MANIFEST' generated from this 'MANIFEST.in' ?
Thank you for your help.
Regards,
phiho
global-include *.c *.cc *.cpp *.h *.hh *.hpp
Dear All,
Please find appended below the 3 input files for the configuration process.
Please advise if this switch from embedded 'resolvelinks' to embedded
$SAGE_ROOT and $SAGE_LOCAL would break any rules in Sage installation.
To this hitchhiker, the switch seems to be beneficial in that she
Hi,
Is it this snippet, would you please elaborate?
# Make sure that SAGE_ROOT is either an absolute physical directory name
# or empty.
if [ -n "$SAGE_ROOT" ]; then
export SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)
fi
BTW, it is rather confusing to see in '$SAGE_LOCAL/bin/sage':
Dear All,
Please advise the use of SAGE_ROOT when it is exported
from '$SAGE_LOCAL/bin/sage':
# Determine SAGE_ROOT, SAGE_LOCAL, and SAGE_VENV.
unset SAGE_VENV
if [ -x "${SELF}-config" ]; then
# optional sage-config console script, installed by sage_conf
export
Hi,
"""
We change the bootstrap scripts so that they invoke
build/bin/sage-package directly
instead of going through the SAGE_ROOT/sage script.
"""
This is great news, a big time saver. Thank you so much.
Until then, this hitchhiker needs to restore the original
'$SAGE_ROOT/sage' before she can
P.S: Sorry, there was a typo, "$SAGE_LOCAL/sage" should read
"$SAGE_LOCAL/bin/sage"
On Mon, May 16, 2022 at 4:35 AM ph h wrote:
> Dear All,
>
> Please find appended below a snippet from $SAGE_ROOT/sage.
>
> Would it be nice if "$SAGE_LOCAL/sage"
Dear All,
Please find appended below a snippet from $SAGE_ROOT/sage.
Would it be nice if "$SAGE_LOCAL/sage" could be used without assumptions
instead of "$SAGE_ROOT/local/bin/sage" with the assumption that 'SAGE_LOCAL
is the "local" subdirectory'
BTW, should "$SAGE_LOCAL/sage" be the first
P.S: Sorry for the noise at an early hour. 'sage --sdist' was run from the
wrong directory.
On Fri, May 13, 2022 at 12:54 AM ph h wrote:
> Dear All,
>
> This happens at 12:52 AM EST, May 13
>
> Please advise if this is expected.
>
> Thank you for your help.
>
> Rega
Dear All,
This happens at 12:52 AM EST, May 13
Please advise if this is expected.
Thank you for your help.
Regards,
phiho
--
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
Hi,
> Renaming the installed "sage" script (you seem to have renamed it to
"sage.orig") is not supported.
Thank you for the information..
Regards,
phiho
On Tue, May 10, 2022 at 7:58 PM Matthias Koeppe
wrote:
> Renaming the installed "sage" script (you seem to have renamed it to
>
Dear All,
Unmodified Sage 9.6 rc3 was configured and installed wtth
"--prefix=/mnt/g/Maths/sage-9.6/0mod" and "~/bin/" is in the PATH.
ln -s
/mnt/g/Maths/sage-9.6/0mod/bin/sage /mnt/g/Maths/sage-9.6/testlinks/0mod
ln -s /mnt/g/Maths/sage-9.6/testlinks/0mod ~/bin/0mod
Under
with the latter?
Would it be nice if 'Sage' has more Python code?
Regards,
phiho
On Wed, May 4, 2022 at 8:15 AM Michael Orlitzky
wrote:
> On Wed, 2022-05-04 at 01:56 -0400, ph h wrote:
> > Hi,
> >
> > > Sadly, readlink is not a POSIX standard utili
xt few weeks, please allow her to catch
up upon her return.
Thank you for your help.
Regards,
phiho
On Tue, May 3, 2022 at 7:39 PM Michael Orlitzky
wrote:
> On Tue, 2022-05-03 at 14:30 -0700, ph h wrote:
> >
> > *SELF=$(readlink -f $0)
>
> Sadly, readlink is not a POSIX sta
at 21:33 -0400, ph h wrote:
> > P.S: What does this mean? Thanks.
> >
> > https://man7.org/linux/man-pages/man2/readlink.2.html
> > CONFORMING TO top
> > <https://man7.org/linux/man-pages/man2/readlink.2.html#top_of_page>
> >
> >*r
1-2008.
*readlinkat*(): POSIX.1-2008.
On Tue, May 3, 2022 at 9:07 PM ph h wrote:
> Hi,
>
> > Sadly, readlink is not a POSIX standard utility; otherwise we would
> > already be using it in place of resolvelinks().
>
> Thank you so much. That's the constraint that
, 2022 at 7:39 PM Michael Orlitzky
wrote:
> On Tue, 2022-05-03 at 14:30 -0700, ph h wrote:
> >
> > *SELF=$(readlink -f $0)
>
> Sadly, readlink is not a POSIX standard utility; otherwise we would
> already be using it in place of resolvelinks().
>
> --
> You received
Dear All,
This hitch hiker has been enjoying scratching her itch (caused by a virus
from the Forth camp she visited many moons ago, smiley)
She has been wondering, it cannot be this simple. She must have missed
something very important. Please help her to find out what she is missing.
Her
Hi,
Thank you for your response.
> This also seems like a lot of work to eliminate some minor code
duplication
Besides being error prone (in maintaining duplicates), it seems to start
small with just 'resolvelinks', then the whole files ('sage', 'sage-env'),
then whole directories?
Furthermore,
Dear All,
> We cannot debug branches for you that we cannot see.
This is so true, it is hard enough to debug one's own code in a big system
like SageMath, let alone the invisible one.
It was hoped that the pattern of this bug is well known to the experienced
SageMath developers.
Please find
;> case scenarios?
>>
>> While waiting for someone to share their secrets, It was found that the
>> "advanced incantations" is missing some important pieces,
>> (like '*sage -cbr*" "Configure" so that advanced users do not
>> have to face que
Hi,
Thank you so much for such a clear explanation on all the 'what', 'why' and
'where'.
Regards,
phiho
On Wednesday, April 27, 2022 at 8:46:11 PM UTC-4 John H Palmieri wrote:
> Why 99%? The code says
>
> for goal in [70, 75, 80, 85, 90, 95, 99]:
> if score < goal:
>
Hi,
> If you have made changes to the code and would like to discuss them,
> the procedure is to open a Trac ticket and to push the branch there.
Thank you for the advice. The idea is still being explored.
It will be shared when tests are encouraging.
Help in testing is much appreciated.
Hi,
Sorry about that. Honestly it is hard to formulate a question from this
output. Let's try.
What are these 1237 functions, where would they come from and why 99% but
not 100%.
Actually, this run was meant to test the Refactor to see if anything
is broken, without knowing what it does and
~/sage-9.6/git/rc2$ sage.mod/sage --coverageall
__init__.py: 100.0% (1 of 1)
algebras/affine_nil_temperley_lieb.py: 100.0% (11 of 11)
algebras/algebra.py: 100.0% (1 of 1)
algebras/askey_wilson.py: 100.0% (21 of 21)
algebras/associated_graded.py: 100.0% (9 of 9)
algebras/cellular_basis.py: 100.0%
Cloning into '/home/hph/sage-9.6/git/rc2/sage.mod/tmp/sage-9.6.rc2'...
done.
Updating files: 100% (9399/9399), done.
Enumerating objects: 841207, done.
Counting objects: 100% (841207/841207), done.
Delta compression using up to 8 threads
Compressing objects: 100% (801365/801365), done.
Writing
Dear All,
Please advise which of the "sage --advanced" should be used to
test "Refactor":
1. After git checkout
2. After 'make configure'
3. After './configure'
4. After 'make'
Some practical use case scenario, where applicable, is much appreciated.
For your convenience, the
.
On Sun, Apr 24, 2022 at 5:52 PM ph h wrote:
> P.S: It happened because sage was run before 'make configure' was done
>
> ~/sage-9.6$ git/sage.mod/sage
>
> On Sun, Apr 24, 2022 at 5:43 PM ph h wrote:
>
>> Dear All,
>>
>> When is it safe to clean up '
r secrets, It was found that the
"advanced incantations" is missing some important pieces,
(like '*sage -cbr*" "Configure" so that advanced users do not
have to face questions like "Did you run configure?"
On Saturday, April 23, 2022 at 8:10:37 PM UTC-4 ph
Dear All,
Someone is trying to build and run 'sage' with this advanced incantation
'sage -br'
~/sage-9.6/rc0.mod2$ sage.GOOD/sage -br
and she was asked " Did you run configure?"
Unfortunately, "sage --advanced" does not give any incantation for this
('sage -c' is NOT for 'configure')
She is
P.S: It happened because sage was run before 'make configure' was done
~/sage-9.6$ git/sage.mod/sage
On Sun, Apr 24, 2022 at 5:43 PM ph h wrote:
> Dear All,
>
> When is it safe to clean up '~./.sage' ?
> How can 'sage-cleaner' be invoked manually?
> Why is it
Dear All,
When is it safe to clean up '~./.sage' ?
How can 'sage-cleaner' be invoked manually?
Why is it invoked because of 'ModuleNotFoundError: No module named 'sage'?
Please find appended below the console output
Regards,
phiho
Sourcing /home/hph/sage-9.6/git/sage.mod/resolvelinks.dot,
uch appreciated.
Regards,
phiho
On Sat, Apr 23, 2022 at 5:14 PM Dima Pasechnik wrote:
>
>
> On Sat, 23 Apr 2022, 19:00 ph h, wrote:
>
>> Hi,
>>
>> Thank you for your response.
>>
>> > Note: the ".in" suffix doesn't mean "incl
because they may not
be familiar with github?
Regards,
phiho
On Sat, Apr 23, 2022 at 12:08 PM Michael Orlitzky
wrote:
> On Sat, 2022-04-23 at 08:28 -0400, ph h wrote:
> > Dear All,
> >
> > If the three files:
> >
> >1. sage/sage
> >2. sa
' is run at $SAGE_ROOT
2. Before './configure' is run at $SAGE_ROOT
3. Before 'make' is run at $SAGE_ROOT
4. After installation is completed
Thank you for your guidance.
Regards,
phiho
On Fri, Apr 22, 2022 at 7:36 AM Michael Orlitzky
wrote:
> On Fri, 2022-04-22 at 01:03 -0400, ph h wr
ot;?
> The function.
What are the problems with the current version of 'resolvelinks', how
should it be factored?
What are the problems when just the function is sourced, not the whole
'sage/src/bin/sage-env' script
When it is properly done, can 'Copy' be replaced with 'source'?
Thank you
Dear All,
While waiting for advice on the questions on the thread "Copy"
"""
BTW, is symlink a solution for "Copy & Paste"?
By another way, are there reasons that "Copy & Paste & Symlinks" is better
than just symlinks.
"""
This is not meant "to look a gift horse in the mouth", but "straight
Dear All,
These two build processes have been stalling for several hours at 'Setting
up build directory...' .
Please advise if this is something related to local connectivity or
overloaded servers or something else.
They have been restarted a few times (including powering off the cable
Dear All,
It was found in 'sage/src/sage/combinat/words/notes/history.txt':
A history of the Words Library
[English history to be done. To be translated from below.]
Please find
ed using its
>>>> actual path.
>>>> 631: nodeenv_activate=`resolvelinks "$nodeenv_activate"`
>>>> 632
>>>>
>>>> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagelib/src/bin/sage:
>>>>4 # the top-level &qu
kgs/sage-conf_pypi/sage_root/build/pkgs/sagemath_objects/src/bin/sage:
>>4 # the top-level "sage" script. Please keep them synchronized.
>>5: resolvelinks() {
>>6 # $in is what still needs to be converted (normally has no
>> starting slash)
>>
velinks "${0}")
82
sage/pkgs/sagemath-standard/bin/sage-env:
35 #
36: resolvelinks() {
37 # $in is what still needs to be converted (normally has no
starting slash)
338 # non-existing directory.
339: DOT_SAGE=`resolvelinks "$HOME/.sage"`
Hi,
> VS code cannot debug python code that is executed by a shell script.
It looks like he has set the expectation too high.
> My strategy usually is to create a new (temporary) python file that
contains the code I want to debug (or calls the method I want to debug),
and then use the python
Dear All,
At the top of 'sage/src/bin/sage' script:
# WARNING: this function is copy/pasted from both src/bin/sage-env and
# the top-level "sage" script. Please keep them synchronized.
resolvelinks() {
Is there any other way to keep them in sync without using Copy?
Just curiosity.
Regards,
Dear All,
There was a related discussion here:
https://ask.sagemath.org/question/43240/sagemath-and-vscode/
Is there any way to debug SageMath using VScode client on Windows and
server on "remote WSL" (on the same machine)?
Your advice is much appreciated.
Regards,
phiho
--
You received
Hi,
> make pytest
Thank you for the info, that will be tried when RC1 comes out
BTW, these tests are great features of this release, 9.6.
Thank you, sage team.
Regards,
phiho
On Tuesday, April 12, 2022 at 12:16:28 AM UTC-4 adarsh.k...@gmail.com wrote:
> I had a similar problem with Sage
o apt-get update
>>>>>>> $ sudo apt-get install libflint-arb-dev libcdd-dev
>>>>>>> libcdd-tools ecl libec-dev eclib-tools libflint-dev libfplll-dev
>>>>>>> libgc-dev
>>>>>>> libgiac-dev xcas lcalc liblfunction-dev libho
t;>>>> configure:
>>>>>
>>>>> hint: After installation, re-run configure using:
>>>>>
>>>>> $ ./config.status --recheck && ./config.status
>>>>>
>>>>>
>>>>> O
uot;copyright", "credits" or "license" for more information.
>>>>>
>>>>> >>> import sqlite3, ctypes, math, hashlib, crypt, socket, zlib,
>>>>> distutils.core, ssl
>>>>> :1: DeprecationWarning: The di
Dear All,
Please advise if there are any documentation on the tests performed in the
Makefile:
TESTALL = ./sage -t --all
PTESTALL = ./sage -t -p --all
# Flags for ./sage -t --all.
# When the documentation is installed, "optional" also includes all tests
marked 'sagemath_doc_html',
# see
atives
>>
>> Should 'setuptools' be installed so that sage will use python-3.10.4 on
>> the system?
>>
>> Thanks for your help
>>
>> Regards,
>>
>> phiho
>>
>>
>> Regards,
>>
>> phiho
>>
>>
>
Dima Pasechnik wrote:
> On Sat, Apr 9, 2022 at 4:50 PM ph h wrote:
> >
> > $ python
> > Python 3.10.4 (main, Mar 24 2022, 16:12:56) [GCC 9.4.0] on linux
> > Type "help", "copyright", "credits" or "license" for more information.
.core' has been deprecated (and removed from
python3.10-dev?)
> Use setuptools or check PEP 632 for potential alternatives
Should 'setuptools' be installed so that sage will use python-3.10.4 on the
system?
Thanks for your help
Regards,
phiho
Regards,
phiho
On Sat, Apr 9, 2022 at 7:37
gure:33052: to try to use a different system python, use ./configure
--with-python=/path/to/python
configure:33079: no suitable system package found for SPKG python3
#
Please advise what else needs to be done to fix this issue.
Thank you for your help.
Regards,
phiho
On Fri, Apr 8, 2022 at 5
Hi,
> sudo apt-get install libffi-dev
Thanks, that works.
phiho
On Fri, Apr 8, 2022 at 5:18 PM Dima Pasechnik wrote:
>
>
> On Fri, 8 Apr 2022, 22:06 ph h, wrote:
>
>> Hi,
>>
>> > Yes, this is needed for Python headers, but still
>> > sudo
Hi,
> Yes, this is needed for Python headers, but still
> sudo apt-get libffi-dev libbz2-dev bzip2 xz-utils liblzma-dev openssl
libssl-dev
~/sage-9.6$ sudo apt-get libffi-dev libbz2-dev bzip2 xz-utils liblzma-dev
openssl libssl-dev
E: Invalid operation libffi-dev
Is something missing on this
Dear All,
In following this thread, it was found out, on this WSL system:
~/sage-9.6$ python --version
Command 'python' not found, did you mean:
command 'python3' from deb python3
command 'python' from deb python-is-python3
~/sage-9.6$ python3 --version
Python 3.8.10
~/sage-9.6$
Dear List,
Sagemath occupies a whole section (Appendix E) in "The Calabi-Yau
Landscape: from Geometry, to Physics, to Machine-Learning" by Yang-Hui He:
https://arxiv.org/abs/1812.02893
Does Sagemath Sagemanifolds have any tutorial on this kind of manifolds?
Any pointer is much appreciated.
Hi,
This link also works for me:
https://link.springer.com/content/pdf/10.1007/s11538-022-00999-4.pdf
Regards,
phiho
On Wed, Feb 23, 2022 at 2:38 PM Dima Pasechnik wrote:
> On Wed, Feb 23, 2022 at 7:23 PM William Stein wrote:
> >
> > Hi
> >
> > UCLA just published a new paper about
Hello List,
Thank you so much for your clarification and insight
I am looking forward to using that special magic with sage in the future.
Best regards,
phiho
On Tue, Feb 22, 2022 at 12:40 PM William Stein wrote:
> On Tue, Feb 22, 2022 at 9:31 AM Nils Bruin wrote:
> >
> > On Sunday, 20
ect syntax is
> sage -n --port 1234
> (no space between -- and port, because --port is just an option name)
>
> it seems to be a doumentation error that one needs a space.
>
>
> On Mon, Feb 21, 2022 at 2:45 AM ph h wrote:
> >
> > Hi,
> >
> > ~/sage-9
Hi,
From http://localhost:/kernelspecs/sagemath/doc/prep/Calculus.html:
%auto
f(x)=x^3+1
@interact
def _(c=(1/3,(-1,1))):
P=plot(f,(x,-1,1))
fprime=derivative(f,x)
L(x)=fprime(c)*(x-c)+f(c)
Q=plot(L,(x,-1,1),color="red", linestyle="--")
show(P+Q+point((c,f(c)),
Hi,
Sage behavior seems to be different on the console:
~/sage-9.6/b01$ ./sage
┌┐
│ SageMath version 9.6.beta1, Release Date: 2022-02-13 │
│ Using Python 3.8.10. Type "help()" for help. │
Hi,
Thanks for the hint but setting SAGE_BUILD_DIR does not seem to work in
this case.
Regards,
phiho
On Thu, Feb 17, 2022 at 7:48 AM Tobias Diez wrote:
> From the logs:
> error: Command "gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong
Hi Matthias,
I have just finished the builds for sage 9.5 and 9.6 b01 successfully on
the root drive (instead of mounted drive which was OK for sage 9.4)
Thank you so much for your patience. I am wondering what is the problem
with the mounted drive.
Is it a bug in WSL or a feature in Ubuntu
Hi,
G: is a local HDD. sage 9.4 was successfully built on the same HDD
BTW, I will try to clone sage under my home directory instead of /mnt (and
cross my fingers, smile) to see if that helps with the build
Regards,
phiho
On Tue, Feb 15, 2022 at 11:47 AM Matthias Koeppe
wrote:
> (Is G: a
Hi,
Actually this approach was tried a few times before. The report was from a
fresh clone and build.
'MAKE="make -j8" make' was just tried again and the re-make ended
with these failed packages:
real 13m20.842s
user 14m38.391s
sys 6m4.781s
87 matches
Mail list logo
