On Sun, Jan 4, 2009 at 9:24 PM, mabshoff <mabsh...@googlemail.com> wrote:
>
>
>
> On Jan 4, 9:15 pm, "William Stein" <wst...@gmail.com> wrote:
>> On Sun, Jan 4, 2009 at 9:01 PM, William Stein <wst...@gmail.com> wrote:
>
> <SNIP>
>
>> OK, I found a temporary workaround.  See the patch at #4934.
>
> Ok, I will take a look.
>
>> It would also be very nice if we could also fix the openSUSE build
>> bug, since I think you said you know how (Michael Abshoff).  I noticed
>> that on both my 32 and 64-bit opensuse build machines,
>
> Yes, I am not 100% happy with the workaround. There are three
> scenarios:
>
>  (a) bash is linked statically against libreadline - we are in the
> clear, no trouble
>  (b) bash is dynamically linked against some oddly patched readline
> and dev packages, i.e. headlers are installed - copy over headers and
> lib and be done
>  (c) bash is dynamically linked against some oddly patched readline
> and no dev packages are installed - build readline, overwrite
> libreadline.so with the system one
>
> (c) is dirty and can cause trouble down the road, i.e. mysterious
> segfaults. And this is also the default setup for OpenSUSE 11.1. I
> have an spkg that does (a) and (c), but not (b) yet, so if at all
> possible I would want to wait for 3.3 to sort this out.
>
> One alternative fix would be to build bash from sources and link it
> statically all the way, but that has its own set of shortcomings. On
> the other hand it would spare us the often system bash, so I can see
> the good here, but this is longer term.
>
> Another alternative would be to build termcap or curses before
> readline, but I am not 100% sure how the bash.rpm on OpenSUSE is build
> to nail the problem down.
>
> Thoughts?

What about if we just don't install a shared readline at all?  That
seems way safer to me than overwriting it with the system readline.
In the spkg-install for readline, if the OS is OpenSuse, we just do
    $RM -f $SAGE_LOCAL/lib/libreadline.so*

I.e., for Sage we build only the static readline.  Can't Python, Gap,
PARI, etc. just link in a static readline?   I'm testing this right
now, and PARI appears to statically link in

      $SAGE_ROOT/local/lib/libreadline.a

just fine.

So please think cynically of what could possibly go wrong with my
suggestion, which is similar to yours, but maybe (?) cleaner.

 -- William

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

Reply via email to