Sponsored Content
Top Forums UNIX for Advanced & Expert Users PA-RISC 2.0 (LP64) and PA-RISC2.0 exec or libraries Post 97694 by gd2352 on Wednesday 1st of February 2006 01:30:33 PM
Old 02-01-2006
Tools PA-RISC 2.0 (LP64) and PA-RISC2.0 exec or libraries

I have a problem with executing an application using the ELF 64 libraries. Previous versions and on other machines where all is well use PA-RISC2.0 (32) . My guess is that the application or executables need to be recompiled and linked with the new ELF 64 libraries. Are these run time compatible ?

I don't think so.

Thanks!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Intel vs. RISC

I am in the process of starting to learn Unix. What is the major difference in the platforms/hardware? Would it be adventageous for me to start working with a cheap Sparc machine or should I just use my Intel machine to start learning? Any help would be appreciated. (11 Replies)
Discussion started by: amucci
11 Replies

2. 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

3. HP-UX

please help need HP-UX 11 for PA RISC

Im not asking for an illegal copy (but from what i understand if i have the system its not illegal to give it to me) just how to get a copy of hp-ux period i have some old hp visualize systems based on the PA8500 400mhz cpu spent days on the phone with hp they no nothing and there website is a... (6 Replies)
Discussion started by: maliqua
6 Replies

4. HP-UX

Debian HPPA for HP PA-RISC

Hi, I just downloaded the debian HPPA distribution. Once I try to install it on my C3000 box, the machine boots, reads a part of the CD but then stalls with an error message about the image on the CD. The CD drive is IDE, maybe debian expects to have a SCSI one. Somebody already tried to... (1 Reply)
Discussion started by: ddegrendele
1 Replies

5. HP-UX

HP-UX 11i v2 for PA-RISC

Hello, i trying to get HP-UX 11i v2 for PA-RISC. I`im to poor to buy this system, so I`am asking that someone can help me. best regards email removed (1 Reply)
Discussion started by: mruczas
1 Replies

6. Programming

IBM Risc migration

Hi all, I have been dealing with the following problem one week now without any progress. I've a source code written in C which is using X libraries in order to create a graphical interface to visualise results produced by another code written in Fortran. The README file of the C code says... (2 Replies)
Discussion started by: Pavlos
2 Replies

7. HP-UX

Access AS400 from HP (RISC) Unix OS

Hi everyone, I am in the need of some software which will allow me to access IBM AS400 from HP unix operating system. I could download the software from IBM site for windows OS and it is working succesfully. I need to do the same on UNIX OS. Could you please guide me to some site... (1 Reply)
Discussion started by: vkoppula
1 Replies

8. HP-UX

Does HP-UX On Itanium always come with PA-RISC compatibility

Does anybody know if HP-UX on Itanium always comes with backwards compatibility for PA-RISC applications? I've heard that there is an emulator called Aries which should do the trick, I just need to know if it always comes as standard with HP-UX Itanium systems. Any help would be greatly... (3 Replies)
Discussion started by: nialler
3 Replies

9. Shell Programming and Scripting

Script Variables Inquiry, Values Okay in Standalone Exec, No-Show in Cron Exec

I have the following bash script lines in a file named test.sh. #!/bin/bash # # Write Date to cron.log # echo "Begin SSI Load $(date +%d%b%y_%T)" # # Get the latest rates file for processing. # d=$(ls -tr /rms/data/ssi | grep -v "processed" | tail -n 1) filename=$d export filename... (3 Replies)
Discussion started by: ginowms
3 Replies
execstack(8)						      System Manager's Manual						      execstack(8)

NAME
execstack - tool to set, clear, or query executable stack flag of ELF binaries and shared libraries SYNOPSIS
execstack [OPTION...] [FILES] DESCRIPTION
execstack is a program which sets, clears, or queries executable stack flag of ELF binaries and shared libraries. Linux has in the past allowed execution of instructions on the stack and there are lots of binaries and shared libraries assuming this behaviour. Furthermore, GCC trampoline code for e.g. nested functions requires executable stack on many architectures. To avoid breaking binaries and shared libraries which need executable stack, ELF binaries and shared libraries now can be marked as requiring executable stack or not requiring it. This marking is done through the p_flags field in the PT_GNU_STACK program header entry. If the marking is missing, kernel or dynamic linker need to assume it might need executable stack. The marking is done automatically by recent GCC versions (objects using trampolines on the stack are marked as requiring executable stack, all other newly built objects are marked as not requiring it) and linker collects these markings into marking of the whole binary or shared library. The user can override this at assembly time (through --execstack or --noexecstack assembler options), at link time (through -z execstack or -z noexecstack linker options) and using the execstack tool also on an already linker binary or shared library. This tool is especially useful for third party shared libraries where it is known that they don't need executable stack or testing proves it. OPTIONS
-s --set-execstack Mark binary or shared library as requiring executable stack. -c --clear-execstack Mark binary or shared library as not requiring executable stack. -q --query Query executable stack marking of binaries and shared libraries. For each file it prints either - when executable stack is not required, X when executable stack is required or ? when it is unknown whether the object requires or doesn't require executable stack (the marking is missing). -V Print execstack version and exit. -? --help Print help message. --usage Print a short usage message. ARGUMENTS
Command line arguments should be names of ELF binaries and shared libraries which should be modified or queried. EXAMPLES
# execstack -s ~/lib/libfoo.so.1 will mark ~/lib/libfoo.so.1 as requiring executable stack. # execstack -c ~/bin/bar will mark ~/bin/bar as not requiring executable stack. # execstack -q ~/lib/libfoo.so.1 ~/bin/bar will query executable stack marking of the given files. SEE ALSO
ld.so(8). BUGS
execstack doesn't support yet marking of executables if they do not have PT_GNU_STACK program header entry nor they have room for program segment header table growth. AUTHORS
Jakub Jelinek <jakub@redhat.com>. 28 October 2003 execstack(8)
All times are GMT -4. The time now is 06:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy