Users of older OS X versions (< 10.6): please test

34 views
Skip to first unread message

Jeroen Demeyer

unread,
May 1, 2011, 6:01:45 AM5/1/11
to sage-devel
It would be useful if everybody who is running OS X 10.5 or older could
report whether sage-4.7.rc1 builds and passes doctests. Be sure to
mention your gcc version (output of gcc --version), OS X version and
whether you have an Intel or PPC processor.

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.

François

unread,
May 1, 2011, 6:06:54 PM5/1/11
to sage-devel
> Source archive for sage-4.7.rc1:http://boxen.math.washington.edu/home/release/sage-4.7.rc1/sage-4.7.r...
>
Hi,

it failed here but I have a somewhat older gcc:
gcc --version
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

The failure is:

g++ -o groebner/src/polynomial_properties.os -c -O3 -Wno-long-long -
Wreturn-type -g -fPIC -ftemplate-depth-100 -O3 -Wno-long-long -Wreturn-
type -g -fPIC -fPIC -fvisibility=hidden -DNDEBUG -DHAVE_GD -
DHAVE_HASH_MAP -DPACKED -DHAVE_M4RI -DHAVE_GD -DHAVE_IEEE_754 -I/Users/
frb15/Desktop/sage-4.7.rc1/local/include -I/Users/frb15/Desktop/
sage-4.7.rc1/local/include/python2.6 -Ipolybori/include -ICudd/obj -
ICudd/util -ICudd/cudd -ICudd/mtr -ICudd/st -ICudd/epd groebner/src/
polynomial_properties.cc
In file included from polybori/include/order_tags.h:16,
from polybori/include/pbori_tags.h:17,
from polybori/include/COrderingTags.h:21,
from polybori/include/CStackSelector.h:28,
from polybori/include/COrderedIter.h:27,
from polybori/include/COrderingBase.h:22,
from polybori/include/COrderingFacade.h:23,
from polybori/include/DegLexOrder.h:20,
from polybori/include/pbori_order.h:26,
from polybori/include/polybori.h:33,
from groebner/src/groebner_defs.h:10,
from groebner/src/polynomial_properties.cc:7:
polybori/include/pbori_defs.h:1: internal compiler error: Segmentation
fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://developer.apple.com/bugreporter> for instructions.
scons: *** [groebner/src/polynomial_properties.os] Error 1
scons: building terminated because of errors.
Error building PolyBoRi.

real 3m28.244s
user 3m3.461s
sys 0m18.471s
sage: An error occurred while installing polybori-0.7.0.p2

François

unread,
May 1, 2011, 6:10:51 PM5/1/11
to sage-devel


On May 2, 10:06 am, François <francois.bis...@canterbury.ac.nz> wrote:
> On May 1, 10:01 pm, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:> It would be useful if everybody who is running OS X 10.5 or older could
> > report whether sage-4.7.rc1 builds and passes doctests.  Be sure to
> > mention your gcc version (output of gcc --version), OS X version and
> > whether you have an Intel or PPC processor.
>
> > Source archive for sage-4.7.rc1:http://boxen.math.washington.edu/home/release/sage-4.7.rc1/sage-4.7.r...
>
> Hi,
>
> it failed here.

Forgot to say 10.5.8, intel core2 duo. XCode 3.0

D. S. McNeil

unread,
May 2, 2011, 12:22:35 AM5/2/11
to sage-...@googlegroups.com
Build succeeded and passed testall long for me on 10.5.8, xcode 3
(921.0/893.0), i686-apple-darwin9-gcc-4.0.1/i686-apple-darwin9-g++-4.0.1.
Quad-Core Intel Xeon.


Doug

Jeroen Demeyer

unread,
May 2, 2011, 4:00:50 AM5/2/11
to sage-...@googlegroups.com
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?

Francois Bissey

unread,
May 2, 2011, 3:21:51 PM5/2/11
to sage-...@googlegroups.com

> 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.

François

unread,
May 2, 2011, 5:48:55 PM5/2/11
to sage-devel
On May 3, 7:21 am, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:
> > 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).
>
4.0.1 is definitely a no go on this machine. Switched to 4.2.1

François

unread,
May 2, 2011, 9:46:07 PM5/2/11
to sage-devel
All clear with gcc-4.2.1 from xcode-3.1.4 on this machine.
All long tests passed.

Dima Pasechnik

unread,
May 4, 2011, 3:47:50 AM5/4/11
to sage-devel
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

it can be:

Internal or unrecoverable error in:
not a lisp data object
[2: No such file or directory]

or

Detected access to an invalid or protected memory address.
Available restarts:

1. (CONTINUE) Ignore signal

or

64 is an illegal index to "Variable in COMMON-LISP package:
The last-but-one top-level forme".
No restarts available.

-------------------------------------------------

the combination of OS/hardware is very unusual, as not many people
upgraded their PPC machines
to 10.5 (I only did this as the HD died, and the only install DVD of
OSX I was
able to get was a 10.5 one)

$ gcc -v
Using built-in specs.
Target: powerpc-apple-darwin9
Configured with: /var/tmp/gcc_42/gcc_42-5577~1/src/configure --disable-
checking --prefix=/usr --mandir=/usr/share/man --enable-
languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/
$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin9 --with-gxx-
include-dir=/usr/include/c++/4.0.0 --program-prefix= --host=powerpc-
apple-darwin9 --target=powerpc-apple-darwin9
Thread model: posix
gcc version 4.2.1 (Apple Inc. build 5577)

$ xcodebuild -version
Xcode 3.1.4
Component versions: DevToolsCore-1204.0; DevToolsSupport-1186.0
BuildVersion: 9M2809

This is the latest Xcode for PPC machines.
(I can also try using gcc 4.0.1, but this might be even worse...)

Dima
> Source archive for sage-4.7.rc1:http://boxen.math.washington.edu/home/release/sage-4.7.rc1/sage-4.7.r...
>
> Thanks,
> Jeroen.

Dima Pasechnik

unread,
May 4, 2011, 4:15:30 AM5/4/11
to sage-devel
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

Francois Bissey

unread,
May 4, 2011, 8:43:00 AM5/4/11
to sage-...@googlegroups.com

> 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

Dima Pasechnik

unread,
May 4, 2011, 9:44:13 AM5/4/11
to sage-devel


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)

Dima Pasechnik

unread,
May 4, 2011, 2:13:49 PM5/4/11
to sage-devel
and this is a log from an older post (on Sage-4.7.alpha3) exhibiting
the same problem:

http://www.google.com/url?sa=D&q=http://boxen.math.washington.edu/home/dima/tmp/sage4.7.aplha3.MacOSX.PPC.install.log.gz

On May 4, 8:43 pm, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:

Francois Bissey

unread,
May 4, 2011, 6:35:11 PM5/4/11
to sage-...@googlegroups.com

> 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.

Dima Pasechnik

unread,
May 5, 2011, 1:09:04 AM5/5/11
to sage-devel


On May 5, 6:35 am, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:
> > 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 seehttp://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. Seehttp://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.

Indeed, this helps! Although the CFLAGS should be passed to configure.
(just 'CFLAGS="-mno-altivec -mabi=no-altivec" make' does not pass
CFLAGS anywhere!)
This is now trac #11297

> You didn't have any problem with previous ecl did you?

No. (Sage 4.6 builds and works on this machine)

Jean-Pierre Flori

unread,
May 5, 2011, 4:44:14 AM5/5/11
to sage-devel
I get the followig failure while building Sage:
g++ -O2 -g -fPIC -pipe -fno-implicit-templates -I. -I../kernel -I/
Users/Shared/sage/sage-4.7.rc1/local/include -I/Users/Shared/sage/
sage-4.7.rc1/local/include -I/Users/Shared/sage/sage-4.7.rc1/local/
include -DNDEBUG -DOM_NDEBUG -DppcMac_darwin -DHAVE_CONFIG_H -c
mpsr_Tok.cc
libtool -dynamic -twolevel_namespace -weak_reference_mismatches weak -
undefined dynamic_lookup -single_module -o libsingular.dylib \
libsingular-tesths.o iparith.o mpsr_Tok.o claptmpl.o \
grammar.o scanner.o attrib.o eigenval_ip.o extra.o fehelp.o feOpt.o
ipassign.o ipconv.o ipid.o iplib.o ipprint.o ipshell.o lists.o sdb.o
fglm.o interpolation.o silink.o subexpr.o janet.o wrapper.o libparse.o
sing_win.o gms.o pcv.o maps_ip.o walk.o walk_ip.o cntrlc.o misc_ip.o
calcSVD.o Minor.o MinorProcessor.o MinorInterface.o slInit_Static.o
mpsr_Put.o mpsr_PutPoly.o mpsr_GetPoly.o mpsr_sl.o mpsr_Get.o
mpsr_GetMisc.o mpsr_Error.o ndbm.o sing_dbm.o -lkernel -L../kernel -
L../factory -L../libfac -L/Users/Shared/sage/sage-4.7.rc1/local/lib -
lsingfac -lsingcf -lntl -lreadline -lgmp -lomalloc
ld: for architecture ppc
ld: ../kernel/libkernel.a(matpol.o) has external relocation entries in
non-writable section (__TEXT,__text) for symbols:
restFP
saveFP
libtool: internal link edit command failed
make[3]: *** [libsingular] Error 1
make[2]: *** [libsingular] Error 2
Unable to build Singular.

real 8m16.136s
user 6m40.147s
sys 1m14.908s
sage: An error occurred while installing singular-3-1-1-4.p8

Here are the machine details:

Machine Name: Power Mac G5
Machine Model: PowerMac11,2
CPU Type: PowerPC G5 (1.1)
Number Of CPUs: 2
CPU Speed: 2.3 GHz

System Version: Mac OS X 10.4.11 (8S165)
Kernel Version: Darwin 8.11.0

XCode 2.4.1
Component versions
Xcode IDE: 762.0
Xcode Core: 762.0
ToolSupport: 764.0

gcc --version
powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.
build 5367)

Francois Bissey

unread,
May 5, 2011, 5:37:15 AM5/5/11
to sage-...@googlegroups.com

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.

Francois Bissey

unread,
May 5, 2011, 5:44:10 AM5/5/11
to sage-...@googlegroups.com

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.

Jean-Pierre Flori

unread,
May 5, 2011, 5:50:52 AM5/5/11
to sage-devel
I do not have the admin password on that computer currently, so I
fear I won't be able to install a newer version of XCode.
IIRC I built Sage 4.6.something on the same computer without (oo
much ?) trouble when I ran some tests for pynac.
You can find the full log at http://perso.telecom-paristech.fr/~flori/sage/singular-3-1-1-4.p8.log

Jeroen Demeyer

unread,
May 5, 2011, 6:01:58 AM5/5/11
to sage-...@googlegroups.com
On 2011-05-05 11:37, Francois Bissey wrote:
>> ld: for architecture ppc
>> ld: ../kernel/libkernel.a(matpol.o) has external relocation entries in
>> non-writable section (__TEXT,__text) for symbols:
>> restFP
>> saveFP
>> libtool: internal link edit command failed
>> make[3]: *** [libsingular] Error 1
>> make[2]: *** [libsingular] Error 2
>> Unable to build Singular.

This is #11278 (needs_review).

Jean-Pierre Flori

unread,
May 5, 2011, 6:18:42 AM5/5/11
to sage-devel
On 5 mai, 12:01, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> This is #11278 (needs_review).
Thanks for pointing that out, I'll have a look at it.

Dima Pasechnik

unread,
May 5, 2011, 11:32:12 PM5/5/11
to sage-devel


On May 5, 5:44 pm, Francois Bissey <francois.bis...@canterbury.ac.nz>
> > > Seehttp://bugs.gentoo.org/show_bug.cgi?id=308909in 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.
>
> > Indeed, this helps! Although the CFLAGS should be passed to configure.
> > (just 'CFLAGS="-mno-altivec -mabi=no-altivec" make' does not pass
> > CFLAGS anywhere!)
> > This is now trac #11297
>
> > > You didn't have any problem with previous ecl did you?
>
> > No. (Sage 4.6 builds and works on this machine)
>
> 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.
>

didn't seem to be needing this.
What were the symptoms at your 2nd wall?

The build has finished with only the patch from trac #11297
applied, running tests now.

Dmitrii


> Francois

Francois Bissey

unread,
May 5, 2011, 11:45:31 PM5/5/11
to sage-...@googlegroups.com

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

Dima Pasechnik

unread,
May 6, 2011, 1:08:36 AM5/6/11
to sage-devel


On May 6, 11:45 am, Francois Bissey <francois.bis...@canterbury.ac.nz>
> > > > > Seehttp://bugs.gentoo.org/show_bug.cgi?id=308909inparticular 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.
>
> > > > Indeed, this helps! Although the CFLAGS should be passed to configure.
> > > > (just 'CFLAGS="-mno-altivec -mabi=no-altivec" make' does not pass
> > > > CFLAGS anywhere!)
> > > > This is now trac #11297
>
> > > > > You didn't have any problem with previous ecl did you?
>
> > > > No. (Sage 4.6 builds and works on this machine)
>
> > > 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.
>
> > didn't seem to be needing this.
> > What were the symptoms at your  2nd wall?
>
> > The build has finished with only the patch from trac #11297
> > applied, running tests now.
>
> 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 inhttp://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,

yes, it passes just fine.

Dima Pasechnik

unread,
May 6, 2011, 6:50:08 AM5/6/11
to sage-devel
OK, so on my OSX 10.5 PPC "make test" passed without errors, after I
applied #11297.
> > > > Seehttp://bugs.gentoo.org/show_bug.cgi?id=308909inparticular the log

Jean-Pierre Flori

unread,
May 10, 2011, 4:53:48 AM5/10/11
to sage-devel
On 5 mai, 12:18, Jean-Pierre Flori <jpfl...@gmail.com> wrote:
> On 5 mai, 12:01, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:> This is #11278 (needs_review).
>
> Thanks for pointing that out, I'll have a look at it.

I was able to build Sage with #11278 applied, but when I ran make
ptestlong I got timeouts for sage/interface/expect.py and sage/
interface/maxima.py
Running expect.py again alone passed, but maxima.py timed out each
time.

Jeroen Demeyer

unread,
May 10, 2011, 8:21:24 AM5/10/11
to sage-...@googlegroups.com

This is an old (and known) problem on Mac OS X 10.4 systems.

Francois Bissey

unread,
May 10, 2011, 8:30:09 AM5/10/11
to sage-...@googlegroups.com

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.

kcrisman

unread,
May 10, 2011, 12:11:40 PM5/10/11
to sage-devel

> > > Running expect.py again alone passed, but maxima.py timed out each
> > > time.
>
> > 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.
>

Interesting. Georg Weber had this problem on his Intel OS X 10.4
system as well, though I believe for some reason that one now passes
this test.

(The test that hangs is the one that checks tab-completion in Maxima
works, by the way, in case that leads someone to a fix.)

- kcrisman

Dima Pasechnik

unread,
May 10, 2011, 9:26:58 PM5/10/11
to sage-devel


On May 10, 8:30 pm, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:
> > On 2011-05-10 10:53, Jean-Pierre Flori wrote:
> > > On 5 mai, 12:18, Jean-Pierre Flori <jpfl...@gmail.com> wrote:
> > >> On 5 mai, 12:01, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:> This is
> > >> #11278 (needs_review).
>
> > >> Thanks for pointing that out, I'll have a look at it.
>
> > > I was able to build Sage with #11278 applied, but when I ran make
> > > ptestlong I got timeouts for sage/interface/expect.py and sage/
> > > interface/maxima.py
> > > Running expect.py again alone passed, but maxima.py timed out each
> > > time.
>
> > 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.

I don't know how old it has to be, but with
Model Name: PowerBook G4 17"
Model Identifier: PowerBook5,5
Processor Name: PowerPC G4 (1.1)
Processor Speed: 1.5 GHz
Number Of CPUs: 1
L2 Cache (per CPU): 512 KB
Memory: 1.5 GB
Bus Speed: 167 MHz
Boot ROM Version: 4.8.6f0

I don't see these problems (although I run 10.5, not 10.4)

Francois Bissey

unread,
May 10, 2011, 9:40:50 PM5/10/11
to sage-...@googlegroups.com

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.

kcrisman

unread,
May 10, 2011, 10:24:18 PM5/10/11
to sage-devel

> > > 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.
>
> I don't know how old it has to be, but with

> I don't see these problems (although I run 10.5, not 10.4)

It was always 10.4 only, for whatever reason. It even happened on my
1.25 GHz one with 1 GB memory, so it wasn't that that was the problem,
as far as I could tell.
Reply all
Reply to author
Forward
0 new messages