Source archive for sage-4.7.rc1:
http://boxen.math.washington.edu/home/release/sage-4.7.rc1/sage-4.7.rc1.tar
Thanks,
Jeroen.
Doug
> On 2011-05-02 00:06, François wrote:
> > it failed here but I have a somewhat older gcc:
> Yes, I believe there are more recent gcc versions for your system, right?
I will see if gcc-4.0.1 from xcode 3.1.4 fared better when I get to work in
about 2 hours. If not I will have to switch to the 4.2 shipped with that
version of xcode. Unfortunately the switch has to be done manually.
I tried the gcc-4.2.1 from my prefix but that created numerous problems
at run time (between versions of freetype).
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
> same problem if I try building a standalone ecl, and if I use gcc
> 4.0.1, too.
> So this looks like the combination of OSX 10.5 and PPC that is not
> working here, nothing Sage-specific.
>
> Dima
>
> On May 4, 3:47 pm, Dima Pasechnik <dimp...@gmail.com> wrote:
> > On MacOSX 10.5.8 (PPC G4) I cannot proceed past ecl.
> > I get crashes (sort or random) after bare.lsp is loaded,
> > ie after the log lines
> > ;;; About to load cmp/load.lsp
> > ;;;
> > ;;; Now we are in shape to do something useful.
> > ;;; End of bare.lsp
> >
Darn, I wish I still had my G4, this is familiar. Can you post the whole
log?
Francois
> On May 4, 8:43 pm, Francois Bissey <francois.bis...@canterbury.ac.nz>
>
> wrote:
> > > same problem if I try building a standalone ecl, and if I use gcc
> > > 4.0.1, too.
> > > So this looks like the combination of OSX 10.5 and PPC that is not
> > > working here, nothing Sage-specific.
> > >
> > > Dima
> > >
> > > On May 4, 3:47 pm, Dima Pasechnik <dimp...@gmail.com> wrote:
> > > > On MacOSX 10.5.8 (PPC G4) I cannot proceed past ecl.
> > > > I get crashes (sort or random) after bare.lsp is loaded,
> > > > ie after the log lines
> > > > ;;; About to load cmp/load.lsp
> > > > ;;;
> > > > ;;; Now we are in shape to do something useful.
> > > > ;;; End of bare.lsp
> >
> > Darn, I wish I still had my G4, this is familiar. Can you post the whole
> > log?
>
> please see http://www1.spms.ntu.edu.sg/~dima/tmp/ppc_ecl_problem_4.7.rc1.gz
> (there are repeated tries to restart the build at the end, sorry...)
>
> there are strange messages about sse there, e.g.
> Unknown symbol: ext::sse-pack-as-elt-type
>
> Unknown symbol: ext::sse-pack
>
> Does it misconfigure? (it's has no SSE support, this machine)
>
The sse messages are not abnormal. I get them on a amd64 machine which has sse
instructions. I know for a fact that ecl has an allergy too altivec
instructions that results in that kind of stuff but it isn't in your CFLAGS,
unless it has been forced down inside gcc. See
http://bugs.gentoo.org/show_bug.cgi?id=308909
in particular the log with gcc-4.3.4.
So could you try to resume the build with:
CFLAGS="-mno-altivec -mabi=no-altivec" make
I am hoping that these options are as valid for ppc-macos as they
are for ppc-linux.
You didn't have any problem with previous ecl did you?
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
First time I see that one. Never dealt with G5 I am afraid and you are using
10.4.11 too, do you have a more recent gcc available? singular does a number
of things between static and dynamic libraries that requires special care, you
may need an extra flag as well.
Could you drop the complete build log for singular somewhere?
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
Something I should add here. When I had my ppc machine and was
extending support to Gentoo linux-ppc I also needed to add these
flags to the compilation of ecl.pyx inside sage itself. Otherwise you hit the
same wall.
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
This is #11278 (needs_review).
Apart from the build breaking? If you don't need anything else that's all
good. I faintly remember that I had the same kind of error as in
http://bugs.gentoo.org/attachment.cgi?id=223091
which may be because when adding -maltivec -mabi=altivec gcc4.4+
doesn't seem to want to do -std=c99 by default or something along
these lines. Just adding -std=c99 probably would have enabled the compilation.
Let's see if the test in sage/libs/ecl.pyx pass, if not we may know where
there is a miscompilation problem. But with my memory coming back I think
it may only be affecting later version of gcc.
Francois
This is an old (and known) problem on Mac OS X 10.4 systems.
Make that old ppc systems. My old G4 running linux had the same kind of
problems. pari was running out of memory too.
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
My G4 was only clocking at 800MHz if I remember correctly it probably
had something to do with it.
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.