Well... yes, that's true, but I also have the 64-bit version: [root@ci ~]# yum info glibc Installed Packages Name : glibc Arch : i686 Version : 2.12 Release : 1.132.el6_5.2 Size : 13 M Repo : installed >From repo : RHEL-65-x86_64-updates Summary : The GNU libc libraries URL : http://sources.redhat.com/glibc/ License : LGPLv2+ and LGPLv2+ with exceptions and GPLv2+ Description : The glibc package contains standard libraries which are used by : multiple programs on the system. In order to save disk space and : memory, as well as to make upgrading easier, common system code is : kept in one place and shared between programs. This particular package : contains the most important sets of shared libraries: the standard C : library and the standard math library. Without these two libraries, a : Linux system will not function.
Name : glibc Arch : x86_64 Version : 2.12 Release : 1.132.el6_5.2 Size : 12 M Repo : installed >From repo : RHEL-65-x86_64-updates Summary : The GNU libc libraries URL : http://sources.redhat.com/glibc/ License : LGPLv2+ and LGPLv2+ with exceptions and GPLv2+ Description : The glibc package contains standard libraries which are used by : multiple programs on the system. In order to save disk space and : memory, as well as to make upgrading easier, common system code is : kept in one place and shared between programs. This particular package : contains the most important sets of shared libraries: the standard C : library and the standard math library. Without these two libraries, a : Linux system will not function. On Wed, Jul 16, 2014 at 6:33 PM, Richard Bywater <[email protected]> wrote: > Ok so looks like you've got the the x86 version of glibc installed on a > 64-bit system (which I don't think is a default position). So I guess the > question for Stephen was whether he had installed the x86 glibc as well > during his testing of CentOS? > > Richard. > > > On Thu, Jul 17, 2014 at 10:18 AM, jieryn <[email protected]> wrote: >> >> -bash-4.1$ uname -a >> Linux ci.acme.com 2.6.32-431.21.1.el6.x86_64 #1 SMP Tue Jun 3 19:11:40 >> EDT 2014 x86_64 x86_64 x86_64 GNU/Linux >> >> -bash-4.1$ ls -la /lib/libc.so.6 >> lrwxrwxrwx. 1 root root 12 Jun 3 09:57 /lib/libc.so.6 -> libc-2.12.so >> >> -bash-4.1$ ldd /lib/libc.so.6 >> /lib/ld-linux.so.2 (0x00813000) >> linux-gate.so.1 => (0x00391000) >> >> -bash-4.1$ file /lib/libc-2.12.so >> /lib/libc-2.12.so: ELF 32-bit LSB shared object, Intel 80386, version >> 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux >> 2.6.18, not stripped >> >> -bash-4.1$ rpm -qf /lib/libc.so.6 >> glibc-2.12-1.132.el6_5.2.i686 >> >> >> On Wed, Jul 16, 2014 at 5:49 PM, Stephen Connolly >> <[email protected]> wrote: >> > >> > >> > On Wednesday, 16 July 2014, Richard Bywater <[email protected]> wrote: >> >> >> >> Is your RHEL6.5 system running as 32-bit or 64-bit? Also what does >> >> 'file >> >> /lib/libc.so.6' show (I imagine it will show symbolic link so if you >> >> then do >> >> a file on the resulting link what does that show?) >> > >> > >> > I am suspecting it could be an ld-script... Perhaps even one that starts >> > with a comment... >> > >> > (Says he who may have found the RCA if not the origin Of the RCA) >> > >> >> Richard. >> >> >> >> >> >> On Thu, Jul 17, 2014 at 4:45 AM, jieryn <[email protected]> wrote: >> >>> >> >>> I'm not using any slave nodes of any kind. I just want to have a >> >>> Jenkins job with access to an SSH agent such that it can work with SCM >> >>> URIs of the type scm:svn:svn+ssh:// without me having to launch the >> >>> master Jenkins instance via ssh-agent directly in the startup script. >> >>> >> >>> This is a RHEL 6.5 system that is fully up to date. It doesn't have >> >>> any unusual hackery for multi-lib. >> >>> >> >>> On Mon, Jul 14, 2014 at 3:46 AM, Stephen Connolly >> >>> <[email protected]> wrote: >> >>> > This is an issue with which I have severe issues trying to >> >>> > reproduce. >> >>> > >> >>> > If you can document how you set up a slave node vm step by step from >> >>> > a >> >>> > known >> >>> > starting point perhaps I may be able to fix the issue, but right now >> >>> > *every* >> >>> > time I try to recreate the issue the damn SSH Agent works for me. >> >>> > >> >>> > One working theory is that you have 32-bit and 64-bit shared >> >>> > libraries >> >>> > being >> >>> > mis-identified... >> >>> > >> >>> > Another working theory is that it is something to do with JNR and >> >>> > classloader conflicts over remoting... >> >>> > >> >>> > All this is speculation though without a test case to verify against >> >>> > >> >>> > >> >>> > On 12 July 2014 03:05, jieryn <[email protected]> wrote: >> >>> >> >> >>> >> I'm using Jenkins LTS 1.554.3, and SSH Agent Plugin 1.4.1. I am >> >>> >> seeing >> >>> >> UnsatisfiedLinkError during jobs which try to use an SSH agent. How >> >>> >> do >> >>> >> I resolve this issue? There are only instructions for MacOS on the >> >>> >> plugin wiki page. >> >>> >> >> >>> >> https://gist.github.com/jieryn/5248b713599321f2d548 >> >>> >> https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin >> >>> >> >> >>> >> Thank you. >> >>> >> >> >>> >> -- >> >>> >> You received this message because you are subscribed to the Google >> >>> >> Groups >> >>> >> "Jenkins Users" group. >> >>> >> To unsubscribe from this group and stop receiving emails from it, >> >>> >> send >> >>> >> an >> >>> >> email to [email protected]. >> >>> >> For more options, visit https://groups.google.com/d/optout. >> >>> > >> >>> > >> >>> > -- >> >>> > You received this message because you are subscribed to the Google >> >>> > Groups >> >>> > "Jenkins Users" group. >> >>> > To unsubscribe from this group and stop receiving emails from it, >> >>> > send >> >>> > an >> >>> > email to [email protected]. >> >>> > For more options, visit https://groups.google.com/d/optout. >> >>> >> >>> -- >> >>> You received this message because you are subscribed to the Google >> >>> Groups >> >>> "Jenkins Users" group. >> >>> To unsubscribe from this group and stop receiving emails from it, send >> >>> an >> >>> email to [email protected]. >> >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "Jenkins Users" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> >> an >> >> email to [email protected]. >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > >> > >> > -- >> > Sent from my phone >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Jenkins Users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to [email protected]. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
