On Jan 4, 10:58 pm, "William Stein" <wst...@gmail.com> wrote:
> On Sun, Jan 4, 2009 at 10:52 PM, mabshoff <mabsh...@googlemail.com> wrote:
<SNIP>
> >> I.e., for Sage we build only the static readline. Can't Python, Gap,
> >> PARI, etc. just link in a static readline?
>
> > Well, I tried that and I ended up with a Python without readline
> > support and Singular failed to build at all without it. These were
>
> That makes sense. OK, so that won't work.
Yes, that trick was my first idea.
> > Other than that if we get it to work I would be fine with that
> > solution since we so rarely update readline that it won't matter if we
> > link static or dynamic libs in this case.
>
> Here's another suggestion. Did you try this? Just use the
> system-wide readline
> with the system-wide devel library, and we don't build ours at all in
> the case of opensuse. We could make the build terminate at the start
> if readline isn't available on opensuse, and document this requirement
> in the README as well.
Yes, but this is a pain and something I would rather not do in 3.2.3.
And sooner or later we have to start working around that problem on
other distributions, so I would prefer something clean for now.
What we could do is to add a special check in readline.spkg that
copies over the readline.so from the system after building readline on
OpenSUSE 11.1 for now. The chance of this introducing trouble is slime
since it is very close release wise and readline development seems to
only happen at a glacial pace anyway.
> Well, my question is first: does this work?
I would prefer to solve it another way, but it would work.
> -- William
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
