Sponsored Content
Top Forums UNIX for Advanced & Expert Users Sqlite3: /lib/ld-Linux.so.2: bad ELF interpreter: Post 302846481 by bartus11 on Saturday 24th of August 2013 08:01:31 AM
Old 08-24-2013
What does this show:
Code:
which sqlite3

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

What does bad elf flags mean?

Hi all! Could anybody tell me what this means? # /usr/local/sbin/sshd ld.so.1: /usr/local/sbin/sshd: fatal: /usr/local/lib/libcrypto.so.0.9.6: bad ELF flags value: 256 Killed Thanx (1 Reply)
Discussion started by: penguin-friend
1 Replies

2. Shell Programming and Scripting

/bin/sh: bad interpreter: Permission denied

today i started the LFS book (version 4.0). Basically i am using slackware 9.0 to try and install a new linux completely from source on another partition. Now i took the book's recommendations and created a user called lfs so i wouldn't have to do the stuff as root, and i have got the new LFS... (4 Replies)
Discussion started by: Calum
4 Replies

3. UNIX for Dummies Questions & Answers

bad interpreter: Permission denied

I am writing an expect script but am getting a bad interpreter: permission denied error. I don't think the error has anything to do with expect itself, I think I am missing something in how I start the file. For instance, when I run the file under the expect directory it works: cd... (7 Replies)
Discussion started by: earnstaf
7 Replies

4. Ubuntu

How to resolve bad interpreter error

Hi, Iam trying to run a gmake command and have the latest version of Gnu in my redhat linux system. I need to execute the following steps; ---> chmod +x utils/* ---> ./utils/AllCodeManagerFix ---> gmake LINUX Iam able to do the chmod command but when I run the second command I get... (2 Replies)
Discussion started by: viji19812001
2 Replies

5. Shell Programming and Scripting

Perl - bad interpreter: No such file or directory

Here is a puzzler. To start, let me say that I've done a search on this issue and it is definitely not related to line endings being encoded in windows returns. I get this error when I run SOME perl scripts. I have a script called hello_world.pl. I do $cp hello_world.pl new_hello_world.pl... (0 Replies)
Discussion started by: mjmtaiwan
0 Replies

6. Shell Programming and Scripting

bad interpreter: Permission denied

Hi I am running a script: #!bin/bash set -x echo"select * from celldatamap;" || sqlcsv -v -h -s ',' -d MTNSA11G -u datasafe -p datasafe > andrea.csv When I run my script ./tablescript.sh I get the following error: $ ./tablescript.sh (3 Replies)
Discussion started by: ladyAnne
3 Replies

7. Shell Programming and Scripting

bad interpreter when running script

Hi All, I'm not confortable in writing script, can someone can help me, when I run that script below i found this error code : -bash: ./script.sh: /bin/sh.: bad interpreter: Here is the script for i in * x=${i##*.} z=$(perl -e 'print time;') t=$(echo $z-$x|bc)... (12 Replies)
Discussion started by: bzb23
12 Replies

8. Shell Programming and Scripting

Bad Interpreter

Hi. My name is Caleb (a.k.a RagingNinja) form the whited00r forums. (Whited00r makes custom firmware for iOS devices). I have been learning and creating simple shells scripts. I have been recently using VIM for Windows or using VirtualBox to run the UBUNTU OS within VirtualBox to create my shell... (2 Replies)
Discussion started by: RagingNinja
2 Replies

9. Solaris

Wrong ELF data format: ELFDATA2MSB at /usr/perl5/5.8.4/lib/i86pc-solaris-64int/DynaLoader.pm

We are trying to install our project on solaris 10 x86 machine. we are getting the following error. Can't load '/u01/apps/WatchMark/FlexPM//R39FOA1/sw/perl/lib/auto/DBI/DBI.so' for module DBI: ld.so.1: perl: fatal: /u01/apps/WatchMark/FlexPM//R39FOA1/sw/perl/lib/auto/DBI/DBI.so: wrong ELF data... (3 Replies)
Discussion started by: Jagandadi
3 Replies

10. Red Hat

Not able to run any command /lib64/ld-Linux-x86-64.so.2: bad ELF interpreter

Hi, I accidentally did this: wadhwaso@nxsdgd01 deps]$sudo rpm -e --nodeps glibc-2.5-107.x86_64 error: %postun(glibc-2.5-107.x86_64) scriptlet failed, exit status 255 and since then I am not able to run any command on this server except 'cd'. I always get the following error: $ ls... (6 Replies)
Discussion started by: stunn3r
6 Replies
ELF_BEGIN(3)						   BSD Library Functions Manual 					      ELF_BEGIN(3)

NAME
elf_begin -- open an ELF file or ar(1) archive LIBRARY
ELF Access Library (libelf, -lelf) SYNOPSIS
#include <libelf.h> Elf * elf_begin(int fd, Elf_Cmd cmd, Elf *elf); DESCRIPTION
Function elf_begin() is used to open ELF files and ar(1) archives for further processing by other APIs in the elf(3) library. It is also used to access individual ELF members of an ar(1) archive in combination with the elf_next(3) and elf_rand(3) APIs. Argument fd is an open file descriptor returned from an open(2) system call. Function elf_begin() uses argument fd for reading or writing depending on the value of argument cmd. Argument elf is primarily used for iterating through archives. The argument cmd can have the following values: ELF_C_NULL Causes elf_begin() to return NULL. Arguments fd and elf are ignored, and no additional error is signalled. ELF_C_READ This value is to be when the application wishes to examine (but not modify) the contents of the file specified by argument fd. It can be used for both ar(1) archives and for regular ELF files. Argument fd should have been opened for reading. If argument elf is NULL, the library will allocate a new ELF descriptor for the file being processed. If argument elf is not NULL, and references a regular ELF file previously opened with elf_begin(), then the activation count for elf is incremented. If argument elf is not NULL, and references a descriptor for an ar(1) archive opened earlier with elf_begin(), a descriptor for an element in the archive is returned as described in the section Processing ar(1) archives below. ELF_C_RDWR The command is used to prepare an ELF file for reading and writing. It is not supported for archives. Argument fd should have been opened for reading and writing. If argument elf is NULL, the library will allocate a new ELF descriptor for the file being processed. If the argument elf is non-null, it should point to a descriptor previously allocated with elf_begin() with the same values for arguments fd and cmd; in this case the library will increment the activation count for descriptor elf and return the same descriptor. Changes to the in-memory image of the ELF file are written back to disk using the elf_update(3) function. This command is not valid for ar(1) archives. ELF_C_WRITE This command is used when the application wishes to create a new ELF file. Argument fd should have been opened for writing. Argument elf is ignored, and the previous contents of file referenced by argument fd are overwritten. Processing ar(1) archives An ar(1) archive may be opened in read mode (with argument cmd set to ELF_C_READ) using elf_begin(). The returned ELF descriptor can be passed into to subsequent calls to elf_begin() to access individual members of the archive. Random access within an opened archive is possible using the elf_next(3) and elf_rand(3) functions. The symbol table of the archive may be retrieved using elf_getarsym(3). RETURN VALUES
The function returns a pointer to a ELF descriptor if successful, or NULL if an error occurred. EXAMPLES
To iterate through the members of an ar(1) archive, use: Elf_Cmd c; Elf *ar_e, *elf_e; ... c = ELF_C_READ; if ((ar_e = elf_begin(fd, c, (Elf *) 0)) == 0) { ... handle error in opening the archive ... } while ((elf_e = elf_begin(fd, c, ar_e)) != 0) { ... process member referenced by elf_e here ... c = elf_next(elf_e); elf_end(elf_e); } To create a new ELF file, use: int fd; Elf *e; ... if ((fd = open("filename", O_RDWR|O_TRUNC|O_CREAT, 0666)) < 0) { ... handle the error from open(2) ... } if ((e = elf_begin(fd, ELF_C_WRITE, (Elf *) 0)) == 0) { ... handle the error from elf_begin() ... } ... create the ELF image using other elf(3) APIs ... elf_update(e, ELF_C_WRITE); elf_end(e); ERRORS
Function elf_begin() can fail with the following errors: [ELF_E_ARGUMENT] An unrecognized value was specified in argument cmd. [ELF_E_ARGUMENT] A non-null value for argument elf was specified when cmd was set to ELF_C_RDWR. [ELF_E_ARGUMENT] The value of argument fd differs from the one the ELF descriptor elf was created with. [ELF_E_ARGUMENT] Argument cmd differs from the value specified when ELF descriptor elf was created. [ELF_E_ARGUMENT] Argument elf was not a descriptor for an ar(1) archive. [ELF_E_ARGUMENT] An ar(1) archive was opened with with cmd set to ELF_C_RDWR. [ELF_E_IO] Function elf_begin() was unable to truncate a file opened for writing using ELF_C_WRITE. [ELF_E_RESOURCE] An out of memory condition was encountered. [ELF_E_SEQUENCE] Function elf_begin() was called before a working version was established with elf_version(3). SEE ALSO
elf(3), elf_end(3), elf_errno(3), elf_memory(3), elf_next(3), elf_rand(3), elf_update(3), gelf(3) BSD
June 21, 2006 BSD
All times are GMT -4. The time now is 05:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy