Pretty sure you'll need to drag it in manually via yum as the x86 libraries
aren't usually installed by default from memory.
Richard.
On Thursday, July 17, 2014, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
>
> On Wednesday, 16 July 2014, Richard Bywater > wrote:
>
>> Ok so look
On Wednesday, 16 July 2014, Richard Bywater 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 o
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
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, jiery
-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 (0x00
On Wednesday, 16 July 2014, Richard Bywater 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-sc
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?)
Richard.
On Thu, Jul 17, 2014 at 4:45 AM, jieryn wrote:
> I'm not using any slave nodes of an
On Wednesday, 16 July 2014, jieryn 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 direc
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 syste
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 wor
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.jenkin
11 matches
Mail list logo
