similar to: version GLIBC_2.0 not defined in file libpthread.so.0

Is anyone using CentOS 4.4 with an EMC Clariion SAN? In particular, I want to know if PowerPath and Naviagent will work on a CentOS 4 system connected to a san using Qlogic or Emulex cards. I tried a couple years ago with Fedora Core 1 or 2, and couldn't get the kernel modules from PowerPath to work since the kernel wasn't the official RHEL one. I'm most interested in

Specs: Oracle 9.2.0.4 OS is Redhat AS2.1 ocfs-2.4.9-e-summit-1.0.12-1 ocfs-tools-1.0.10-1 ocfs-support-1.0.10-1 ocfs-2.4.9-e-enterprise-1.0.12-1 Shared Storage: Dell/EMC CX600 naviagentcli-6.19.0.4.14-1.noarch.rpm PowerPath 4.4 Post navisphere shuttingdown, The ocfs service attempts to stop Then I get errors: Ocfs:Unmounting drive on [privatenic] 7959 err: unable to sendmsg error: -101,

Dear All, I have installed CentOS release 5.2 (Final). EMC SAN partition is mounted by using EMC Powerpath for resolving multiple paths. I was able write and read data over to SAN partition without any issues. Subsequently I have unmounted EMC SAN partition from the system and deleted LUN using Navisphere user interface. After rebooting system, I still see SAN mappings in system. Here

Hi Jerry and crew, Our solaris 2.8 machine running Samba 2.2.8a ran out of swap. The Sun engineer sent us the following which seemed to point to Samba. Have you seen something like this before? Thanks, Dom Verlezza (704)988-3156 Joe requested that I provide an update on the analysis when it was complete. The kernel engineer who analyzed the core file provided the following: release:

Hello, I've just updated to wine 0.9 and now I get following error when running diablo2: err:module:load_builtin_dll failed to load .so lib for builtin L"dbghelp.dll": /usr/lib/wine/dbghelp.dll.so: symbol regexec, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference err:module:import_dll Loading library dbghelp.dll (which is needed by

Hello all, I have just configured a 64-bit CentOS 5.5 machine to support an XFS filesystem as specified in the subject line. The filesystem will be used to store an extremely large number of files (in the tens of millions). Due to its extremely large size, would there be any non-standard XFS build/configuration options I should consider? Thanks. Boris. -------------- next part -------------- An

The XCB developers have introduced a new library, libpthread-stubs. This library provides weak aliases for pthread functions not provided in libc or otherwise available by default. Libraries like libxcb rely on pthread stubs to use pthreads optionally, becoming thread-safe when linked to libpthread, while avoiding any performance hit when running single-threaded. libpthread-stubs supports this

I compile Samba for the first time on LINUX (SLES 10) and have a weird libpthread warning message. I dug the list to find some explanations about the way I have to handle this problem, without success. Below are the 'configure' parameters and the part of config.log about libpthread. Is there a way to not link libpthread to avoid this performance degradation ? What must I do with this

Hi, On Sat, Oct 31, 2009 at 11:42 AM, Nan Zhu <zhunansjtu at gmail.com> wrote: > Hi,all > > I tried to run the generated whole-program bitcode of BIND,but I got some > information: > > 0   lli             0x0000000000feda16 > 1   lli             0x0000000000fed88f > 2   libpthread.so.0 0x0000003df340eee0 > 3   libc.so.6       0x0000003df28332f5 gsignal + 53 >

Mahadevan R wrote: > Hi, > > On Sat, Oct 31, 2009 at 11:42 AM, Nan Zhu <zhunansjtu at gmail.com> wrote: >> Hi,all >> >> I tried to run the generated whole-program bitcode of BIND,but I got some >> information: >> >> 0 lli 0x0000000000feda16 >> 1 lli 0x0000000000fed88f >> 2 libpthread.so.0

> That worked, but I do get a few linking warnings. Are these serious? > > /usr/lib/libc.so.4: WARNING! setkey(3) not present in the system! > /usr/lib/libc.so.4: warning: this program uses gets(), which is unsafe. > /usr/lib/libc.so.4: warning: mktemp() possibly used unsafely; consider using mkstemp() > /usr/lib/libc.so.4: WARNING! des_setkey(3) not present in the system!

It appears that Mingw gcc included in RTools is missing a dependent library. If I compile a program with '-lgomp' switch (for OpenMP support), I get a errors about undefined references to functions like '_imp__pthread_mutex_destroy'. Adding the '-static' switch, I get the following error: c:/rtools/mingw/bin/../lib/gcc/mingw32/4.5.0/../../../../mingw32/bin/ld.exe:

This project provides a a pkg-config [.pc] file, pthread-stubs.pc, which provides the necessary flags for the given platform to link with the most lightweight implementation of the POSIX threads functions for that platform which is known to work with the XCB family of libraries. This release mainly affects the build & distribution process - the primary change to the installed contents is the

Heres a question for anyone awake at this hour, does icecast2 require libpthread? I'm trying to build it on a freebsd 4.3 box, and it wants to link against libpthread. If this is not required on the freebsd platform, then is it safe to just take out of the makefile? Thanks Mike -- <mystica@darktech.org> --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project

Hi there, have a strange behavior if i?ll create a zfs pool at an EMC PowerPath pseudo device. I can create a pool on emcpower0a but not on emcpower2a zpool core dumps with invalid argument .... ???? Thats my second maschine with powerpath and zfs the first one works fine, even zfs/powerpath and failover ... Is there anybody who has the same failure and a solution ? :) Greets Dominik

I get the errors: zip4_lnx.a(generic.o)(.text+0xb16): more undefined references to `__ctype_b' follow zip4_lnx.a(libdl.so): undefined reference to `_dl_close at GLIBC_2.0' zip4_lnx.a(libdl.so): undefined reference to `_dl_catch_error at GLIBC_2.0' zip4_lnx.a(libdl.so): undefined reference to `_dl_addr at GLIBC_2.0' zip4_lnx.a(libdl.so): undefined reference to

How much fun can you have with a simple thing like powerpath? Here''s the story: I have a (remote) system with access to a couple of EMC LUNs. Originally, I set it up with mpxio and created a simple zpool containing the two LUNs. It''s now been reconfigured to use powerpath instead of mpxio. My problem is that I can''t import the pool. I get: pool: ###### id:

A couple years ago, we moved to Oracle RAC on Linux using ocfs that is SAN attached to an EMC CLARiiON. At the time, there was a reason that we did NOT use EMC's Powerpath (I just can't recall what that reason was). What I'd like to know is if there are any issues with introducing Powerpath now. * RHEL 2.1 AS * 2.4.9-e.38enterprise * ocfs-2.4.9-e-enterprise-1.0.13-1 * EMC

On Mon, 22 Oct 2001 00:07:39 -0600 Jack Moffitt <jack@xiph.org> wrote: > It needs pthreads. FreeBSD provides this in the reentrant c library. > > For FreeBSD, you should remove -lpthread from LIBS and add -pthread to > CFLAGS. I believe this should be the only change required. > > I will fix FreeBSD building in the next few days (or at least this is my > intention)

On some machines running PowerPath, there''s sometimes issues after an update/upgrade of the PowerPath software. Sometimes the pseudo devices get remapped and change names. ZFS appears to handle it OK, however sometimes it then references half native device names and half the emcpower pseudo device names. So the SA can easily be confused. Is there a way to tell ZFS which device names