Operating System - Linux
1753875 Members
7348 Online
108809 Solutions
New Discussion юеВ

Re: Migrating our app from HP-UX PA-RISC to HP-UX 11.23 Integrity

 
SOLVED
Go to solution
JaganKumar
Advisor

Re: Migrating our app from HPUX PA RISC to HPUX 11i

Thanks for your response.

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.
Dennis Handly
Acclaimed Contributor

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

JaganKumar
Advisor

Re: Migrating our app from HPUX PA RISC to HPUX 11i

Thanks for your valuable comments.

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.

Dennis Handly
Acclaimed Contributor

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.

JaganKumar
Advisor

Re: Migrating our app from HPUX PA RISC to HPUX 11i

We found the same in some of the header. problem is the IF condition never goes true, so we are facing problem since some struct are declared into the if block.

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?
V. Nyga
Honored Contributor

Re: Migrating our app from HPUX PA RISC to HPUX 11i

@rick,

could you please visit this one:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1126273

Volkmar
*** Say 'Thanks' with Kudos ***
Dennis Handly
Acclaimed Contributor

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.