#1284 closed enhancement (fixed)
IPP won't build/run on Suse 11 with readline-5.2 (forced by default)
| Reported by: | Sebastian Jester | Owned by: | eugene |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | DVO | Version: | current |
| Severity: | blocker | Keywords: | suse readline |
| Cc: |
Description
One of our machines was upgraded to OpenSUSE 11, and after that, a previously compiled IPP (dvo to be precise) had a runtime error because a symbol defined in the readline-5.2 compiled into IPP has become undefined. The symbol in question is "PC", which is defined in the libncurses library on Suse 10.
We tried copying libncurses from a machine with Suse 10 to the one with Suse 11, but still couldn't get it to work. Compiling both libncurses and libreadline into IPP didn't help, either (and takes quite a long time, too).
Instead, compiling IPP with forcing of libreadline turned off (in psconfig/tagsets/ipp-2.9.libs) seems to have fixed the problem on the Suse11 machine; that IPP version even seems to work on the Suse10 machines. Just in case more people run into similar problems!
Change History (2)
comment:1 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 17 years ago
Just to confirm that svn export -r {2009-08-10} with the patched readline indeed works again on SuSE 11. However, bug #1079 persists.
this bug was caused by a) libreadline on the system being compiled with -lncurses, b) other binaries depending on that linkage to supply the needed symbols, and c) the IPP-installed libreadline not having libncurses built in.
libreadline does not provide a command-line hook to add this argument (-lncurses), so I needed to update the support/shobj-conf file and create a new libreadline tarball (patch 13).