topic Re: aCC compilation error. in Operating System - HP-UX

aCC compilation error.

Rajesh SB — Sat, 28 Jun 2003 12:25:51 GMT

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

Re: aCC compilation error.

Caesar_3 — Sat, 28 Jun 2003 12:34:40 GMT

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

Re: aCC compilation error.

Rajesh SB — Sat, 28 Jun 2003 12:46:25 GMT

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

Re: aCC compilation error.

Caesar_3 — Sat, 28 Jun 2003 13:04:20 GMT

Hi,

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

Caesar

Re: aCC compilation error.

Umapathy S — Sat, 28 Jun 2003 17:45:26 GMT

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

Re: aCC compilation error.

A. Clay Stephenson — Sat, 28 Jun 2003 18:01:03 GMT

Do an env and compare environment variables. Check how your makefiles set compiler and linker flags.

Re: aCC compilation error.

Rajesh SB — Sun, 29 Jun 2003 08:05:59 GMT

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

Re: aCC compilation error.

Robert-Jan Goossens — Sun, 29 Jun 2003 08:48:49 GMT

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.

Re: aCC compilation error.

Robert-Jan Goossens — Sun, 29 Jun 2003 08:58:34 GMT

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.

Re: aCC compilation error.

Steven Gillard_2 — Mon, 30 Jun 2003 07:04:50 GMT

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

Re: aCC compilation error.

Armin Kunaschik — Mon, 30 Jun 2003 07:55:28 GMT

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

Re: aCC compilation error.

Armin Kunaschik — Mon, 30 Jun 2003 08:21:33 GMT

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