Given two matrices G and H, the matrix K = [G, 0; 0, H] has determinant
det(K) = det(G) det(H)
So if you want this formula to remain true if one of the matrices is 0x0, then
you want the determinant of a 0x0 matrix to be 1.
From: sage-devel@googlegroups.com [sage
away.
>
> François
>
>> On 20/05/2015, at 15:50, Montgomery-Smith, Stephen
>> wrote:
>>
>> I have been having some trouble building documentation for sage on my
>> FreeBSD system. Mostly the errors are inconsistent. But I finally
>> found a consiste
I have been having some trouble building documentation for sage on my
FreeBSD system. Mostly the errors are inconsistent. But I finally
found a consistent error.
As Sphinx traverses the doctree, it creates files called
environment.pickle. I discovered that Sphinx was crashing when
performing th
Hey people,
FreeBSD people do like to build their ports as root. The problem
described below could be easily fixed by simply removing the group write
permissions of all the files in the tarball upstream/pynac-0.3.2.tar.bz2.
It's not such a great deal if this isn't fixed by the time sage-6.3
come
1. This is great. Thank you. I hope it gets included in sage-6.3.
2. I erroneously said that I had to remove package-version.txt. But it
was actually the uuid patch I had to remove. But I see from the trac
ticket that you guys are already on top of this.
On 05/29/2014 08:51 PM, Travis Scri
I am having great trouble getting sage to build on FreeBSD version 10
and above. I was finally able to fix the problem by switching out the
python-2.7.5 source code that comes with sage with python-2.7.6 source
code. Amazingly this fixed a lot of the problems.
So, is there any interest in having
No PKG* variables were set by my system.
pkgconf-0.9.5
http://svnweb.freebsd.org/ports/head/devel/pkgconf/
I looked at the dates on pkg-config in $SAGE_ROOT/local/bin, and it was
created 4 seconds after libm4ri-20130416 was installed.
I did create a ticket, but you can close it if you like.
http
On 05/16/2014 05:38 PM, leif wrote:
> Montgomery-Smith, Stephen wrote:
>> I was building sage-6.2 using FreeBSD. I found out that the subpackage
>> libm4ri was picking up the system libpng rather than the sage libpng. I
>> was able to fix it with the following patch:
>>
I was building sage-6.2 using FreeBSD. I found out that the subpackage
libm4ri was picking up the system libpng rather than the sage libpng. I
was able to fix it with the following patch:
--- build/pkgs/libm4ri/spkg-install-orig2014-05-16
18:34:53.0 +
+++ build/pkgs/libm4ri/s
I am trying to build sage-6.2 on FreeBSD. I get errors like the
following in sage-6.2/logs/pkgs/libgap-4.7.4.log
. lots of configure stuff .
config.status: creating src/config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Building libGAP...
make[3]
If it is just one of those things (and maybe my fault), then it is OK.
Just checking it is not a new policy or something.
On 01/29/2014 05:03 PM, Volker Braun wrote:
> I'm pretty sure that we haven't changed the source tarball since its
> release on 2013-12-18. Are you sure not one of your downlo
I downloaded sage-6.0.tar.gz a few days ago, and again recently. The
md5 numbers of the file had changed.
Was this a one time occurrence, or is it part of the way distributions
are distributed that the tarballs change once in a while? If the
latter, this will be very hard for me, because I am ma
On 01/27/2014 05:12 AM, Volker Braun wrote:
> The build/pkg/* subdirectories contain only patches and metadata, but no
> upstream source code. There shouldn't be any src subdirectories. The
> tarballs go into upstream.
>
> The actual building is done in the src/bin/sage-spkg script.
OK, I get it
I notice that in sage 6.0 that the source code of the subpackages are
stored in one of two places: build/pkg/* and upstream/*. Now in some
build/pkg/* directories, the src directories already exist. Whereas in
other build/pkg/* directories, the src directories don't exist. In the
latter case, I
On 03/12/2013 03:53 AM, Dima Pasechnik wrote:
> On 2013-03-09, Stephen Montgomery-Smith wrote:
>> This is the 4th time I tried sending this message. I think it gets
>> flagged as spam by google.
> Are your MX records configured? It doesn't look they are. This makes
> your mails go to spam, IMHO.
I think it may well be related to the semaphore issue. But if that is the
case, it might take more time to fix than I have right now. So for a while, I
guess the FreeBSD port of sage will stay with 5.7.
In the mean time, if someone tells which part of the python code does the
document buildin
So I ran the make process again. After getting to the point of freezing, using
top, I could see that there were a couple of invocations of python2.7. FreeBSD
uses truss in place of strace, and using "truss -p pid" where pid was the pid
of one of the invocations of python2.7, I could see lines
Building on FreeBSD, the doc creation process freezes after this point:
[history_a] loading pickled environment... not yet created
[history_a] building [inventory]: targets for 1 source files that are
out of date
[history_a] updating environment: 1 added, 0 changed, 0 removed
[history_a] reading s
18 matches
Mail list logo
