- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Migrating our app from HP-UX PA-RISC to HP-UX ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2007 07:18 PM
тАО05-20-2007 07:18 PM
Re: Migrating our app from HPUX PA RISC to HPUX 11i
we did what, strings, ldd and chatr, but we got
What - it just display
/usr/local/lib/libdbtraps.sl:
Strings - we got all the strings in the lib but we got this info with nm command itself.
ldd - this lib file is 32 bit and ldd throws error as 'invalid file type'.
chatr - returns some info, which we are not sure how to take it.
/usr/local/lib/libdbtraps.sl:
shared library
shared library dynamic path search:
SHLIB_PATH disabled second
embedded path disabled first Not Defined
shared vtable support disabled
static branch prediction disabled
executable from stack: D (default)
kernel assisted branch prediction enabled
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
third quadrant private data space disabled
fourth quadrant private data space disabled
data page size: D (default)
instruction page size: D (default)
Out of this lib file in our code we are using some functions. we are trying to figure out the src for this lib file.
Is there any command which will find a word in given dir and its sub dir,so that we can give a find from / path.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2007 04:04 AM - edited тАО10-02-2011 12:04 AM
тАО05-21-2007 04:04 AM - edited тАО10-02-2011 12:04 AM
Re: Migrating our app from HP-UX PA-RISC to HP-UX 11.23 Integrity
>strings - we got all the strings in the lib but we got this info with nm command itself.
Did you use "strings -a"?
>we are trying to figure out the src for this lib file.
If you used HP's PA32 compilers, you could use:
$ odump -comp libdbtraps.sl
This will tell you the source filename and the compiler options.
>Is there any command which will find a word in given dir and its subdir, so that we can give a find from / path.
You mean using grep?
$ find path -exec grep -w -e string1 -e string2 ... +
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2007 09:00 PM
тАО05-21-2007 09:00 PM
Re: Migrating our app from HPUX PA RISC to HPUX 11i
No we are using Ansi C compiler for this migration. can we have any command which can get us the src file like odump?
and one more query, we have #ifdef MSC and declaration of some struct and varibles in the if block. we see this if condition is always failing and get undeclaration error for those variables and Structs.
we found in google that it is Microsoft C compiler in some links. but we are not sure about it. Is there any other possible value that might be get assigned to this MSC. or how to check this in old box? expecting your valuable comments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2007 09:10 PM - edited тАО10-02-2011 12:05 AM
тАО05-21-2007 09:10 PM - edited тАО10-02-2011 12:05 AM
Re: Migrating our app from HP-UX PA-RISC to HP-UX 11.23 Integrity
>No we are using ANSI C compiler for this migration. can we have any command which can get us the src file like odump?
As I said, if you used HP's compilers (and didn't strip it) then you can use odump on your PA box:
$ /usr/ccs/bin/odump -comp libdbtraps.sl
If you used gcc, you are out of luck, unless you have debug info.
>we have #ifdef MSC ... we found in google that it is Microsoft C compiler in some links. ... Is there any other possible value that might be get assigned to this MSC.
It seems that MSC is Microsoft C. Some of our RogueWave headers test _MSC_VER.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2007 09:54 PM
тАО05-21-2007 09:54 PM
Re: Migrating our app from HPUX PA RISC to HPUX 11i
how to check this whether MSC is compiler specific.
is there a possiblity that this might be there define in older version of Ansi C and some other variable for Ansi C V5.5?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2007 11:33 PM
тАО05-21-2007 11:33 PM
Re: Migrating our app from HPUX PA RISC to HPUX 11i
could you please visit this one:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1126273
Volkmar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2007 11:44 AM - edited тАО10-02-2011 12:07 AM
тАО05-22-2007 11:44 AM - edited тАО10-02-2011 12:07 AM
Re: Migrating our app from HP-UX PA-RISC to HP-UX 11.23 Integrity
>how to check this whether MSC is compiler specific.
Look at some MS documentation?
>is there a possibility that this might be defined in older version of ANSI C and some other variable for ANSI C A.05.50?
Of course not. It is illegal for an ANSI C compiler to define any macros that are in the user's namespace. I.e. don't start with __ or _ uppercase.
- « Previous
-
- 1
- 2
- Next »