From user-return-7401-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Fri Nov 06 19:03:09 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 55914 invoked from network); 6 Nov 2009 19:03:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Nov 2009 19:03:09 -0000 Received: (qmail 92926 invoked by uid 500); 6 Nov 2009 19:03:08 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 92834 invoked by uid 500); 6 Nov 2009 19:03:08 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 92824 invoked by uid 99); 6 Nov 2009 19:03:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 19:03:08 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [129.59.4.20] (HELO mailgate.vanderbilt.edu) (129.59.4.20) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 19:03:06 +0000 Received: from mailbe16.email.Vanderbilt.edu (mailbe16.email.vanderbilt.edu [129.59.1.154]) by mailgate02 (8.14.3/8.14.3) with ESMTP id nA6J2ixX011070 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 6 Nov 2009 13:02:44 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA5F13.B938394F" Subject: RE: Lounge issues Date: Fri, 6 Nov 2009 13:02:44 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: RE: Lounge issues Thread-Index: AcpfE7j4mXnJiDkvQR2RJtHt0kDFXQ== From: "Coffman, Timothy A" To: X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-11-06_06:2009-10-29,2009-11-06,2009-11-06 signatures=0 X-PPS: No, score=0 ------_=_NextPart_001_01CA5F13.B938394F Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Well, that illuminates my problem a bit more. It's not just one symbol: =20 [tcoffman]$ ldd /usr/lib64/libjson.so /usr/lib64/libjson.so: /lib64/libc.so.6: version `GLIBC_2.8' not found (required by /usr/lib64/libjson.so) libc.so.6 =3D> /lib64/libc.so.6 (0x00002b1897c18000) /lib64/ld-linux-x86-64.so.2 (0x0000555555554000) =20 yum seems to have a pretty clear answer for me: =20 [tcoffman]$ yum list glibc Installed Packages glibc.x86_64 2.5-24 installed =20 glibc.i686 2.5-24 installed =20 =20 =20 Now I just have to determine if it's safe for me to update to a more recent version. glibc seems to be a critical core component, so I don't want to just assume my system will keep working if I upgrade. Tricky. =20 Perhaps a better approach would be to install json-c 0.7 from src, building against the glibc 2.5 that is already installed. The problem I foresee there will be, I don't have the spec file for making an RPM for json-c, and Lounge won't build against a json-c that wasn't installed via an RPM. I could be wrong about that, so perhaps I should just give it a try. =20 Tim Coffman Vanderbilt University Medical Center (615) 936-6496 =20 ------_=_NextPart_001_01CA5F13.B938394F--