[sage-support] Re: Problem with minimize_constrained

I filed this issue for your question. An analytical solution : # Potential extrema : points where all first derivatives are zero. PE = [{u:d[u].n() for u in d.keys()} for d in solve([G(x, y).diff(u) for u in (x, y)], (x, y), solution_dict=True)]

[sage-support] Re: Problem with rebuilding Sage

File On Saturday, December 16, 2023 at 1:46:44 AM UTC+5:30 David Ayotte wrote: > Can you post the following log file: > > /home/ruchitjagodara/sage/sage/logs/pkgs/sagelib-10.3.beta0.log > > here? There might

Re: [sage-support] Re: Problem with plot

It's probably just a build error. I'd try something like make sage_conf && make On Sat, Dec 16, 2023 at 9:36 AM Emmanuel Charpentier wrote: > > Le mercredi 13 décembre 2023 à 12:35:42 UTC+1, Philippe Delavalade a écrit : > > Hi. > > I'm using sage-10.2 with linux (slint-15.0 based on slackware 1

[sage-support] Re: Problem with plot

Le mercredi 13 décembre 2023 à 12:35:42 UTC+1, Philippe Delavalade a écrit : Hi. I'm using sage-10.2 with linux (slint-15.0 based on slackware 15.0) on the console. When I run p=plot(x^2); p there is no graphics on the screen, just the line Launched png viewer for Graphics object consist

[sage-support] Re: Problem with rebuilding Sage

Can you post the following log file: /home/ruchitjagodara/sage/sage/logs/pkgs/sagelib-10.3.beta0.log here? There might be some error message that would help us find the problem. Best, David A. Le vendredi 15 décembre 2023 à 14:00:02 UTC-5, Ruchit Jagodara a écrit : > I am trying to rebuil

[sage-support] Re: Problem iniciating sage

You are trying to run Sage on a virtual machine. This Linix virtual machine requires you to log in. I note that this virtual machine runs Linux 2.6.32 on a 32-bit virtual machine, which is downright paleontologic... Are you trying to run a pre-packaged "appliance" ? Those weren't updated for a

[sage-support] Re: Problem installing sage on Ubuntu.

Hi Maarten, Binaries for Sage 9.3 and Sage 9.4 were prepared taking advantage of too modern instruction sets not available on older processors, so they only work with recent cpus. The upcoming Sage 9.5 should work for everyone. In the meantime, workarounds include - build from source - install v

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

Sage 9.3 has been released. Try it and not 9.2 please. On Tue, 18 May 2021, 06:27 Mike Lensi, wrote: > I seem to be having a similar issue. Are there any new recommendations? > > On Wednesday, October 7, 2020 at 8:39:59 AM UTC-6 wdjo...@gmail.com wrote: > >> Hi: >> >> The compiler still can't f

[sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

I seem to be having a similar issue. Are there any new recommendations? On Wednesday, October 7, 2020 at 8:39:59 AM UTC-6 wdjo...@gmail.com wrote: > Hi: > > The compiler still can't find installed python3: > > wdj@jeeves sage-9.2.rc0 % which python3 > > /Library/Frameworks/Python.framework/Versi

[sage-support] Re: Problem with load in sagemath 9.0 on ubuntu 20.04

On Tuesday, October 20, 2020 at 11:57:21 AM UTC-7, Carl Eberhart wrote: > > Thanks. After looking for the definition of of preparse_file it appears > that it is imported from a binary file. Will I have to download the source > and recompile to fix this? > Your code in orthogtraps19.sage like

[sage-support] Re: Problem with load in sagemath 9.0 on ubuntu 20.04

Thanks. After looking for the definition of of preparse_file it appears that it is imported from a binary file. Will I have to download the source and recompile to fix this? Carl On Monday, October 19, 2020 at 4:15:27 PM UTC-5 Matthias Koeppe wrote: > On Monday, October 19, 2020 at 10:36:05

[sage-support] Re: Problem with load in sagemath 9.0 on ubuntu 20.04

On Monday, October 19, 2020 at 10:36:05 AM UTC-7, Carl Eberhart wrote: > > I can't load a sage file in either the notebook or terminal version of Sage > File "", line 121 > if s<>_sage_const_0 : > ^ > SyntaxError: invalid syntax > The syntax <> for "not equal" is no longer valid in

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

On Thu, Oct 8, 2020 at 2:47 PM slelievre wrote: > 2020-10-08 17:38:08 UTC, David Joyner: > > > > I can log in but don't seem to have permission to add a comment to trac. > > Your trac account was missing a name and an email. > I filled those in, can you try again? > That must have worked, thank

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

2020-10-08 17:38:08 UTC, David Joyner: > > I can log in but don't seem to have permission to add a comment to trac. Your trac account was missing a name and an email. I filled those in, can you try again? -- You received this message because you are subscribed to the Google Groups "sage-support

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

On Thu, Oct 8, 2020 at 9:48 AM slelievre wrote: > 2020-10-07 21:09:18 UTC, John H Palmieri: > > > > including details of which homebrew packages you've installed. > > To get your installed homebrew packages listed in a file: > ``` > $ brew list --versions > brew-list-versions.txt > ``` > Thank y

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

2020-10-07 21:09:18 UTC, John H Palmieri: > > including details of which homebrew packages you've installed. To get your installed homebrew packages listed in a file: ``` $ brew list --versions > brew-list-versions.txt ``` Or to add the date to the filename: ``` $ brew list --versions > brew-list-

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

I would suggest not to touch macOS 11 until it is running Homebrew (or help them), because they basically have the same issues to solve. On Wed, 7 Oct 2020, 22:09 John H Palmieri, wrote: > I think you should report this at #30651, including details of which > homebrew packages you've installed.

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

I think you should report this at #30651, including details of which homebrew packages you've installed. It was suggested at https://trac.sagemath.org/ticket/30494#comment:92 that homebrew's gfortran may not work with Big Sur, so you might want to install Sage's version of that, too. On Wednes

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

On Wed, Oct 7, 2020 at 12:37 PM David Lowry-Duda wrote: > sage -f [opts] [packages] is a shortcut for force-building specified > packages. If you examine the output of `sage -advanced` on a commandline, > this is noted there. The command `sage -advanced` is a more complete > version of the typica

Re: [sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

On Wed, Oct 7, 2020 at 1:06 PM John H Palmieri wrote: > Building Sage on Big Sur is being tracked at > https://trac.sagemath.org/ticket/30651; see also > https://trac.sagemath.org/ticket/30494. Do you have homebrew installed, > and if so, which packages? You could try forcing Sage to build its ow

[sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

Building Sage on Big Sur is being tracked at https://trac.sagemath.org/ticket/30651; see also https://trac.sagemath.org/ticket/30494. Do you have homebrew installed, and if so, which packages? You could try forcing Sage to build its own zlib, for example, to try to get Sage's Python to find it.

[sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

sage -f [opts] [packages] is a shortcut for force-building specified packages. If you examine the output of `sage -advanced` on a commandline, this is noted there. The command `sage -advanced` is a more complete version of the typical help command `sage -h`. (I don't know how to solve your actu

[sage-support] Re: problem compiling sage-9.2.rc0 on big sur, xcode 12.01

On a lark, I ran ./sage -f This is undocumented as far as I can tell and I've no idea what it does (of course ./sage doesn't work since it didn't compile - see my previous email in this thread). It seemed to try to compile python 3.8.5. I pasted the tail end below, in case this is useful. BTW, what

[sage-support] Re: Problem with sagetex and fancyhdr

(By the way, I wasn't able to ask at https://ask.sagemath.org/ because my question was detected as spam. So was an answer or comment I tried to post earlier in the day.) -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this

[sage-support] Re: Problem with factor in SymbolicRing

Possible workaround: sage: num -1/2*(12*r^4*x + 4*r^2*x^3 + 4*r^2*x*y^2 - 4*r^2*x + 4*x^3 + 4*x*y^2)^2/(r^6 + 6*r^4*x^2 + r^2*x^4 + 2*r^4*y^2 + 2*r^2*x^2*y^2 + r^2*y^4 - 2*r^2*x^2 + x^4 + 2*r^2*y^2 + 2*x^2*y^2 + y^4)^2 - 1/2*(4*r^4*y + 4*r^2*x^2*y + 4*r^2*y^3 + 4*r^2*y + 4*x^2*y + 4*y^3)^2/(r^6

[sage-support] Re: Problem with factor in SymbolicRing

I forgot to add, it worked in 8.1 version and it does not work since 8.4 (at least). Adding the option dontfactor=[some variable not involved in h] it works but much slower. El miércoles, 24 de julio de 2019, 13:31:08 (UTC+2), Enrique Artal escribió: > > I have encountered a problem with factor

[sage-support] Re: problem with matrix over finite field

Hi Harald, On 2019-07-12, Harald Schilly wrote: >> Do you literally mean "user", not the specific name of a single user? > > yes, all cocalc projects run under the same user "user" in their own > container. > No, /home/user is a read/write mounted volume and ~/.sage is a > directory inside of it

Re: [sage-support] Re: problem with matrix over finite field

On Fri, Jul 12, 2019 at 3:38 PM Simon King wrote: > > sage: DOT_SAGE > > '/home/user/.sage/' > > Do you literally mean "user", not the specific name of a single user? yes, all cocalc projects run under the same user "user" in their own container. $ echo $USER user $ id uid=2001(user) gid=2001(us

[sage-support] Re: problem with matrix over finite field

Hi Harald, On 2019-07-12, Harald Schilly wrote: > Interestingly, this works: > > matrix(GF(16), [[1,0], [0, 1]]) while matrix(GF(25), [[1,0], [0, 1]]) fails > with the above error. MeatAxe is only used for finite non-prime fields of order <255, and I forgot to add: Only in odd characteristic (

[sage-support] Re: problem with matrix over finite field

Hi Harald, On 2019-07-12, Harald Schilly wrote: > Ok... To me, this sounds like we have to uninstall MeatAxe on CoCalc. > > The CoCalc setup is quite easy to explain, and so far I wasn't aware of any > issues. Sage is in a globally shared read-only directory > /ext/sage/sage- and permissions ar

[sage-support] Re: problem with matrix over finite field

Hi Dima, On 2019-07-12, Dima Pasechnik wrote: > Hi Simon, > isn't MeatAxe interfaced via a library, rather than via files?! > Doing arithmetics on small matrices storing them on a disk is insanely > inefficient... Maybe. Do you mean one should instead compute a new multiplication table in memory

[sage-support] Re: problem with matrix over finite field

Hi Harald, On 2019-07-12, Harald Schilly wrote: > On Friday, July 12, 2019 at 11:48:40 AM UTC+2, Simon King wrote: >> >> sage: DOT_SAGE >> '/home/king/.sage/' > > It's > > sage: DOT_SAGE > '/home/user/.sage/' Do you literally mean "user", not the specific name of a single user? Does that per

Re: [sage-support] Re: problem with matrix over finite field

by the way, libgap will get a direct interface to GAP matrices, which might be a useful matrix backend for various purposes. See https://github.com/gap-system/gap/pull/3554 On Fri, Jul 12, 2019 at 1:29 PM Harald Schilly wrote: > > Ok... To me, this sounds like we have to uninstall MeatAxe on CoC

Re: [sage-support] Re: problem with matrix over finite field

Ok... To me, this sounds like we have to uninstall MeatAxe on CoCalc. The CoCalc setup is quite easy to explain, and so far I wasn't aware of any issues. Sage is in a globally shared read-only directory /ext/sage/sage- and permissions are set such that a user "user" can read/exec it. Hence, onl

Re: [sage-support] Re: problem with matrix over finite field

Le 12/07/2019 à 11:56, Harald Schilly a écrit : I've no idea why this is happening on CoCalc. My first guess is there is an optional package installed, which is causing this. As Simon already said, there is meataxe installed. While Interestingly, this works: matrix(GF(16), [[1,0], [0, 1]]) w

Re: [sage-support] Re: problem with matrix over finite field

Hi Simon, isn't MeatAxe interfaced via a library, rather than via files?! Doing arithmetics on small matrices storing them on a disk is insanely inefficient... Dima On Fri, Jul 12, 2019 at 11:48 AM Simon King wrote: > > Hi Hal, > > On 2019-07-11, Hal Snyder wrote: > > sage: a = var('a') > > ...

[sage-support] Re: problem with matrix over finite field

On Friday, July 12, 2019 at 11:48:40 AM UTC+2, Simon King wrote: > > > sage: DOT_SAGE > '/home/king/.sage/' It's sage: DOT_SAGE '/home/user/.sage/' Which I bet is the wrong place to look. (all cocalc projects are essentially linux docker containers, where /home/user is $HOME, though)

[sage-support] Re: problem with matrix over finite field

On Friday, July 12, 2019 at 11:48:40 AM UTC+2, Simon King wrote: > > > sage: DOT_SAGE > '/home/king/.sage/' It's sage: DOT_SAGE '/home/user/.sage/' Which I bet is the wrong place to look. (all cocalc projects are essentially linux docker containers, where /home/user is $HOME, though)

[sage-support] Re: problem with matrix over finite field

I've no idea why this is happening on CoCalc. My first guess is there is an optional package installed, which is causing this. Interestingly, this works: matrix(GF(16), [[1,0], [0, 1]]) while matrix(GF(25), [[1,0], [0, 1]]) fails with the above error. -- You received this message because you

[sage-support] Re: problem with matrix over finite field

Hi Hal, On 2019-07-11, Hal Snyder wrote: > sage: a = var('a') > : matrix(GF(25, a), [[1,0], [0, 1]]) > : > p025.zzz: No such file or directory > --- > RuntimeError Traceback (most recent

[sage-support] Re: Problem compiling Sage

Le jeudi 6 octobre 2011 21:16:37 UTC+2, Loïc a écrit : > > Hello list > > I try to compile sage-4.7.1 under debian Squeeze > > It failes on python compiling; > > here is my error message. > >File "./setup.py", line 1934, in > main() >File "./setup.py", line 1929, in main > 'Lib

[sage-support] Re: Problem installing on Ubuntu 18.04

So it seems that when I make a symbolic link to /usr/share, running sage crashes But when I run it directly from the install directory using : ./sage, everything runs fine, patches are compiled, and I get through to running a notebook. -- You received this message because you are subscribed

[sage-support] Re: Problem with Sage's pexpect interface to Gap

Hi Dima, On 2018-09-29, Dima Pasechnik wrote: > How many (single) cosets are you talking about? > Once you have a permutation representation, these double coset > computations are very fast. > I am almost sure GAP first enumerates (single) cosets, anyway. There are 7 double cosets, but G.Order()

[sage-support] Re: Problem with Sage's pexpect interface to Gap

Hi Dima, On 2018-09-29, Dima Pasechnik wrote: > I believe making libGAP the default GAP interface is the way to go, and > much of the work needed for this conversion is already done... > > libgap's GAP objects are just thin cython wrappers around GAP's objects in > memory. > So you basically need

Re: [sage-support] Re: Problem with Sage's pexpect interface to Gap

On Sat, 29 Sep 2018, 10:32 Simon King, wrote: > Hi Dima, > > On 2018-09-29, Dima Pasechnik wrote: > > On Sat, Sep 29, 2018 at 9:58 AM Simon King > wrote: > >> > >> On 2018-09-29, Simon King wrote: > >> > Too bad: When the error occurs and I adjust the pool size then > >> > afterwards the previ

[sage-support] Re: Problem with Sage's pexpect interface to Gap

Hi Dima, On 2018-09-29, Dima Pasechnik wrote: > On Sat, Sep 29, 2018 at 9:58 AM Simon King wrote: >> >> On 2018-09-29, Simon King wrote: >> > Too bad: When the error occurs and I adjust the pool size then >> > afterwards the previously defined objects in gap are gone. >> >> Additional problem:

Re: [sage-support] Re: Problem with Sage's pexpect interface to Gap

On Sat, Sep 29, 2018 at 10:09 AM Simon King wrote: > > Hi Dima, > > On 2018-09-29, Dima Pasechnik wrote: > > There is no real harm in doing > > set_gap_memory_pool_size(10*get_gap_memory_pool_size()) > > Yes, there is (see my other post). The computation takes much much > longer than in libgap. >

[sage-support] Re: Problem with Sage's pexpect interface to Gap

Hi Dima, On 2018-09-29, Dima Pasechnik wrote: > There is no real harm in doing > set_gap_memory_pool_size(10*get_gap_memory_pool_size()) Yes, there is (see my other post). The computation takes much much longer than in libgap. > If coset enumeration is the bottleneck, you should not use GAP's >

Re: [sage-support] Re: Problem with Sage's pexpect interface to Gap

On Sat, Sep 29, 2018 at 9:58 AM Simon King wrote: > > On 2018-09-29, Simon King wrote: > > Too bad: When the error occurs and I adjust the pool size then > > afterwards the previously defined objects in gap are gone. > > Additional problem: Even when I increase the memory limit sufficiently, > ga

[sage-support] Re: Problem with Sage's pexpect interface to Gap

On 2018-09-29, Simon King wrote: > Too bad: When the error occurs and I adjust the pool size then > afterwards the previously defined objects in gap are gone. Additional problem: Even when I increase the memory limit sufficiently, gap-via-pexpect takes substantially longer than libgap to compute

Re: [sage-support] Re: Problem with Sage's pexpect interface to Gap

On Sat, Sep 29, 2018 at 9:46 AM Simon King wrote: > > Hi Dima, > > On 2018-09-29, Simon King wrote: > > Anyway, using set_gap_memory_pool_size(2*get_gap_memory_pool_size()) > > till everything works sounds like a reasonable way out. > > Too bad: When the error occurs and I adjust the pool size th

[sage-support] Re: Problem with Sage's pexpect interface to Gap

Hi Dima, On 2018-09-29, Simon King wrote: > Anyway, using set_gap_memory_pool_size(2*get_gap_memory_pool_size()) > till everything works sounds like a reasonable way out. Too bad: When the error occurs and I adjust the pool size then afterwards the previously defined objects in gap are gone. So

Re: [sage-support] Re: Problem with Sage's pexpect interface to Gap

On Sat, Sep 29, 2018 at 9:19 AM Simon King wrote: > > Hi Dima, > > On 2018-09-29, Dima Pasechnik wrote: > > set_gap_memory_pool_size() > > controls the amount of memory GAP and libGAP get if started from Sage. > > The latter is dynamic, as opposed to "sage --gap" > > Do I understand correctly: li

[sage-support] Re: Problem with Sage's pexpect interface to Gap

Hi Dima, On 2018-09-29, Dima Pasechnik wrote: > set_gap_memory_pool_size() > controls the amount of memory GAP and libGAP get if started from Sage. > The latter is dynamic, as opposed to "sage --gap" Do I understand correctly: libgap has dynamic pool size, but gap-via-pexpect has not? That would

[sage-support] Re: Problem with Sage's pexpect interface to Gap

PS: I just found that libgap is able to compute the double coset representatives, whereas gap-via-pexpect isn't. So, this might be a way out, in the sense that I would need to change many lines of code from gap to libgap, which is not just copy-and-paste, since apparently gap('foo') corresponds to

[sage-support] Re: Problem in new Sage version

On 2018-07-10, slelievre wrote: > you have the choice between the following: > > sage: V = PolynomialRing(GF(2), 49, xxz) > ... > sage: V = BooleanPolynomialRing(49, xxz) I think that's a very dangerous statement, as the boolean polynomial ring is a *quotient* of the above polynomial

[sage-support] Re: Problem in new Sage version

In other words, either use BooleanPolynomialRing without specifying GF(2), or use PolynomialRing and specify GF(2). If you set sage: xxz = ['x%d'%(i) for i in range(1, 49)] + ['Z'] you have the choice between the following: sage: V = PolynomialRing(GF(2), 49, xxz) sage: V Multiv

[sage-support] Re: Problem in new Sage version

What is your point? Remove GF(2) as this is over GF(2) by default. On Saturday, July 7, 2018 at 2:00:34 PM UTC+9, chandra chowdhury wrote: > > Initial version of Sage this worked perfectly > > *V=BooleanPolynomialRing(GF(2),49,['x%d'%(i) for i in range(1,49)]+['Z'])* > > But now I am getting error

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

It looks like you haven't installed the OS X command line tools, or they got removed when you updated to High Sierra. Try (re)installing them: run "xcode-select --install" from a terminal window. On Monday, October 16, 2017 at 7:58:33 PM UTC-7, moep wrote: > > Thanks for the response! I tried ou

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

You have at least two choices. For both, start by downloading (http://www.sagemath.org/download-source.html) and unpacking sage-8.0.tar.gz wherever you plan to build it. Choice 1: install git-trac-config: see http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-comman

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Hi, I'm having a similar problem, since I have to install Sage on a new computer (Macbook Pro 2017 with OS10.13). I think the issue is again with building gcc-5.4.0, which was mentioned in ticket ##23898. Since I'm not familiar with git, I cloned the repository for both the master and developer

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

After many hours of compiling (and when it seemed close to completing), it gave an error while installing curl-7.53.1, as John had predicted. The error is funny because this is MacOS 10.13: [curl-7.53.1] libtool: compile: clang -DHAVE_CONFIG_H -I../include/curl > -I../include -I../include -I..

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Oh, I am sorry, I have not realised that this won't work on Xcode 9 without https://trac.sagemath.org/ticket/23898 (even with clang you still need to build a fortran compiler, provided by the gcc package gfortran) If you just need working Sage, it might be easier to use only #23898 but not #1242

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

On Monday, October 9, 2017 at 4:16:47 AM UTC+1, Arvind Ayyer wrote: > > Thanks for your response, Dima. When you say that I need this ticket or > that, do you mean that I should get that particular branch from git and > install? I tried to check with get #12426, but that does not seem to be on

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Thanks for your response, John. Yes, I do have the command-line tools. Why do you think I'm installing Sage 6.2? Is it only because of the directory name? That's only because that was my first install on the Mac. I've installed 6.7 after that. I'm getting the latest version from git following t

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Thanks for your response, Dima. When you say that I need this ticket or that, do you mean that I should get that particular branch from git and install? I tried to check with get #12426, but that does not seem to be on the git server. The tickets you suggested seem to go in opposite directions.

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Also, if you have problems with the curl package, try https://trac.sagemath.org/ticket/23991 On Sunday, October 8, 2017 at 10:02:36 AM UTC-7, John H Palmieri wrote: > > Are you trying to install Sage 6.2 (as your log seems to indicate)? That > is extremely old. Try with a fresh source installati

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Are you trying to install Sage 6.2 (as your log seems to indicate)? That is extremely old. Try with a fresh source installation: either http://www.sagemath.org/download-source.html for stable source or http://www.sagemath.org/download-latest.html for the latest development version. Also, do you

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

On Sunday, October 8, 2017 at 12:06:20 PM UTC+1, Arvind Ayyer wrote: > > Dear all, > > > I recently upgraded my Mac OS to HighSierra and have installed the latest > version of XCode. Strangely enough, the gcc version is still 4.2.1. > is this Xcode 9? Then you need either https://trac.sagemat

[sage-support] Re: Problem with pdflatex.

Thanks a lot. It Best, On Thursday, September 14, 2017 at 4:59:04 AM UTC+5:30, slelievre wrote: > > Wed 2017-09-13 05:11:50 UTC, Venkataraman S: > > I am using sage 7.6. Recently installed GAP packages. > > The following input produces pdflatex error. > > > > R=PolynomialRing(RR,'x') > > points=

[sage-support] Re: Problem with pdflatex.

Wed 2017-09-13 05:11:50 UTC, Venkataraman S: > I am using sage 7.6. Recently installed GAP packages. > The following input produces pdflatex error. > > R=PolynomialRing(RR,'x') > points=[(0,1),(1,-3),(2,33),(3,589)] > f=R.lagrange_polynomial(points) > produces the following error message. You see

[sage-support] Re: Problem with upgrade on OS X

On Thursday, September 7, 2017 at 12:53:54 PM UTC-4, John H Palmieri wrote: > > Sage will build its own gcc, so as long as you have some functioning > version of gcc, you shouldn't need to worry about upgrading that. >> >> As a technical matter for any future reader of this thread, some gc

[sage-support] Re: Problem with upgrade on OS X

Sage will build its own gcc, so as long as you have some functioning version of gcc, you shouldn't need to worry about upgrading that. Just try installing a new version of Sage (from scratch, not by upgrading 6.7) and see what happens. John On Thursday, September 7, 2017 at 8:56:03 AM UTC-7

[sage-support] Re: Problem with upgrade on OS X

Thanks a lot, Dima! I managed to downgrade to 6.7 successfully for now. Once I upgrade my gcc, I'll go for the latest version. Regards, Arvind On Wednesday, 6 September 2017 18:14:04 UTC+4, Dima Pasechnik wrote: > > > > On Wednesday, September 6, 2017 at 2:27:55 PM UTC+1, Arvind Ayyer wrote: >>

[sage-support] Re: Problem with upgrade on OS X

On Wednesday, September 6, 2017 at 2:27:55 PM UTC+1, Arvind Ayyer wrote: > > > Dear developers, > > > I'm trying to upgrade from 6.7 to the current version using my git account > (userid: ayyer) using the guidelines from the TentativeConventions file. > > > I have a 2013 MacBook Pro Retina 13-

Re: [sage-support] Re: Problem compiling Sage 7.6 from source

On 2017-06-01 02:13, Bernardo Feijoo wrote: Then I tried to install again and the installation stopped with an error about linbox. I just started it again and it seems to be progressing past linbox, so I think it's making progress. I'm just gonna keep trying. This suggests a hardware problem of

[sage-support] Re: Problem compiling Sage 7.6 from source

Thank you for your help, Dima. I had version 6.3.0 of gcc installed. I tried to downgrade it but I was not able to. I also installed gfortran. Then I unistalled gcc, g++ and gfortran and installed them again (I was trying to install version 5.4.0, but failed again!). Then I tried to install ag

[sage-support] Re: Problem with an integral

On Sunday, April 9, 2017 at 5:37:55 AM UTC+2, Andrey Novoseltsev wrote: > > As reported, > > var('r') > assume(r>0) > integrate(r * sqrt( (2*r*cos(x)/sqrt(3))^2 + ( 2/3 + 4*r*sin(x)/3 )^2 ), > x) > > gives > > -1/12*(2*r*x - r*sin(2*x))*r > > which is indeed incorrect. Is the root cause kn

[sage-support] Re: Problem building GSL in cygwin64

See also a thread with the same subject on sage-devel at https://groups.google.com/d/topic/sage-devel/53rlxMo7_6w/discussion -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send a

[sage-support] Re: Problem building GSL in cygwin64

On Tuesday, January 24, 2017 at 1:53:15 AM UTC, Frank Garvan wrote: > > > I am trying to install sage on my PC with cygwin64 (running windows10) > Install failed for GSL package. > Have attached log file. > > Is the right place to post this? > > Any solution for this problem? > > Could not find

Re: [sage-support] Re: Problem building GSL in cygwin64

Maybe you could try sagemathcloud ? Le 24/01/2017 à 07:00, slelievre a écrit : Tue 2017-01-24 02:53:15 UTC+1, Frank Garvan: > I am trying to install sage on my PC with cygwin64 (running windows10) > Install failed for GSL package. > Have attached log file. > > Is the right place to post this?

[sage-support] Re: Problem building GSL in cygwin64

Tue 2017-01-24 02:53:15 UTC+1, Frank Garvan: > I am trying to install sage on my PC with cygwin64 (running windows10) > Install failed for GSL package. > Have attached log file. > > Is the right place to post this? > > Any solution for this problem? > > Could not find anything relevant in > http

Re: [sage-support] Re: Problem with the minus sign in symbolic expression

P.S. The original question was also asked on Ask Sage: https://ask.sagemath.org/question/35947/problem-with-the-minus-sign-in-symbolic-expression/ -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receivin

Re: [sage-support] Re: Problem with the minus sign in symbolic expression

Thu 2016-12-08 13:06:23 UTC+1, John Cremona: > I think that trying to combine symbolic variables (x1 and x2) with > modular arithmetic is known to create difficulties. If you want to do > the computation mod 101 then something like > > F = GF(101) > R. = F[] > > # The above 2 lines tell Sage tha

Re: [sage-support] Re: Problem with the minus sign in symbolic expression

On 8 December 2016 at 10:35, Anastasia Theodouli wrote: > UPDATE: The problem was that I was working modulo 101 when I was defining a1 > and b1. I think that trying to combine symbolic variables (x1 and x2) with modular arithmetic is known to create difficulties. If you want to do the computatio

[sage-support] Re: Problem with the minus sign in symbolic expression

*UPDATE:* The problem was that I was working modulo 101 when I was defining a1 and b1. On Thursday, December 8, 2016 at 11:49:04 AM UTC+2, Anastasia Theodouli wrote: > > Hi all! > > In my code, I have a multivariate polynomial with a sign symbol which > doesn't return the correct result. I.e.

[sage-support] Re: Problem with the minus sign in symbolic expression

On Thursday, December 8, 2016 at 12:08:21 PM UTC+2, Anastasia Theodouli wrote: > > My Sage version is 6.9 > > The exact code I use is as follows: > > A1 = [(', '.join('x%i'%i for i in [1.. n]))]; ### construct a suitable > multivariate ring > V = var(A1[0]) #

[sage-support] Re: Problem with the minus sign in symbolic expression

My Sage version is 6.9 The exact code I use is as follows: A1 = [(', '.join('x%i'%i for i in [1.. n]))]; ### construct a suitable multivariate ring V = var(A1[0]) ### define a str variable x=vector(list(V)) ### convert to ve

[sage-support] Re: Problem in Trac authentication through SSH

Thank you very much. I got this fixed and successfully connected. Thanks again for your time and concern. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-su

[sage-support] Re: Problem in Trac authentication through SSH

On Saturday, October 15, 2016 at 6:33:21 PM UTC, Dima Pasechnik wrote: > > > > On Saturday, October 15, 2016 at 11:36:37 AM UTC, B Krishnan Iyer wrote: >> >> Hello, >> >> I have used the instruction from developers guide. I would be very much >> thankful if anyone help me out. The screenshot is

[sage-support] Re: Problem in Trac authentication through SSH

On Saturday, October 15, 2016 at 11:36:37 AM UTC, B Krishnan Iyer wrote: > > Hello, > > I have used the instruction from developers guide. I would be very much > thankful if anyone help me out. The screenshot is attached. > > Thank you > I think that is a part of old documentation that we forgo

[sage-support] Re: Problem with installing sageserver

Problem solved! -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@goo

[sage-support] Re: Problem compiling 7.3 from source

Luis Finotti wrote: > On Wednesday, August 24, 2016 at 5:41:37 PM UTC-4, leif wrote: > > Luis Finotti wrote: > > I can't compile 7.3 using Debian Unstable. > > Do you intentionally (try to) build Sage's GCC? (I have to admit I > haven't tried to build 4.9.3 with 6.x, but building

[sage-support] Re: Problem compiling 7.3 from source

On Wednesday, August 24, 2016 at 5:41:37 PM UTC-4, leif wrote: > > Luis Finotti wrote: > > I can't compile 7.3 using Debian Unstable. > > Do you intentionally (try to) build Sage's GCC? (I have to admit I > haven't tried to build 4.9.3 with 6.x, but building older GCCs with > newer versions

[sage-support] Re: Problem compiling 7.3 from source

leif wrote: > Dima Pasechnik wrote: >> Do we support gcc 6.1.1 now? > > Sure. (Modulo building Sage's GCC 4.9.3 with it... ;-) ) The only thing we missed in Sage 7.3 is Givaro's testsuite, which currently only builds when manually passing '-std=c++98' in CXXFLAGS. -leif -- You received this

[sage-support] Re: Problem compiling 7.3 from source

Dima Pasechnik wrote: > Do we support gcc 6.1.1 now? Sure. (Modulo building Sage's GCC 4.9.3 with it... ;-) ) (6.2 has just been released, but that's a bugfix release in the 6.x series.) -leif > This is what is used during the build. -- You received this message because you are subscribed

[sage-support] Re: Problem compiling 7.3 from source

Do we support gcc 6.1.1 now? This is what is used during the build. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To

[sage-support] Re: Problem compiling 7.3 from source

Luis Finotti wrote: > I can't compile 7.3 using Debian Unstable. Do you intentionally (try to) build Sage's GCC? (I have to admit I haven't tried to build 4.9.3 with 6.x, but building older GCCs with newer versions of it in my experience is likely to fail.) If not, take a look at config.log, whi

[sage-support] Re: Problem with git and trac server

I see all commits in the individual commit list, its just red = does not merge cleanly with the current develop branch On Sunday, August 21, 2016 at 11:05:48 PM UTC+2, Paul Mercat wrote: > > In fact nothing is missing in your list of commit. I'm happy to see that. > What is missing is what appea

[sage-support] Re: Problem with git and trac server

On Sunday, August 21, 2016 at 10:05:48 PM UTC+1, Paul Mercat wrote: > > In fact nothing is missing in your list of commit. I'm happy to see that. > What is missing is what appear in the ticket #21072 ( > https://trac.sagemath.org/ticket/21072 ) > The two last commits are here but not the two pre

  1   2   3   4   5   6   7   8   >