On 06/21/2013 12:47 AM, Jeroen Demeyer wrote:
> On 06/20/2013 07:51 PM, Stephen Montgomery-Smith wrote:
>> It is easy to provide a working patch, but why was this compilation done
>> with -Werror set?
> Good question, it's only this one file which is compiled with -Werror.
This is in the build of ppl-1.0.p0, on FreeBSD-8.2, using its gcc46
compiler.
The relevant lines seem to be:
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../interfaces/C
-I/usr/home/stephen/sage-devel/work/sage-5.11.beta2/local/include
-pedantic -std=gnu89 -Werror -g -O2 -frounding-math -pipe
-Wl,-rpath
On 05/27/2013 04:55 PM, Jean-Pierre Flori wrote:
>
>
> On Monday, May 27, 2013 11:49:04 PM UTC+2, Stephen Montgomery-Smith wrote:
>
> On 05/27/2013 04:36 PM, Jean-Pierre Flori wrote:
> >
> >
> > On Monday, May 27, 2013 11:32:20
On 05/27/2013 04:36 PM, Jean-Pierre Flori wrote:
>
>
> On Monday, May 27, 2013 11:32:20 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Monday, May 27, 2013 11:27:58 PM UTC+2, Jean-Pierre Flori wrote:
>
> IIRC scipy adds strange prefix to atlas library names on FreeBSD
> (_r
out removing
> the (reference) blas and lapack spkg, it seems scipy found the libraries
> built by the blas and lapack spkgs.
>
> On Monday, May 27, 2013 11:17:08 PM UTC+2, Stephen Montgomery-Smith wrote:
>
> There isn't one. It looks like scipy uses setup.py instead o
There isn't one. It looks like scipy uses setup.py instead of configure.
On 05/27/2013 04:06 PM, Jean-Pierre Flori wrote:
> And config.log from scipy build folder?
>
> On Monday, May 27, 2013 10:59:12 PM UTC+2, Stephen Montgomery-Smith wrote:
>
> On 05/27/2013 03:55 P
On 05/27/2013 03:55 PM, Jean-Pierre Flori wrote:
> Heyn
>
> On Monday, May 27, 2013 9:52:59 PM UTC+2, Stephen Montgomery-Smith wrote:
>
> This is building with the FreeBSD port, using
> SAGE_ATLAS_LIB=/usr/local/lib.
>
> I really don't know what to
This is building with the FreeBSD port, using SAGE_ATLAS_LIB=/usr/local/lib.
I really don't know what to look for, or which errors are fatal and
which are just warnings.
See attachment.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscr
On 05/13/2013 04:56 PM, John H Palmieri wrote:
> On Monday, May 13, 2013 2:11:59 PM UTC-7, ManDay wrote:
>
> Could anyone shed a bit of light on this?
>
> The more I try, the more SAGE's types get in my way. It turns out to be
> an unpredictable element. Unless I make sure *every* inv
When I build sage, during the build of maxima-5.29.1.p1 it executes the
command sequence:
make[6]: Entering directory
`/usr/home/stephen/sage-devel/work/sage-5.9.rc0/spkg/build/maxima-5.29.1.p1/src/interfaces/xmaxima'
tclsh < /dev/null > /dev/null 2>&1 && \
(cd Tkmaxima ; \
ec
Just to tell people that the first and second errors listed below no
longer occur with 5.9.beta3.
As for the third error, I have a trac ticket that fixes it:
http://trac.sagemath.org/sage_trac/ticket/14392
On 03/20/2013 10:09 PM, Stephen Montgomery-Smith wrote:
> This is under FreeBSD. (Th
On 03/21/2013 02:03 AM, Jeroen Demeyer wrote:
> On 2013-03-21 04:09, Stephen Montgomery-Smith wrote:
>> 1. I notice that many tests (like "sage -t
>> devel/sage/sage/rings/arith.py") are run three times.
> Any suspicious environment variables? What is
> $ env
This is under FreeBSD. (There are other failures, but so far they are
all legitimate floating point disagreements, or similar to the ones I
report here.)
1. I notice that many tests (like "sage -t
devel/sage/sage/rings/arith.py") are run three times.
2. I get some strange errors like "sage -t
On 03/19/2013 06:07 AM, leif wrote:
> Jeroen Demeyer wrote:
>> On 2013-03-19 04:30, John H Palmieri wrote:
>>> Is there any good way of testing whether multithreading is broken
>> That would of course be ideal, but we should first find out exactly
>> why/how it's broken on FreeBSD.
>
> Yep. As sa
On 03/17/2013 02:48 PM, Stephen Montgomery-Smith wrote:
> On 03/09/2013 06:40 PM, Montgomery-Smith, Stephen wrote:
>> Building on FreeBSD, the doc creation process freezes at some point
I have done more investigation. The following patch fixes the problem,
so it is definitely a p
On 03/09/2013 06:40 PM, Montgomery-Smith, Stephen wrote:
> 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] upda
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
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
Building on FreeBSD, the doc creation process freezes after this point:
[history_a] writing output... [100%] index
[history_a] dumping object inventory... done
[history_a] build succeeded.
P.S. I sent this email twice before. Perhaps google flagged it as spam.
--
You received this messag
This is the 3rd time I tried sending this message. I think it gets
flagged as spam by google.
I have a problems building docs on sage-5.8.beta4. On FreeBSD, the doc
creation process freezes after this point:
[history_a] writing output... [100%] index
[history_a] dumping object inventory...
This is the 4th time I tried sending this message. I think it gets
flagged as spam by google.
I have a problems building docs on sage-5.8.beta4. On FreeBSD, the doc
creation process freezes. I cannot tell you where, because the text
must be flagged as spam. If this when gets through, I'll try
On 01/28/2013 02:47 AM, Jeroen Demeyer wrote:
> Could you please provide the complete build log of SciPy and ATLAS?
>
Do you still need it? I deleted the build, so I would need to rebuild
it to get it back.
Also, the FreeBSD version of sage uses FreeBSD's port of atlas.
--
You received this
I am getting this error when building scipy-0.11.0.p0.
/usr/home/stephen/sage-devel/work/sage-5.7.beta1/local/bin/gfortran
-Wall -shared
-Wl,-rpath=/usr/home/stephen/sage-devel/work/sage-5.7.beta1/local/lib
-Wl,-rpath=/usr/local/lib/gcc46
build/temp.freebsd-8.3-STABLE-amd64-2.7/build/src.freebsd-
On 12/26/2012 11:23 AM, kcrisman wrote:
>
>
> On Wednesday, December 26, 2012 6:51:42 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> > When I am building sage-5.5 inside of sage-5.5
> What does this mean? If it mean
On 12/25/2012 01:22 PM, Stephen Montgomery-Smith wrote:
> When I am building sage-5.5 inside of sage-5.5, I get the following
> error in my build log. I was able to build sage-5.5.rc1 with no
> problem. Am I unique with this problem? I am building under FreeBSD-8.2.
>
>
&g
When I am building sage-5.5 inside of sage-5.5, I get the following
error in my build log. I was able to build sage-5.5.rc1 with no
problem. Am I unique with this problem? I am building under FreeBSD-8.2.
gcc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -pipe
-Wl,-rpath=/usr/ports/math/sa
On 12/15/2012 08:51 PM, kcrisman wrote:
> Just sayin'.
>
> http://science.slashdot.org/story/12/12/14/214231/ask-slashdot-replacing-a-ti-84-with-software-on-a-linux-box
>
> and then check the comments.
The original poster didn't like maxima, because it doesn't have a
"degrees" button where all t
While trying to compile sage-5.4beta1 on FreeBSD, it failed because of
another place using "#!/bin/bash". As I understand it, it should be
"#!/usr/bin/env bash".
This time it is in fflas_ffpack-1.6.0//src/fflas-ffpack-config.in
I'll file a ticket (except trac.sage isn't working for me right n
I am "top-posting" agnostic. So when I reply to a top poster, I top
post. When replying to a bottom poster I bottom post. But
On 09/12/12 07:21, kcrisman wrote:
Great!
On Wednesday, September 12, 2012 5:39:21 AM UTC-4, Stephen
Montgomery-Smith wrote:
Yes, that wor
Yes, that works as well.
(Is it OK to top post in this mailing list?)
On 09/12/2012 04:26 AM, Volker Braun wrote:
Or the third and most portable way:
#!/usr/bin/env bash
On Wednesday, September 12, 2012 4:22:32 AM UTC+1, Stephen
Montgomery-Smith wrote:
Unfortunately in FreeBSD, this has
The package jmol contains testjava.sh. The top of the file is
#!/bin/bash
Unfortunately in FreeBSD, this has to be one of:
#!/usr/local/bin/bash
or
#!/bin/sh
Do I need to create a ticket, or will the creator of jmol see this
email, and make this simple change?
Thanks, Stephen
--
You recei
On 07/09/12 08:45, John W. Foster wrote:
Jan: I did as you suggested & restarted the compiling process on my
system. I did have to restart it 2 times to get it to finish, but I do
have it running now and it appears fine. I will be testing it out and
look forward to the final release. Thanks for
On 06/20/2012 03:16 PM, kcrisman wrote:
On Wednesday, June 20, 2012 3:40:24 PM UTC-4, Stephen Montgomery-Smith
wrote:
On 06/20/2012 02:30 PM, kcrisman wrote:
>
>
> On Thursday, April 19, 2012 3:25:44 PM UTC-4, leif wrote:
>
> On 19 Apr., 05:33, Ste
On 06/20/2012 02:34 PM, kcrisman wrote:
Another reason I want to use the FreeBSD port build of gcc-4.6 is this.
The work required to get atlas to build on FreeBSd is huge. I don't
want to mess with copying all those patches into sage. But the port
build of atlas requires the Free
On 06/20/2012 02:30 PM, kcrisman wrote:
On Thursday, April 19, 2012 3:25:44 PM UTC-4, leif wrote:
On 19 Apr., 05:33, Stephen Montgomery-Smith
wrote:
> I think I have found the problem with sympow. It is nothing to do
with
> elliptic curves. It is simply a mallo
On 06/20/2012 01:39 PM, kcrisman wrote:
I'm a little confused on why
http://trac.sagemath.org/sage_trac/ticket/5873 wasn't necessary, since
you used newer versions of FreeBSD. That should have generated some kind
of key error at
https://github.com/matplotlib/matplotlib/blob/master/setupext.py#L
On 06/20/2012 11:05 AM, kcrisman wrote:
On Tuesday, June 19, 2012 10:21:31 PM UTC-4, Stephen Montgomery-Smith wrote:
On 06/19/2012 07:29 PM, kcrisman wrote:
>
>
> On Tuesday, June 19, 2012 5:28:29 PM UTC-4, Stephen
Montgomery-Smith wrote:
>
> W
On 06/20/2012 01:39 AM, Jeroen Demeyer wrote:
On 2012-06-20 04:21, Stephen Montgomery-Smith wrote:
I got a whole different set of errors:
Sorry to ask the obvious, but did you run ./sage -b?
I must admit that I didn't know about ./sage -b. I ended up rebuilding
the whole of sage, wit
On 06/19/2012 07:29 PM, kcrisman wrote:
On Tuesday, June 19, 2012 5:28:29 PM UTC-4, Stephen Montgomery-Smith wrote:
When I run "sage testall" for sage-5.1.beta5 on FreeBSD/amd64, I get
the
Does this imply you get no other failures? Even close to that would be
great news
When I run "sage testall" for sage-5.1.beta5 on FreeBSD/amd64, I get the
following failure, which is new since version 5.0:
File
"/usr/home/stephen/sage-devel/work/sage-5.1.beta5/devel/sage/sage/rings/real_double.pyx",
line 1741:
sage: all( check_error(x) for x in sxrange(0.01, 2.00, 0.01
What does the acronym "FAT" in "SAGE_FAT_BINARY" refer to?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-dev
On 05/20/2012 10:44 AM, Stephen Montgomery-Smith wrote:
On 05/20/2012 10:39 AM, Dr. David Kirkby wrote:
On 05/20/12 03:38 PM, Stephen Montgomery-Smith wrote:
On 05/20/2012 06:50 AM, David Kirkby wrote:
On 20 May 2012 00:58, Volker Braun wrote:
Currently, the cephes package only prints:
&qu
On 05/20/2012 10:39 AM, Dr. David Kirkby wrote:
On 05/20/12 03:38 PM, Stephen Montgomery-Smith wrote:
On 05/20/2012 06:50 AM, David Kirkby wrote:
On 20 May 2012 00:58, Volker Braun wrote:
Currently, the cephes package only prints:
"We do not install the cephes library on any operating s
On 05/20/2012 06:50 AM, David Kirkby wrote:
On 20 May 2012 00:58, Volker Braun wrote:
Currently, the cephes package only prints:
"We do not install the cephes library on any operating system except
Cygwin."
I believe when someone else (I forget who), was working on the FreeBSD
port, he need
On 05/17/2012 11:24 AM, Jeroen Demeyer wrote:
As noted on sage-support, the sage-5.0 *binary* requires the boost
library libboost_unit_test_framework at runtime, if the binary was built
on such a machine. I.e. PolyBoRi checks for boost_unit_test_framework
and links against it if available.
This
On 05/02/2012 02:18 PM, Stephen Montgomery-Smith wrote:
On 05/02/12 12:46, Dima Pasechnik wrote:
On Wednesday, May 2, 2012 4:01:09 PM UTC, Stephen Montgomery-Smith wrote:
I just built sage-5.0.rc0 on FreeBSD. When I do make test, one of the
test failures is puzzling me:
sage -t -force_lib
On 05/02/2012 02:18 PM, Stephen Montgomery-Smith wrote:
On 05/02/12 12:46, Dima Pasechnik wrote:
On Wednesday, May 2, 2012 4:01:09 PM UTC, Stephen Montgomery-Smith wrote:
I just built sage-5.0.rc0 on FreeBSD. When I do make test, one of the
test failures is puzzling me:
sage -t -force_lib
On 05/02/2012 04:18 PM, kcrisman wrote:
On May 2, 3:43 pm, Jeroen Demeyer wrote:
On 2012-05-02 21:18, Stephen Montgomery-Smith wrote:> Would it be fair to say
that the optional packages should be considered
unreliable?
Indeed. That could be one of the reasons they are conside
On 05/02/12 12:46, Dima Pasechnik wrote:
On Wednesday, May 2, 2012 4:01:09 PM UTC, Stephen Montgomery-Smith wrote:
I just built sage-5.0.rc0 on FreeBSD. When I do make test, one of the
test failures is puzzling me:
sage -t -force_lib "devel/sage/sage/tests/start
I just built sage-5.0.rc0 on FreeBSD. When I do make test, one of the
test failures is puzzling me:
sage -t -force_lib "devel/sage/sage/tests/startup.py"
**
File
"/usr/home/stephen/sage-devel/work/sage-5.0.rc0/devel/sage/sage
fires? If that is the case we should probably ignore it in
use_fork.py
On Saturday, April 21, 2012 3:36:44 PM UTC-4, Stephen Montgomery-Smith
wrote:
I did some research, and I found that you are completely correct. I
don't know why FreeBSD is misbehaving, because the os.wait co
:39:13 AM UTC-4, Stephen Montgomery-Smith
wrote:
In parallel/use_fork.py, around line 120, there seems to be a race
problem. This seems to be a genuine problem with my FreeBSD build:
sage -t -force_lib "devel/sage/sage/parallel/decorate.py"
goes into a permanent loop.
Supp
In parallel/use_fork.py, around line 120, there seems to be a race
problem. This seems to be a genuine problem with my FreeBSD build:
sage -t -force_lib "devel/sage/sage/parallel/decorate.py"
goes into a permanent loop.
Suppose that timeout has been set, and the forked process is too slow.
So
I think I have found the problem with sympow. It is nothing to do with
elliptic curves. It is simply a malloc/free error.
In util.c there is a function free_data, which frees TACKS[0]. TACKS[0]
is meant to be allocated in disk.c, but there are circumstances when
TACKS[0] is not allocated.
On 04/18/12 12:14, Dima Pasechnik wrote:
The complex_double.pyx problem seems to be PARI-related. Is there a PARI
port of FreeBSD?
Yes there is. it is version 2.3.5, which is several versions earlier
than sage is using.
What pari commands can I use to test if the problem is the same for pa
On 04/15/2012 12:14 AM, Stephen Montgomery-Smith wrote:
On 04/14/2012 09:33 PM, kcrisman wrote:
I would appreciate any help understanding the cause of the remaining
errors.
Luckily, first we want it to build - then we can fix the errors. Most
look fairly technical - does sympow not work on
On 04/14/2012 09:33 PM, kcrisman wrote:
I would appreciate any help understanding the cause of the remaining errors.
Luckily, first we want it to build - then we can fix the errors. Most
look fairly technical - does sympow not work on it, for instance? The
errors in complex_double.pyx bother
On 03/27/2012 02:10 PM, Jeroen Demeyer wrote:
On 2012-03-27 20:05, Stephen Montgomery-Smith wrote:
Actually the error appeared with beta9. The error seems to have
disappeared with beta10.
Are you *sure* it was beta9 and not an earlier version? There was a
change in Linbox in sage-5.0.beta8
On 03/27/2012 10:58 AM, Jeroen Demeyer wrote:
On 2012-03-27 17:52, Stephen Montgomery-Smith wrote:
I am attempting to compile sage-5.0.beta10. I see there is a new patch
in linbox for commentator.C. But it is not working for me.
Could you at least say why it's not working? How does it
On 03/27/2012 11:03 AM, leif wrote:
On 27 Mrz., 17:52, Stephen Montgomery-Smith
wrote:
I am attempting to compile sage-5.0.beta10. I see there is a new patch
in linbox for commentator.C. But it is not working for me.
The attached patch did work for me, and I was wondering if it would be a
I am attempting to compile sage-5.0.beta10. I see there is a new patch
in linbox for commentator.C. But it is not working for me.
The attached patch did work for me, and I was wondering if it would be a
problem for anyone else if this patch was used instead. This is a
replacement for linbox
On 02/15/2012 12:34 AM, William Stein wrote:
On Tue, Feb 14, 2012 at 10:15 PM, Dr. David Kirkby
wrote:
On 02/15/12 05:58 AM, William Stein wrote:
Hi,
A student in my class (Andrey Sarantsev) just pointed out to me that
in Sage-4.8 and Sage-5.0, we have
sage: I^(0.5)
None
What? That's not
On 02/01/2012 03:31 PM, David Kirkby wrote:
On 22 January 2012 21:54, Stephen Montgomery-Smith mailto:step...@missouri.edu>> wrote:
I fixed the problem as follows:
sed -i .bak -e 's/Commentator/Commensator/g' \
That's not a fix. The POSIX definition of '
On 01/30/2012 08:27 PM, kcrisman wrote:
Just to make sure this is found by anyone searching this thread:
http://trac.sagemath.org/sage_trac/ticket/12399
http://trac.sagemath.org/sage_trac/ticket/12400
http://trac.sagemath.org/sage_trac/ticket/12401
are followup tickets with some of the stuff fr
So if you move the sage-4.8 directory, and run sage, it recodes various
paths.
Can someone tell me where in the source code these operations are
programmed? And which files are touched by this operation?
Thanks, Stephen
--
To post to this group, send an email to sage-devel@googlegroups.com
On 01/24/12 08:31, kcrisman wrote:
I just found
this.http://trac.sagemath.org/sage_trac/attachment/ticket/9543/cephes-2.8
I'm trying it now.
It caused build errors in other sub-packages. But I have spent too many
late nights on figuring out the FreeBSD build, and I am going to have to
On 01/24/2012 07:56 AM, kcrisman wrote:
On Jan 24, 12:19 am, Stephen Montgomery-Smith
wrote:
On 01/23/2012 05:40 PM, Stephen Montgomery-Smith wrote:
On 01/23/2012 12:34 PM, Jeroen Demeyer wrote:
On 2012-01-23 14:27, Stephen Montgomery-Smith wrote:
"ccosh" not found seemed lik
Looking in
http://www.sagemath.org/doc/installation/source.html
it says that "make -j4" is respected. This works really great when
building the source code.
But the documentation also suggests that it should be building in
parallel when creating the documentation? Should there by 4 invocatio
On 01/23/2012 05:40 PM, Stephen Montgomery-Smith wrote:
On 01/23/2012 12:34 PM, Jeroen Demeyer wrote:
On 2012-01-23 14:27, Stephen Montgomery-Smith wrote:
"ccosh" not found seemed like a common error.
This might be solvable by installing cephes on FreeBSD. This is
included in Sag
On 01/23/2012 05:40 PM, Stephen Montgomery-Smith wrote:
On 01/23/2012 12:34 PM, Jeroen Demeyer wrote:
On 2012-01-23 14:27, Stephen Montgomery-Smith wrote:
"ccosh" not found seemed like a common error.
This might be solvable by installing cephes on FreeBSD. This is
included in Sag
On 01/23/2012 05:52 PM, Stephen Montgomery-Smith wrote:
On 01/23/2012 04:39 PM, Stephen Montgomery-Smith wrote:
On 01/23/2012 08:12 AM, Dima Pasechnik wrote:
missing ccosh probably is a deficiency of libc/libm on your system.
Can you compile/link
#include
#include
int main() { double
On 01/23/2012 04:39 PM, Stephen Montgomery-Smith wrote:
On 01/23/2012 08:12 AM, Dima Pasechnik wrote:
missing ccosh probably is a deficiency of libc/libm on your system.
Can you compile/link
#include
#include
int main() { double complex x=ccosh(1.); }
on your system, and what extra libs
On 01/23/2012 12:34 PM, Jeroen Demeyer wrote:
On 2012-01-23 14:27, Stephen Montgomery-Smith wrote:
"ccosh" not found seemed like a common error.
This might be solvable by installing cephes on FreeBSD. This is
included in Sage but only installed on Cygwin.
According to "spkg
On 01/23/2012 08:12 AM, Dima Pasechnik wrote:
missing ccosh probably is a deficiency of libc/libm on your system.
Can you compile/link
#include
#include
int main() { double complex x=ccosh(1.); }
on your system, and what extra libs does it need?
On my system, complex cosh is the cosh functi
On 01/23/2012 07:27 AM, Stephen Montgomery-Smith wrote:
On 01/22/2012 11:40 PM, Stephen Montgomery-Smith wrote:
I have tested this port at least up until a working sage is created. I
am going to do a complete build tonight.
In the meantime, others can try this out if they like.
Also, I made
On 01/22/2012 11:40 PM, Stephen Montgomery-Smith wrote:
I have tested this port at least up until a working sage is created. I
am going to do a complete build tonight.
In the meantime, others can try this out if they like.
So it built successfully. I ran "sage -testall" and it
I have tested this port at least up until a working sage is created. I
am going to do a complete build tonight.
In the meantime, others can try this out if they like.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-d
On 01/22/2012 07:36 PM, Paulo César Pereira de Andrade wrote:
Since the problem appears to be related to linbox ...
It was related to linbox. My "fix" using sed wasn't working.
What I did was to rebuild linbox. I removed any reference to
-DDISABLE_COMMENTATOR (which I did by hacking com
One thing I want to rule out is that the problem is created by python.
FreeBSD has a working python version 2.7. How do I tell the sage build
to use the FreeBSD python rather than building its own?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
On 01/22/2012 04:28 PM, Stephen Montgomery-Smith wrote:
On 01/22/2012 04:24 PM, François Bissey wrote:
On Sun, 22 Jan 2012 15:54:19 Stephen Montgomery-Smith wrote:
On 01/21/2012 08:23 PM, Stephen Montgomery-Smith wrote:
On 01/21/2012 08:05 PM, Stephen Montgomery-Smith wrote:
I am able to
On 01/22/2012 04:24 PM, François Bissey wrote:
On Sun, 22 Jan 2012 15:54:19 Stephen Montgomery-Smith wrote:
On 01/21/2012 08:23 PM, Stephen Montgomery-Smith wrote:
On 01/21/2012 08:05 PM, Stephen Montgomery-Smith wrote:
I am able to build sage on FreeBSD. I have attached a tar file which
On 01/21/2012 08:23 PM, Stephen Montgomery-Smith wrote:
On 01/21/2012 08:05 PM, Stephen Montgomery-Smith wrote:
I am able to build sage on FreeBSD. I have attached a tar file which
contains a "port" to build sage on FreeBSD. (FreeBSD users will know
what I mean by a "port.&quo
On 01/22/2012 02:35 AM, Paulo César Pereira de Andrade wrote:
2012/1/22 Stephen Montgomery-Smith:
On 01/21/2012 08:05 PM, Stephen Montgomery-Smith wrote:
I am able to build sage on FreeBSD. I have attached a tar file which
contains a "port" to build sage on FreeBSD. (FreeBSD users
On 01/21/2012 08:05 PM, Stephen Montgomery-Smith wrote:
I am able to build sage on FreeBSD. I have attached a tar file which
contains a "port" to build sage on FreeBSD. (FreeBSD users will know
what I mean by a "port.")
It does seem to work, but it segfaul
I am able to build sage on FreeBSD. I have attached a tar file which
contains a "port" to build sage on FreeBSD. (FreeBSD users will know
what I mean by a "port.")
It does seem to work, but it segfaults on exit:
%./sage
--
|
On 01/21/2012 03:27 PM, Stephen Montgomery-Smith wrote:
I am embarking on trying to build sage under FreeBSD. Thus far, the main
problem that seems to be holding me up is when I try to build the
sage4.8 subpackage. I get an error that says that sem_opn is not
functioning. However I am using a
I am embarking on trying to build sage under FreeBSD. Thus far, the
main problem that seems to be holding me up is when I try to build the
sage4.8 subpackage. I get an error that says that sem_opn is not
functioning. However I am using a version of FreeBSD that has
semaphores installed by de
87 matches
Mail list logo
