Sponsored Content
Full Discussion: IBM Risc migration
Top Forums Programming IBM Risc migration Post 302101244 by Pavlos on Friday 29th of December 2006 01:52:44 PM
Old 12-29-2006
Power 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 clearly that it is written only for IBM Risc 6000 machines.
Does anyone know if this code can run on any other unix/linux platform.
I have to add that the makefile uses the xlc compiler made by IBM for certain IBM platforms.
My feeling is that this code is impossible to run somewhere else.
Is it correct?
I appreciate any feedback because I have DEATH-lines (deadlines0 to respect

Pavlos
Cranfield, UK
 

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

4. AIX

PCI Ethernet NIC's for IBM RISC 600 Model B50

I am trying to locate a non IBM PCI Ethernet card that will work with the Model B50 RISC box. Alternatively, I need to find AIX drivers for standard PCI Ethernet NIC's ?. (0 Replies)
Discussion started by: rahe
0 Replies

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

6. High Performance Computing

IBM Scheduler for High Throughput Computing on IBM Blue Gene P

A lightweight scheduler that supports high-throughput computing (HTC) applications on Blue Gene/P. (NEW: 06/12/2008 in grid) More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

7. AIX

IBM AIX on IBM Eseries & x series server

Hi, I want to know whether IBM AIX can be installed on the IBM e series and x series server hardware? Thanks & Regards Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies

8. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies

9. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
DH_STRIP(1)							     Debhelper							       DH_STRIP(1)

NAME
dh_strip - strip executables, shared libraries, and some static libraries SYNOPSIS
dh_strip [debhelperoptions] [-Xitem] [--dbg-package=package] [--keep-debug] DESCRIPTION
dh_strip is a debhelper program that is responsible for stripping executables, shared libraries, and static libraries that are not used for debugging. This program examines your package build directories and works out what to strip on its own. It uses file(1) and file permissions and filenames to figure out what files are shared libraries (*.so), executable binaries, and static (lib*.a) and debugging libraries (lib*_g.a, debug/*.so), and strips each as much as is possible. (Which is not at all for debugging libraries.) In general it seems to make very good guesses, and will do the right thing in almost all cases. Since it is very hard to automatically guess if a file is a module, and hard to determine how to strip a module, dh_strip does not currently deal with stripping binary modules such as .o files. OPTIONS
-Xitem, --exclude=item Exclude files that contain item anywhere in their filename from being stripped. You may use this option multiple times to build up a list of things to exclude. --dbg-package=package This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Causes dh_strip to save debug symbols stripped from the packages it acts on as independent files in the package build directory of the specified debugging package. For example, if your packages are libfoo and foo and you want to include a foo-dbg package with debugging symbols, use dh_strip --dbg-package=foo-dbg. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym or --dbgsym-migration. -k, --keep-debug This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Debug symbols will be retained, but split into an independent file in usr/lib/debug/ in the package build directory. --dbg-package is easier to use than this option, but this option is more flexible. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym. --dbgsym-migration=package-relation This option is used to migrate from a manual "-dbg" package (created with --dbg-package) to an automatic generated debug symbol package. This option should describe a valid Replaces- and Breaks-relation, which will be added to the debug symbol package to avoid file conflicts with the (now obsolete) -dbg package. This option implies --automatic-dbgsym and cannot be used with --keep-debug, --dbg-package or --no-automatic-dbgsym. Examples: dh_strip --dbgsym-migration='libfoo-dbg (<< 2.1-3~)' dh_strip --dbgsym-migration='libfoo-tools-dbg (<< 2.1-3~), libfoo2-dbg (<< 2.1-3~)' --automatic-dbgsym, --no-automatic-dbgsym Control whether dh_strip should be creating debug symbol packages when possible. The default is to create debug symbol packages. --ddebs, --no-ddebs Historical name for --automatic-dbgsym and --no-automatic-dbgsym. --ddeb-migration=package-relation Historical name for --dbgsym-migration. NOTES
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1 "Binaries"). This will also inhibit the automatic creation of debug symbol packages. The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS environment variable. However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure that the regular deb package will be identical with and without this flag (assuming it is otherwise "bit-for-bit" reproducible). CONFORMS TO
Debian policy, version 3.0.1 SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_STRIP(1)
All times are GMT -4. The time now is 08:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy