Hi all,
I'm getting
"""
Oops…
*Trac detected an internal error:*
TypeError: object of type 'listreverseiterator' has no len()
There was an internal error in Trac. It is recommended that you notify your
local Trac administrator with the information needed to reproduce the issue.
To that end
I've been building Sage on Solaris recently, without too much trouble
(except building a 64 bit gcc which I still cannot achive whatever i try).
If someone has admin rights on skynet to create acocunts (xhich was not the
case last time I tried), I'd give it a shot with pleasere.
On Saturday, Jan
On Wednesday, January 1, 2014 11:09:31 PM UTC+1, R. Andrew Ohana wrote:
>
> Please try again. This should now be fixed.
>
> Works again!
Thanks.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving e
I'm getting an error:
*Trac detected an internal error:*
IOError: [Errno 13] Permission denied:
u'/home/www-data/gitolite/keydir/03/jpflori.pub'
Did I do something wrong?
Best,
JP
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscrib
On Wednesday, January 1, 2014 5:30:09 AM UTC+1, john_perry_usm wrote:
>
> I sometimes illustrate techniques of polynomial factorization in a class
> by starting with a polynomial in ZZ[x] and converting it to a polynomial in
> GF(insert_large_prime)[x]. I realize this is not an instance of two
Dear all,
Currently one can obtain surprising results in Sage when converting
polynomial over finite fields (or elements of quotient rings of univariate
polynomial ring even though tht's not the primary concern of the ticket).
See http://trac.sagemath.org/ticket/11239
Basically the generators of
On Monday, December 30, 2013 5:32:37 PM UTC+1, John Cremona wrote:
>
> A ticket I am reviewing, and am personally quite happy with (#11630)
> has a failing patchbot red blob meaning "apply failed". According to
> the log, what failed was a line "./sage -i ccache".
>
> I can see the same issue
On Friday, December 27, 2013 7:10:13 PM UTC+1, Volker Braun wrote:
>
> There is the "bsd" machine that you could use. I've ordered a new mac,
> though it hasn't arrived yet and we have pretty bad networking in our new
> building...
>
I don't have access to bsd :(
--
You received this message
On Friday, December 27, 2013 6:10:13 PM UTC, Volker Braun wrote:
>
> There is the "bsd" machine that you could use. I've ordered a new mac,
> though it hasn't arrived yet and we have pretty bad networking in our new
> building...
>
> I wanted to move all the hardcoded atlas libraries into a scr
Dear all,
I'd like to cleanup the way we build a bunch of packages more or less
related to ATLAS:
* remove the dirty configure hack to IML which makes it so that IML does
not link to CBLAS/ATLAS and as a consequence LinBox does not use IML
because of undefined symbols.
* patch LinBox with upstr
On Wednesday, December 25, 2013 8:40:27 PM UTC+1, Jean-Pierre Flori wrote:
>
> On a slightly unrelated topic, currently the only function of pycrypto
> used in the Sage library is indeed in the monoid stuff and that's the
> byte_to_long function.
> Although I don
On a slightly unrelated topic, currently the only function of pycrypto used
in the Sage library is indeed in the monoid stuff and that's the
byte_to_long function.
Although I don't feel we should remove pycrypto from standard packages, I
feel we could implement this ourselves if this prevents a
On Wednesday, December 25, 2013 7:58:27 PM UTC+1, Martin Albrecht wrote:
>
> On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote:
> > I think having pycrypto in Sage is cool for ... cryptographers :)
>
> I am not sure this is true. PyCrypto is quite high-level, i
On Wednesday, December 25, 2013 7:45:05 PM UTC+1, François wrote:
>
> Going back to the general subject. Could we have a shortcut on the ticket
> report page
> grabbing update/upgrade of packages. Unless the potential reviewer(s) are
> cc automatically
> that would any review easier, as in mo
On Wednesday, December 25, 2013 7:08:15 PM UTC+1, Volker Braun wrote:
>
> On Wednesday, December 25, 2013 5:52:39 PM UTC, Jean-Pierre Flori wrote:
>>
>> #12399
>>
>
> I just want to point out that this took you half a year... IMHO there is
> no point to if if
I'd prefer to have a quick review for everything.
Just having someone else having a quick look at the diff is also a good
idea, and I think the peer-reviewing system of Sage is a real plus value.
By the way a bunch of more or less trivial updates, upstream patch
inclusion: #12399, #14333, #14854
On Wednesday, December 18, 2013 6:24:40 AM UTC+1, R. Andrew Ohana wrote:
>
> I've made #15530 to track the progress on supporting python3 (and there is
> already a good amount there that is up for review).
>
>
> Also, other than the trivial usage in
> sage.monoids.string_monoid(_element), I'm n
Done.
On Wednesday, December 25, 2013 2:03:29 PM UTC+1, Volker Braun wrote:
>
> This should be an easy one... I think everything that can be said on the
> ticket has already been, it just then fizzled out without somebody pressing
> positive review...
>
> http://trac.sagemath.org/ticket/15441
>
On Tuesday, December 24, 2013 1:37:57 AM UTC+1, Fredrik Johansson wrote:
>
> On Mon, Dec 23, 2013 at 3:47 PM, Jean-Pierre Flori
> >
> wrote:
> > I've opened #15574 for updating FLINT in Sage.
> > It should be trivial, though I've had no time to craft an
On Monday, December 23, 2013 9:10:31 PM UTC+1, Jean-Pierre Flori wrote:
>
> By the way, did the valgrind package disappear?
>
Hum I guess it just hasn't been upgraded.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
By the way, did the valgrind package disappear?
On Monday, December 23, 2013 9:03:37 PM UTC+1, Jean-Pierre Flori wrote:
>
> I mean in the http://www.sagemath.org/download-packages.html page link.
>
> On Monday, December 23, 2013 9:02:58 PM UTC+1, Jean-Pierre Flori wrote:
>>
>
I mean in the http://www.sagemath.org/download-packages.html page link.
On Monday, December 23, 2013 9:02:58 PM UTC+1, Jean-Pierre Flori wrote:
>
> It seems that http://www.sagemath.org/upstream lacks packages in the
> middle.
>
> Best,
> JP
>
--
You received this me
It seems that http://www.sagemath.org/upstream lacks packages in the middle.
Best,
JP
--
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...@googl
On Monday, December 23, 2013 4:02:35 PM UTC+1, Volker Braun wrote:
>
> For the record, this is explained in the new developer manual which you
> can find in SAGE_ROOT/src/doc/output/html/en/developer/index.html
>
Is this online somewhere?
sagemath.org still points to the 5.13 doc.
--
You rec
(https://github.com/fredrik-johansson/bland)
>
> Contributors
>
>
> (At least) the following people contributed to flint-2.4, including code
> contributions, bug reports, corrections to the documentation and patches:
>
>Tom Bachmann, Martin Lee, Lina
On Wednesday, December 11, 2013 3:08:56 PM UTC+1, Volker Braun wrote:
>
> My 5 cents:
>
> * Magma is not a spkg.
>
>
Sure whence the third party software, though most optional spkgs ship third
party software as well.
> * Library code that depends on optional / third-party software uses the
Hi all,
Do we have any policy concerning integration of python/cython glue into the
Sage library which depends on optional spkgs or third party software
shipping mostly independent code?
And what about optional spkgs which are actually mostly python/cython code ?
It seems to me that in the form
On Friday, November 22, 2013 2:27:28 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2013-11-22 10:15, Fran�ois wrote:
> > On the subject of the time taken to compile R: R itself compiles in
> > parallel relatively
> > fast.
> Really? I find that, when building sufficiently in parallel, R is
> actu
On Friday, November 22, 2013 10:48:26 AM UTC+1, Jean-Pierre Flori wrote:
> A few random remarks:
> * I directly built it on the raspberry pi (I don't think Sage own build
> system is flexible enough to cross compile as lmonade could do).
> * it took something like 5 days.
I've put a binary for raspberry pi at
http://boxen.math.washington.edu/home/jpflori/dist at some point.
It's was for 5.10.
A few random remarks:
* I directly built it on the raspberry pi (I don't think Sage own build
system is flexible enough to cross compile as lmonade could do).
* it took some
On Wednesday, November 13, 2013 5:10:07 PM UTC+1, Paweł Bogdan wrote:
>
> Hi!
>
> I'm new here. I'm fresh PhD student at Jagiellonian University in Poland.
> I have been using Sage for few months. I think it is great piece of
> software.
>
>
I am getting into zeta functions of elliptic curves
Just a random thought: Can't you use explicitly a CartesianProduct of
AdditiveAbelianGroup if you don't want Sage to be too smart?
On Friday, November 8, 2013 9:09:24 AM UTC+1, Nathann Cohen wrote:
>
> Yooo !
>
> > This expects input from Z/161, so a length-one list:
> >
> > sage: G([160]) +
day, November 8, 2013 9:10:49 AM UTC+1, Jean-Pierre Flori wrote:
>
> Hi,
>
> IIRC we had some problem with SchemeMorphism recently while making (or
> while Simon wa making I must say) the coercion system more cache friendly.
> See #14711 and especially:
> * http://trac.sagemath.org
Hi,
IIRC we had some problem with SchemeMorphism recently while making (or
while Simon wa making I must say) the coercion system more cache friendly.
See #14711 and especially:
* http://trac.sagemath.org/ticket/14711#comment:85
* http://trac.sagemath.org/ticket/14711#comment:93
* and whatever is
On Wednesday, November 6, 2013 11:20:00 PM UTC+1, William wrote:
>
> On Mon, Nov 4, 2013 at 5:56 PM, Mike Zabrocki
> >
> wrote:
> >[...]
> > After I installed the new command line tools then I was able to build
> from
> > source also for about 3 hours and then I encountered the same errors
On Monday, November 4, 2013 7:15:19 AM UTC+1, Nils Bruin wrote:
>
> On Sunday, November 3, 2013 6:51:48 PM UTC-8, P Purkayastha wrote:
>
>> If you check out the branch locally, you can run a
>>
>> git diff
>>
>> to see the cumulative changes.
>>
>
> That's good to know. However, when trying
On Tuesday, October 29, 2013 1:48:55 PM UTC+1, vdelecroix wrote:
>
> I do not see why RIF might be slower than RR. By construction, RIF is
> a pair of real numbers. For arithmetic involving only +,-,*,/ we
> should get a ratio of 2 for the execution time because all rounding
> are implemented
On Wednesday, October 16, 2013 8:55:41 PM UTC+2, John Cremona wrote:
>
> Thanks! That worked for me too.
>
> Whoever made building the docs work in parallel deserves a prize (but
> does it have to say "Build finished" quite so many time?)! Using make
> -j48 it only took 194s. Watching that
On ednesday, October 16, 2013 2:01:18 PM UTC+2, Dima Pasechnik wrote:
>
> On 2013-10-16, Jean-Pierre Flori > wrote:
> > Dear all,
> >
> > There is an easy update to boehm_gc at
> > http://trac.sagemath.org/ticket/14710 waiting for review.
> > This is
Dear all,
There is an easy update to boehm_gc at
http://trac.sagemath.org/ticket/14710 waiting for review.
This is needed for Cygwin 64, but also replace the beta versoin we used to
ship by a more recent stable version.
Best,
JP
--
You received this message because you are subscribed to the G
On Sunday, October 13, 2013 6:59:05 PM UTC+2, William wrote:
>
> On Sun, Oct 13, 2013 at 9:54 AM, Jean-Pierre Flori
> >
> wrote:
> > Hi William,
> >
> >
> > On Saturday, October 12, 2013 7:21:23 PM UTC+2, William wrote:
> >>
> >>
On Sunday, October 13, 2013 10:03:49 AM UTC+2, Dr David Kirkby wrote:
>
> I could have swore I see a message on the screen that the package had
> not installed and the build stopped. I just looked in
> sage-5.13.beta0/spkg/installed and see the atlas file is there, so I
> guess it must have in
s, then wants to see how many bits it is?
>
> I stuck the config.log here
>
> http://trac.sagemath.org/ticket/15273
>
> it is from the original source code.
>
> If you want to play with it, I can create you an account on this machine.
>
> Dave
>
> On 13 Octobe
cket/15273
>
> it is from the original source code.
>
> If you want to play with it, I can create you an account on this machine.
>
> Dave
>
> On 13 October 2013 15:54, Jean-Pierre Flori >
> wrote:
> > By any chance, does your hardware does not support
Hi William,
On Saturday, October 12, 2013 7:21:23 PM UTC+2, William wrote:
>
> There is no such thing as Cloud "the company". However, my
> motivation for laying the groundwork to create such a company is to
> make profits that would go toward the development of Sage "the free
> software".
>
By any chance, does your hardware does not support SSE2?
We had trouble with that recently.
On Sunday, October 13, 2013 4:52:39 PM UTC+2, Jean-Pierre Flori wrote:
>
> Could you post config.log from gf2xx build directory please?
>
> On Sunday, October 13, 2013 10:06:32 AM UTC+2, Dr
Could you post config.log from gf2xx build directory please?
On Sunday, October 13, 2013 10:06:32 AM UTC+2, Dr David Kirkby wrote:
>
> drkirkby@hawk:~/unsets/sage-5.13.beta0$ ./sage -i gf2x-1.1.p0
> This looks like the first time you are running Sage.
> Updating various hardcoded paths...
> (Pl
Is it down again ?
--
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@googleg
There is some discussion about the licence issue on ecl mailing list.
Juan did not reply yet.
http://sourceforge.net/p/ecls/mailman/ecls-list/thread/E1VTECl-ZM-2W%40hera.math.uni.wroc.pl/#msg31493829
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gr
I confirm it fails in the same way for me and agree with VOlker: we don't
care if upstream shared stuff fails at the moment.
On Friday, October 11, 2013 4:32:08 PM UTC+2, Volker Braun wrote:
>
> We can just ignore the error and continue with our own libtool-based
> library build. This is now htt
(and I'm using the Sun ld as well)
On Friday, October 11, 2013 1:11:52 PM UTC+2, Jean-Pierre Flori wrote:
>
> I'm currently building sage 5.12 as well on sparc/solaris, I'll report the
> status of ATLAS for me here.
>
> On Friday, October 11, 2013 11:43:2
I'm currently building sage 5.12 as well on sparc/solaris, I'll report the
status of ATLAS for me here.
On Friday, October 11, 2013 11:43:27 AM UTC+2, Volker Braun wrote:
>
> There are two attempts to build shared libraries, once using upstream's
> method of a hand-crafted makefile (in ATLAS-bui
Thanks!
Hopefully youll find what the real problem was.
On Thursday, October 10, 2013 8:00:52 PM UTC+2, Keith Clawson wrote:
>
> Trac is back up. Something causes Trac to use nearly 100% CPU and memory
> after running for a few weeks, and eventually it becomes impossible to ssh
> into the VM run
On Thursday, October 10, 2013 4:15:30 PM UTC+2, Jean-Pierre Flori wrote:
> I think I used to have the same problem on exotic archs where I did not
> have libjpeg installed.
>
Or at least the devel files.
So if you can install the equivalent of libjpeg-devel on your distrib, PIL
shoul
On Thursday, October 10, 2013 4:13:36 PM UTC+2, Andrew Mathas wrote:
>
> I'm having trouble compiling 5.12. Sage build to the extend that I get an
> executable which runs, but the compile fails to compile pil-1.1.6.p4 and
> exits with the error from the end of the log file is below. It's a bi
Same here...
It was down at some point this morning, then came back to life and is down
again now.
On Thursday, October 10, 2013 11:50:15 AM UTC+2, Jeroen Demeyer wrote:
>
> Trac is not responding at all, I get 504 Gateway Time-out.
>
--
You received this message because you are subscribed to
On Thursday, October 10, 2013 11:19:01 AM UTC+2, Jean-Pierre Flori wrote:
>
> I guess http://trac.sagemath.org/ticket/15080 takes care of this?
>>
>>
>> (Or at least is worth a try)
--
You received this message because you are subscribed to the Google Groups
I guess http://trac.sagemath.org/ticket/15080 takes care of this?
On Thursday, October 10, 2013 2:45:24 AM UTC+2, Nils Bruin wrote:
>
> Some further info that may be helpful:
>
> $ ldd /usr/local/sage/sage-git/local/lib/python2.7/lib-dynload/_curses.so
> linux-vdso.so.1 => (0x7fff5a884000
On Monday, October 7, 2013 4:20:15 PM UTC+2, Ivan Andrus wrote:
>
> Valgrind complains about glibc being too recent. It should be updated
> from 3.7.0 to 3.8.1 anyway. This is
> http://trac.sagemath.org/ticket/13060which unfortunately has issues on OS X.
>
Indeed, on OSX, Valgrind build syste
Same happens to me with firefox, not sure which version as I often switch
computers.
Really annoying indeed.
On Saturday, October 5, 2013 8:45:09 PM UTC+2, Simon King wrote:
>
> Hi!
>
> I just tested: If I scroll up to see the blob, after the jump has
> occurred, and then scroll down to continu
It seems I only sent my reply to Emmanuel.
So briefly:
- Andrew: can you please confirm that the latest tarball provided by
Emmanuel is fixed?
- if that's the case, I'll open a trac ticket to update the gf2x spkg
provided by Sage and it should make its way into Sage 5.12 or 5.13.
Best,
JP
On Fr
On Tuesday, October 1, 2013 10:56:21 PM UTC+2, John Cremona wrote:
>
> The patchbot puts a blob on ticket
> http://trac.sagemath.org/ticket/13615 which to me looks dark grey and
> hence bad news. But when I click on the blob I see the page
> http://patchbot.sagemath.org/ticket/13615/ which ha
On Friday, September 27, 2013 11:29:19 PM UTC+2, Harald Schilly wrote:
>
> On Friday, September 27, 2013 7:30:23 PM UTC+2, kcrisman wrote:
>>
>> Thoughts?
>>
>
> There exists this model of "user groups" with regular meetings. "Hello,
> I'm addicted to Sage for 1 1/2 years. Please help me with my
Hey,
I seem to remember that Frederik Johansson recently implemented similar
functionalities into FLINT.
At least a fast version of the Eratosthenes' sieve.
Did you have a look at it?
Best,
JP
On Sunday, September 22, 2013 1:24:23 AM UTC+2, R. Andrew Ohana wrote:
>
> I'm trying to review #7539 w
Hey,
I think you should report this to the gf2x dev as well... you never know.
I've CC'ed Paul Zimmermann in case he cares.
Best,
JP
On Friday, September 20, 2013 3:01:13 PM UTC+2, Andrew Fiori wrote:
>
> This is likely a build error bug on all systems which do not support SSE2
> but where buil
Hi,
I think I also had similar problems because of accented letters in my
building path.
I don't know if that would be easy to fix, but you can always build Sage
lesewhere and then move it back where you want to store it even if that
includes accented letters.
Best,
JP
On Wednesday, September
Hi,
Static libs can be faster than shared ones, especially for something like
gmp/mpir.
That reason is mentioned in the mpir spkg IIRC, and says it is benefit for
ECM (which has a critical need for speed).
But I must admit I'm not completely convinced that ECM (or rather the way
we build it) is
On Monday, September 2, 2013 4:19:37 AM UTC+2, nil...@gmail.com wrote:
>
>
>
>> try rebasing some more...
>>
>>
> I tried hard, no way. Even my colleagues report all the same error as the
> initiator of this theme did (no relation to). We've also tried 5.9 and
> 5.11 with 64bit Cygwin, but t
So it seems it was the commit.
Reported upstream at
https://groups.google.com/d/msg/mpir-devel/Oe0qnDiiHrc/TI9ymEOq9i8J
The new spkg reverts this commit.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop rec
It's either that I did not test anything with --enable-cxx before or that
a81efe8936cb997d2c0e29fbab0863099898a18d is to blame.
On Wednesday, August 7, 2013 11:55:00 AM UTC+2, Jean-Pierre Flori wrote:
>
> It seems the very latest tarball has troubles with the C++ bindings...
> It
It seems the very latest tarball has troubles with the C++ bindings...
It fails part of its testsuite and PPL rants.
That may be one of the latest commits from Brian.
On Wednesday, August 7, 2013 11:41:31 AM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Wednesday, August 7, 2013 11:40
On Wednesday, August 7, 2013 11:40:20 AM UTC+2, Jean-Pierre Flori wrote:
>
> New spkg up at #15015 or directly at
> http://boxen.math.washington.edu/home/jpflori/spkg/mpir-2.6.1.spkg .
>
(I've not tested it on Cygwin (nor on anything in fact) so cannot promise
anything...)
New spkg up at #15015 or directly at
http://boxen.math.washington.edu/home/jpflori/spkg/mpir-2.6.1.spkg .
This is based on my github branch (mostly merged into the official one,
though there won't be an official new release soon, or at least I'm not
aware of it).
--
You received this message b
On Wednesday, August 7, 2013 8:05:42 AM UTC+2, Travis Scrimshaw wrote:
>
> Okay, python works from the build directory for cygwin32, even though the
> spkg install still fails. I couldn't install the mpir spkg on my cygwin64;
> here's the log:
>
> $ sage -i mpir
> Found package mpir in spkg/st
Hi,
On Thursday, August 1, 2013 6:53:59 PM UTC+2, Jean-Pierre Flori wrote:
>
> As far as MPIR is concerned I've put a (dirty) spkg at
> http://boxen.math.washington.edu/home/jpflori/spkg/mpir-2.6.0.p3.spkgwhich
> should work both on Cygwin 32 and 64 (and MinGW with a li
As far as MPIR is concerned I've put a (dirty) spkg at
http://boxen.math.washington.edu/home/jpflori/spkg/mpir-2.6.0.p3.spkg which
should work both on Cygwin 32 and 64 (and MinGW with a little help when
configuring Yasm).
--
You received this message because you are subscribed to the Google G
On Thursday, August 1, 2013 10:16:45 AM UTC+2, Travis Scrimshaw wrote:
>
> Also I just tried using the 5.9 source on cygwin32 and got the same error
> when building python. Sorry I'm posting more questions and no solutions and
> thank you for the help.
>
> Good, that's what I first suggested.
On Thursday, August 1, 2013 4:20:00 AM UTC+2, Travis Scrimshaw wrote:
>
> Hey Jean-Pierre,
>I have been trying to do it on Cygwin32 and with zlib-1.2.6.p0 (I had
> to make my own from zlib-1.2.6 since the link on the trac ticket is no
> longer there) and now python-2.7.5.p1 fails to build (
You can get an MPIR working on Cygwin64 at https://github.com/jpflori/mpir
(clone, configure, make dist, craft your own spkg)
As a side effect, I broke it on Cygwin32 :)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this grou
es on it
> as (if) I make progress.
>
> Thanks,
> Travis
>
>
> On Saturday, July 27, 2013 8:02:47 PM UTC+9, Jean-Pierre Flori wrote:
>
>> For MPIR see http://cygwin.com/ml/cygwin/2013-06/msg00539.html
>> You'll have to craft your own spkg though (or wait for the
For MPIR see http://cygwin.com/ml/cygwin/2013-06/msg00539.html
You'll have to craft your own spkg though (or wait for the end of my
vacations).
On Saturday, July 27, 2013 1:01:15 PM UTC+2, Jean-Pierre Flori wrote:
>
> I got the same problem a few weeks ago and just ended up using the
I got the same problem a few weeks ago and just ended up using the old zlib
spkg.
Beware that youll have several other issues later, especially with MPIR,
Boehm GC...
I reported a few of them at http://trac.sagemath.org/wiki/Cygwin64Port
On Friday, July 26, 2013 3:24:00 PM UTC+2, Travis Scrims
On Friday, July 12, 2013 11:12:11 AM UTC+2, Jean-Pierre Flori wrote:
>
> Could you "export PKG_CONFIG_DEBUG_SPEW=yes" before launching Sage's
> python?
> (You can try something like "import os; print
> os.environ['PKG_CONFIG_DEBUG_SPEW'] to make sur
e sure pkg-config is correctly detected.
On Friday, July 12, 2013 11:08:40 AM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Friday, July 12, 2013 10:53:26 AM UTC+2, Paul Mercat wrote:
>>
>> MacBook-Pro-de-Paul:src mercat$ sage --python
>> Python 2.6.4 (r264:75706, Aug 12 2
On Friday, July 12, 2013 10:53:26 AM UTC+2, Paul Mercat wrote:
>
> MacBook-Pro-de-Paul:src mercat$ sage --python
> Python 2.6.4 (r264:75706, Aug 12 2011, 00:49:46)
> [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >
irlist is: ['/Users/mercat/sage-5.10/local']
>> >>> module = setupext.make_extension("test", [])
>> Traceback (most recent call last):
>> File "", line 1, in
>> AttributeError: 'module' object has no attribute 'make_exte
On Thursday, July 11, 2013 11:59:58 PM UTC+2, Jean-Pierre Flori wrote:
>
> FYI, on a raspberry pi i get similar problems (also similar to what
> Stephen reported for FreeBSD):
Or not, retrying it once over the night, it finished properly.
--
You received this message becaus
in get
raise TimeoutError
multiprocessing.TimeoutError
make: *** [doc-html] Error 1
}}}
On Thursday, April 25, 2013 9:07:39 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Thursday, April 25, 2013 6:10:07 PM UTC+2, kcrisman wrote:
>>
>>
>>
>> On Tuesday, March 19, 2013 7:51:42 AM UTC-
ol.py", line
550, in get
raise TimeoutError
multiprocessing.TimeoutError
make: *** [doc-html] Error 1
}}}
On Saturday, June 8, 2013 8:31:28 PM UTC+2, Snark wrote:
>
> Le 08/06/2013 20:16, Jean-Pierre Flori a �crit :
> >
> >
> > On Saturday, June 8, 2013 7:59:35 PM
On Thursday, July 11, 2013 11:23:41 PM UTC+2, Paul Mercat wrote:
>
> Ok, sorry I've type that in the sage shell.
> Now in the sage python shell :
>
> >>> import setupext
> Traceback (most recent call last):
> File "", line 1, in
> ImportError: No module named setupext
>
>
> Did you "cd" to th
On Thursday, July 11, 2013 5:27:27 PM UTC+2, Paul Mercat wrote:
>
> If I do
>
> import setupext
>
> in the sage shell, I get
>
I meant a sage python shell, i.e. run ./sage --python, is it what you've
done?
--
You received this message because you are subscribed to the Google Groups
"sage-deve
On Thursday, July 11, 2013 3:30:57 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Thursday, July 11, 2013 3:18:53 PM UTC+2, Paul Mercat wrote:
>>
>> In the Sage shell, the command
>>
>> pkg-config --variable pc_path pkg-config
>>
>> gives nothing.
&
On Thursday, July 11, 2013 3:18:53 PM UTC+2, Paul Mercat wrote:
>
> In the Sage shell, the command
>
> pkg-config --variable pc_path pkg-config
>
> gives nothing.
> And the command
>
> export PKG_CONFIG_DEBUG_SPEW=yes;
> pkg-config --libs --cflags libpng
>
> gives
>
> PKG_CONFIG_DEBUG_SPEW variab
And from a sage shell again, "export PKG_CONFIG_DEBUG_SPEW=yes" and then
"pkg-config --libs --cflags libpng" or run "pkg-config --print-errors
--libs --cflags libpng"
On Thursday, July 11, 2013 3:07:44 PM UTC+2, Jean-Pierre Flori wrote:
>
> And from
And from a sage shell can you run "pkg-config --variable pc_path pkg-config"as
well?
--
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...@google
On Thursday, July 11, 2013 2:05:58 PM UTC+2, Paul Mercat wrote:
>
> ./sage --sh -c "echo $PKG_CONFIG_PATH"
>
> gives
>
>
> (nothing)
>
> For me as well in fact...
And from a real Sage shell (./sage --sh) ?
There I get something.
--
You received this message because you are subscribed to the Goo
On Thursday, July 11, 2013 1:31:31 PM UTC+2, Paul Mercat wrote:
>
> The result of
>
> pkg-config --libs --cflags libpng
>
> is
>
> Package libpng was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libpng.pc'
> to the PKG_CONFIG_PATH environment variabl
and so the configuration falls
back to using -lpng.
It may be safer to call "try_pkgconfig(bla, libpng, png12)" if my
interpretation is correct.
On Thursday, July 11, 2013 1:01:59 PM UTC+2, Jean-Pierre Flori wrote:
>
> What is the output of "pkg-config --libs --cflags libpn
What is the output of "pkg-config --libs --cflags libpng"?
On Thursday, July 11, 2013 12:57:49 PM UTC+2, Jean-Pierre Flori wrote:
>
> So you have pkg-config and linpng install looks fine...
> I don't really have other ideas right now.
>
> Might be nice to see what
>
> The command
>
> command -v pkg-config
>
> gives
>
> /usr/local/bin/pkg-config
>
> And
>
> $?
>
> gives
>
> 0
>
>
> The file $SAGE_LOCAL/lib/pkgconfig/libpng.pc is a symbolic link to
> $SAGE_LOCAL/lib/pkgconfig/libpng12.pc
>
>
401 - 500 of 875 matches
Mail list logo
