Bug 79225

Summary: Prelinking can break C++ apps
Product: [Retired] Red Hat Linux Reporter: Nicholas Miell <nmiell>
Component: prelinkAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: bill, michael, mitr
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-02-19 15:34:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nicholas Miell 2002-12-08 06:49:05 UTC 
Prelink is supposed to fall back to normal linking whenever a library an
executable has been prelinked against is changed. This doesn't work in C++
executables.

What happened:
I prelinked everything on my system, and the basically forgot about it.

Several months later, I decided to rebuild the freetype library with the
bytecode interpreter enabled.

After building and installing the package, prelinked C++ executables which
linked to freetype no longer worked. (They died at startup with a message along
the lines of "Unknown reloc type: 0x5" -- I know it was a unknown relocation
type error, and I'm pretty sure it was 0x5)

Undoing the prelink "fixes" the problem, which lead me to undo prelinking
everything on my system.

This is with prelink-0.2.0-8, and I discovered the problem with xpdf and
openoffice before and disabled prelinking entirely.
Comment 1 Jakub Jelinek 2003-02-19 15:34:46 UTC 
This should be fixed in glibc-2.3.1-7 and later.