Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 161536 - libslang-utf8.so uses glibc-internal symbol
libslang-utf8.so uses glibc-internal symbol
Product: Fedora
Classification: Fedora
Component: slang (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Petr Raszyk
Depends On:
  Show dependency treegraph
Reported: 2005-06-23 22:08 EDT by Ulrich Drepper
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version: slang-1.4.9, Release 23
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-24 10:27:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ulrich Drepper 2005-06-23 22:08:50 EDT
Description of problem:
libslang-utf8.so uses the symbol __libc_enable_secure which is internal to
glibc.  This is not allowed.  The symbol can go away at any time, the type can
change, whatever.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.readelf -s /usr/lib*/libslang-utf8.so | fgrep GLIBC_PRIVATE
Actual results:
   677: 0000000000000000     4 OBJECT  GLOBAL DEFAULT  UND
__libc_enable_secure@GLIBC_PRIVATE (6)

Expected results:
No output.

Additional info:
rpm actually should have could that.
Comment 1 Ulrich Drepper 2005-06-23 22:57:20 EDT
rpm should have *caught* that.
Comment 2 Robert Scheck 2005-10-16 17:16:28 EDT
This is catched up by rpm:

error: Failed dependencies:
        ld-linux.so.2(GLIBC_PRIVATE) is needed by slang-1.4.9-20.i386

Florian worked around it in rpm spec file of -21 using _filter_GLIBC_PRIVATE.
Comment 3 Arjan van de Ven 2005-10-17 07:11:16 EDT
That is not a valid workaround obviously...
Comment 4 Petr Raszyk 2005-10-24 10:27:05 EDT
Fixed in slang-1.4.9, Release 22, patch slang-nointerlibc.patch

Note You need to log in before you can comment on or make changes to this bug.