Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

[Jaap Spies]

Dima,
The word "G..v..d...e" is the worst curse in the Dutch language. The first
three letters needs no translation. The rest translates to 'damn'. You
shouldn't use it lightly.

Jaap


Op wo 26 apr. 2023 21:20 schreef Dima Pasechnik :

> On Wed, Apr 26, 2023 at 8:18 PM Matthias Koeppe
>  wrote:
> >
> > On Wednesday, April 26, 2023 at 12:14:26 PM UTC-7 Dima Pasechnik wrote:
> >
> > This discussion happened 2 years ago
> >
> >
> > That's correct, and you have not brought forward any new points.
>
> Godverdomme, this was about GFORTRAN!!!
> WE ARE TAKLKING ABOUT PYTHON!!! PYTHON!!!
>
> Learn to read.
>
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-devel+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/27c5cb9d-76da-48d8-a7e9-defa8453a6cen%40googlegroups.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0xPZf6Mt10BQFOxcbfepEPN1f8O9bCfiYr-_h402Oh5A%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAK0%3DbK187m0-m5s%3D%3DKyRKpH3QifcyZRU2LxZUWDvNAjjzWRo8A%40mail.gmail.com.

Re: [sage-devel] VOTE: move Sage development to Github

[Jaap Spies]

+1 for Github

Op wo 21 sep. 2022 19:23 schreef David Roe :

> Dear Sage developers,
> Following extensive discussion, both recently
>  
> (prompted
> by issues upgrading the trac server) and over
>  the
>  last
> 
> decade
> , we
> are calling a vote on switching Sage development from Trac
>  to Github .  We've
> created a summary of the pros and cons of each system
> , a 
> description
> of the development model to be used on github
> ,
> and a trac ticket  for
> coordinating work on the transition.  More work will need to be done to
> carry out the actual transition once voting is complete.
>
> The voting will last until noon Eastern time (16:00 UTC) on Wednesday,
> October 5.  Please use this thread only for sending votes, to make it
> easier to count them afterward; there is a parallel thread where you can
> make arguments in favor of either system.
>
> Finally, I will close with a plea to be involved in this vote and
> discussion even if you are not a core Sage developer.  By definition, core
> Sage developers have become comfortable with trac, and I think that one of
> the major arguments in favor of github is that it will help bring in new
> contributors who are not familiar with Sage's development workfow
> .  Anyone who has
> ever contributed to the Sage code base or who maintains a Sage user package
> is welcome to vote.
> David
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAChs6_%3DyvZ869L66E1tFmziWDirbawSEABf_uc_j9Dy8VBFW8w%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAK0%3DbK2ThW_Sf0_uk8J9ukdAgoLWBDrqYAcskXZ9ywM867pFfw%40mail.gmail.com.

[sage-devel] Re: Reviving the Annual SageMath Development Prize

[Jaap Spies]

Excellent idea! For me it was good in the early years of sage to contribute 
some code and
give some financial support in the form of the Spies Prize. I'm not in the 
position now to lineup
as a donor, but I probably will for the 2022 version. 

Best regards,

Jaap Spies

On Wednesday, April 13, 2022 at 7:15:29 AM UTC+2 wst...@gmail.com wrote:

> Hi sage-devel,
>
> We (Matthias Koeppe and William Stein) would like to propose that we
> revive the Annual SageMath Development Prize, which was awarded in
> the years 2008–2014 thanks to
> donations from Jaap Spies (a retired Dutch mathematician) – see
> https://www.sagemath.org/development-prize.html
>
> To catch up, it would make sense to retroactively award one prize for
> each of the years 2015–2021. I’m sure that there would be plenty of
> deserving candidates for the prize for each year. There is no specific
> donor for the prize money lined up, but from a look at our Open
> Collective account balance, I (William) would feel very comfortable
> with $250/person using the funds already at hand.
>
> Continuing the tradition of the prize, the goal is to acknowledge the
> work done by the recipient and to encourage them to continue to do
> excellent development or community work on SageMath, so it would make
> sense for these retroactively awarded prizes to go developers or
> community leaders who are still at least somewhat active in the
> project today.
>
> We would ask for 3 or 4 volunteers to form a prize committee that
> would be tasked to come up with a list of 7 names. (Anybody
> volunteering to be on the committee is recusing themselves from
> consideration for the prizes for 2015–2021.)
>
> Best regards,
>
> Matthias Koeppe & William Stein
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3d36bc9f-8deb-45fb-93c4-951130fa80ddn%40googlegroups.com.

[sage-devel] **WARNING** /var/cache/sympow/datafiles/le64 yields insufficient permissions

[Jaap Spies]

On Fedora 34 on an i7 running ptestlong I get some failures all related to 
subject.
Never seen this before. A chmod 0777 /var/cache/sympow/datafiles/le64
'solved' the problem, but is it a solution?



[jaap@vrede sage-9.4]$ ./sage -t --long --warn-long 129.3 --random-seed=0 
src/sage/modular/abvar/abvar.py 
Running doctests with ID 2021-08-28-22-28-00-c0990165. 
Git branch: develop 
Using --optional=build,dochtml,fedora,pip,sage,sage_spkg 
Doctesting 1 file. 
sage -t --long --warn-long 129.3 --random-seed=0 
src/sage/modular/abvar/abvar.py 
** 
File "src/sage/modular/abvar/abvar.py", line 3758, in 
sage.modular.abvar.abvar.ModularAbelianVariety_abstract.dual 
Failed example: 
E.modular_degree() 
Expected: 
3 
Got: 
**WARNING** /var/cache/sympow/datafiles/le64 yields insufficient 
permissions 
3 
** 
1 item had failures: 
   1 of  13 in sage.modular.abvar.abvar.ModularAbelianVariety_abstract.dual 
[640 tests, 1 failure, 8.71 s] 
-- 
sage -t --long --warn-long 129.3 --random-seed=0 
src/sage/modular/abvar/abvar.py  # 1 doctest failed 


Cheers,
Jaap Spies

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/117b265b-93fb-4d16-82d2-8d06b4751a34n%40googlegroups.com.

Re: [sage-devel] Making Sagemath available to Raspberry Pi

[Jaap Spies]

On Sunday, July 12, 2020 at 11:21:15 PM UTC+2, Jaap Spies wrote:
>
> Instructions: Go to https://www.raspberrypi.org/downloads/
> Download your Pi Imager if you want.
> I use BalenaEtcher on an old windows loaptop with card reader.
> I could also use another Raspbery Pi with USB card reader to dd the image 
> to the SD card.
> My main machine has no card reader at all.
>
> So you need a card reader to write the image.
>
> Download the Raspberry Pi OS, previously called Raspbian: choose "with 
> desktop and recommended software"
> There is working underway to release a 64-bit version, but not yet 
> available.
>
> Your SD card is at least 64 GB one. I prefer SanDisk Ultra microSDHC UHS
> You want space for several versions of sagemath!
> dd or etch, flash or whatever you choose the image to the SD card.
>
> Prepare your Raspberry Pi. Have a powersupply of at least 3A, better 4A.
> For best experience connect a monitor or TV with a micro HDMI to HDMI 
> cable.
> Choose HDMI-1 the connector next to the power supply.
> An USB keyboard and mouse.
> Connect ethernet.
>
> Put the power on. The system will boot. Click on the Raspberry, select 
> Preferences -> Raspberry Pi Configuration
> Choose hostname and change the password.
> In the label Interfaces enable SSH and VNC
>
> Open Chromium, go to the download pages of sagemath, make your pick.
> Make a directory /home/pi/sagemath
> cd to it
> mv or cp /home/Downloads/sage-9.2.beta5.gz .
> tar xvf sage-9.2.whatever
> cd sage-..
>
> etcetera
>
>
>
 For serious work my advise is to use an ssd. The latest RP4's allow 
booting from USB.
On my older system I have to do a trick: booting from SD card and run the 
system from / (root)
on the ssd. This faster and safer.

Some suppliers have integrated systems available: My home supplier: 
https://www.freva.com/our-shop/
https://www.freva.com/product/raspberry-pi-4b-with-120-gb-ssd-starter-kit/

Jaap


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d5da5d81-f1a9-4eb8-bf18-30db99a4d816o%40googlegroups.com.

Re: [sage-devel] Making Sagemath available to Raspberry Pi

[Jaap Spies]

On Tuesday, July 14, 2020 at 1:06:58 AM UTC+2, Dima Pasechnik wrote:
>
> There is an official Rasbrian package for Sage, sagemath, it gives you 
> Sage 8.6. 
>
> I suppose it's the result of semi-automatic import of Debian Buster 
> into Rasbrian. 
>
> I did 
>
> pi@raspberrypi:~ $ sudo apt install sagemath 
>
> and after a long download, I could do 
>
> pi@raspberrypi:~ $ sage 
> ┌┐ 
> │ SageMath version 8.6, Release Date: 2019-01-15 │ 
> │ Using Python 2.7.16. Type "help()" for help.   │ 
> └┘ 
> Setting permissions of DOT_SAGE directory so only you can read and write 
> it. 
> sage: 
> Exiting Sage (CPU time 0m0.12s, Wall time 0m9.49s). 
>
>
> Naturally one wants newer versions, but still this is a start. 
>
> pi@rasp4g:~/sagemath/sage-9.2.beta4 $ ./sage
┌┐
│ SageMath version 9.2.beta4, Release Date: 2020-07-08   │
│ Using Python 3.7.3. Type "help()" for help.│
└┘
┏┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗┛
sage: 

It would be great to get it in debian and raspbian!


 

> Dima 
>
> On Fri, Jul 10, 2020 at 12:01 PM Jaap Spies  > wrote: 
> > 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/847712ee-1213-4ea6-9dcf-1d483e6a90d4o%40googlegroups.com.

Re: [sage-devel] Making Sagemath available to Raspberry Pi

[Jaap Spies]

Instructions: Go to https://www.raspberrypi.org/downloads/
Download your Pi Imager if you want.
I use BalenaEtcher on an old windows loaptop with card reader.
I could also use another Raspbery Pi with USB card reader to dd the image 
to the SD card.
My main machine has no card reader at all.

So you need a card reader to write the image.

Download the Raspberry Pi OS, previously called Raspbian: choose "with 
desktop and recommended software"
There is working underway to release a 64-bit version, but not yet 
available.

Your SD card is at least 64 GB one. I prefer SanDisk Ultra microSDHC UHS
You want space for several versions of sagemath!
dd or etch, flash or whatever you choose the image to the SD card.

Prepare your Raspberry Pi. Have a powersupply of at least 3A, better 4A.
For best experience connect a monitor or TV with a micro HDMI to HDMI cable.
Choose HDMI-1 the connector next to the power supply.
An USB keyboard and mouse.
Connect ethernet.

Put the power on. The system will boot. Click on the Raspberry, select 
Preferences -> Raspberry Pi Configuration
Choose hostname and change the password.
In the label Interfaces enable SSH and VNC

Open Chromium, go to the download pages of sagemath, make your pick.
Make a directory /home/pi/sagemath
cd to it
mv or cp /home/Downloads/sage-9.2.beta5.gz .
tar xvf sage-9.2.whatever
cd sage-..

etcetera



>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6f8ba6c6-ba2e-4abe-bc4b-ee480607138bo%40googlegroups.com.

Re: [sage-devel] Making Sagemath available to Raspberry Pi

[Jaap Spies]

On Sunday, July 12, 2020 at 4:45:44 PM UTC+2, Dima Pasechnik wrote:
>
>
>
> On Sun, 12 Jul 2020, 13:27 Sverre Lunøe-Nielsen,  > wrote:
>
>> Dima, 
>>
>> > I would rather plug ethernet cable, and ssh into, but this seems to be 
>> unsupported.
>>
>> You can accomplish this by following the instructions under 
>> "3: Enable SSH on a headless Raspberry Pi (add file to SD card on another 
>> machine)" found here: 
>>
>> https://www.raspberrypi.org/documentation/remote-access/ssh/ 
>>
>
> thanks - however the headless install seems to require a modification of 
> the micro SD - something that needs a working reader - and for some reason 
> I can't get it to work on an old MacAir with an old adaptor.
>
> It looks like an oversight that by default it is not already shipped 
> prepared this way.
>
>
Since 2016 the Raspberry Pi Organisation disables sshon start up. Why? I 
don't know.
What is your configuration? What kind of SD card are you using. Is it 
preconfigured by your
supplier?



> Can Pi double up as a card reader?
>
>
No, only if you have it up and running you can use an USB cardreader.

Best
> Dima
>
>
>> Regards, 
>>
>> Sverre Lunøe-Nielsen 
>>
>> On Sunday, July 12, 2020 at 1:52:52 PM UTC+2, Dima Pasechnik wrote:
>>>
>>>
>>>
>>> On Fri, 10 Jul 2020, 12:03 Dima Pasechnik,  wrote:
>>>
>>>> On Fri, Jul 10, 2020 at 12:01 PM Jaap Spies  wrote:
>>>> >
>>>> > In a previous post I wrote:
>>>> >
>>>> > \begin quote
>>>> > Saying Raspberry Pi is saying education. There are zillion Raspberry 
>>>> Pi's out there.
>>>> > Almost all of them are running Raspbian, now called Raspberry Pi OS.
>>>> > On every raspbian system there is an implementation of Mathematica.
>>>> > Wolfram was clever when he decided to make Matematica available to the
>>>> > people of Raspberries.
>>>> >
>>>> > I did some experimentation out of an old book Mathematica Second 
>>>> Edition.
>>>> > You can really do some math on a Raspberry Pi 4.
>>>> > [snipped]
>>>> >
>>>> > I think it is of major importance to have at least a binary for 
>>>> Raspberry Pi OS!
>>>> >
>>>> > I'm old and have no time and no energy to pursue this to the end, but 
>>>> I plea
>>>> > someone would take this serious.
>>>> >
>>>> > Jaap
>>>> >
>>>> > early adapter of sage
>>>> > \end quote
>>>> >
>>>> > I wanted to start a discussion on the need to be present on the 
>>>> Raspberry Pi platform.
>>>> > But my intentions were buried under a lot of technicalities.
>>>> >
>>>> > SAGE was intended to by an opensource alternative for the big M's, 
>>>> among them Mathematica.
>>>> > What we see on the rasbian distribution:
>>>> > du:
>>>> > 32000 Wolfram/WolframEngine/12.0/AddOns/Applications
>>>> > 36244 Wolfram/WolframEngine/12.0/AddOns
>>>> > 1097480 Wolfram/WolframEngine/12.0
>>>> > 1097484 Wolfram/WolframEngine
>>>> > 1101392 Wolfram/
>>>> > root@rasp4g:/opt#
>>>> >
>>>> > You see Wolfram was very clever in getting Mathematica in raspbian: 
>>>> 1.1 GB of disk space
>>>> >
>>>> > We will never get that space in the official distro, but I plea to 
>>>> make Sagemath
>>>> > more available and known on the Raspberry Pi platform.
>>>> >
>>>> > There are a lot of computer labs in schools and colleges all running 
>>>> rasbian.
>>>> > And users easily link Math and Mathematics to Mathematica.
>>>> > Try Google Search: math Raspberry Pi of raspberry math
>>>> > and you will be overwhelmed by Wolfram's Mathematica
>>>> >
>>>> > Do a Google Search: raspberry pi sagemath
>>>> > and you see some pages from the year 2013 and a page of my website.
>>>> >
>>>> > The only thing we can do is to try getting Sagemath more visible.
>>>> > In documentation, on the website and make a binary available.
>>>>
>>>> I'm getting the latest Rasberry Pi with 8GB of RAM, we'll see how far
>>>> it will do.
>>>>
>>>
>>> I have it now

[sage-devel] Re: Making Sagemath available to Raspberry Pi

[Jaap Spies]

On Saturday, July 11, 2020 at 2:05:13 PM UTC+2, Jonathan wrote:
>
> Although this is a laudable goal, I think it is important to realize that 
> for many
> educational situations there is an alternative that is probably adequate:
> SymPy.
>
> SymPy does not have all the capabilities of Sagemath, but is one of the
> packages within Sagemath that provides most of the capabilities that are
> needed in a symbolic math/CAS system for educational purposes in most
> fields.
>
>
Yes sagemath is unifying all the package you want to use, among them surely 
SymPy.
 

> I think the key is to make the connection between Sagemath and SymPy
> capabilities obvious. Think of SymPy as a lightweight/introductory version
> of Sagemath.
>
>
You are missing my point. It is not what is individually needed. If you 
knew me you would
know my middle name is "permanent". I wrote same code in SAGE, I used some 
code on permanents. What else?
You can put that under a fingernail and it gets lost.

I want the name "sagemath" is known in Rasberry Pi circles next to the 
world wide presence of Wolfram's Mathematica.
Make experiments possible using sagemath. Publishing use cases of sagemath.
I would like to write article in MagPi, the official Raspberry Pi Magazine.
Therefor we need a binary distribution.
Since the end of last year I know you can build sagemath on Raspbian. There 
are
some errors in sage -ptestlong, most related to timeouts. But a port is 
nearby.

SymPy can easily be installed on a Raspberry Pi using pip. I have it 
> running on
> multiple Pi 3B+ and 4Bs.
>
> Regards,
> Jonathan
>
> On Friday, July 10, 2020 at 6:01:17 AM UTC-5 jaap... wrote:
>
>>
>> We will never get that space in the official distro, but I plea to make 
>> Sagemath 
>> more available and known on the Raspberry Pi platform.
>>
>>
>>
>> The only thing we can do is to try getting Sagemath more visible.
>> In documentation, on the website and make a binary available.
>> (William are you here?)
>>
>> Jaap Spies
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/35c05a61-b516-4cbe-af31-d81fcce6ee76o%40googlegroups.com.

[sage-devel] Making Sagemath available to Raspberry Pi

[Jaap Spies]

In a previous post I wrote:

\begin quote
Saying Raspberry Pi is saying education. There are zillion Raspberry Pi's 
out there.
Almost all of them are running Raspbian, now called Raspberry Pi OS.
On every raspbian system there is an implementation of Mathematica.
Wolfram was clever when he decided to make Matematica available to the
people of Raspberries.

I did some experimentation out of an old book Mathematica Second Edition.
You can really do some math on a Raspberry Pi 4.
[snipped]

I think it is of major importance to have at least a binary for Raspberry 
Pi OS!

I'm old and have no time and no energy to pursue this to the end, but I plea
someone would take this serious.

Jaap

early adapter of sage
\end quote

I wanted to start a discussion on the need to be present on the Raspberry 
Pi platform.
But my intentions were buried under a lot of technicalities.

SAGE was intended to by an opensource alternative for the big M's, among 
them Mathematica.
What we see on the rasbian distribution:
du:
32000 Wolfram/WolframEngine/12.0/AddOns/Applications
36244 Wolfram/WolframEngine/12.0/AddOns
1097480 Wolfram/WolframEngine/12.0
1097484 Wolfram/WolframEngine
1101392 Wolfram/
root@rasp4g:/opt# 

You see Wolfram was very clever in getting Mathematica in raspbian: 1.1 GB 
of disk space

We will never get that space in the official distro, but I plea to make 
Sagemath 
more available and known on the Raspberry Pi platform.

There are a lot of computer labs in schools and colleges all running 
rasbian.
And users easily link Math and Mathematics to Mathematica.
Try Google Search: math Raspberry Pi of raspberry math
and you will be overwhelmed by Wolfram's Mathematica

Do a Google Search: raspberry pi sagemath
and you see some pages from the year 2013 and a page of my website.

The only thing we can do is to try getting Sagemath more visible.
In documentation, on the website and make a binary available.
(William are you here?)

Jaap Spies

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/36e28475-07f7-4938-aaed-410526534b18o%40googlegroups.com.

Re: [sage-devel] Re: Porting sagemath to Raspberry Pi OS

[Jaap Spies]

Raspberry Pi OS is the new name of raspbian.
And indeed raspbian uses apt to deal with packages, but have their own 
repositories
based on debian


On Friday, July 10, 2020 at 11:22:30 AM UTC+2, Dima Pasechnik wrote:
>
> On Fri, Jul 10, 2020 at 10:11 AM Dima Pasechnik  > wrote: 
> > 
> > On Fri, Jul 10, 2020 at 9:08 AM Jaap Spies  > wrote: 
> > > 
> > > After this technicalities I reclaim my points: We need a port of 
> sagemath to Raspbery Pi OS. 
>
> As far as I see, it is 
> https://www.raspberrypi.org/downloads/raspberry-pi-desktop/ 
> (based on Debian Buster) - it uses apt to deal with packages, so the 
> setup we use on Debian/Ubuntu should 
> in principle be working. 
>
> Is this the OS you are referring to? 
>
> I don't know whether they try to import all the Debian packages, but 
> it looks as if Debian 
> effort to have Sage in Debian would be helpful here. 
>
> Thanks, 
> Dima 
>
> > > At least we need a binary of sagemath for Raspberry Pi OS. 
> > the binaries are made using 
> > https://github.com/sagemath/binary-pkg 
> > 
> > Could you try this on your Rasberry Pi? 
> > (probably nobody ever tested this on ARM, so YMMV). 
> > 
> > Dima 
> > > 
> > > Jaap Spies 
> > > 
> > > On Thursday, July 9, 2020 at 2:31:52 PM UTC+2, Jaap Spies wrote: 
> > >> 
> > >> Saying Raspberry Pi is saying education. There are zillion Raspberry 
> Pi's out there. 
> > >> Almost all of them are running Raspbian, now called Raspberry Pi OS. 
> > >> On every raspbian system there is an implementation of Mathematica. 
> > >> Wolfram was clever when he decided to make Matematica available to 
> the 
> > >> people of Raspberies. 
> > >> 
> > >> I did some experimentation out of an old book Mathematica Second 
> Edition. 
> > >> You can really do some math on a Raspberry Pi 4. 
> > >> 
> > >> Some time ago I could build sage-9.0 on my RPi4's, but now there are 
> problems 
> > >> with fplll. I opened a ticket, someone changed the priority to minor. 
> > >> 
> > >> I think it is of major importance to have at least a binary for 
> Raspberry Pi OS! 
> > >> 
> > >> I'm old and have no time and no energy to pursue this to the end, but 
> I plea 
> > >> someone would take this serious. 
> > >> 
> > >> Jaap 
> > >> 
> > >> early adapter of sage 
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-...@googlegroups.com . 
> > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/8ff7114f-29e6-46ec-9b96-87be8fcd778co%40googlegroups.com.
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3de87549-f9b6-46f8-aa8d-7c047cdb0513o%40googlegroups.com.

Re: [sage-devel] Re: Porting sagemath to Raspberry Pi OS

[Jaap Spies]

No

On Friday, July 10, 2020 at 11:22:30 AM UTC+2, Dima Pasechnik wrote:
>
> On Fri, Jul 10, 2020 at 10:11 AM Dima Pasechnik  > wrote: 
> > 
> > On Fri, Jul 10, 2020 at 9:08 AM Jaap Spies  > wrote: 
> > > 
> > > After this technicalities I reclaim my points: We need a port of 
> sagemath to Raspbery Pi OS. 
>
> As far as I see, it is 
> https://www.raspberrypi.org/downloads/raspberry-pi-desktop/ 
> (based on Debian Buster) - it uses apt to deal with packages, so the 
> setup we use on Debian/Ubuntu should 
> in principle be working. 
>
> Is this the OS you are referring to? 
>
> I don't know whether they try to import all the Debian packages, but 
> it looks as if Debian 
> effort to have Sage in Debian would be helpful here. 
>
> Thanks, 
> Dima 
>
> > > At least we need a binary of sagemath for Raspberry Pi OS. 
> > the binaries are made using 
> > https://github.com/sagemath/binary-pkg 
> > 
> > Could you try this on your Rasberry Pi? 
> > (probably nobody ever tested this on ARM, so YMMV). 
> > 
> > Dima 
> > > 
> > > Jaap Spies 
> > > 
> > > On Thursday, July 9, 2020 at 2:31:52 PM UTC+2, Jaap Spies wrote: 
> > >> 
> > >> Saying Raspberry Pi is saying education. There are zillion Raspberry 
> Pi's out there. 
> > >> Almost all of them are running Raspbian, now called Raspberry Pi OS. 
> > >> On every raspbian system there is an implementation of Mathematica. 
> > >> Wolfram was clever when he decided to make Matematica available to 
> the 
> > >> people of Raspberies. 
> > >> 
> > >> I did some experimentation out of an old book Mathematica Second 
> Edition. 
> > >> You can really do some math on a Raspberry Pi 4. 
> > >> 
> > >> Some time ago I could build sage-9.0 on my RPi4's, but now there are 
> problems 
> > >> with fplll. I opened a ticket, someone changed the priority to minor. 
> > >> 
> > >> I think it is of major importance to have at least a binary for 
> Raspberry Pi OS! 
> > >> 
> > >> I'm old and have no time and no energy to pursue this to the end, but 
> I plea 
> > >> someone would take this serious. 
> > >> 
> > >> Jaap 
> > >> 
> > >> early adapter of sage 
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group. 
> > > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-...@googlegroups.com . 
> > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/8ff7114f-29e6-46ec-9b96-87be8fcd778co%40googlegroups.com.
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/46d4e1d4-62a5-471b-a775-bee57208208do%40googlegroups.com.

[sage-devel] Re: Porting sagemath to Raspberry Pi OS

[Jaap Spies]

After this technicalities I reclaim my points: We need a port of sagemath 
to Raspbery Pi OS.
At least we need a binary of sagemath for Raspberry Pi OS.

Jaap Spies

On Thursday, July 9, 2020 at 2:31:52 PM UTC+2, Jaap Spies wrote:
>
> Saying Raspberry Pi is saying education. There are zillion Raspberry Pi's 
> out there.
> Almost all of them are running Raspbian, now called Raspberry Pi OS.
> On every raspbian system there is an implementation of Mathematica.
> Wolfram was clever when he decided to make Matematica available to the
> people of Raspberies.
>
> I did some experimentation out of an old book Mathematica Second Edition.
> You can really do some math on a Raspberry Pi 4.
>
> Some time ago I could build sage-9.0 on my RPi4's, but now there are 
> problems 
> with fplll. I opened a ticket, someone changed the priority to minor.
>
> I think it is of major importance to have at least a binary for Raspberry 
> Pi OS!
>
> I'm old and have no time and no energy to pursue this to the end, but I 
> plea
> someone would take this serious.
>
> Jaap
>
> early adapter of sage
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8ff7114f-29e6-46ec-9b96-87be8fcd778co%40googlegroups.com.

[sage-devel] Re: Porting sagemath to Raspberry Pi OS

[Jaap Spies]

Done.

On Thursday, July 9, 2020 at 3:58:20 PM UTC+2, Matthias Koeppe wrote:
>
> On Thursday, July 9, 2020 at 5:31:52 AM UTC-7, Jaap Spies wrote:
>>
>> ... Raspberry Pi ...
>>
>   
> https://trac.sagemath.org/ticket/29091, which adds test infrastructure 
> for raspbian-buster, still needs review.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/508422c0-6e53-423f-8d15-1f55528fe93bo%40googlegroups.com.

Re: [sage-devel] Porting sagemath to Raspberry Pi OS

[Jaap Spies]

real 51m45.870s
user 65m53.661s
sys 1m28.486s
Copying package files from temporary location 
/home/pi/sagemath/sage-9.2.beta4/local/var/tmp/sage/build/fplll-5.3.3/inst 
to /home/pi/sagemath/sage-9.2.beta4/local
Successfully installed fplll-5.3.3
Deleting temporary build directory
/home/pi/sagemath/sage-9.2.beta4/local/var/tmp/sage/build/fplll-5.3.3
Finished installing fplll-5.3.3

Now waiting ...


On Thursday, July 9, 2020 at 2:35:05 PM UTC+2, Dima Pasechnik wrote:
>
> The fplll upgrade which should work on ARM (and thus on Raspberry Pi) has 
> been merged in the latest beta, 9.2.beta4
>
> Please report whether it works for you or not.
>
>
> On Thu, 9 Jul 2020, 13:31 Jaap Spies, > 
> wrote:
>
>> Saying Raspberry Pi is saying education. There are zillion Raspberry Pi's 
>> out there.
>> Almost all of them are running Raspbian, now called Raspberry Pi OS.
>> On every raspbian system there is an implementation of Mathematica.
>> Wolfram was clever when he decided to make Matematica available to the
>> people of Raspberies.
>>
>> I did some experimentation out of an old book Mathematica Second Edition.
>> You can really do some math on a Raspberry Pi 4.
>>
>> Some time ago I could build sage-9.0 on my RPi4's, but now there are 
>> problems 
>> with fplll. I opened a ticket, someone changed the priority to minor.
>>
>> I think it is of major importance to have at least a binary for Raspberry 
>> Pi OS!
>>
>> I'm old and have no time and no energy to pursue this to the end, but I 
>> plea
>> someone would take this serious.
>>
>> Jaap
>>
>> early adapter of sage
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/0bba0441-a053-40dc-bc74-8c57bf08e0c4o%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/0bba0441-a053-40dc-bc74-8c57bf08e0c4o%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/53351a22-56b0-4ea9-b719-ee73550b17f4o%40googlegroups.com.

[sage-devel] Porting sagemath to Raspberry Pi OS

[Jaap Spies]

Saying Raspberry Pi is saying education. There are zillion Raspberry Pi's 
out there.
Almost all of them are running Raspbian, now called Raspberry Pi OS.
On every raspbian system there is an implementation of Mathematica.
Wolfram was clever when he decided to make Matematica available to the
people of Raspberies.

I did some experimentation out of an old book Mathematica Second Edition.
You can really do some math on a Raspberry Pi 4.

Some time ago I could build sage-9.0 on my RPi4's, but now there are 
problems 
with fplll. I opened a ticket, someone changed the priority to minor.

I think it is of major importance to have at least a binary for Raspberry 
Pi OS!

I'm old and have no time and no energy to pursue this to the end, but I plea
someone would take this serious.

Jaap

early adapter of sage

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0bba0441-a053-40dc-bc74-8c57bf08e0c4o%40googlegroups.com.

Re: [sage-devel] Apple on ARM

[Jaap Spies]

Yes. Sorry Martin. I mixed things up.

Martin knows of the problem. He reacted in the thread.

Jaap

On Wednesday, June 24, 2020 at 11:58:14 AM UTC+2, Dima Pasechnik wrote:
>
>
>
> On Wed, 24 Jun 2020, 10:34 Jaap Spies, > 
> wrote:
>
>> This was me on sagerelease. Starting with sage-9.1.beta1 fplll failed. 
>> According to Bill Hart they never test on ARM.
>>
> fplll bug tracker is here:
> https://github.com/fplll/fplll/issues
> In the past they dealt with ARM bugs.
> Please file yours there.
>
> (it is Martin Albrecht's project mostly, I don't think Bill Hart is 
> involved)
>
>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/019bccce-a263-4875-b124-42afd1343d9co%40googlegroups.com.

Re: [sage-devel] Apple on ARM

[Jaap Spies]

See ticket: https://trac.sagemath.org/ticket/29091

Jaap

On Wednesday, June 24, 2020 at 11:34:40 AM UTC+2, Jaap Spies wrote:
>
> This was me on sagerelease. Starting with sage-9.1.beta1 fplll failed. 
> According to Bill Hart they never test on ARM.
>
> Jaap
>
>
> On Wednesday, June 24, 2020 at 8:21:48 AM UTC+2, tdumont wrote:
>>
>> Some weeks ago, there was a post on this list (or an other sage list) 
>> where somebody said he succeeded compiling sage on a Raspberry 4... so... 
>> t. 
>>
>> Le 23/06/2020 à 14:11, Dima Pasechnik a écrit : 
>> > Sage used to work on ARM chips, we stopped testing on it due to lack of 
>> > hardware in 2015 or so. 
>> > 
>> > We can pick it up again. 
>> > 
>> > 
>> > On Tue, 23 Jun 2020, 13:03 kcrisman, > > <mailto:kcri...@gmail.com>> wrote: 
>> > 
>> > See e.g. 
>> > 
>> https://www.theverge.com/2020/6/21/21298607/first-arm-mac-macbook-pro-imac-ming-chi-kuo-wwdc-2020
>>  
>> > 
>> > When Apple moved to Intel, there were definitely some impacts for 
>> > Sage - obviously needing to provide two sets of binaries - but I 
>> > wonder if maybe the Sage ecosystem is a lot more stable w.r.t. 
>> > processors this time around (e.g. assembly code already available 
>> > for major upstream packages).  Maybe it's so trivial that I am 
>> > foolish for mentioning it, but I thought I would ask if anyone has 
>> > thoughts on this, as I couldn't find anything on this forum about 
>> it 
>> > yet. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "sage-devel" group. 
>> > To unsubscribe from this group and stop receiving emails from it, 
>> > send an email to sage-...@googlegroups.com 
>> > <mailto:sage-devel+unsubscr...@googlegroups.com>. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/sage-devel/7aa3429b-d2d6-4453-b708-793da943275ao%40googlegroups.com
>>  
>> > <
>> https://groups.google.com/d/msgid/sage-devel/7aa3429b-d2d6-4453-b708-793da943275ao%40googlegroups.com?utm_medium=email_source=footer>.
>>  
>>
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "sage-devel" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to sage-...@googlegroups.com 
>> > <mailto:sage-devel+unsubscr...@googlegroups.com>. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0B_TZssoMRqwvrp7bgjz99WRm4OzQ%3DguZcy5CP1atxtg%40mail.gmail.com
>>  
>> > <
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0B_TZssoMRqwvrp7bgjz99WRm4OzQ%3DguZcy5CP1atxtg%40mail.gmail.com?utm_medium=email_source=footer>.
>>  
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/47e78128-0d36-4d57-b5bc-6811cc046049o%40googlegroups.com.

Re: [sage-devel] Apple on ARM

[Jaap Spies]

This was me on sagerelease. Starting with sage-9.1.beta1 fplll failed. 
According to Bill Hart they never test on ARM.

Jaap


On Wednesday, June 24, 2020 at 8:21:48 AM UTC+2, tdumont wrote:
>
> Some weeks ago, there was a post on this list (or an other sage list) 
> where somebody said he succeeded compiling sage on a Raspberry 4... so... 
> t. 
>
> Le 23/06/2020 à 14:11, Dima Pasechnik a écrit : 
> > Sage used to work on ARM chips, we stopped testing on it due to lack of 
> > hardware in 2015 or so. 
> > 
> > We can pick it up again. 
> > 
> > 
> > On Tue, 23 Jun 2020, 13:03 kcrisman,  
> > > wrote: 
> > 
> > See e.g. 
> > 
> https://www.theverge.com/2020/6/21/21298607/first-arm-mac-macbook-pro-imac-ming-chi-kuo-wwdc-2020
>  
> > 
> > When Apple moved to Intel, there were definitely some impacts for 
> > Sage - obviously needing to provide two sets of binaries - but I 
> > wonder if maybe the Sage ecosystem is a lot more stable w.r.t. 
> > processors this time around (e.g. assembly code already available 
> > for major upstream packages).  Maybe it's so trivial that I am 
> > foolish for mentioning it, but I thought I would ask if anyone has 
> > thoughts on this, as I couldn't find anything on this forum about it 
> > yet. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, 
> > send an email to sage-...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/sage-devel/7aa3429b-d2d6-4453-b708-793da943275ao%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/sage-devel/7aa3429b-d2d6-4453-b708-793da943275ao%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "sage-devel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to sage-...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0B_TZssoMRqwvrp7bgjz99WRm4OzQ%3DguZcy5CP1atxtg%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0B_TZssoMRqwvrp7bgjz99WRm4OzQ%3DguZcy5CP1atxtg%40mail.gmail.com?utm_medium=email_source=footer>.
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6fb5f524-76c5-4565-a545-36c41a2bffbbo%40googlegroups.com.

Re: [sage-devel] Re: 10 years ago

[Jaap Spies]

Maybe you noticed that Dima did his first contribution to sage 10 years ago.

Cheers, Jaap

Op ma 24 feb. 2020 02:07 schreef Samuel Lelievre :

> Ten years ago:
>
> Sage Days 20
> https://wiki.sagemath.org/daysmarseille
> https://www.lirmm.fr/arith/wiki/MathInfo2010/SageDays
>
> was the fourth week of the 5-week long thematic month
>
> MathInfo2010 -- "Towards new interactions
> between Mathematics and Computer Science"
> Thematic month at Cirm, Luminy, Marseille, France
> 01 Feb 2010 -- 06 Mar 2010
> https://www.lirmm.fr/arith/wiki/MathInfo2010
>
> I think that's when I fell into Sage.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/819d3452-ced0-42db-9973-d8c34cd7929e%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAK0%3DbK3PCYup_V9Dj1rcTR_RqpNRWoDsXmRo3ipO3DSGzCo0Rg%40mail.gmail.com.

[sage-devel] 10 years ago

[Jaap Spies]

https://github.com/sagemath/website/blob/master/src/changelogs/sage-4.3.3.txt

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ad8b01fa-52ea-4aa4-b119-b81ee81932ea%40googlegroups.com.

[sage-devel] Re: Buiding sage on a Raspberry Pi 4B

[Jaap Spies]

I did run the failing tests! This is really frustrating.


./sage -t --long  src/sage/rings/tests.py # Killed due to segmentation 
fault NOW: All test passed!!
./sage -t --long  src/sage/schemes/elliptic_curves/ell_rational_field.py # 
Killed due to segmentation fault NOW: All test passed!!
./sage -t --long  src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to 
segmentation fault NOW: All test passed!!
./sage -t --long  src/sage/structure/coerce_dict.pyx # 1 failure len(LE) 
Expected 1 Got: 50 
./sage -t --long  src/sage/modular/modform_hecketriangle/abstract_space.py 
# Killed due to segmentation fault NOW: All test passed!!
./sage -t --long  src/sage/modular/modform/cuspidal_submodule.py # Timed 
out  NOW: All test passed!!  in NB 51.16 seconds
./sage -t --long  src/sage/modular/arithgroup/congroup_gammaH.py # Timed 
out total time 1832.3 seconds NOW: All test passed in 11.74 seconds
./sage -t --long  src/sage/combinat/designs/evenly_distributed_sets.pyx  # 
Timed out NOW:  All test passed in 8.11 seconds
./sage -t --long  src/sage/modular/modform/tests.py # Times out 1822.7 
seconds NOW: All test passed in 4.12 seconds 
./sage -t --long  src/sage/sets/set.py # Times out 1821.5 seconds  NOW: All 
test passed in 2.08 seconds
./sage -t --long  src/sage/misc/weak_dict.pyx  # 11 doctests failed
./sage -t --long  src/sage/cpython/dict_del_by_value.pyx # 1 doctest failed 


On Tuesday, December 31, 2019 at 10:58:38 AM UTC+1, Jaap Spies wrote:
>
>
>
> On Monday, December 30, 2019 at 11:21:34 PM UTC+1, Jaap Spies wrote:
>>
>>
>>
>> I'll make a bash script to do the tests stand alone.
>>
>>
>>>
> bash test_errors_rc1 >> err.log 2>&1 &
>
> Resume:
> ./sage -t --long  src/sage/rings/tests.py # Killed due to segmentation 
> fault 
> ./sage -t --long  src/sage/schemes/elliptic_curves/ell_rational_field.py # 
> Killed due to segmentation fault 
> ./sage -t --long  src/sage/rings/function_field/function_field.py  # All 
> tests passed
> ./sage -t --long  
> src/sage/schemes/cyclic_covers/cycliccover_finite_field.py  # All tests 
> passed
> ./sage -t --long  src/sage/combinat/sf/macdonald.py  # All tests passed
> ./sage -t --long  src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to 
> segmentation fault 
> ./sage -t --long  src/sage/algebras/lie_algebras/classical_lie_algebra.py  
> # All tests passed
> ./sage -t --long  
> src/sage/rings/function_field/function_field_valuation.py  # All tests 
> passed
> ./sage -t --long  src/sage/rings/number_field/number_field.py  # All tests 
> passed
> ./sage -t --long  src/sage/geometry/cone.py  # All tests passed
> ./sage -t --long  src/sage/modular/btquotients/pautomorphicform.py  # All 
> tests passed
> ./sage -t --long  src/sage/arith/misc.py  # All tests passed
> ./sage -t --long  src/sage/graphs/strongly_regular_db.pyx  # All tests 
> passed
> ./sage -t --long  src/sage/structure/coerce_dict.pyx # 1 failure len(LE) 
> Expected 1 Got: 50 
> ./sage -t --long  src/sage/modular/modform_hecketriangle/abstract_space.py 
> # Killed due to segmentation fault 
> ./sage -t --long  src/sage/modular/modform/find_generators.py  # All tests 
> passed
> ./sage -t --long  src/sage/modular/modform/cuspidal_submodule.py # Timed 
> out  
> ./sage -t --long  src/sage/schemes/toric/chow_group.py  # All tests passed
> ./sage -t --long  src/sage/groups/matrix_gps/finitely_generated.py  # All 
> tests passed
> ./sage -t --long  src/sage/rings/function_field/ideal.py  # All tests 
> passed
> ./sage -t --long  src/sage/misc/functional.py  # All tests passed
> ./sage -t --long  src/sage/rings/number_field/totallyreal_rel.py  # All 
> tests passed
> ./sage -t --long  src/sage/modular/hypergeometric_motive.py  # All tests 
> passed
> ./sage -t --long  src/sage/categories/loop_crystals.py  # All tests passed
> ./sage -t --long  src/sage/algebras/iwahori_hecke_algebra.py  # All tests 
> passed
> ./sage -t --long  src/sage/schemes/curves/projective_curve.py  # All tests 
> passed
> ./sage -t --long  src/sage/modular/overconvergent/genus0.py  # All tests 
> passed
> ./sage -t --long  src/sage/combinat/permutation.py  # All tests passed
> ./sage -t --long  src/sage/rings/number_field/number_field_ideal.py  # All 
> tests passed
> ./sage -t --long  
> src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx  # All tests 
> passed
> ./sage -t --long  src/sage/geometry/triangulation/element.py  # All tests 
> passed
> ./sage -t --long  src/sage/schemes/elliptic_curves/period_lattice.py  # 
> All tests passed
> ./sage -t --long  src/sage/schemes/elliptic_curves/ell_field.py  # All 
> tests passed
> ./sage -t --long  src/sage/modular/arithgroup/congroup_gammaH.py # Timed 
> out total time 1832.3 seconds 
> ./sage -t --long  src/sage/r

[sage-devel] Re: Buiding sage on a Raspberry Pi 4B

[Jaap Spies]

On Monday, December 30, 2019 at 11:21:34 PM UTC+1, Jaap Spies wrote:
>
>
>
> I'll make a bash script to do the tests stand alone.
>
>
>>
bash test_errors_rc1 >> err.log 2>&1 &

Resume:
./sage -t --long  src/sage/rings/tests.py # Killed due to segmentation 
fault 
./sage -t --long  src/sage/schemes/elliptic_curves/ell_rational_field.py # 
Killed due to segmentation fault 
./sage -t --long  src/sage/rings/function_field/function_field.py  # All 
tests passed
./sage -t --long  
src/sage/schemes/cyclic_covers/cycliccover_finite_field.py  # All tests 
passed
./sage -t --long  src/sage/combinat/sf/macdonald.py  # All tests passed
./sage -t --long  src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to 
segmentation fault 
./sage -t --long  src/sage/algebras/lie_algebras/classical_lie_algebra.py  
# All tests passed
./sage -t --long  
src/sage/rings/function_field/function_field_valuation.py  # All tests 
passed
./sage -t --long  src/sage/rings/number_field/number_field.py  # All tests 
passed
./sage -t --long  src/sage/geometry/cone.py  # All tests passed
./sage -t --long  src/sage/modular/btquotients/pautomorphicform.py  # All 
tests passed
./sage -t --long  src/sage/arith/misc.py  # All tests passed
./sage -t --long  src/sage/graphs/strongly_regular_db.pyx  # All tests 
passed
./sage -t --long  src/sage/structure/coerce_dict.pyx # 1 failure len(LE) 
Expected 1 Got: 50 
./sage -t --long  src/sage/modular/modform_hecketriangle/abstract_space.py 
# Killed due to segmentation fault 
./sage -t --long  src/sage/modular/modform/find_generators.py  # All tests 
passed
./sage -t --long  src/sage/modular/modform/cuspidal_submodule.py # Timed 
out  
./sage -t --long  src/sage/schemes/toric/chow_group.py  # All tests passed
./sage -t --long  src/sage/groups/matrix_gps/finitely_generated.py  # All 
tests passed
./sage -t --long  src/sage/rings/function_field/ideal.py  # All tests passed
./sage -t --long  src/sage/misc/functional.py  # All tests passed
./sage -t --long  src/sage/rings/number_field/totallyreal_rel.py  # All 
tests passed
./sage -t --long  src/sage/modular/hypergeometric_motive.py  # All tests 
passed
./sage -t --long  src/sage/categories/loop_crystals.py  # All tests passed
./sage -t --long  src/sage/algebras/iwahori_hecke_algebra.py  # All tests 
passed
./sage -t --long  src/sage/schemes/curves/projective_curve.py  # All tests 
passed
./sage -t --long  src/sage/modular/overconvergent/genus0.py  # All tests 
passed
./sage -t --long  src/sage/combinat/permutation.py  # All tests passed
./sage -t --long  src/sage/rings/number_field/number_field_ideal.py  # All 
tests passed
./sage -t --long  
src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx  # All tests 
passed
./sage -t --long  src/sage/geometry/triangulation/element.py  # All tests 
passed
./sage -t --long  src/sage/schemes/elliptic_curves/period_lattice.py  # All 
tests passed
./sage -t --long  src/sage/schemes/elliptic_curves/ell_field.py  # All 
tests passed
./sage -t --long  src/sage/modular/arithgroup/congroup_gammaH.py # Timed 
out total time 1832.3 seconds 
./sage -t --long  src/sage/rings/number_field/galois_group.py  # All tests 
passed
./sage -t --long  src/sage/rings/valuation/limit_valuation.py  # All tests 
passed
./sage -t --long  src/sage/combinat/e_one_star.py  # All tests passed
./sage -t --long  src/sage/combinat/designs/latin_squares.py  # All tests 
passed
./sage -t --long  src/sage/combinat/designs/evenly_distributed_sets.pyx  # 
Timed out
./sage -t --long  
src/sage/geometry/polyhedron/combinatorial_polyhedron/polyhedron_face_lattice.pyx
 
# All tests passed  
./sage -t --long  src/sage/calculus/wester.py   # All tests passed
./sage -t --long  src/sage/groups/artin.py   # All tests passed
./sage -t --long  src/sage/symbolic/ring.pyx   # All tests passed
./sage -t --long  src/sage/structure/coerce.pyx   # All tests passed
./sage -t --long  src/sage/modular/modsym/tests.py   # All tests passed
./sage -t --long  src/sage/modular/modform/ambient_g1.py   # All tests 
passed
./sage -t --long  
src/sage/tests/books/judson-abstract-algebra/fields-sage.py   # All tests 
passed
./sage -t --long  src/sage/rings/polynomial/multi_polynomial_element.py   # 
All tests passed
./sage -t --long  src/sage/repl/preparse.py   # All tests passed
./sage -t --long  src/sage/tests/book_stein_modform.py   # All tests passed
./sage -t --long  src/sage/modular/modform/tests.py # Times out 1822.7 
seconds 
./sage -t --long  src/sage/homology/simplicial_complex_morphism.py   # All 
tests passed
./sage -t --long  src/sage/algebras/quaternion_algebra_element.py   # All 
tests passed
./sage -t --long  src/sage/structure/factorization.py   # All tests passed
./sage -t --long  src/sage/sets/set.py # Times out 1821.5 seconds 
./sage -t --long  
src/sage/quadratic_forms/quadratic_form__split_local_covering.py   # All 
tests passed
./sage -t --long  src/sage/misc/weak_dict.pyx  # 11 doctests failed
./sage -t --lon

[sage-devel] Re: Buiding sage on a Raspberry Pi 4B

[Jaap Spies]

Hi Dima,

I don't understand what I see and I hate that. Seeing 4 CPU's producing 
heat, four instances of python 3 gathering CPU time.
producing 0 test of 0.00s duration. There is something not OK in the 
Raspberry Pi system.
I don't trust the memory management system at all.

make ptestlong ended:
--
sage -t --long --warn-long 253.8 src/sage/rings/tests.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 253.8 
src/sage/schemes/elliptic_curves/ell_rational_field.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 253.8 
src/sage/rings/function_field/function_field.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/schemes/cyclic_covers/cycliccover_finite_field.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/combinat/sf/macdonald.py  # 
Killed due to segmentation fault
sage -t --long --warn-long 253.8 src/sage/combinat/ncsf_qsym/ncsf.py  # 
Killed due to segmentation fault
sage -t --long --warn-long 253.8 
src/sage/algebras/lie_algebras/classical_lie_algebra.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/rings/function_field/function_field_valuation.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/rings/number_field/number_field.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/geometry/cone.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/modular/btquotients/pautomorphicform.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/arith/misc.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/graphs/strongly_regular_db.pyx  # 
Timed out
sage -t --long --warn-long 253.8 src/sage/structure/coerce_dict.pyx  # 1 
doctest failed
sage -t --long --warn-long 253.8 
src/sage/modular/modform_hecketriangle/abstract_space.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 253.8 
src/sage/modular/modform/find_generators.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/modular/modform/cuspidal_submodule.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/schemes/toric/chow_group.py  # 
Timed out
sage -t --long --warn-long 253.8 
src/sage/groups/matrix_gps/finitely_generated.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/rings/function_field/ideal.py  # 
Killed due to segmentation fault
sage -t --long --warn-long 253.8 src/sage/misc/functional.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/rings/number_field/totallyreal_rel.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 253.8 src/sage/modular/hypergeometric_motive.py  
# Timed out
sage -t --long --warn-long 253.8 src/sage/categories/loop_crystals.py  # 
Timed out
sage -t --long --warn-long 253.8 
src/sage/algebras/iwahori_hecke_algebra.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/schemes/curves/projective_curve.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/modular/overconvergent/genus0.py  
# Timed out
sage -t --long --warn-long 253.8 src/sage/combinat/permutation.py  # Timed 
out
sage -t --long --warn-long 253.8 
src/sage/rings/number_field/number_field_ideal.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx  # Timed out
sage -t --long --warn-long 253.8 
src/sage/geometry/triangulation/element.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/schemes/elliptic_curves/period_lattice.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/schemes/elliptic_curves/ell_field.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/modular/arithgroup/congroup_gammaH.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/rings/number_field/galois_group.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/rings/valuation/limit_valuation.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/combinat/e_one_star.py  # Timed 
out
sage -t --long --warn-long 253.8 
src/sage/combinat/designs/latin_squares.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/combinat/designs/evenly_distributed_sets.pyx  # Timed out
sage -t --long --warn-long 253.8 
src/sage/geometry/polyhedron/combinatorial_polyhedron/polyhedron_face_lattice.pyx
  
# Timed out
sage -t --long --warn-long 253.8 src/sage/calculus/wester.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/groups/artin.py  # Timed out
sage -t --long --warn-long 253.8 src/sage/symbolic/ring.pyx  # Timed out
sage -t --long --warn-long 253.8 src/sage/structure/coerce.pyx  # Timed out
sage -t --long --warn-long 253.8 src/sage/modular/modsym/tests.py  # Timed 
out
sage -t --long --warn-long 253.8 src/sage/modular/modform/ambient_g1.py  # 
Timed out
sage -t --long --warn-long 253.8 
src/sage/tests/books/judson-abstract-algebra/fields-sage.py  # Timed out
sage -t --long --warn-long 253.8 
src/sage/rings/polynomial/multi_polynomial_element.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 253.8 src/sage/repl/preparse.py  # Timed out
sage -t --long --warn-long 253.8 

[sage-devel] Buiding sage on a Raspberry Pi 4B

[Jaap Spies]

Why? Because it is possible. And the OS Raspbian is distributed with a 
version of Mathematica 12.0

First attempt was building sage-8.9. Just did a 'make' after downloading. 
The RPi 4 showed unstable.
The little computer stalled a few times. Power off and power on. After 12 
hours there was a running sage.
Building the docs failed consistently. I ran a few tests.

Secondly I did a "MAKE='make -j4' make". After a few hick-ups I changed to 
'make -j3' and got sage running, but building the docs
failed on the same spot.

Third was a try to build sage-9.0.beta9 with 'make -j3'. Again a few 
freezes, but the building of the docs succeeded!
The same with sage-9.0.beta10. Testing with 'make ptestlong' lasted long. 
It was good my RPi 4 had active cooling with temperatures
up to 75 degrees Celcius. There were 60 failures, some segmentation faults 
some Time Outs.
Most of the errors were resolved by running a bash script to test files 
individually.

The building of sage-9.0.rc0 ended in problems with building scipy. My idea 
of computers being deterministic is chocked.
I started with a clean source. And to my surprise only a few hick-ups and 
after 'make ptestlong' 56 failed tests.
Most of them were resolved. See above.

As we speak now sage-9.0.rc1 is doing a 'make ptestlong'. Probably will 
finish in a few hours.

My conclusion so far: Sage can be built on a Rarpberry Pi 4, but certainly 
not unattended.

Most remarkable:
Saved trace to /home/pi/.sage/crash_logs/crash_s8ljau3w.log

Unhandled SIGSEGV: A segmentation fault occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.


**

sage -t --long --warn-long 248.7 
src/sage/rings/function_field/function_field.py  # Timed out
sage -t --long --warn-long 248.7 
src/sage/schemes/elliptic_curves/ell_rational_field.py  # Timed out
sage -t --long --warn-long 248.7 
src/sage/schemes/elliptic_curves/isogeny_class.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 248.7 src/sage/modular/pollack_stevens/modsym.py 
 # Timed out
sage -t --long --warn-long 248.7 
src/sage/rings/function_field/function_field_valuation.py  # Timed out
sage -t --long --warn-long 248.7 src/sage/rings/padics/padic_base_leaves.py 
 # Timed out
sage -t --long --warn-long 248.7 src/sage/combinat/tableau.py  # Killed due 
to segmentation fault
sage -t --long --warn-long 248.7 
src/sage/rings/valuation/augmented_valuation.py  # Timed out
sage -t --long --warn-long 248.7 
src/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py  # Timed 
out
sage -t --long --warn-long 248.7 
src/sage/combinat/root_system/root_lattice_realization_algebras.py  # 
Killed due to segmentation fault
sage -t --long --warn-long 248.7 
src/sage/modular/modform_hecketriangle/readme.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 248.7 src/sage/structure/coerce_dict.pyx  # 1 
doctest failed
sage -t --long --warn-long 248.7 
src/sage/schemes/elliptic_curves/constructor.py  # Timed out
sage -t --long --warn-long 248.7 
src/sage/combinat/crystals/kirillov_reshetikhin.py  # Timed out
sage -t --long --warn-long 248.7 
src/sage/combinat/shifted_primed_tableau.py  # Killed due to segmentation 
fault
sage -t --long --warn-long 248.7 src/sage/categories/finite_monoids.py  # 
Timed out
sage -t --long --warn-long 248.7 
src/sage/combinat/root_system/integrable_representations.py  # Timed out
sage -t --long --warn-long 248.7 
src/sage/combinat/crystals/littelmann_path.py  # Timed out
sage -t --long --warn-long 248.7 src/sage/rings/tests.py  # Killed due to 
segmentation fault
sage -t --long --warn-long 248.7 src/doc/ca/intro/index.rst  # Timed out
sage -t --long --warn-long 248.7 src/sage/modular/abvar/homspace.py  # 
Timed out
sage -t --long --warn-long 248.7 src/sage/groups/libgap_morphism.py  # 
Timed out
sage -t --long --warn-long 248.7 
src/sage/rings/function_field/differential.py  # Killed due to segmentation 
fault
sage -t --long --warn-long 248.7 src/sage/combinat/posets/poset_examples.py 
 # Timed out
sage -t --long --warn-long 248.7 
src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py 
 # Timed out
sage -t --long --warn-long 248.7 
src/sage/algebras/lie_algebras/verma_module.py  # Timed out
sage -t --long --warn-long 248.7 src/sage/rings/padics/padic_valuation.py 
 # Killed due to segmentation fault
sage -t --long --warn-long 248.7 src/sage/rings/complex_number.pyx  # 
Killed due to segmentation fault
sage -t --long --warn-long 248.7 src/sage/geometry/fan.py  # Timed out
sage -t --long --warn-long 248.7 src/sage/rings/function_field/element.pyx 
 # Timed out
sage -t --long --warn-long 248.7 
src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx  # 

[sage-devel] Re: Please test sage-5.1.rc1

[Jaap Spies]

Jeroen Demeyer wrote:

Because many of the Sage testing machines (redhawk and all of Skynet)
are down, version sage-5.1.rc1 has been tested much less than usual.

So, please build sage-5.1.rc1 and report unexpected problems, especially
if you have an unusual system.  Downloads at:
http://www.sagemath.org/download-latest.html

If there are no problems, then sage-5.1 will be released identical to
sgae-5.1.rc1.


Jeroen.


[jaap@vrede sage-5.1.rc1]$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.6.3/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla 
--enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions 
--enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-java-awt=gtk 
--disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode 
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 
--build=x86_64-redhat-linux

Thread model: posix
gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC)
[jaap@vrede sage-5.1.rc1]$ uname -a
Linux vrede 3.3.2-6.fc16.x86_64 #1 SMP Sat Apr 21 12:43:20 UTC 2012 x86_64 
x86_64 x86_64 GNU/Linux
[jaap@vrede sage-5.1.rc1]$

make ptestlong:

--
All tests passed!
Total time for all tests: 2776.8 seconds
[jaap@vrede sage-5.1.rc1]$


--
--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: MathCad-like front end for Sage

[Jaap Spies]

David Roe wrote:

On Mon, Nov 28, 2011 at 08:56, Dima Pasechnikdimp...@gmail.com  wrote:



On Monday, 28 November 2011 21:29:32 UTC+8, Emil Widmann wrote:


On Nov 28, 11:33 am, Dima Pasechnikdim...@gmail.com  wrote:

It's much more urgent to work on the Sage notebook, than to create yet
another frontend.
IMHO.


Probably true. Anyhow, people will work on whatever project they
like...


People should not work on projects that are a waste of resources.


I strongly disagree.  If someone want to work on Sage, then we should
provide advice but by no means tell them what to do.  It's a plus for
the Sage community to get people involved, even if at first they work
on something of interest to them that others might consider a waste
of resources.  I think it's a shame that the tone on the sage-devel
list is not as welcoming as it used to be, and I think we suffer a
loss of developers because of it.


+1

Jaap



David




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Valgrind package very old

[Jaap Spies]

Dr. David Kirkby wrote:

On 03/29/11 04:36 PM, Volker Braun wrote:

I also noticed that the valgrind package is old; In particular it doesn't
even compile on Fedora 14. But then its such a commonly-used tool that
its
already on every machine that is used for software development. The fact
that nobody every complained about the outdated valgrind spkg should
probably be taken as a sign that nobody needs it.



In that case is there an argument for not having the package at all -
i.e. simply remove it as an optional package?



There is a new spkg: http://trac.sagemath.org/sage_trac/ticket/7766#comment:9

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: vtk

[Jaap Spies]

Mag Gam wrote:

Has anyone compiled VTK, http://www.vtk.org/, into sage? I would like
to compile this but would need some assistance and/or tips.



This is very old, but it used to work:

http://sage.math.washington.edu/home/jsp/SPKGS/ETS/

Somehow I lost interest, so you are mostly on your own.

Cheers,

Jaap

--



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: inconsistent results for characteristic polynomial?

[Jaap Spies]

John Cremona wrote:

On 15 June 2010 17:17, Minh Nguyennguyenmi...@gmail.com  wrote:

Hi folks,

I appreciate the feedbacks. I have documented the definition of
characteristic polynomials for graphs at ticket #9246:

http://trac.sagemath.org/sage_trac/ticket/9246

The immortal words of Humpty Dumpty ring through the ages:

When I use a word, it means just what I choose it to mean -- neither
more nor less. --Humpty Dumpty in Through the Looking-Glass and What
Alice Found There



-- which was, of course, written by a mathematician / logician!



http://www.sabian.org/Alice/lgchap04.htm

`I know what you're thinking about,' said Tweedledum; `but it isn't so, nohow.'

`Contrariwise,' continued Tweedledee, `if it was so, it might be; and if it 
were so,
it would be; but as it isn't, it ain't. That's logic.'

:-)

Jaap



John



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

[Jaap Spies]

Paul Leopardi wrote:

Thanks, Georg,
I moved -lm to just before -o test in the makefile for symmetrica-2.0.p5, used
tar zcf to creat a replacement spkg, and the make now continues past
symmetrica-2.0.p5. The make is still running.

I have the following environment variables defined:

SAGE64=yes
SAGE_CHECK=yes


Don't do this! SAGE64=yes is reserved for building 64 bit on OSX and (Open) 
Solaris!

Don't set SAGE_CHECK unless you know what you are doing.


Jaap



SAGE_ROOT=

Best, Paul




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: is the latest valgrind optional spkg at version valgrind-3.5.0.p0?

[Jaap Spies]

Minh Nguyen wrote:

Hi folks,

At ticket #7440 [1], I see that the valgrind optional spkg was
upgraded to version valgrind-3.5.0.p0. However, on the Sage website
page [2] for downloading optional packages, I see that the latest
version available for download is valgrind-3.3.1. Is there any reasons
for the discrepancy? It is the case that the upgraded valgrind spkg
was not uploaded to the Sage website at all when ticket #7440 was
closed?

[1] http://trac.sagemath.org/sage_trac/ticket/7440

[2] http://www.sagemath.org/packages/optional/



See: http://trac.sagemath.org/sage_trac/ticket/7766
for a newer valgrind.

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage 4.4.2.alpha0 released

[Jaap Spies]

Minh Nguyen wrote:

Hi folks,

This release of Sage 4.4.2.alpha0 is earlier than I scheduled [1]. But
I have found some doctest failures that could take a while to resolve.
So getting this release out early should help with resolving them.



On Fedora 12, 64 bit all troubles seem far away!

--
All tests passed!

Upgrade from sage-4.4.1

Jaap

--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: MPIR and GMP: an announcement

[Jaap Spies]

Tom Boothby wrote:

On Thu, Apr 1, 2010 at 7:58 AM, Francesco Biscanibluesca...@gmail.com  wrote:

Erm, April 1st?


An Australian, playing a prank?  I shouldn't think they'd know how.
They're such a serious bunch.  I've hardly even seen Bill crack a
smile, let alone laugh!



You clearly didn't met him at dinner with a glass of good Australian wine.

Jaap


--
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-devel
URL: http://www.sagemath.org

To unsubscribe, reply using remove me as the subject.

[sage-devel] Re: Can a 4.3.5 be created to fix the Fedora/Mandriva/OpenSUSE build problem?

[Jaap Spies]

Dr. David Kirkby wrote:

William was keen that a new release was made quickly to fix the issues
which prevent 4.3.4 building on several linux distros.

A patch is here:

http://trac.sagemath.org/sage_trac/ticket/8567

If that is added, Sage should build ok on these linux distros, which
otherwise do not like it when there are two copies of iconv (system
install and $SAGE_LOCAL)



+1

Jaap




Dave




--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Annual Spies Prize Winner Announced!

[Jaap Spies]

Florent Hivert wrote:

Minh Van Nguyen is an integral part of the Sage development effort.
He is awarded the 2010 Spies Development Prize in recognition of his
code contributions, release management, support for new users and
outstanding work on documentation.


[...]

To bad he went to sleep 1 hour ago ! And Bravo to Minh ! Two thumbs up !



When we shout out loud, he'll probably wake up from his snooze.

Jaap



Cheers,

Florent




--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Annual Spies Prize Winner Announced!

[Jaap Spies]

Harald Schilly wrote:

On Mar 21, 7:14 pm, William Steinwst...@gmail.com  wrote:

Minh Van Nguyen is an integral part of the Sage development effort.


Congratulations, and yes, that's so true !!

H



Thanks for updating: http://www.sagemath.org/development-prize.html

Jaap


--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Bug advertisement

[Jaap Spies]

Alec Mihailovs wrote:

On Mar 21, 11:38 am, Ronan Paixãoronanpai...@yahoo.com.br  wrote:

Also, since I'm using that ugly OS,


For me, Windows 7 is beautiful!



You are joking!


Unfortunately, I have to use that ugly Linux most of the time when I
want to use Sage.



You are joking once more. But wait! A native Windows Sage is almost there.

Jaap



--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Bug advertisement

[Jaap Spies]

Alec Mihailovs wrote:

Jaap,


But wait! A native Windows Sage is almost there.


That would be excellent! I'm not sure that cygwin would work on my 64-
bit system (never tried it though.)



On my ugly 64 bit system I can run 32 bit software without a problem :)

Jaap



Alec




--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Sage-4.3.4 fails to build on openSuSE 11.1 x86_64.

[Jaap Spies]

Dr. David Kirkby wrote:

Dr. David Kirkby wrote:


I'm too busy to search for it, but there was a report the problem goes
away if an option like ''without-freetype' was added to gd's configure
script. You will need to search the recent posts to find the exact
details - I don't have time to do it for you just now - sorry.

dave



A better option might be to specify the path of libiconv if the gd
configure script will allow this to be done.



I'm looking into that.

Jaap



dave




--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: sage-4.3.4 does not build on Mandriva 2010 64 bits

[Jaap Spies]

Jean-Yves Thibon wrote:


Note: sage-4.3.3 did build correctly on the same machine.
-
[...@scriabine sage-4.3.4]$ uname -a
Linux scriabine 2.6.31.12-server-1mnb #1 SMP Tue Jan 26 03:35:57 EST
2010 x86_64 Intel(R) Xeon(R) CPU   E5540  @ 2.53GHz GNU/Linux



Here is the end of install.log
---
../.libs/libgd.so: undefined reference to
`libiconv'
../.libs/libgd.so: undefined reference to
`libiconv_close'
../.libs/libgd.so: undefined reference to
`libiconv_open'
collect2: ld a retourné 1 code d'état
d'exécution
make[4]: *** [annotate] Erreur



This is ticket: http://trac.sagemath.org/sage_trac/ticket/8567

[...]


Jaap



--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Sage-4.3.4 fails to build on openSuSE 11.1 x86_64.

[Jaap Spies]

Florent Hivert wrote:

   Hi,

On Sat, Mar 20, 2010 at 02:22:20PM +, Dr. David Kirkby wrote:

Dima Pasechnik wrote:

I suppose you can edit install-spkg in unpacked gd spkg, i.e.
SAGE_ROOT/spkg/standard/gd-2.0.35.p4.spkg
ans specify --with-libiconv-prefix=... in the ./configure call.


That looks very sensible to me. I created a ticket for it, but don't have
time to do it now.

http://trac.sagemath.org/sage_trac/ticket/8567


Unfortunately, I didn't manage to get it work ! I had to hack by hand the
into makefile... and then make install...

By the way, I got the same problem on a

massena-~ $ uname -a
Linux massena 2.6.23-gentoo-r6 #1 SMP Wed Feb 6 21:49:58 CET 2008 x86_64 
Intel(R) Xeon(R) CPU   X5365  @ 3.00GHz GenuineIntel GNU/Linux

massena-/etc $ cat gentoo-release
Gentoo Base System release 1.12.9



moving /usr/bin/iconv and /usr/include/iconv.h out of the way made it possible 
to build
gd

So nothing wrong with the libiconv in SAGE_LOCAL

Jaap




Cheers,

Florent




--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Sage 4.3.4 released

[Jaap Spies]

Minh Nguyen wrote:

Hi folks,

Sage 4.3.4 was released on March 19, 2010. It is available at

http://www.sagemath.org/download.html

* About Sage (http://www.sagemath.org)

Sage is developed by volunteers and combines over 90 open source packages.
It is available for download from www.sagemath.org and its mirrors in
source or binary form. If you have any questions and/or problems,
please report them to the Google groups sage-devel or sage-support.
You can also drop by in #sage-devel on freenode.

Source tarball:

http://sage.math.washington.edu/home/release/sage-4.3.4/sage-4.3.4.tar



On Fedora 12 x86_64 I had build failures with gd and atlas.

The gd issue could be resolved by putting /usr/include/iconv.h and 
/usr/bin/iconv aside.


make[9]: Entering directory 
`/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/atlas-3.8.3.p12/ATLAS-build/tune/sysinfo'
gcc -O -fomit-frame-pointer -fPIC -m64 -fno-tree-loop-optimize -c muladd.c
gcc -O -fomit-frame-pointer -fPIC -m64 -o xsmuladd muladd.o time.o
/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/atlas-3.8.3.p12/ATLAS-build/bin/ATLrun.sh 
/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/atlas-3.8.3.p12/ATLAS-build/tune/sysinfo xsmuladd

Finding granularity of timer:
  0: NFLOP=15999120, tim=0.024996
  0: NFLOP=63996480, tim=0.086986
  0: NFLOP=255985920, tim=0.349947
  0: NFLOP=1023943680, tim=1.400787
Done.
0.0:   Combined MULADD, lat=1, time=1.401787, mflop=730.455968
0.0:   Combined MULADD, lat=1, time=1.400787, mflop=730.977429
0.0:   Combined MULADD, lat=1, time=1.399787, mflop=731.499635
make[9]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/atlas-3.8.3.p12/ATLAS-build/tune/sysinfo'
make[9]: Entering directory 
`/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/atlas-3.8.3.p12/ATLAS-build/tune/sysinfo'
gcc -O -fomit-frame-pointer -fPIC -m64 -fno-tree-loop-optimize -c muladd.c
gcc -O -fomit-frame-pointer -fPIC -m64 -o xsmuladd muladd.o time.o
muladd.o: file not recognized: File truncated
collect2: ld returned 1 exit status
make[9]: *** [xsmuladd] Error 1


The atlas issue could be resolved by copying the relevant files from the system 
atlas.



The following tests failed:

sage -t  devel/sage/sage/modular/ssmod/ssmod.py # Killed/crashed
sage -t  devel/sage/sage/tests/benchmark.py # Killed/crashed
sage -t  devel/sage/sage/modular/modsym/modsym.py # Killed/crashed
sage -t  devel/sage/sage/modular/modsym/space.py # Killed/crashed
sage -t  devel/sage/sage/modular/modform/ambient.py # Killed/crashed
sage -t  devel/sage/sage/matrix/matrix_sparse.pyx # Killed/crashed
sage -t  devel/sage/sage/matrix/matrix_space.py # Killed/crashed
sage -t  devel/sage/sage/matrix/matrix2.pyx # Killed/crashed
sage -t  devel/sage/sage/coding/linear_code.py # Killed/crashed
sage -t  devel/sage/sage/coding/code_constructions.py # Killed/crashed
sage -t  devel/sage/sage/rings/finite_field_morphism.py # Killed/crashed
sage -t  devel/sage/sage/rings/finite_field_ntl_gf2e.pyx # 
Killed/crashed
sage -t  devel/sage/sage/rings/finite_field_ext_pari.py # Killed/crashed
sage -t  devel/sage/sage/rings/number_field/number_field_rel.py # 
Killed/crashed
sage -t  devel/sage/sage/rings/number_field/number_field.py # 
Killed/crashed
sage -t  
devel/sage/sage/rings/polynomial/polynomial_quotient_ring_element.py # 
Killed/crashed
sage -t  devel/sage/sage/modules/free_module.py # Killed/crashed
sage -t  devel/sage/sage/schemes/elliptic_curves/ell_point.py # 
Killed/crashed
sage -t  
devel/sage/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py # 
Killed/crashed
sage -t  
devel/sage/sage/schemes/hyperelliptic_curves/hyperelliptic_generic.py # 
Killed/crashed
sage -t  devel/sage/sage/groups/generic.py # Killed/crashed
--
Timings have been updated.
Total time for all tests: 1202.5 seconds
[j...@vrede sage-4.3.4]$

Mark the new comment # Killed/crashed
This replaces the earlier comment # Segfault

Jaap


--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Sage 4.3.4 released

[Jaap Spies]

William Stein wrote:

On Sat, Mar 20, 2010 at 1:05 PM, Jaap Spiesj.sp...@hccnet.nl  wrote:

Minh Nguyen wrote:


Hi folks,

Sage 4.3.4 was released on March 19, 2010. It is available at

http://www.sagemath.org/download.html

* About Sage (http://www.sagemath.org)

Sage is developed by volunteers and combines over 90 open source packages.
It is available for download from www.sagemath.org and its mirrors in
source or binary form. If you have any questions and/or problems,
please report them to the Google groups sage-devel or sage-support.
You can also drop by in #sage-devel on freenode.

Source tarball:

http://sage.math.washington.edu/home/release/sage-4.3.4/sage-4.3.4.tar



On Fedora 12 x86_64 I had build failures with gd and atlas.

The gd issue could be resolved by putting /usr/include/iconv.h and
/usr/bin/iconv aside.



FYI:  This gd issue also happens on eno, which is the main build
machine on Skynet (our build farm), which is a Fedora 12 machine.
This is probably the first release of Sage ever that doesn't work on
eno.   Oops.



I first warned on sage-4.3.4.alpha1 I had this gd issue. I had no time
to investigate. I should have opened a blocker ticket.


I'm not sure how we managed to do a release without testing that it
even works on eno (skynet).   Hmm.



:-(


I like all the talk about checklists on sage-devel recently:
checklists are good, and would prevent this sort of thing.



+1

I think the Fedora 12 distro is somehow broken. Not only Fedora, but
other distros failed as well.

But this would have been shown in an adequate test.

Jaap


--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Sage 4.3.4.rc0 builds ok on Solaris 10 (SPARC)

[Jaap Spies]

Dr. David Kirkby wrote:

Robert Bradshaw wrote:

[snipped]

For spkgs, changes to shell scripts, etc. a it is much more important
to test on a wide variety of platforms. Fortunately, most
contributions are plain vanilla Python/Cython.

Thanks for bringing this up, this is an example of what separates (in
my mind) the sage-build level stuff from the sage-devel level stuff.

- Robert



What you say about 'most' being Python/Cython is undoubtedly true.

However, there is still a significant number of .spkg updates each release.

The recent update to R, which screwed up on Solaris, resulted in iconv
being added to Sage rather hurriedly (directly as a standard package).
Iconv seems to be the cause of some problems on Fedora building gd,
though it appears it can be solved by removing an option to gd's
configure script.


Whoever introduced this package or/and the one who gave it a positive review
should have tested this change on all supported platforms :)!?

Moreover the releasemanager should have tested it on all available machines.



IMHO, the updates to .spkg files are not being done carefully enough.


+1

Jaap


--
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-devel
URL: http://www.sagemath.org

To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or 
reply to this email with the words REMOVE ME as the subject.

[sage-devel] Re: Sage 4.3.4.rc0 released

[Jaap Spies]

Minh Nguyen wrote:

Hi folks,

This release candidate cleans up warnings resulting from building the
Sage documentation. If there are no show stoppers, then this release
is considered the final release candidate.



Sorry, but once again the build failed:

gcc -fPIC -g -I/home/jaap/downloads/sage-4.3.4.rc0/local/include -I/home/jaap/downloads/sage-4.3.4.rc0/local/include/freetype2/ -Wl,--rpath 
-Wl,/home/jaap/downloads/sage-4.3.4.rc0/local/lib -o .libs/gd2copypal gd2copypal.o  -L/home/jaap/downloads/sage-4.3.4.rc0/local/lib ./.libs/libgd.so 
-lfontconfig /home/jaap/downloads/sage-4.3.4.rc0/local/lib/libfreetype.so /home/jaap/downloads/sage-4.3.4.rc0/local/lib/libpng12.so -lz -lm -Wl,--rpath 
-Wl,/home/jaap/downloads/sage-4.3.4.rc0/local/lib

./..libs/libgd.so/:. undefined referencelibs /to libgd.so`: libiconv'undefined
 .reference/ .tolibs /`libgd.solibiconv:' undefined
 .reference/ .tolibs /`libgd.so:libiconv_close '
undefined. /reference. libsto/ `libgd.so:libiconv_close 'undefined
 .reference/ .tolibs /`libgd.solibiconv_open:'
undefined reference to `libiconv_open'
collect2: collect2: ld returned 1 exit status
ld returned 1 exit status
make[4]: *** [gdtopng] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: *** [annotate] Error 1
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [gdparttopng] Error 1
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [gd2copypal] Error 1
make[4]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/gd-2.0.35.p4/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/gd-2.0.35.p4/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/gd-2.0.35.p4/src'
Error building gd.

real0m8.984s
user0m7.703s
sys 0m5.884s
sage: An error occurred while installing gd-2.0.35.p4
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/jaap/downloads/sage-4.3.4.rc0/install.log.  Describe your computer, 
operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/gd-2.0.35.p4 and type 'make 
check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/home/jaap/downloads/sage-4.3.4.rc0/spkg/build/gd-2.0.35.p4'  
'/home/jaap/downloads/sage-4.3.4.rc0/sage' -sh)
When you are done debugging, you can type exit to leave the
subshell.
make[1]: *** [installed/gd-2.0.35.p4] Error 1
make[1]: Leaving directory `/home/jaap/downloads/sage-4.3.4.rc0/spkg'

real11m4.109s
user14m5.462s
sys 2m28.947s
Error building Sage.

This is on Fedora 12 64 bit.

Jaap

--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage 4.3.4.alpha1 released!

[Jaap Spies]

Mike Hansen wrote:

Hello all,

This release should fix many of the outstanding issues on Solaris as
well as some more of the combinatorics code from Sage Days 20.

Source tarball:

http://sage.math.washington.edu/home/release/sage-4.3.4.alpha1/sage-4.3.4.alpha1.tar

Binary for sage.math:

http://sage.math.washington.edu/home/release/sage-4.3.4.alpha1/sage-4.3.4.alpha1-sage.math.washington.edu-x86_64-Linux.tar.gz

Upgrade path:

http://sage.math.washington.edu/home/release/sage-4.3.4.alpha1/sage-4.3.4.alpha1/



Hi, I had a stange build failure on Fedora 12 64 bit. Never had this before:

[j...@vrede ~]$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla 
--enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions 
--enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux

Thread model: posix
gcc version 4.4.3 20100127 (Red Hat 4.4.3-4) (GCC)


gcc -fPIC -g -I/home/jaap/downloads/sage-4.3.4.alpha1/local/include -I/home/jaap/downloads/sage-4.3.4.alpha1/local/include/freetype2/ -Wl,--rpath 
-Wl,/home/jaap/downloads/sage-4.3.4.alpha1/local/lib -o .libs/gdtopng gdtopng.o  -L/home/jaap/downloads/sage-4.3.4.alpha1/local/lib ./.libs/libgd.so 
-lfontconfig /home/jaap/downloads/sage-4.3.4.alpha1/local/lib/libfreetype.so /home/jaap/downloads/sage-4.3.4.alpha1/local/lib/libpng12.so -lz -lm -Wl,--rpath 
-Wl,/home/jaap/downloads/sage-4.3.4.alpha1/local/lib

./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [annotate] Error 1
make[4]: *** Waiting for unfinished jobs
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [gd2copypal] Error 1
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [gdparttopng] Error 1
make[4]: *** [pngtogd] Error 1
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [gd2topng] Error 1
./.libs/libgd.so: undefined reference to `libiconv'
./.libs/libgd.so: undefined reference to `libiconv_close'
./.libs/libgd.so: undefined reference to `libiconv_open'
collect2: ld returned 1 exit status
make[4]: *** [gdtopng] Error 1
make[4]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.alpha1/spkg/build/gd-2.0.35.p4/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.alpha1/spkg/build/gd-2.0.35.p4/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/jaap/downloads/sage-4.3.4.alpha1/spkg/build/gd-2.0.35.p4/src'
Error building gd.

Ideas?

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Is CMake OK for a standard spkg?

[Jaap Spies]

Bjarke Hammersholt Roune wrote:

If Singular moves to CMake that could seriously be a pain for us,
since we'll likely have to add cmake as a standard package to Sage,
which will of course involves headaches.


OK - thanks for the information. There would be advantages to CMake,
too, e.g. it works on lots of platforms like Solaris, Linux and
Windows according to

   http://en.wikipedia.org/wiki/CMake



An experimental spkg can be found here:

http://boxen.math.washington.edu/home/jsp/SPKGS/ETS/cmake-2.6.2.spkg

An update to cmake-2.8 is easy.

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Bipartite graphs in Sage

[Jaap Spies]

Jason Grout wrote:

On 02/27/2010 01:41 PM, Rob Beezer wrote:




This is in the BipartiteGraph class as reduced_adjacency_matrix().
I can't recall ever seeing this matrix given a name, so I don't know
if this is how one would expect to find it. In the research for your
graph theory book have you learned what others call it?



There was some discussion several years ago about what this should be
called. I believe this term came from Richard Brualdi's combinatorial
matrix theory book (I remember running down the hall to my advisor's
office to look it up! :), but my memory may be inaccurate.



You remember correctly a discussion on IRC. I offered to put a scan of
the relevant page on line.

Jaap




Thanks,

Jason





--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Bipartite graphs in Sage

[Jaap Spies]

David Joyner wrote:



There was some discussion several years ago about what this should be
called. I believe this term came from Richard Brualdi's combinatorial
matrix theory book (I remember running down the hall to my advisor's
office to look it up! :), but my memory may be inaccurate.



You remember correctly a discussion on IRC. I offered to put a scan of
the relevant page on line.


I'm interested. Please do.


Hold on. I'm scanning.

Jaap





Jaap




Thanks,

Jason





--
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-devel
URL: http://www.sagemath.org






--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Bipartite graphs in Sage

[Jaap Spies]

David Joyner wrote:



There was some discussion several years ago about what this should be
called. I believe this term came from Richard Brualdi's combinatorial
matrix theory book (I remember running down the hall to my advisor's
office to look it up! :), but my memory may be inaccurate.



You remember correctly a discussion on IRC. I offered to put a scan of
the relevant page on line.


I'm interested. Please do.



I will not put this scan in the open. My lady friend who happens to be a lawyer,
advised me so. I'll send it by email.

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage 4.3.3 (with patches) builds on Solaris 10 (SPARC) !!!

[Jaap Spies]

Dr. David Kirkby wrote:

I believe I have *finally* got the latest Sage (with some patches) to
build on Solaris 10 (SPARC).

Feel free to see at

http://redstart.drkirkby.co.uk:8000/

I'd be interested if it works for others.



1+1 gives:  

Traceback (click to the left of this block for traceback)
...
NameError: name '_interact_' is not defined

Traceback (most recent call last):
  File stdin, line 1, in module
  File _sage_input_3.py, line 8, in module
_interact_.SAGE_CELL_ID=1
NameError: name '_interact_' is not defined

I'm sorry,

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage 4.3.3 (with patches) builds on Solaris 10 (SPARC) !!!

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

Dr. David Kirkby wrote:

I believe I have *finally* got the latest Sage (with some patches) to
build on Solaris 10 (SPARC).

Feel free to see at

http://redstart.drkirkby.co.uk:8000/

I'd be interested if it works for others.



1+1 gives:
Traceback (click to the left of this block for traceback)
...
NameError: name '_interact_' is not defined

Traceback (most recent call last):
File stdin, line 1, in module
File _sage_input_3.py, line 8, in module
_interact_.SAGE_CELL_ID=1
NameError: name '_interact_' is not defined

I'm sorry,

Jaap




Yes, I thought it was too good to be true. I could log in ok.

Any ideas what might be the cause of that?



No, not for the moment. It's late here and at your place. Do you ever sleep?

I'm off for now at 02:55

Jaap


Dave





--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Solaris port / Implement 2-isogeny descent / or Fix ???

[Jaap Spies]

Dr. David Kirkby wrote:

Robert Miller wrote:

David,


I don't know how important #6583 it so Sage, or how important William
sees a Solaris port as important, but at the minute, these two
appear to be
mutually exclusive.


I don't know if I agree with that. Have you tried tinkering with the
build flags on t2? We had several different suggestions of
modifications to make to the build flags, e.g. for ratpoints... Have
any of these been tested yet?





I have put some comments on the trac ticket

http://trac.sagemath.org/sage_trac/ticket/6583

but in essence, I've tried building ratpoints with

* -D_XOPEN_SOURCE=600
* -std=c99
* -std=c99 -D_XOPEN_SOURCE=600



There seems to be a lot of issues with _XOPEN_SOURCE and Solaris, see:

http://bugs.python.org/issue1759169

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Solaris port / Implement 2-isogeny descent / or Fix ???

[Jaap Spies]

Mike Hansen wrote:

On Wed, Feb 24, 2010 at 2:05 PM, Jaap Spiesj.sp...@hccnet.nl  wrote:

There seems to be a lot of issues with _XOPEN_SOURCE and Solaris, see:

http://bugs.python.org/issue1759169


 From this discussion, it seems that we should strip out

_XOPEN_SOURCE_EXTENDED
_XOPEN_SOURCE
_POSIX_C_SOURCE

when building Python on Solaris.  In that discussion, there's a patch
to configure.in or a couple of Perl commands.  It seems like this
would be a good thing to try.



That's what Sun does in building python.

There is a related problem when building extensions for python

building c++ extensions we need #define _XOPEN_SOURCE_EXTENTED 0,
but building c extensions we need #define _XOPEN_SOURCE_EXTENTED 1

This is what I found on Open Solaris.

Jaap



--Mike




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Vpython?

[Jaap Spies]

William Stein wrote:

On Wed, Feb 24, 2010 at 8:18 AM, Arthur Gaerg...@math.harvard.edu  wrote:

William,

Curt was just asking me about Vpython cause I gather some of his undergrads
showed him some cool mathematical graphics utilizing it.  He thinks they
might use it in a CS course or two here.

What's the deal with Vpython?  It's not already in SAGE, I don't think?


VPython is a distribution of PYthon with some of the other components
of Sage (e.g., numpy) and a library (that uses something called Boost)
to provide interactive 3d capabilities.  It's useful for 3d graphics.

Yes, VPython is not in Sage.  Nobody has mentioned it seriously on any
Sage mailing lists for about a year, when Jaap made a highly
experimental spkg which would on some versions of Linux, which he
posted here:

http://sage.math.washington.edu/home/jsp/SPKGS/VPython/


Is there a good reason?


It's difficult.


Do you have the equivalent functionality in some other way?


No.  The main functionality that VPython evidently provides is truly
interactive 3d graphics.Sage doesn't have that.



I used VPython to teach programming to mechanical engineering students
(they used to get a C++ programming course :( )

The main advantage of VPython is that visualisation is a side effect.
type sphere(centre, radius) and magically there is a sphere visualized.

Some pictures: http://picasaweb.google.nl/j.spies88/Vpython#
This was sage-2.10.alpha2 :)



Curt's wanting to get it on all our machines, which I tend to resist since
it will mean upgrading, maintaining it, etc. in perpetuity and adds to
administrative complexity, and because I've had noone else ever ask for it.
  For things like that I tend to put it on an personal user's computer and
wait to see if there's ever any more call for it.

What do you think?


I've never used VPython, so I'm not sure what to say.   Probably
getting VPython to actually work cross-platform in Sage would be quite
difficult, and that it will almost certainly never be included
standard in Sage.  It could be an optional spkg at some point.



Optional at the most. There is a OSX version, but I never saw any effort
to port it to Solaris, just to mention an issue.


Jaap



  -- William



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: c++ question related to porting sage to Open Solaris

[Jaap Spies]

Dima Pasechnik wrote:

http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6395191
It's a bug, known for 4 years, and nobody is fixing it, it seems...



See: http://bugs.python.org/issue1759169

for some further reading.

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: c++ question related to porting sage to Open Solaris

[Jaap Spies]

David Kirkby wrote:

On 1 February 2010 19:29, Jaap Spiesj.sp...@hccnet.nl  wrote:

Jaap Spies wrote:


Hi c++ experts,

My C++ is a little bit rusty, so I'll ask here.

Building matplotlib, pynac, scipy and scipysandbox fail in the end with




A build log can be found here:

http://boxen.math.washington.edu/home/jsp/tests/matplotlib_build.log

I'm coming closer but I don't understand the issues completely.

Jaap


I'm a  railway station, so can't really start looking in the source
code. But the man page suggests

#includewchar.h

would be needed. If it is not included, then I would be tempted to
conditionally include that on OpenSolaris.



It is included, but in the wrong way. I'm getting closer:

Try this on Open Solaris:

#define _XOPEN_SOURCE_EXTENDED 1
#include iostream

int main() { return 0; }

in say t.cpp

$ g++ -m64 t.cpp
In file included from 
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/postypes.h:42,
 from 
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/iosfwd:42,
 from 
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/ios:39,
 from 
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/ostream:40,
 from 
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/iostream:40,
 from t.cpp:2:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:143:
 error: ‘::btowc’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:148:
 error: ‘::fwide’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:149:
 error: ‘::fwprintf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:150:
 error: ‘::fwscanf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:153:
 error: ‘::mbrlen’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:154:
 error: ‘::mbrtowc’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:155:
 error: ‘::mbsinit’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:156:
 error: ‘::mbsrtowcs’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:159:
 error: ‘::swprintf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:160:
 error: ‘::swscanf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:162:
 error: ‘::vfwprintf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:166:
 error: ‘::vswprintf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:170:
 error: ‘::vwprintf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:174:
 error: ‘::wcrtomb’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:185:
 error: ‘::wcsrtombs’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:195:
 error: ‘::wctob’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:196:
 error: ‘::wmemcmp’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:197:
 error: ‘::wmemcpy’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:198:
 error: ‘::wmemmove’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:199:
 error: ‘::wmemset’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:200:
 error: ‘::wprintf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:201:
 error: ‘::wscanf’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:205:
 error: ‘::wcsstr’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:206:
 error: ‘::wmemchr’ has not been declared
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/cwchar:
 In function ‘wchar_t* std::wcsstr(wchar_t*, const wchar_t*)’:
/usr/local/gcc-4.4.2

[sage-devel] Re: Can one run all doctests from the GUI ?

[Jaap Spies]

Dr. David Kirkby wrote:

Dr. David Kirkby wrote:


[...]



However, on OpenSolaris, the issue is more severe. Both Jaap and William
will confirm that the test in python for hashlib has failed.



To a certain extend. I had opensll installed on Open Solaris, but more than once
on different places. That causes problems installing python. Once I cleared
this, I could build a proper python having hashlib available.


Jaap




Dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Rips complex in Sage?

[Jaap Spies]

kcrisman wrote:



It also says it needs Cmake


Cmake 2.4.8 is actually a current experimental spkg, but Dionysos says
it needs 2.6 or above.



You can find one here:
http://boxen.math.washington.edu/home/jsp/cmake-2.6.2.spkg

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Rips complex in Sage?

[Jaap Spies]

kcrisman wrote:



On Feb 5, 5:47 am, Jaap Spiesj.sp...@hccnet.nl  wrote:

kcrisman wrote:


It also says it needs Cmake



Cmake 2.4.8 is actually a current experimental spkg, but Dionysos says
it needs 2.6 or above.


You can find one here:http://boxen.math.washington.edu/home/jsp/cmake-2.6.2.spkg


This should be put on the experimental page (Harald?) because it
installed fine.  Is there any way to check it?



Last year I made a lot of experimental packages. They didn't made it in
for several reasons. See: http://boxen.math.washington.edu/home/jsp/SPKGS/
And lost interest somehow!

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Rips complex in Sage?

[Jaap Spies]

Harald Schilly wrote:

On Feb 5, 6:59 pm, kcrismankcris...@gmail.com  wrote:

This should be put on the experimental page (Harald?) because it
installed fine.


Ok, together with a short description text, ... but ...

On Feb 5, 7:51 pm, Jaap Spiesj.sp...@hccnet.nl  wrote:

Last year I made a lot of experimental packages. They didn't made it in
for several reasons.


What are the reasons for not including an experimental package? What
are the criteria?



At first William had rather strong criteria, like building on sage.math.
Later this was dropped. And mabshoff was about to put them up in
experimental. The rest is history. Some of the packages like mayavi2
were picked up by Ondrej, but I don't see the follow up in experimental.

If there is some interest I can put some effort in it. As it is winter
and sailing is impossible here :)

Jaap



H




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Where is the log file for the tests kept?

[Jaap Spies]

Dr. David Kirkby wrote:

If I run

./sage -t devel

where is the log file kept? In particular, where is it kept if you use a
global install of Sage, and so don't have write access to any
directories under $SAGE_ROOT?



just do ./sage -t devel 21 | tee /tmp/testdevel.log

or so.

Jaap




I seem to have spent a lot of time running tests, and have no record of
the result, which is annoying when they scroll off the screen.

dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Error building v4.3.1 on Fedora 12 (32-bit)

[Jaap Spies]

Gokhan Sever wrote:



On Jan 24, 10:59 am, gsevergokhanse...@gmail.com  wrote:

Hello,

Am I getting the similar error of FC12 (i686) binaries not pushed in
the download section?

[gse...@ccn sage-4.3.1]$ uname -a
Linux ccn 2.6.31.9-174.fc12.i686.PAE #1 SMP Mon Dec 21 06:04:56 UTC
2009 i686 i686 i386 GNU/Linux

[gse...@ccn sage-4.3.1]$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 23
model name  : Intel(R) Core(TM)2 Duo CPU T9300  @ 2.50GHz
stepping: 6
cpu MHz : 2500.000
cache size  : 6144 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est
tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi
flexpriority
bogomips: 4986.77
clflush size: 64
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 23
model name  : Intel(R) Core(TM)2 Duo CPU T9300  @ 2.50GHz
stepping: 6
cpu MHz : 800.000
cache size  : 6144 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est
tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi
flexpriority
bogomips: 4986.03
clflush size: 64
power management:

Successfully installed r-2.9.2
Running the test suite.
make[2]: Entering directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src'
make[3]: Entering directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src/tests'
make[4]: Entering directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src/tests'
make[4]: warning: -jN forced in submake: disabling jobserver mode.
make[5]: Entering directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src/tests/Examples'
make[5]: warning: -jN forced in submake: disabling jobserver mode.

Collecting examples for package ‘base’
Running examples in package ‘base’

Collecting examples for package ‘tools’
Running examples in package ‘tools’

Collecting examples for package ‘utils’
Running examples in package ‘utils’
Error: testing 'utils' failed
Execution halted
make[5]: *** [test-Examples-Base] Error 1
make[5]: Leaving directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src/tests/Examples'
make[4]: *** [test-Examples] Error 2
make[4]: Leaving directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src/tests'
make[3]: *** [test-all-basics] Error 1
make[3]: Leaving directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src/tests'
make[2]: *** [check] Error 2
make[2]: Leaving directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg/build/r-2.9.2/src'
Error while running the R testsuite ... exiting
*
Error testing package ** r-2.9.2 **
*
sage: An error occurred while testing r-2.9.2
Please email sage-develhttp://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/gsever/Desktop/python-repo/sage-4.3.1/install.log.  Describe
your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/gsever/Desktop/python-repo/sage-4.3.1/spkg/build/r-2.9.2 and
type 'make check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/home/gsever/Desktop/python-repo/sage-4.3.1/spkg/build/r-2.9.2'
  '/home/gsever/Desktop/python-repo/sage-4.3.1/sage' -sh)
When you are done debugging, you can type exit to leave the
subshell.
make[1]: *** [installed/r-2.9.2] Error 1
make[1]: Leaving directory `/home/gsever/Desktop/python-repo/
sage-4.3.1/spkg'

real124m58.197s
user125m3.126s
sys 11m14.695s
Error building Sage.


Testing sage-4.3.2.rc0 with export SAGE_CHECK=yes yields a different
set of errors this time:

Successfully installed pyprocessing-0.52.p0


OK, pyprocessing is in principle out iirc.

Are you building with SAGE_CHECK = something non empty?
I think this will fail not only here.

I would do a unset SAGE_CHECK,
and 

[sage-devel] Re: c++ question related to porting sage to Open Solaris

[Jaap Spies]

Jaap Spies wrote:

Hi c++ experts,

My C++ is a little bit rusty, so I'll ask here.

Building matplotlib, pynac, scipy and scipysandbox fail in the end with




A build log can be found here:

http://boxen.math.washington.edu/home/jsp/tests/matplotlib_build.log

I'm coming closer but I don't understand the issues completely.

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Should updates only be permitted with same gcc version?

[Jaap Spies]

Dr. David Kirkby wrote:
[snipped]


Fair enough. I mis understood this. But I still think we should not let
someone upgrade Sage with a version different to what they used to build
it.



-1

I've a system wide install of sage upgraded 86 times:
[r...@paix installed]# ls sage-*
sage-1.5.1.2  sage-2.1.0.1  sage-2.4.1.2  sage-2.8.12   sage-2.8.6
sage-3.0.6  sage-4.0
sage-1.5.3sage-2.10.1   sage-2.4.2sage-2.8.13   sage-2.8.7sage-3.1  
  sage-4.0.1
sage-1.6  sage-2.10.2   sage-2.5  sage-2.8.14   sage-2.8.8
sage-3.1.1  sage-4.0.2
sage-1.6.1sage-2.10.3   sage-2.5.0.2  sage-2.8.15   sage-2.8.8.1  
sage-3.1.2  sage-4.1
sage-1.7  sage-2.10.4   sage-2.5.1sage-2.8.2sage-2.8.9
sage-3.1.4  sage-4.1.1
sage-1.7.1sage-2.11 sage-2.5.2sage-2.8.3sage-2.9  sage-3.2  
  sage-4.1.2
sage-1.8  sage-2.1.3sage-2.5.3sage-2.8.3.3  sage-2.9.1.1  
sage-3.2.1  sage-4.2
sage-1.8.1sage-2.1.3.1  sage-2.6  sage-2.8.3.6  sage-2.9.2
sage-3.2.2  sage-4.2.1
sage-1.8.2.1  sage-2.1.4sage-2.7  sage-2.8.4sage-3.0  
sage-3.2.3  sage-4.3
sage-1.9  sage-2.2  sage-2.7.3sage-2.8.4.1  sage-3.0.2sage-3.3
sage-2.0  sage-2.3  sage-2.8  sage-2.8.4.2  sage-3.0.3sage-3.4
sage-2.1  sage-2.4  sage-2.8.10   sage-2.8.5sage-3.0.4sage-3.4.1
sage-2.10 sage-2.4.1sage-2.8.11   sage-2.8.5.1  sage-3.0.5sage-3.4.2
[r...@paix installed]# ls sage-* | wc
 87  87 945

Only last time things went wrong in upgrading to sage-4.3.1.

I have to look into that.

Jaap



Dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: c++ question related to porting sage to Open Solaris

[Jaap Spies]

Jaap Spies wrote:

Hi c++ experts,

My C++ is a little bit rusty, so I'll ask here.

Building matplotlib, pynac, scipy and scipysandbox fail in the end with


/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
In static member function ‘static int
std::char_traitswchar_t::compare(const wchar_t*, const wchar_t*,
size_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:330:
error: ‘wmemcmp’ was not declared in this scope
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
In static member function ‘static const wchar_t*
std::char_traitswchar_t::find(const wchar_t*, size_t, const wchar_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:338:
error: invalid conversion from ‘const wchar_t*’ to ‘wchar_t*’
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:338:
error: initializing argument 1 of ‘wchar_t* std::wmemchr(wchar_t*,
wchar_t, size_t)’
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
In static member function ‘static wchar_t*
std::char_traitswchar_t::move(wchar_t*, const wchar_t*, size_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:342:
error: ‘wmemmove’ was not declared in this scope
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
In static member function ‘static wchar_t*
std::char_traitswchar_t::copy(wchar_t*, const wchar_t*, size_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:346:
error: ‘wmemcpy’ was not declared in this scope
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
In static member function ‘static wchar_t*
std::char_traitswchar_t::assign(wchar_t*, size_t, wchar_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:350:
error: ‘wmemset’ was not declared in this scope



Any thoughts?

Jaap





Ok, I seem to be on the ban list of everybody? Please help.

jaap





--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: c++ question related to porting sage to Open Solaris

[Jaap Spies]

Minh Nguyen wrote:

Hi Jaap,

On Mon, Feb 1, 2010 at 8:20 AM, Jaap Spiesj.sp...@hccnet.nl  wrote:

SNIP


Ok, I seem to be on the ban list of everybody?


Certainly not. Not on mine.




Thanks!


Please help.


I'm very new with OpenSolaris. But is there an OpenSolaris machine
somewhere I could use to help?




I use Open Solaris in VirtualBox, so be welcome.

My question is c++ related. I did my search, but found no solution yet.

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] c++ question related to porting sage to Open Solaris

[Jaap Spies]

Hi c++ experts,

My C++ is a little bit rusty, so I'll ask here.

Building matplotlib, pynac, scipy and scipysandbox fail in the end with


/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
 In static member function ‘static int std::char_traitswchar_t::compare(const 
wchar_t*, const wchar_t*, size_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:330:
 error: ‘wmemcmp’ was not declared in this scope
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
 In static member function ‘static const wchar_t* 
std::char_traitswchar_t::find(const wchar_t*, size_t, const wchar_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:338:
 error: invalid conversion from ‘const wchar_t*’ to ‘wchar_t*’
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:338:
 error:   initializing argument 1 of ‘wchar_t* std::wmemchr(wchar_t*, wchar_t, 
size_t)’
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
 In static member function ‘static wchar_t* 
std::char_traitswchar_t::move(wchar_t*, const wchar_t*, size_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:342:
 error: ‘wmemmove’ was not declared in this scope
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
 In static member function ‘static wchar_t* 
std::char_traitswchar_t::copy(wchar_t*, const wchar_t*, size_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:346:
 error: ‘wmemcpy’ was not declared in this scope
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:
 In static member function ‘static wchar_t* 
std::char_traitswchar_t::assign(wchar_t*, size_t, wchar_t)’:
/usr/local/gcc-4.4.2/lib/gcc/i386-pc-solaris2.11/4.4.2/../../../../include/c++/4.4.2/bits/char_traits.h:350:
 error: ‘wmemset’ was not declared in this scope



Any thoughts?

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Should sage-env exit if CFLAGS is set ?

[Jaap Spies]

Dr. David Kirkby wrote:

We know from recent discussions over sage-env and the hassles that

http://trac.sagemath.org/sage_trac/ticket/7818

caused, that setting CFLAGS, CXXFLAGS etc globally will cause a build
failure in Sage. It would therefore seem sensible that we exit with an
error message if someone sets CFLAGS when building Sage.



I think it is more sensible that the spkgs involved do an 'unset CFLAGS', etc..
Laying the resposibilities were they belong.

A lot of spkgs will not built in 64 bit mode unless CFLAGS has a sensible flag.

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Should sage-env exit if CFLAGS is set ?

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

Dr. David Kirkby wrote:

We know from recent discussions over sage-env and the hassles that

http://trac.sagemath.org/sage_trac/ticket/7818

caused, that setting CFLAGS, CXXFLAGS etc globally will cause a build
failure in Sage. It would therefore seem sensible that we exit with an
error message if someone sets CFLAGS when building Sage.



I think it is more sensible that the spkgs involved do an 'unset
CFLAGS', etc..
Laying the resposibilities were they belong.

A lot of spkgs will not built in 64 bit mode unless CFLAGS has a
sensible flag.

Jaap


I would normally agree with you, but think this could be risky.



Risky? What is wrong with cython unset CFLAGS?

I plea to put responsibilities where they belon.



Having had my fingers burnt once over setting CFLAGS globally, I would
avoid that at all costs. Which is why I wondered whether we should check
they are not set, to avoid any surprises later on.



Quite a few spkg-install are a simply: python setup.py install.
They fail on Open Solaris x64 if CFLAGS does not include -m64.



As I proposed the other day, which William liked, we set

SAGE_COMMON_CFLAGS

to a sensible set of compiler flags, suitable for most packages.
spkg-install then use

CFLAGS=SAGE_COMMON_CFLAGS
export CFLAGS

That way, CFLAGS is not set globally, but any package can get a sensible
set if they choose to.

This may not be the most convenient approach, but it is the most risk-free.



Future music!

Jaap




Dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Should sage-env exit if CFLAGS is set ?

[Jaap Spies]

Robert Bradshaw wrote:

On Jan 29, 2010, at 1:52 PM, Jaap Spies wrote:


Dr. David Kirkby wrote:

Jaap Spies wrote:

Dr. David Kirkby wrote:

We know from recent discussions over sage-env and the hassles that

http://trac.sagemath.org/sage_trac/ticket/7818

caused, that setting CFLAGS, CXXFLAGS etc globally will cause a build
failure in Sage. It would therefore seem sensible that we exit with an
error message if someone sets CFLAGS when building Sage.



I think it is more sensible that the spkgs involved do an 'unset
CFLAGS', etc..
Laying the resposibilities were they belong.

A lot of spkgs will not built in 64 bit mode unless CFLAGS has a
sensible flag.

Jaap


I would normally agree with you, but think this could be risky.



Risky? What is wrong with cython unset CFLAGS?

I plea to put responsibilities where they belon.



Having had my fingers burnt once over setting CFLAGS globally, I would
avoid that at all costs. Which is why I wondered whether we should check
they are not set, to avoid any surprises later on.



Quite a few spkg-install are a simply: python setup.py install.
They fail on Open Solaris x64 if CFLAGS does not include -m64.


There's nothing special about Cython, it basically is just another
python setup.py install package. Are you saying we should unset CFLAGS
for all of those? I seems extensions should be compiled with -m64 iff
Python is compiled with -m64 (is it?).

Can you try running

  import distutils.sysconfig
  distutils.sysconfig.get_config_var('CFLAGS')

in your build of Python?



j...@opensolaris:~/Downloads/sage-4.3.2.alpha0$ ./sage -python
Python 2.6.4 (r264:75706, Jan 27 2010, 22:37:41)
[GCC 4.4.2] on sunos5
Type help, copyright, credits or license for more information.
 import distutils.sysconfig
 distutils.sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g  -O3 -Wall -Wstrict-prototypes'


As you see no -m64 as would be appropriate.

Jaap



- Robert





--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Should sage-env exit if CFLAGS is set ?

[Jaap Spies]

Robert Bradshaw wrote:

On Jan 29, 2010, at 2:59 PM, Jaap Spies wrote:


Robert Bradshaw wrote:

On Jan 29, 2010, at 1:52 PM, Jaap Spies wrote:


Quite a few spkg-install are a simply: python setup.py install.
They fail on Open Solaris x64 if CFLAGS does not include -m64.


There's nothing special about Cython, it basically is just another
python setup.py install package. Are you saying we should unset CFLAGS
for all of those? I seems extensions should be compiled with -m64 iff
Python is compiled with -m64 (is it?).

Can you try running

 import distutils.sysconfig
 distutils.sysconfig.get_config_var('CFLAGS')

in your build of Python?



j...@opensolaris:~/Downloads/sage-4.3.2.alpha0$ ./sage -python
Python 2.6.4 (r264:75706, Jan 27 2010, 22:37:41)
[GCC 4.4.2] on sunos5
Type help, copyright, credits or license for more information.
 import distutils.sysconfig
 distutils.sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes'


As you see no -m64 as would be appropriate.


Hmm did Python not need an -m64 to build in 64-bit mode then?



Yes it needed -m64. As p5 get screwed up by William I put -m64 in at
a place I think was appropriate.

Maybe we have to sort out the p5 question first. David Kirkby had a patch,
which was overwritten by a following patch p5.

I made python build with 64 bit support on my Open Solaris.

Jaap



- Robert





--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Trac #7761 - was not integrated, despite trac says it is.

[Jaap Spies]

Dr. David Kirkby wrote:

http://trac.sagemath.org/sage_trac/ticket/7761

Python 2.6.2.p4 faills to build on OpenSolaris

is a fix of mine for python. But despite being shown as merged in
sage-4.3.1.alpha2, it is not in sage 4.3.1

Dave




I hope someone will step forward to resolve this mess!

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Trac #7761 - was not integrated, despite trac says it is.

[Jaap Spies]

Dr. David Kirkby wrote:

http://trac.sagemath.org/sage_trac/ticket/7761

Python 2.6.2.p4 faills to build on OpenSolaris

is a fix of mine for python. But despite being shown as merged in
sage-4.3.1.alpha2, it is not in sage 4.3.1



Without setting CFLAGS=-64 and CXXFLAGS=-m64 globally Python fail to build

I hacked it in my build.

There should be a ticket to solve this problem. Last night (and today)
I forgot about it. Sorry.

Jaap



Dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Trac #7761 - was not integrated, despite trac says it is.

[Jaap Spies]

Dr. David Kirkby wrote:

http://trac.sagemath.org/sage_trac/ticket/7761

Python 2.6.2.p4 faills to build on OpenSolaris

is a fix of mine for python. But despite being shown as merged in
sage-4.3.1.alpha2, it is not in sage 4.3.1



Your python-2.6.2.p5.spkg was replaced by a p5 package from William:

== Changelog ==

=== python-2.6.4.p5 (William Stein, Jan 20, 2010) ===
* Fix bug on Itanium introduced by typo by Craig in #60.  See trac 8020.

Jaap




Dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Trac #7761 - was not integrated, despite trac says it is.

[Jaap Spies]

Robert Miller wrote:

I remember merging both of those. :) Sorry guys, my bad.


Looks like once again I've spoken too soon. I guess I only merged the
first fix..




At one time there were two release managers :)

Jaap



--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Exhibit booth for 2011 joint meetings

[Jaap Spies]

William Stein wrote:

On Wed, Jan 27, 2010 at 7:24 AM, kcrismankcris...@gmail.com  wrote:

I think it would be very useful in following up to the PREP workshop
as well.  I think I can commit to staffing it for a significant period
of time, though I do not have a funding source.  If 50 people each
committed $10 to the Sage foundation for this purpose, that would get
us halfway there, though.

- kcrisman


UW sends out personal thank you letters that certify that you've made
a tax-deductible contribution to every single contribution to the Sage
Foundation.

It's *really* easy to donate with a credit card:


https://secure.gifts.washington.edu/as_mathematics/gift.asp?page=makeCode=MATSAG



I can confirm. Even from Europe you can select your country. There is one
problem left. In The Netherlands we have a zip code with a space like:
7824 BM. The form doesn't handle that correctly.

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage 4.3.2.alpha0 test failures on Fedora 12

[Jaap Spies]

Gokhan Sever wrote:

Hello,

uname -a
Linux ccn 2.6.31.9-174.fc12.i686.PAE #1 SMP Mon Dec 21 06:04:56 UTC
2009 i686 i686 i386 GNU/Linux

Getting many errors after ./sage -testall

--
The following tests failed:

sage -t  devel/sage/sage/modules/free_module.py # Segfault
sage -t  devel/sage/sage/coding/code_constructions.py # Segfault
sage -t  devel/sage/sage/coding/linear_code.py # Segfault
sage -t  devel/sage/sage/groups/generic.py # Segfault
sage -t  devel/sage/sage/modular/ssmod/ssmod.py # Segfault
sage -t  devel/sage/sage/modular/modform/ambient.py # Segfault
sage -t  devel/sage/sage/modular/modsym/space.py # Segfault
sage -t  devel/sage/sage/modular/modsym/modsym.py # Segfault
sage -t  devel/sage/sage/matrix/matrix_sparse.pyx # Segfault
sage -t  devel/sage/sage/matrix/matrix2.pyx # Segfault
sage -t  devel/sage/sage/matrix/matrix_space.py # Segfault


Finally some one with test failures that relate to mine on Fedora 12!

See ticket: http://sagetrac.org/sage_trac/ticket/7773

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] numpy and Open Solaris 64 bit

[Jaap Spies]

Hi,

I have a patch. Numpy builds ok on Open Solaris, but ...

There are a few problems in trac. There are patches on p2 and there is even a 
numpyp3.spkg
waiting for review and inclusion.

Maintainers, please solve this issues, so I can go on.

I'll wait until this is sorted out.

Jaap




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: SAGE_FORTRNA on OS X.

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

Dr. David Kirkby wrote:

Jaap Spies wrote:


There is a hiatus in the spkg-install. If you only export SAGE_FORTRAN
on Open Solaris with SAGE64=yes the script picks up the wrong lib.

../lib/amd64/libgfortran is needed.


That is not going to work on SPARC though. Instead, use:

../lib/`isainfo -n`/libgfortran.so

as that will substitute the correct library on either Solaris platform.
(It's not portable across other platforms though - AIX, HP-UX etc)

SAGE_FORTRAN and SAGE_FORTRAN_LIB are quite separate things.

SAGE_FORTRAN has nothing to do with the library.



The only point I would like to make is that the script as is picks up
the wrong lib if SAGE_FORTRAN_LIB is not set to the right libgfortran.so

Jaap



It would be good if there was a check that SAGE_FORTRAN_LIB was pointing
at a 64-bit library, if the build is 64-bit. I know that was one of the
mistakes I made.

There's some discussion of this at

http://trac.sagemath.org/sage_trac/ticket/7484

I could add such a check in 'prereq' to make sure that SAGE_FORTRAN_LIB
was a 64-bit library if SAGE64 was exported to yes. (I could work out
how to do that on Solaris and HP-UX, but I'm not sure how to handle it
on OS X).



OS X is a case on its own. Forced to use the included binary, as far as I
understand things.

On Open Solaris things went wrong with the spkg-install python scrypt
assuming the libgfortran.so is  ../../lib/libgfortran.so in stead of
(you and I know) ../../lib/amd64/libgfortran.so :(

Jaap



The problem with 'prereq' is that it is only run at the start of the
build, and not again if the build fails, and someone restarts it. But
doing a test there, is better than doing no tests at all.

Dave




--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: sage-4.3.1.rc0 released!

[Jaap Spies]

William Stein wrote:

On Fri, Jan 22, 2010 at 9:31 AM, Dima Pasechnikdimp...@gmail.com  wrote:

Robert,
the advantage is that it will simplify the *development* of Sage.
Right now  lots of stoppers seem to come from upstream packages.

I also do not see a  real problem with specific versions of
packages. Somehow,
all the other open-source math projects seem to be able to manage this
well,
e.g. Singular manages to coordinate with GMP.
As well, lots of things like needlessly tying Sage up to a very
particular version or
an environment can be sorted out simply by using autoconf properly...


I so wish you were right!The programs you refer to like Singular
are very simple and tiny compared to Sage.  If things were so easy as
you think, somebody would already have set things up so one can do
things that way.  Nothing is stopping anyway from doing that now.



Happens that Singular is a stumbling stone in the port of Sage to
Open Solaris 64 bit! As it comes to building libsingular I have no clue at
the moment.

Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: sage-4.3.1.rc0 released!

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

William Stein wrote:

On Fri, Jan 22, 2010 at 9:31 AM, Dima Pasechnikdimp...@gmail.com
wrote:

Robert,
the advantage is that it will simplify the *development* of Sage.
Right now lots of stoppers seem to come from upstream packages.

I also do not see a real problem with specific versions of
packages. Somehow,
all the other open-source math projects seem to be able to manage this
well,
e.g. Singular manages to coordinate with GMP.
As well, lots of things like needlessly tying Sage up to a very
particular version or
an environment can be sorted out simply by using autoconf properly...


I so wish you were right! The programs you refer to like Singular
are very simple and tiny compared to Sage. If things were so easy as
you think, somebody would already have set things up so one can do
things that way. Nothing is stopping anyway from doing that now.



Happens that Singular is a stumbling stone in the port of Sage to
Open Solaris 64 bit! As it comes to building libsingular I have no
clue at
the moment.

Jaap


I'll help you on that, but I need to sort out the 'prereq' script and
now feel I need to devote some time to trying to fix this issue created
somewhere between 4.3 and 4.3.1, where the SPARC port got broken.

It looks like there are plenty of patches to singular: spkg-install
contains

patch()
{
# work-around patches
cp patches/mminit.cc src/kernel/
cp patches/assert.h src/factory/
cp patches/kernel.rmodulon.cc src/kernel/rmodulon.cc
cp patches/src.Singular.Makefile.in src/Singular/Makefile.in
cp patches/Singular.libsingular.h src/Singular/libsingular.h
cp patches/factory.GNUmakefile.in src/factory/GNUmakefile.in
cp patches/libfac.charset.alg_factor.cc src/libfac/charset/alg_factor.cc
cp patches/kernel.Makefile.in src/kernel/Makefile.in
cp patches/Singular.Makefile.in src/Singular/Makefile.in
cp patches/Singular.tesths.cc src/Singular/tesths.cc
#cp patches/Singular.configure src/Singular/configure
#cp patches/Singular.configure.in src/Singular/configure.in
}

I suspect some of them have GNUisms in them, though this does build
32-bit SPARC.




Hi,

Singular as such is no problem. It is building libsingular that fails!

malb to the rescue?

Good luck with the SPARC port!


Jaap


--
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: [sage-release] sage -upgrade

[Jaap Spies]

On Thu, Jan 21, 2010 at 5:21 PM, William Stein wst...@gmail.com wrote:
 Hi,

 WARNING: On Linux, if you do sage -upgrade right now, you may need to do

  ./sage -f numpy-1.3.0.p2.spkg scipy_sandbox-20071020.p4.spkg 
 scipy-0.7.p3.spkg

 (or something very similar) to force rebuild of some code that depends
 on fortran libraries.
 See http://trac.sagemath.org/sage_trac/ticket/8025


Even with this trick upgrading my system wide install on Fedora failed.

This was meant to be upgrade number 87 :-)!

Jaap


  -- William

-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Not the best week for the Solaris port.

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

Dr David Kirkby wrote:



From what I have read of the GNU linker documentation on the linker
'ld'

http://sourceware.org/binutils/docs-2.20/ld/Options.html#Options

there is no such flag as -m64. So I can't understand how it works.
(There is an opton -64 on the Sun linker, but it rarely needed).

Can you explain this?



There are spkgs which use g++ as linker, e.g. givaro, linbox.

Jaap


But I don't understand why that should make any difference, as
ultimately g++ will call the linker.



g++ needs the -m64 flag to produce a 64 bit shared library.

Jaap



See below, where I purposely changed the permissions of the linker, so
it was unreadable. Then tried to compile a program with g++, and it
fails due to a permission denied error on the linker. So I would have
thought it immaterial how the program is linked.

drkir...@hawk:~# ls -l /usr/ccs/bin/ld
lrwxrwxrwx 1 root root 12 Oct 26 17:20 /usr/ccs/bin/ld - .../../bin/ld
drkir...@hawk:~# ls -l /bin/ld
-rwxr-xr-x 1 root bin 13748 May 14 2009 /bin/ld
drkir...@hawk:~# chmod 000 /bin/ld
drkir...@hawk:~# g++ test.cpp
collect2: error trying to exec '/usr/ccs/bin/ld': execvp: Permission denied
collect2: ld returned 255 exit status

I clearly don't understand what is going on. I will ask on gcc-help, to
see what they say, as I think it is more complicated than the fact g++
is used for linking.

Dave




-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Not the best week for the Solaris port.

[Jaap Spies]

Dr David Kirkby wrote:



 From what I have read of the GNU linker documentation on the linker
'ld'

http://sourceware.org/binutils/docs-2.20/ld/Options.html#Options

there is no such flag as -m64. So I can't understand how it works.
(There is an opton -64 on the Sun linker, but it rarely needed).

Can you explain this?



There are spkgs which use g++ as linker, e.g. givaro, linbox.

Jaap




Dave





-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: numpy on Open Solaris 64 bit

[Jaap Spies]

Jaap Spies wrote:

Hi,

A patched version of numpy-1.3.0 seems to build and install On Open
Solaris 06/09

real 0m46.014s
user 0m41.791s
sys 0m2.656s
Successfully installed numpy-1.3.0.p3


[...]


from numpy.linalg import lapack_lite
ImportError: ld.so.1: python: fatal: relocation error: file
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/linalg/lapack_lite.so:
symbol zungqr_: referenced symbol not found
 
j...@opensolaris:~/Downloads/sage-4.3.1.rc0$




Problem solved: sage_fortran is misconfigured in Open Solaris.

I'll open tickets shortly.

Jaap



Any thoughts?

Jaap





-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] numpy on Open Solaris 64 bit

[Jaap Spies]

Hi,

A patched version of numpy-1.3.0 seems to build and install On Open Solaris 
06/09

real0m46.014s
user0m41.791s
sys 0m2.656s
Successfully installed numpy-1.3.0.p3
You can safely delete the temporary build directory
/export/home/jaap/sage_port/sage-4.3.1.rc0/spkg/build/numpy-1.3.0.p3
Making Sage/Python scripts relocatable...
Making script relocatable
Finished installing numpy-1.3.0.p3.spkg
-bash-3.2$


But importing numpy in python fails:

Finished installing numpy-1.3.0.p3.spkg
j...@opensolaris:~/Downloads/sage-4.3.1.rc0$ ./sage -python
Python 2.6.2 (r262:71600, Jan 16 2010, 14:09:26)
[GCC 4.3.4] on sunos5
Type help, copyright, credits or license for more information.
 import numpy
Traceback (most recent call last):
  File stdin, line 1, in module
  File 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/__init__.py,
 line 130, in module
import add_newdocs
  File 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/add_newdocs.py,
 line 9, in module
from lib import add_newdoc
  File 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/lib/__init__.py,
 line 13, in module
from polynomial import *
  File 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/lib/polynomial.py,
 line 18, in module
from numpy.linalg import eigvals, lstsq
  File 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/linalg/__init__.py,
 line 47, in module
from linalg import *
  File 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/linalg/linalg.py,
 line 22, in module
from numpy.linalg import lapack_lite
ImportError: ld.so.1: python: fatal: relocation error: file 
/export/home/jaap/Downloads/sage-4.3.1.rc0/local/lib/python2.6/site-packages/numpy/linalg/lapack_lite.so: symbol zungqr_: referenced symbol not found


j...@opensolaris:~/Downloads/sage-4.3.1.rc0$

Any thoughts?

Jaap


-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Error in building/installing linbox on Open Solaris 64 bit

[Jaap Spies]

Clement Pernet wrote:

Hi,

This part of the interface is actually terrible. In particular, I don't
see the rationale for the use of static's here.
Hopefully this will be all gone when we'll switch to have LinBox and
matrix_modn_dense support use natively the same matrix type (#4258).

But given your compilation error trace, I don't see the error: the
static thing is only a warning. isn't the error somewhere earlier in the
trace, that you cut off?



Yes:
[...]

 g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I. -I../../linbox -g -I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include/linbox 
-I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include -O2 -DDISABLE_COMMENTATOR -I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include 
-I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include -I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include -Wall -g -m64 -g -fPIC 
-I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include -I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include/linbox 
-L/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/lib -I/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/src 
-I/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/src/linbox -I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include 
-I/export/home/jaap/Downloads/sage-4.3.1.alpha2/local/include -D__LINBOX_HAVE_CBLAS -c linbox-sage.C  -fPIC -DPIC -o .libs/linbox-sage.o

In file included from ../../linbox/blackbox/apply.h:18,
 from ../../linbox/algorithms/lifting-container.h:33,
 from ../../linbox/algorithms/rational-solver.inl:36,
 from ../../linbox/algorithms/rational-solver.h:970,
 from ../../linbox/algorithms/rational-solver-adaptive.h:9,
 from ../../linbox/algorithms/smith-form-adaptive.inl:17,
 from ../../linbox/algorithms/smith-form-adaptive.h:76,
 from linbox-sage.C:46:
../../linbox/randiter/multimod-randomprime.h: In static member function ‘static 
void LinBox::MultiModRandomPrime::setSeed(long unsigned int)’:
../../linbox/randiter/multimod-randomprime.h:81: error: ‘seeding’ is not a 
member of ‘LinBox::integer’
In file included from ../../linbox/algorithms/matpoly-mult.h:27,
 from ../../linbox/algorithms/sigma-basis.h:42,
 from ../../linbox/blackbox/block-hankel-inverse.h:32,
 from ../../linbox/algorithms/lifting-container.h:41,
 from ../../linbox/algorithms/rational-solver.inl:36,
 from ../../linbox/algorithms/rational-solver.h:970,
 from ../../linbox/algorithms/rational-solver-adaptive.h:9,
 from ../../linbox/algorithms/smith-form-adaptive.inl:17,
 from ../../linbox/algorithms/smith-form-adaptive.h:76,
 from linbox-sage.C:46:
[...]

Maybe this is more informative.

Jaap



-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage build hangs on fplll

[Jaap Spies]

Robert Miller wrote:

One of the patches recently merged into rc0 is causing fplll to take
forever to compile on {sage, boxen...}.math:

building 'sage.libs.fplll.fplll' extension
gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -Wall -g -Wall -g -fPIC -
I/mnt/usb1/scratch/rlm/sage-4.3.1.alpha3/local/include/fplll -I/mnt/
usb1/scratch/rlm/sage-4.3.1.alpha3/local//include -I/mnt/usb1/scratch/
rlm/sage-4.3.1.alpha3/local//include/csage -I/mnt/usb1/scratch/rlm/
sage-4.3.1.alpha3/devel//sage/sage/ext -I/mnt/usb1/scratch/rlm/
sage-4.3.1.alpha3/local/include/python2.6 -c sage/libs/fplll/fplll.cpp
-o build/temp.linux-x86_64-2.6/sage/libs/fplll/fplll.o -w
cc1plus: warning: command line option -Wstrict-prototypes is valid
for Ada/C/ObjC but not for C++
...



I don't think this will ever finish:

12527 rlmill20   0  923m 903m 7800 R  100  0.7 ***981:28.46***
cc1plus

Any ideas what might cause this?




I had this hang on Fedora 12 with MAKE = make -j6

Building with make -j1 worked ok. Testing with ./sage -tp 6 hangs to.

Make test finished with the usual errors.

Jaap


-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: mpir-1.2.2.p0 fails on centos32, debian32, and opensuse32

[Jaap Spies]

Robert Miller wrote:

I'm not sure whether you are trying to build a 32-bit or 64-bit
sage (there's nothing in prereq which clearly states one way or
the other) but it looks like mpir is building all the assembler
code in 64-bit mode and all the C code in 32-bit mode.  That
definitely isn't going to work.


This is on 32-bit opensuse.




Strange. It uses ABI=64

Jaap



-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Building ATLAS libraries failed on Open Solaris

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

I'm almost there:

Finished building ATLAS core
The Makefile generated in ATLAS for building shared libraries
assumes the linker is the GNU linker, which it not true in
your setup. (It is generally considered better to use the
Sun linker in /usr/ccs/bin rather than the GNU linker from binutils)
The linker flags in
/export/home/jaap/Downloads/sage-4.3.1.alpha1/spkg/build/atlas-3.8.3.p10/ATLAS-build/lib/Makefile
will be changed.
'-shared' will be changed to '-G'
'-soname' will be changed to '-h'
'--whole-archive' will be changed to '-zallextract'
'--no-whole-archive' will be changed to '-zdefaultextract'
A copy of the original Makefile will be copied to Makefile.orig
rm -f libatlas.so liblapack.so
make libatlas.so liblapack.so libf77blas.so libcblas.so liblapack.so
make[1]: Entering directory
`/export/home/jaap/Downloads/sage-4.3.1.alpha1/spkg/build/atlas-3.8.3.p10/ATLAS-build/lib'

ld -melf_x86_64 -G -h libatlas.so -o libatlas.so \
-z allextract libatlas.a -z defaultextract -lc -lm
ld: warning: file libatlas.a(ATL_flushcache.o): wrong ELF class:
ELFCLASS64
ld: fatal: entry point symbol `lf_x86_64' is undefined
make[1]: *** [libatlas.so] Error 1
make[1]: Leaving directory
`/export/home/jaap/Downloads/sage-4.3.1.alpha1/spkg/build/atlas-3.8.3.p10/ATLAS-build/lib'



I know how to fix this on the command line:

ld -64 -G -h libatlas.so -o libatlas.so \
-z allextract libatlas.a -z defaultextract -lc -lm

produces the shared library. But I don't know where this -melf_x86_64
comes from. I don't know if its supposed to be a linker option. I
suspect I could hack this to work at the command line. Sorting out the
script might be a bit more difficult, but I expect it can be done.




 vi src/CONFIG/src/SpewMakeInc.c

   fprintf(fpout,LDFLAGS =);
   if (MachIsX86(mach))
   {
  if (ptrbits == 32)
 fprintf(fpout,  -melf_i386);
  else if (ptrbits == 64)
 fprintf(fpout,  -melf_x86_64);
   }

This program generates the Make.inc
included in every Makefile, more important it is included in the Makefile
in lib.

I don't understand why there must an emulation mode at all.

Changing SpewMakeInc.c such that LDFLAGS = -64 resp. -32

gives me a working atlas!

Is this
make[1]: Leaving directory 
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/atlas-3.8.3.p10/ATLAS-build'
Deleting liblapack.so on Solaris due to bug in numpy/scipy
needed for Open Solaris?



It's possible

export LDFLAGS=-64

(not -m64, but -64)

might help. I've not tried that.



I don't think this helps. See above.

Jaap



dave





-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: Linbox complains GMP is not installed on Solaris 10 (64-bit mode)

[Jaap Spies]

Dr. David Kirkby wrote:

Dr. David Kirkby wrote:

Bill Hart wrote:

There are two problems I see.

1) The invalid option -64 is passed to the compiler (I think this is
being ignored anyway).

2) It links against libgmpxx, which it fails to find. It is not clear
to me why. It should be in sage/local/lib along with libgmp.

Bill.


I believe the -64 is ignored too. The library does exist

drkir...@swan:[~] $ file gcc64/sage-4.3.1.alpha2/local/lib/libgmpxx.so.3
gcc64/sage-4.3.1.alpha2/local/lib/libgmpxx.so.3: ELF 64-bit MSB
dynamic lib SPARCV9 Version 1, dynamically linked, not stripped, no
debugging information available
drkir...@swan:[~] $

Conventionally on Solaris, 32-bit libraries go in places like /usr/lib
/usr/local/lib, and 64-bit libraries go in /usr/lib/sparcv4 (SPARC) or
/usr/lib/amd64 (x86). In both cases /usr/lib/64 is a symbolic link to
the 'amd64' or 'sparcv9' as appropriate. Sage is not following that
convention, so I did wonder if that was the problem.

So I created the directory sage-4.3.1.alpha2/local/lib/sparcv9 and
copied the

drkir...@swan:[~/gcc64] $ ls -l sage-4.3.1.alpha2/local/lib/sparcv9
total 18184
-rwxr-xr-x 1 drkirkby other 818 Jan 14 17:09 libgmp.la
-rwxr-xr-x 1 drkirkby other 727880 Jan 14 17:09 libgmp.so
-rwxr-xr-x 1 drkirkby other 727880 Jan 14 17:09 libgmp.so.3
-rwxr-xr-x 1 drkirkby other 727880 Jan 14 17:09 libgmp.so.3.4.6
-rwxr-xr-x 1 drkirkby other 954 Jan 14 17:09 libgmpxx.la
-rwxr-xr-x 1 drkirkby other 37600 Jan 14 17:09 libgmpxx.so
-rwxr-xr-x 1 drkirkby other 37600 Jan 14 17:09 libgmpxx.so.3
-rwxr-xr-x 1 drkirkby other 37600 Jan 14 17:09 libgmpxx.so.3.1.6
-rwxr-xr-x 1 drkirkby other 3278536 Jan 14 17:09 libpari-gmp.so.2
-rwxr-xr-x 1 drkirkby other 3278536 Jan 14 17:09 libpari-gmp.so.2.3.3

and tried again. But it still can't find the library.

I suspect this might be related to the fact that somehow the compiler
is looking in a different place for the libraries.

This fails in 32-bit mode if the Sun compiler is used. I've not got a
build of that, so I can't see exactly why GMP was not found then.

dave



The problem seems to be that SAGE sets LD_LIBRARY_PATH to include
$SAGE_LOCAL/lib, but Solaris will ignore that setting in 64-bit mode.
Its LD_LIBRARY_PATH_64 which needs setting. If that is done, so Linbox
gets a bit further.

export
LD_LIBRARY_PATH_64=/usr/local/lib/sparcv9:/export/home/drkirkby/gcc64/sage-4.3.1.alpha2/local/lib/


checking size of long... 8
checking for long long... yes
checking size of long long... 8
checking for __int64... no
checking size of __int64... 0
checking whether byte ordering is bigendian... yes
Default path = /usr /usr/local
checking whether to compile the drivers... no
checking for GMP = 3.1.1... found
checking whether GMP is 4.0 or greater... yes
checking whether GMP was compiled with --enable-cxx... yes

So Linbox is happy with GMP now.

checking for NTL = 5.0... found
checking for GIVARO = 3.2.10... found
checking whether to compile the sage interface... yes
checking for C interface to BLAS... not found
checking for others BLAS... not found





Building of linbox on Open Solaris 06/2009 in VirtualBox ends with:
--
Libraries have been installed in:
   /export/home/jaap/Downloads/sage-4.3.1.alpha2/local/lib

[...]

linbox-sage.C: At global scope:
linbox-sage.C:72: warning: ‘void linbox_set_modn_matrix(mod_int**, LinBox::DenseMatrixLinBox::Modulardouble , size_t, size_t)’ declared ‘static’ but never 
defined

make[4]: *** [linbox-sage.lo] Error 1
make[4]: Leaving directory 
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/src/interfaces/sage'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory 
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/src/interfaces'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory 
`/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2/src'
Error installing linbox

real0m52.563s
user0m33.152s
sys 0m17.425s
sage: An error occurred while installing linbox-1.1.6.p2
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /export/home/jaap/Downloads/sage-4.3.1.alpha2/install.log.  Describe your 
computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2 and 
type 'make check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg/build/linbox-1.1.6.p2' 
 '/export/home/jaap/Downloads/sage-4.3.1.alpha2/sage' -sh)
When you are done debugging, you can type exit to leave the
subshell.
make[1]: *** [installed/linbox-1.1.6.p2] Error 1
make[1]: Leaving directory `/export/home/jaap/Downloads/sage-4.3.1.alpha2/spkg'

[sage-devel] Re: mpir-1.2.2.p0 fails on centos32, debian32, and opensuse32

[Jaap Spies]

Dr. David Kirkby wrote:

Robert Miller wrote:

These seem related to #7910... Any thoughts?


When you say they seem to be related to #7910, what makes you think that?

I realise there is a mix of 32 and 64-bit objects in those list of error
messages, but I think the reasons for #7910 are pretty well understood -
Flint does not properly reconise Japp's processor. Flint believes the
processor is a 486 (i.e. 32-bit) and so offers no 64-bit ABI.

I can't see any connection myself.




flint - mpir
Japp - Jaap :-)

But I agree. Can't see a connection.

Jaap



-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: mpir.1.2.2 fails to build on Open Solaris 06/2009 in VirtualBox

[Jaap Spies]

Bill Hart wrote:

MPIR should detect all known intel and amd CPU's (MPIR 1.3 will also
detect via and atom's), but for some reason it doesn't detect yours.

To perform the detection it asks the CPU what it is, using the CPUID
instruction.

2 possiblities:

1) The CPUID instruction is returning the wrong thing

2) It isn't in our list.

To check the latter, can you tell us what you get when you issue the
equivalent of

cat /proc/cpuinfo

if OpenSolaris has such a thing.

Bill.



j...@opensolaris:~/Downloads/sage-4.3.1.alpha1$ /usr/sbin/psrinfo -v
Status of virtual processor 0 as of: 01/13/2010 11:25:49
  on-line since 01/12/2010 05:53:06.
  The i386 processor operates at 2780 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 1 as of: 01/13/2010 11:25:49
  on-line since 01/12/2010 05:53:09.
  The i386 processor operates at 2780 MHz,
and has an i387 compatible floating point processor.
j...@opensolaris:~/Downloads/sage-4.3.1.alpha1$

This is in VirtualBox, so virtual processors?

But I have built dozens of ELF 64 programs!

Jaap



-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: mpir.1.2.2 fails to build on Open Solaris 06/2009 in VirtualBox

[Jaap Spies]

Bill Hart wrote:

Ah, I see in a later trac update you have the same problem in Fedora.
But surely there you have cat /proc/cpuinfo. What information does it
give you? We might be able to tackle the problem from there.



I had the wrong Fedora running.

On Fedora 12 64 bit in Virtualbox:

gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make -j2 sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=64
checking compiler gcc -O2 -m64 ... yes
checking compiler gcc -O2 -m64  -march=k8... yes

Sorry for the noise!

Jaap


-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: mpir.1.2.2 fails to build on Open Solaris 06/2009 in VirtualBox

[Jaap Spies]

Gonzalo Tornaria wrote:

On Wed, Jan 13, 2010 at 11:43 AM, Jaap Spiesj.sp...@hccnet.nl  wrote:

gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu


Still misdetected, it should be nehalem-unknown-linux-gnu for
optimal results if you are running on an i7. But that is probably be a
virtualbox issue.



Not quite. In Fedora 12 on the real machine I get:
gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make -j6 sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=64
checking compiler gcc  -Wall -g ... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes




On the solaris side you get i486-pc-solaris2.11, but you should be
getting at least x86_64-* (as for linux). I think that you must fix
the config.guess in mpir somehow... Check out

http://groups.google.com/group/mpir-devel/browse_thread/thread/aeb271247ae0eec9/a90654677f9db1d5

which is quite related to this: I had the same issue running on a kvm
virtual cpu, and that fixed it at least for linux. The strategy is
that for 64 bit builds on x86 hardware, you always fallback to
x86_64-* even if the family/model reported by cpuid seems to be of an
older 32 bit only cpu.



Thanks,

Jaap



Gonzalo




-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: mpir.1.2.2 fails to build on Open Solaris 06/2009 in VirtualBox

[Jaap Spies]

Gonzalo Tornaria wrote:

On Wed, Jan 13, 2010 at 12:06 PM, Jaap Spiesj.sp...@hccnet.nl  wrote:

Gonzalo Tornaria wrote:


On Wed, Jan 13, 2010 at 11:43 AM, Jaap Spiesj.sp...@hccnet.nlwrote:


gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu


Still misdetected, it should be nehalem-unknown-linux-gnu for
optimal results if you are running on an i7. But that is probably be a
virtualbox issue.



Not quite. In Fedora 12 on the real machine I get:
gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu


Then that needs to be fixed with mpir itself.

Can you copy cpu family, model and flags from /proc/cpuinfo? I'm think
yours is a model 30 nehalem which is currently undetected by mpir.



[j...@vrede sage-4.3.1.alpha1]$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 30
model name  : Intel(R) Core(TM) i7 CPU 860  @ 2.80GHz
stepping: 5
cpu MHz : 2808.816
cache size  : 8192 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 11
wp  : yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc 
arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm 
ida tpr_shadow vnmi flexpriority ept vpid

bogomips: 5617.63
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

[...]

processor   : 7
vendor_id   : GenuineIntel
cpu family  : 6
model   : 30
model name  : Intel(R) Core(TM) i7 CPU 860  @ 2.80GHz

[...]



CC to mpir-devel as this needs to be fixed in cpuid.c

The processor in question is a core i7 860, namely:
http://processorfinder.intel.com/details.aspx?sSpec=SLBJJ#

[ afaict, the main difference of the i7 800 series wrt the i7 900/xeon
5500 series is the former has 2 memory channels vs. the latter 3
memory channels ]




Thanks,

Jaap



Gonzalo




-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: [sage-release] Re: 4.3.1.alpha2

[Jaap Spies]

Minh Nguyen wrote:

Hi folks,

On Wed, Jan 13, 2010 at 10:58 PM, Robert Millerrlmills...@gmail.com  wrote:

I've finished merging for sage-4.3.1.alpha2, but due to... technical
difficulties, the best place I can put it right now is in /scratch/rlm
on boxen.math.washington.edu. The source tarball and boxen.math-
specific binary are there. Hopefully someone can post a better set of
links while I'm sleeping this off :)




Let's forget this release. It seems to come untested.

Hangs on Fedora 12 x86_64. On the other hand I managed to build
80% of all packages on Open Solaris 06/2009 in VirtualBox!

Jaap


-- 
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-devel
URL: http://www.sagemath.org

[sage-devel] Re: [sage-release] Re: 4.3.1.alpha2

[Jaap Spies]

Dr. David Kirkby wrote:

Jaap Spies wrote:

Minh Nguyen wrote:

Hi folks,

On Wed, Jan 13, 2010 at 10:58 PM, Robert Millerrlmills...@gmail.com
wrote:

I've finished merging for sage-4.3.1.alpha2, but due to... technical
difficulties, the best place I can put it right now is in /scratch/rlm
on boxen.math.washington.edu. The source tarball and boxen.math-
specific binary are there. Hopefully someone can post a better set of
links while I'm sleeping this off :)




Let's forget this release. It seems to come untested.


Well, it is an alpha.


Hangs on Fedora 12 x86_64. On the other hand I managed to build
80% of all packages on Open Solaris 06/2009 in VirtualBox!

Jaap


That's good news. I'm still trying to download it. It's going incredibly
slowly for me.



It is on your machine in my home directory export/home/jaap/sage_port


Since there was not a publicly accessible link, I used 'scp' to download
it. I know on high speed links, the CPU resources used by the encryption
will limit performance, but between me and the USA I doubt that makes
any difference. For whatever reason it will have taken almost two hours
to download for me by the time it finishes.

Let me know what OpenSolaris things don't work.



Sure.


As soon as I have a local copy, I'll stick one in your home directory on
my machine, so you can compare the two, to see if there are any issues
on one machine but not another.



Don't bother :)


Cheers,

Jaap



Dave




-- 
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-devel
URL: http://www.sagemath.org