Operating System - HP-UX
1833440 Members
3372 Online
110052 Solutions
New Discussion

Re: aCC compilation error.

 
SOLVED
Go to solution
Rajesh SB
Esteemed Contributor

aCC compilation error.

Hi,

We are getting the following compilation error, when we run "make" on HP K570 Server with HPUX 11.0. But same "make" works fine on HP L2000 Server with HPUX 11.0.
In both cases required binary is built properly and source code is also same.

Can any one throw some light on it.

ERROR Details:

/usr/ccs/bin/ld: (Warning) At least one PA 2.0 object file (BMPSpace.o) was
dete
cted. The linked output may not run on a PA 1.x system.
pxdb32: seek to offset 0 (0) in ../bin/alcatel_traffic_md failed
pxdb32: internal error. File won't be debuggable (still a valid executable)
*** Error exit code 1

Thanks in advance.

Rajesh
11 REPLIES 11
Caesar_3
Esteemed Contributor

Re: aCC compilation error.

Hello!

Check if you have the same patch level for
ld (linker) on the machines.

Use the swlist for the check
You may find that some patch installed on the L2000 but not on the K570

Caesar
Rajesh SB
Esteemed Contributor

Re: aCC compilation error.

Thanks Mr.Caesar for your quick response.

We have the same ld patch level on the both the servers.

i.e.
PHSS_22514 11.0 ld(1) and linker tools cumulative patch

Really strange, what could be other?

Thanks & Regds,
Rajesh
Caesar_3
Esteemed Contributor
Solution

Re: aCC compilation error.

Hi,

Two thing: does both system 64/32bit?
Write here pls what return the what on the
/usr/ccs/bin/ld

Caesar
Umapathy S
Honored Contributor

Re: aCC compilation error.

Rajesh,
Just a thought. There may be some problem with debug flag. Remove the debug flag and try to compile and link. Revert back with details.

HTH,
Umapathy
Arise Awake and Stop NOT till the goal is Reached!
A. Clay Stephenson
Acclaimed Contributor

Re: aCC compilation error.

Do an env and compare environment variables. Check how your makefiles set compiler and linker flags.
If it ain't broke, I can fix that.
Rajesh SB
Esteemed Contributor

Re: aCC compilation error.

Hi,

Good pointers I gor from you guys.

1. Both servers are 64 Bit (HPUX11.0)
2. When we remove the "-g" flag, it works fine in K-Class also. But, same make file works well with "-g" option on L-Class.

Any more pointers?

Thanks & Regds,
Rajesh
Robert-Jan Goossens
Honored Contributor

Re: aCC compilation error.

Hi,

./bin/alcatel_traffic_md failed

My guess is that make can not find the right files, double check your echo $PATH outputs from both servers as Clay suggested.

Robert-Jan.
Robert-Jan Goossens
Honored Contributor

Re: aCC compilation error.

By the way check the version of make on both servers, you said you have installed the latest ld linker patch, is it configured ? And check SHLIB_PATH too.

# what /usr/ccs/bin/ld

http://www2.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=PHSS_28434

Robert-Jan.
Steven Gillard_2
Honored Contributor

Re: aCC compilation error.

You're getting an internal error from pxdb, which is only called when you use the -g flag to add debug information.

Try the latest pxdb patch PHSS_27983.

Regards,
Steve

Armin Kunaschik
Esteemed Contributor

Re: aCC compilation error.

Hi,

the L2000 is a PA-2.0 architecture and K570 is a PA-1.x machine.
Therefore you get the error if you want to use newer object files on the older platform.
Every newer machine with PA-RISC 8xxx CPU's is PA-2.0 architecure.

Try adding the switch +DAportable to your Compiler and Linker calls, this will generate
PA-1.0 code which runs on all platforms (even a bit slower on PA-2.0).

Alternatively use seperate builds for every platform...

Armin
And now for something completely different...
Armin Kunaschik
Esteemed Contributor

Re: aCC compilation error.

I have to correct myself... K570 is PA-8200.
So this means somebody is linking PA-1.x code on
one machine and PA-2.0 on the other.
Check the compiler environment/Makefile for any +DA switch.
Maybe you use any third party libraries/archives which
where built on PA-1.x hosts? Or the compiler versions differ?

As stated in the error message the executable is still valid
but does not run on older (PA-7xxx) systems.
So you can live with this error :-)

And you can use +DA2.0 to generate explicitly 2.0 code
if you have access to all modules.

Finally get more information using aCC +help!

Armin
And now for something completely different...