Is it just me, or is trac broken?
$ git trac checkout 20918
Loading ticket #20918...
Traceback (most recent call last):
File "/home/jm58660/bin/git-trac", line 18, in
cmdline.launch()
File "/home/jm58660/git-trac-command/git_trac/cmdline.py", line 209, in
launch
app.checkout(args.t
Hi,
On Mon, Jul 04, 2016 at 02:14:20PM +1200, François Bissey wrote:
> So I have been inspecting giac, as any discussion of making something
> a standard package as an impact for sage-on-gentoo.
> We have an old version in the science overlay so I am working on
> upgrading it.
>
> 1) current 1.2.
> On 4/07/2016, at 20:45, Thierry wrote:
>
> Hi,
>
> On Mon, Jul 04, 2016 at 02:14:20PM +1200, François Bissey wrote:
>> So I have been inspecting giac, as any discussion of making something
>> a standard package as an impact for sage-on-gentoo.
>> We have an old version in the science overlay
You need the latest version of git-trac-command, e.g. by checking
out https://github.com/sagemath/git-trac-command
On Monday, July 4, 2016 at 10:36:16 AM UTC+2, Jori Mäntysalo wrote:
>
> Is it just me, or is trac broken?
>
> $ git trac checkout 20918
> Loading ticket #20918...
> Traceback (m
Le lundi 4 juillet 2016 04:14:26 UTC+2, François a écrit :
>
> So I have been inspecting giac, as any discussion of making something
> a standard package as an impact for sage-on-gentoo.
> We have an old version in the science overlay so I am working on
> upgrading it.
>
> 1) current 1.2.2-63
I'm fixing the build for --disable-gui and I will also add a --disable-ao
flag in configure.in (ao is used for the playsnd command). You can
--disable-lapack if you think it will cause problems, LAPACK is interesting
inside giac only for large matrices (more than 1000x1000, otherwise giac
buil
> On 4/07/2016, at 22:41, parisse wrote:
>
>
> I'm fixing the build for --disable-gui and I will also add a --disable-ao
> flag in configure.in (ao is used for the playsnd command). You can
> --disable-lapack if you think it will cause problems, LAPACK is interesting
> inside giac only for l
On Monday, July 4, 2016 at 6:09:59 AM UTC+1, saad khalid wrote:
>
> So, after fixing a small typo, here is the output from an example:
>
> sage: macaulay2.eval("""
> : K = toField(QQ[zet]/(zet^8 - zet^7 +zet^5 - zet^4 +zet^3 -zet + 1))
> : A=matrix{{zet^1,0},{0,zet^14}}
> : needsPacka
You are welcome if you know how to fix configure.in for lapack support (as
long as it does not break my current compilations configurations).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving email
On Monday, July 4, 2016 at 12:07:40 PM UTC+1, parisse wrote:
>
> You are welcome if you know how to fix configure.in for lapack support
> (as long as it does not break my current compilations configurations).
>
> do you have an online repo available?
Currently http://www-fourier.ujf-grenoble.fr/
It's back online.
--
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegr
On Monday, July 4, 2016 at 1:06:06 PM UTC+1, parisse wrote:
>
> It's back online.
>
OK, I just wanted to look at congure.in we are talking about.
There are AX_BLAS and AX_LAPACK macros which are (semi)standard:
http://www.gnu.org/software/autoconf-archive/ax_blas.html
and
http://www.gnu.org/
On Sun, Jul 3, 2016 at 7:35 PM, leif wrote:
> Erik Bray wrote:
>> git and trac should both be back up again.
>>
>> [...]
>>
>> Please let me know via e-mail, and also CC
>> sagemath-adm...@googlegroups.com if you notice something amiss.
>
> Not that important, so I'm posting here:
>
> What happene
How is it supposed to work? I have copied the m4 files into m4/, then if I
put
AX_BLAS([],AX_LAPACK())
instead of
AC_CHECK_LIB(gfortran, main)
AC_CHECK_LIB(blas, main)
AC_CHECK_LIB(lapack, main, [], [CONFIG_LAPACK="no"])
configure fails
./configure: line 15831: syntax error near unex
something like :
AX_BLAS([have_blas=yes], [have_blas=no]) if test "x${have_blas}" = xno;
then ... stuff.. ... this is how I used them
here: https://github.com/dimpase/csdp/blob/master/configure.ac
On Monday, July 4, 2016 at 2:11:54 PM UTC+1, parisse wrote:
>
> How is it supposed to work? I h
also note that lapack needs blas, and in fact AX_LAPACK calls AX_BLAS
itself.
Perhaps your line has lead to unwanted recursion...
On Monday, July 4, 2016 at 2:11:54 PM UTC+1, parisse wrote:
>
> How is it supposed to work? I have copied the m4 files into m4/, then if I
> put
> AX_BLAS([],AX_LAP
On Fri, Jul 1, 2016 at 8:11 PM, leif wrote:
> Jori Mäntysalo wrote:
>> On Fri, 1 Jul 2016, Erik Bray wrote:
>>
>>> One thing that will help, which has already been discussed up-thread,
>>> is having Trac help take care of the little nitty-gritty checks on
>>> tickets.
>>
>> True. It feels extremel
Tried
AX_BLAS([have_blas=yes],[have_blas=no])
AX_LAPACK([have_lapack=yes],[have_lapack=no])
without success as I feared (my autoconf is 2.69). I will stick to the
current checks.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
Thanks! That makes much more sense and seems simpler, I'm glad I know that
now!
Side note: Never use += on a string in a loop. Here it's even worse,
> since you are concatenating strings on the right hand side as well.
>
>
Is it because it's slow?
Also, do you think I should have the to_sag
Could this kind of discussion can be done on sage-support? As it name
suggests sage-devel is dedicated to development discussions. If we want
to keep developers reading it, it is better to not flood it with users
usage questions.
On 02/07/16 14:13, saad khalid wrote:
Hey everyone:
I was hopi
Sorry about that, I thought sage-devel was for talking/asking questions
related to doing development on Sage. Since I was editting the source, I
assumed it would be okay to post it here, but if it's not, I'll definitely
remember that in the future.
I created a trac for review:
https://trac.sage
Erik Bray wrote:
> On Fri, Jul 1, 2016 at 8:11 PM, leif wrote:
>> Jori Mäntysalo wrote:
>>> On Fri, 1 Jul 2016, Erik Bray wrote:
>>>
One thing that will help, which has already been discussed up-thread,
is having Trac help take care of the little nitty-gritty checks on
tickets.
>>>
IMHO this is borderline between devel and support - it is about extending
Sage interface to Macaulay2 with a new type.
On Monday, July 4, 2016 at 6:08:48 PM UTC+1, vdelecroix wrote:
>
> Could this kind of discussion can be done on sage-support? As it name
> suggests sage-devel is dedicated to de
I wouldn’t try to use one of these. Detecting blas/lapack automatically is
a fool’s errand. There are no standard naming scheme for the libraries
and distress can mess things up on top of it.
The only safe way is to get the stuff needed to link on the command line.
You may want to add detection of
saad khalid wrote:
> Sorry about that, I thought sage-devel was for talking/asking questions
> related to doing development on Sage. Since I was editting the source, I
> assumed it would be okay to post it here, but if it's not, I'll
> definitely remember that in the future.
Well it is, but neithe
> On 5/07/2016, at 09:10, Francois Bissey
> wrote:
>
> I wouldn’t try to use one of these. Detecting blas/lapack automatically is
> a fool’s errand. There are no standard naming scheme for the libraries
> and distress can mess things up on top of it.
distress -> distros [thank you automatic sp
On 04/07/16 22:41, parisse wrote:
I will also add a --disable-ao flag in configure.in (ao is used for the
playsnd command)
Do you have an ETA for that? I noticed it has not landed in 1.2.2-65.
Francois
--
You received this message because you are subscribed to the Google Groups
"sage-devel"
On 04/07/16 22:41, parisse wrote:
I'm fixing the build for --disable-gui
And I am guessing you didn't mean that it would be in 1.2.2-65 either.
I am still getting
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++
-DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I..
disable-gui should be working. If not, then I probably made a mistake while
copying the archive, you can try
http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz
I don't know what you mean by ETA, but disable-ao should also be working.
For lapack, it was a little nightmare before I
On Tuesday, July 5, 2016 at 6:13:53 AM UTC+1, parisse wrote:
>
> disable-gui should be working. If not, then I probably made a mistake
> while copying the archive, you can try
> http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz
> I don't know what you mean by ETA, but disable-a
> On 5/07/2016, at 17:13, parisse wrote:
>
> disable-gui should be working. If not, then I probably made a mistake while
> copying the archive, you can try
> http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz
Yes that tarball has the goods. I’ll wait for a new 1.2.2-xx tarball
31 matches
Mail list logo
