Hi,
I'm trying to run Norman anti-virus on a CentOS 3 box, x64. Is it possible?
Running the binary gives me this error:
[root@server bin]# ./nvcc -bash: ./nvcc: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I guess I would have to install i386 libraries that it requires, as well.
It it possible?
Regards,
Ugo
On Thu, Nov 09, 2006 at 08:35:25AM -0500, Ugo Bellavance enlightened us:
I'm trying to run Norman anti-virus on a CentOS 3 box, x64. Is it possible?
Running the binary gives me this error:
[root@server bin]# ./nvcc -bash: ./nvcc: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I guess I would have to install i386 libraries that it requires, as well.
No such file or directory
Have you tried using yum to see what package provides that file? Is it installed?
Matt Hyclak wrote:
On Thu, Nov 09, 2006 at 08:35:25AM -0500, Ugo Bellavance enlightened us:
I'm trying to run Norman anti-virus on a CentOS 3 box, x64. Is it possible?
Running the binary gives me this error:
[root@server bin]# ./nvcc -bash: ./nvcc: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I guess I would have to install i386 libraries that it requires, as well.
No such file or directory
Have you tried using yum to see what package provides that file? Is it installed?
On an i386 system:
[root@server services]# rpm -q --whatprovides ld-linux.so.2 glibc-2.3.2-95.44
On an x64 system:
[root@server /home/test # rpm -q glibc glibc-2.3.2-95.44
So it realy looks like an architecture problem...
On Thu, Nov 09, 2006 at 08:35:25AM -0500, Ugo Bellavance wrote:
Hi,
I'm trying to run Norman anti-virus on a CentOS 3 box, x64. Is it possible?
Running the binary gives me this error:
[root@server bin]# ./nvcc -bash: ./nvcc: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I guess I would have to install i386 libraries that it requires, as well.
It it possible?
yes, you are probably missing glibc-2.3.2-95.44.i686 package.
I have downloaded a 30 days evaluation:
[tru@sillage bin]$ file nvcc nvcc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2. 0.30, dynamically linked (uses shared libs), stripped [tru@sillage bin]$ ldd nvcc libdl.so.2 => /lib/libdl.so.2 (0x40037000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x4003b000) libc.so.6 => /lib/tls/libc.so.6 (0x4004b000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) [tru@sillage bin]$ ./nvcc NORMAN Norman Virus Control Version 5.70.01 Jun 15 2004 10:37:11 Copyright (c) 1993-2003 Norman ASA
No arguments. Use -? to obtain list. [tru@sillage bin]$ rpm -q glibc glibc-2.3.2-95.44.x86_64 glibc-2.3.2-95.44.i686
Tru ~/.rpmmacros: %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Tru Huynh wrote:
On Thu, Nov 09, 2006 at 08:35:25AM -0500, Ugo Bellavance wrote:
Hi,
I'm trying to run Norman anti-virus on a CentOS 3 box, x64. Is it possible?
Running the binary gives me this error:
[root@server bin]# ./nvcc -bash: ./nvcc: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I guess I would have to install i386 libraries that it requires, as well.
It it possible?
yes, you are probably missing glibc-2.3.2-95.44.i686 package.
That is what I thought, but how do I instlal a x86 package on an x64?
Ugo Bellavance wrote:
That is what I thought, but how do I instlal a x86 package on an x64?
yum install glibc.i686?
Ralph
On Thu, Nov 09, 2006 at 09:53:53AM -0500, Ugo Bellavance enlightened us:
Ralph Angenendt wrote:
Ugo Bellavance wrote:
That is what I thought, but how do I instlal a x86 package on an x64?
yum install glibc.i686?
It looked obvious for you, but where is this documented?
How about the yum man page. See the section under MISC called "specifying package names".
Matt Hyclak wrote:
On Thu, Nov 09, 2006 at 09:53:53AM -0500, Ugo Bellavance enlightened us:
Ralph Angenendt wrote:
Ugo Bellavance wrote:
That is what I thought, but how do I instlal a x86 package on an x64?
yum install glibc.i686?
It looked obvious for you, but where is this documented?
How about the yum man page. See the section under MISC called "specifying package names".
Only available on CentOS4's yum. I can see it now.
Specifying package names All the list options mentioned above take file-glob-syntax wildcards or package names as arguments, for example yum list available foo* will list all available packages that match foo*.
'yum list available glibc' works fine on centOS 4, but on centos 3 it lists seems to be displaying all available packages.
Thanks,
Ugo
On Thu, Nov 09, 2006 at 10:11:34AM -0500, Matt Hyclak wrote:
On Thu, Nov 09, 2006 at 09:53:53AM -0500, Ugo Bellavance enlightened us:
Ralph Angenendt wrote:
Ugo Bellavance wrote:
That is what I thought, but how do I instlal a x86 package on an x64?
yum install glibc.i686?
It looked obvious for you, but where is this documented?
How about the yum man page. See the section under MISC called "specifying package names".
He's on CentOS-3 the man page for yum-2.0 does not have that section. It's only on the CentOS-4 with yum-2.4.
Maybe I should add it to yum-2.0.x in a next version? <quote> MISC Specifying package names A package can be referred to for install,update,list,remove etc with any of the following:
name name.arch name-ver name-ver-rel name-ver-rel.arch name-epoch:ver-rel.arch epoch:name-ver-rel.arch
For example: yum remove kernel-2.4.1-10.i686 </quote>
Tru
Tru Huynh wrote:
On Thu, Nov 09, 2006 at 10:11:34AM -0500, Matt Hyclak wrote:
On Thu, Nov 09, 2006 at 09:53:53AM -0500, Ugo Bellavance enlightened us:
Ralph Angenendt wrote:
Ugo Bellavance wrote:
That is what I thought, but how do I instlal a x86 package on an x64?
yum install glibc.i686?
It looked obvious for you, but where is this documented?
How about the yum man page. See the section under MISC called "specifying package names".
He's on CentOS-3 the man page for yum-2.0 does not have that section. It's only on the CentOS-4 with yum-2.4.
Maybe I should add it to yum-2.0.x in a next version?
<quote> MISC Specifying package names A package can be referred to for install,update,list,remove etc with any of the following:
name name.arch name-ver name-ver-rel name-ver-rel.arch name-epoch:ver-rel.arch epoch:name-ver-rel.arch For example: yum remove kernel-2.4.1-10.i686</quote>
That would have helped :).
but how is arch defined? x86, i386, i686, how does one know?
Ugo
That would have helped :).
but how is arch defined? x86, i386, i686, how does one know?
That's what the rpmmacros content Tru listed earlier will tell you. It will also alter yum output to display package arch as well. This is doco'd at the centos wiki -> http://wiki.centos.org/TipsAndTricks/YumAndRPM
On 11/9/06, Jim Perrin jperrin@gmail.com wrote:
but how is arch defined? x86, i386, i686, how does one know?
I've been following this thread, and I am seeing that what hasn't been pointed out yet is a reference explaining the use of 32-bit and 64-bit packages on a 64-bit system.
And since there have been several threads over the last little while wherein people have been confused about having apparent duplicate packages (one each of the 32 and 64 bit variety), I think lots of people are not realizing/understanding this issue.
The CentOS Wiki doesn't even have (at least not apparent and search-able) entries for 64 bit related questions that I could find, and while there may be useful information in the forum, it is again not readily apparent.
So, have I missed this resource, or do we need to get one created?
Dave K wrote:
The CentOS Wiki doesn't even have (at least not apparent and search-able) entries for 64 bit related questions that I could find, and while there may be useful information in the forum, it is again not readily apparent.
So, have I missed this resource, or do we need to get one created?
You are hereby invited to join the centos-doc http://lists.centos.org/mailman/listinfo/centos-docs where such issues are discussed. I'd really appreciate if you would like to help us with that. That doesn't mean that you have to edit the wiki page for that (although you can if you want to).
Thanks in advance,
Ralph
On 11/9/2006 2:35 PM, Ugo Bellavance wrote:
[root@server bin]# ./nvcc -bash: ./nvcc: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I guess I would have to install i386 libraries that it requires, as well.
What does strace tell you when you feed it with ./nvcc ? Regards, Michael
-
Dave K -
Jim Perrin -
Matt Hyclak -
Michael Kress -
Ralph Angenendt -
Tru Huynh -
Ugo Bellavance