Alternative solution for Performer 2.4 vs glibc2.2

From: Bram Stolk (bram++at++sara.nl)
Date: 09/04/2001 03:38:23

• Next message: Qinxin Yu: "loading error?"
• Previous message: hans-peter.hofer++at++ruag.com: "PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe"

Hello,

After avoiding libc upgrade due to the infamous unresolved stat symbol,
I finally surrendered, and upgraded anyway.

For those interested, I found an alternative solution to the problem,
which could save you from having to do the LD_PRELOAD trick, and also
saves you from having to build a cusom libpfstat library.

Just try linking against c_nonshared, to resolve the stat symbol.
On debian/unstable, there is a /usr/lib/libc_nonshared.a which contains
a weak symbol for stat.
I do not know if this works for other debian dists, or even other
GNU/Linux dists. Just try.

When working with autoconf/automake systems, you can simply do:

   dnl Work-around for Perfomer bug against glibc2.2
   AC_CHECK_LIB("c_nonshared", stat, L_FIX="-lc_nonshared $L_FIX",,)

Then, add L_FIX to your LIBS.

    Bram

• Next message: Qinxin Yu: "loading error?"
• Previous message: hans-peter.hofer++at++ruag.com: "PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe"

This archive was generated by hypermail 2b29 : Tue Sep 04 2001 - 03:44:24 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.