Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Inputs required in decoding file on AIX- executable (RISC System/6000) or object module not stripped
Top Forums Shell Programming and Scripting Inputs required in decoding file on AIX- executable (RISC System/6000) or object module not stripped Post 302988659 by Don Cragun on Friday 30th of December 2016 12:54:53 PM
Old 12-30-2016
To get the information you provided (executable (RISC System/6000) or object module not stripped), you had to be able to read its contents (probably using something like the file command). If you're going to try to replace that AIX executable file with an executable file that can be run by your Linux system, you're going to need to understand the difference between "read" and "execute". You can:
  1. Find the source code for the object file you want to convert, modify it to replace any AIX specific code to use code that works on both systems or to use code that is specific to your Linux system, and recompile it on your Linux system.
  2. Contact the vendor that produced the object file you want to run on your Linux system and ask them to provide you a version of that object file that will run on your Linux system.
  3. You can write down specifications describing what that object file does and write code that does that on your Linux system.
  4. You can write an emulator that will run AIX RISC System/6000 code on your Linux system.
  5. Or, you can write down specifications describing what that object file does and hire someone to write code that meets those specifications that will run on your Linux system.
Or, of course, if none of the above are possible and this object file is crucial to your business, you could decide to keep running this object file on AIX instead of on your Linux system.
 

10 More Discussions You Might Find Interesting

1. AIX

Ibm Risc/6000 Os

:o Unix Sirs, :eek:RE: IBM RISC/6000 1990 Used on Application: Image buffer: 3D "Catia" (3D "Autocad" sim.) engineering C.A.D. Written by Deso. Cash prior to main frame dump:cool: * :oCan I purchase the oem operating system from you unix people? :cool: ... (1 Reply)
Discussion started by: penguins
1 Replies

2. AIX

PCI Ethernet Cards for IBM RISC 6000 - B50's

I am trying to find PCI Ethernet cards that are compatible with the IBM RISC 6000 - B50 Power PC. None of the regular NIC's seem to have AIX drivers. Does anyone know of AIX drivers for standard PCI Ethernet NIC's or a non IBM NIC that works with the Model B50 at 10/100 MB ? (0 Replies)
Discussion started by: rahe
0 Replies

3. Programming

dbx error ("Executable contains object file compiled on ...")

Hi, We are trying to run dbx on a core file for which we have the original executable and libs, but not the source / object tree. We have recompiled the objects from the original source, but dbx complains that they were compiled at a different time, and refuses to read them: Object file:... (0 Replies)
Discussion started by: Sabari Nath S
0 Replies

4. UNIX for Dummies Questions & Answers

0403-015 - Cannot access a required executable file. It is in use.

How is this error resolved please? I'm just trying to run a shell script and am getting this error. All file permissions are fine. Thanks (0 Replies)
Discussion started by: miwinter
0 Replies

5. AIX

Fibre channel drivers on RS/6000 aix 5L

Want to configure IBM raid strorage but the aix 5L cds do not have the drivers for the fibre channels. The machine is RS/6000. I have gone to IBM downlaodable sites but i can't find the drivers? help pliz:mad: (4 Replies)
Discussion started by: Zim-Aix-Guru
4 Replies

6. UNIX for Advanced & Expert Users

How can i read a non text file in unix - ELF-64 executable object file - IA64

The binary file is ELF-64 executable object file - IA64. How i know that the source is Is there any comamnd in unix i can read these kind of files or use a thirty party software? Thanks for your help (8 Replies)
Discussion started by: alexcol
8 Replies

7. Shell Programming and Scripting

Can't locate loadable object for module GD in @INC

I am trying to use the GD module on a on Unix Solaris environment machine by including gd.pm from a temporary location but I am receiving the following error: perl -w polyline.pl > imageoutput.png Can't locate loadable object for module GD in @INC (@INC contains:... (1 Reply)
Discussion started by: wadhwa.pooja
1 Replies

8. Linux

"not stripped" executable file

Hi, What exactly is meant by a "not stripped" executable file? (4 Replies)
Discussion started by: bruceblacklaws
4 Replies

9. UNIX for Advanced & Expert Users

Can AIX 5.3 - 6 Boot From HP EVA 6000 SAN

Hi There, Has anyone had any luck with or know how to get AIX 5+ to boot from a HP EVA 6000 SAN? The servers used here will be P Class Blades My initial searches on this so far did not bring results so I am guessing this may not be possible on HP SAN's but please let me know if I am... (0 Replies)
Discussion started by: fazzasx
0 Replies

10. Shell Programming and Scripting

Can't locate loadable object for module IO::Tty

I am getting this error: Can't locate loadable object for module IO::Tty in @INC (@INC contains: /production/79p/perl5/lib/site_perl/5.28.0/x86_64-linux /production/79p/perl5/lib/site_perl/5.28.0 /production/79p/perl5/lib/5.28.0/x86_64-linux /production/79p/perl5/lib/5.28.0... (2 Replies)
Discussion started by: mrn6430
2 Replies

LEARN ABOUT CENTOS

s390_runtime_instr

S390_RUNTIME_INSTR(2)						System Calls Manual					     S390_RUNTIME_INSTR(2)

NAME

       s390_runtime_instr - enable/disable s390 CPU run-time instrumentation

SYNOPSIS

       #include <asm/runtime_instr.h>

       int s390_runtime_instr(int command, int signum);

DESCRIPTION

       The s390_runtime_instr() system call starts or stops CPU run-time instrumentation for the calling thread.

       The   command  argument	controls  whether  run-time  instrumentation  is  started  (S390_RUNTIME_INSTR_START,  1)  or  stopped	(S390_RUN-
       TIME_INSTR_STOP, 2) for the calling thread.

       The signum argument specifies the number of a real-time signal.	The real-time signal is sent to the thread if the run-time instrumentation
       buffer is full or if the run-time-instrumentation-halted interrupt occurred.

RETURN VALUE

       On  success,  s390_runtime_instr() returns 0 and enables the thread for run-time instrumentation by assigning the thread a default run-time
       instrumentation control block.  The caller can then read and modify the control block and start the run-time instrumentation.  On error, -1
       is returned and errno is set to one of the error codes listed below.

ERRORS

       EINVAL The value specified in command is not a valid command or the value specified in signum is not a real-time signal number.

       ENOMEM Allocating memory for the run-time instrumentation control block failed.

       EOPNOTSUPP
	      The run-time instrumentation facility is not available.

VERSIONS

       This system call is available since Linux 3.7.

CONFORMING TO

       This  Linux-specific  system call is available only on the s390 architecture.  The run-time instrumentation facility is available beginning
       with System z EC12.

NOTES

       Glibc does not provide a wrapper for this system call, use syscall(2) to call it.

SEE ALSO

       syscall(2), signal(7)

COLOPHON

       This page is part of release 3.53 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

Linux Programmer's Manual					    2012-12-17						     S390_RUNTIME_INSTR(2)
All times are GMT -4. The time now is 07:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy