2009/8/4 William Stein wst...@gmail.com:
On Tue, Aug 4, 2009 at 1:06 AM, David Kirkbydavid.kir...@onetel.net wrote:
I often wonder if there should be a 'feature freeze' in Sage and
devote some time to sorting out why these warnings are occuraing and
whether they could result in the
brandon.bar...@gmail.com wrote:
I think my current gcc toolchain may be doomed, as it uses the sun
linker and the gnu assembler! (I read this was a good thing to do, at
least at some point in history).
Mixing the GNU and Sun assemblers/linkers could issues in Sage, due to
the way some
brandon.bar...@gmail.com wrote:
Actually this seems to be an issue with it trying to link to the
system mpfr. Shouldn't sage built its own mpfr?
I agree with you it looks like termcap is linking to the wrong library,
but it does appear that gcc has generated an internal error. That is
I did try setting LD_LIBRARY_PATH but this resulted in the same
problem. I even tried temporarily changing the ld.config search order
with crle (the solaris cousin of the linux ldconfig) from:
/lib:/usr/lib:/usr/local/lib
to:
/usr/local/lib:/lib:/usr/lib
But this didn't help. Perhaps If I
Strangely after rebuilding under these conditions it is now failing on
mpir (it is capable of building software so it isn't completely
broken):
configure:4497: checking compiler /usr/local/bin/gcc -O2 -fomit-frame-
pointer
Test compile:
configure:4511: /usr/local/bin/gcc -O2 -fomit-frame-pointer
brandon.bar...@gmail.com wrote:
I did try setting LD_LIBRARY_PATH but this resulted in the same
problem. I even tried temporarily changing the ld.config search order
with crle (the solaris cousin of the linux ldconfig) from:
/lib:/usr/lib:/usr/local/lib
to:
/usr/local/lib:/lib:/usr/lib
2009/8/4 Simon King simon.k...@nuigalway.ie:
Your implication that ECL should note the error and then continue to
compile somehow reminds a recent thread (probably on sage-devel)
where it was reported that some spkg sends compiler warnings to /dev/
null.
Yes it was in sage-devel. I raised
On Tue, Aug 4, 2009 at 1:06 AM, David Kirkbydavid.kir...@onetel.net wrote:
2009/8/4 Simon King simon.k...@nuigalway.ie:
Your implication that ECL should note the error and then continue to
compile somehow reminds a recent thread (probably on sage-devel)
where it was reported that some spkg
I think my current gcc toolchain may be doomed, as it uses the sun
linker and the gnu assembler! (I read this was a good thing to do, at
least at some point in history).
Configured with: ../gcc-4.4.0/configure --prefix=/usr/local --enable-
shared --disable-static --disable-libtool-lock
Well, I didn't have any trouble with MPIR in 4.1.1.rc0!
bash-3.2$ ls spkg/installed/
bzip2-1.0.5 conway_polynomials-0.2
dir-0.1 mpir-1.2.p4
prereq-0.3 sage_scripts-4.1.1.rc0
But it looks like termcap is having linker problems - I'll try using
gnu ld/as
Actually this seems to be an issue with it trying to link to the
system mpfr. Shouldn't sage built its own mpfr?
On Aug 4, 9:01 pm, brandon.bar...@gmail.com
brandon.bar...@gmail.com wrote:
Well, I didn't have any trouble with MPIR in 4.1.1.rc0!
bash-3.2$ ls spkg/installed/
bzip2-1.0.5
Dr. David Kirkby wrote:
I need some guidance on what do about some issues we have. I'll
summarise, since not everyone is going to be aware of them.
1) Sage will not build on Solaris SPARC due to issues in the latest
official ecl. (It is not the only issue, but is one of them).
2) The
On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkbydavid.kir...@onetel.net wrote:
I need some guidance on what do about some issues we have. I'll
summarise, since not everyone is going to be aware of them.
1) Sage will not build on Solaris SPARC due to issues in the latest
official ecl. (It is
On Mon, Aug 3, 2009 at 6:18 AM, David Joynerwdjoy...@gmail.com wrote:
On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkbydavid.kir...@onetel.net
wrote:
I need some guidance on what do about some issues we have. I'll
summarise, since not everyone is going to be aware of them.
1) Sage will
William Stein wrote:
On Mon, Aug 3, 2009 at 6:18 AM, David Joynerwdjoy...@gmail.com wrote:
On Mon, Aug 3, 2009 at 7:38 AM, Dr. David Kirkbydavid.kir...@onetel.net
wrote:
I need some guidance on what do about some issues we have. I'll
summarise, since not everyone is going to be aware of
William Stein wrote:
+1 Make packages so that everything works, but don't include them in
sage-4.1.1. When will the next Maxima come out? Maybe that's for
sage-4.2 or sage-4.1.2?
I'm on the verge of making the Maxima 5.19 release branch
(today or tomorrow). I'll try the patches from
Robert Dodier wrote:
William Stein wrote:
+1 Make packages so that everything works, but don't include them in
sage-4.1.1. When will the next Maxima come out? Maybe that's for
sage-4.2 or sage-4.1.2?
I'm on the verge of making the Maxima 5.19 release branch
(today or tomorrow).
On Aug 3, 8:56 am, Dr. David Kirkby david.kir...@onetel.net wrote:
So we can expect 5.19 sometime in August, is that correct? Any rough
idea when it might be - first half/second half of the month?
I'll start turning out releases on the 5.19 branch -- 5.19.0,
5.19.1, etc. Usually the branch
Robert Dodier wrote:
On Aug 3, 8:56 am, Dr. David Kirkby david.kir...@onetel.net wrote:
So we can expect 5.19 sometime in August, is that correct? Any rough
idea when it might be - first half/second half of the month?
I'll start turning out releases on the 5.19 branch -- 5.19.0,
5.19.1,
I look forward to testing and building it on opensolaris / intel.
On Aug 3, 4:21 pm, Dr. David Kirkby david.kir...@onetel.net wrote:
Robert Dodier wrote:
On Aug 3, 8:56 am, Dr. David Kirkby david.kir...@onetel.net wrote:
So we can expect 5.19 sometime in August, is that correct? Any
2009/8/3 brandon.bar...@gmail.com brandon.bar...@gmail.com:
I look forward to testing and building it on opensolaris / intel.
Give Sage a try on OpenSolaris and let me know what happens. I posted
ealier today some notes on what I needed to do to get it build on
SPARC. OpenSolaris might be a
I think it is worth pointing out that
(a) The bug found is a static typing error in which a program which,
in some circumstance, would do a list operation on
an argument which is an integer.
(b) This line of code in Maxima has probably been there for 35 years,
and so far as anyone knows, that
Your implication that ECL should note the error and then continue to
compile somehow reminds a recent thread (probably on sage-devel)
where it was reported that some spkg sends compiler warnings to /dev/
null.
Unless you can *prove* that the special circumstance (static typing
error in which a
23 matches
Mail list logo
