Operating System - HP-UX
1824338 Members
3758 Online
109669 Solutions
New Discussion юеВ

Re: error when do make on lzib

 
Hanry Zhou
Super Advisor

error when do make on lzib

# make
cc -O -DNO_snprintf -DHAS_sprintf_void -DNO_ERRNO_H -c adler32.c
(Bundled) cc: warning 480: The -O option is available only with the C/AN
SI C product; ignored.
(Bundled) cc: "adler32.c", line 70: error 1701: Unsigned suffix is an A
NSI feature.
(Bundled) cc: "adler32.c", line 71: error 1701: Unsigned suffix is an A
NSI feature.
*** Error exit code 1

Stop.



Any idea what causes the problem, and how to solved. ANSI/C installed on this hp 11.0 server.
none
3 REPLIES 3
Michael Tully
Honored Contributor

Re: error when do make on lzib

ALthough ANSI/C may in fact be installed, from the message
"The -O option is available only with the C/ANSI C product; ignored."
indicates that perhaps an incorrect compiler is being used.

$ which cc
Anyone for a Mutiny ?
Sundar_7
Honored Contributor

Re: error when do make on lzib

Hi,

I have never compiled lzib. So I am taking a wild guess here :-)

Did you run "configure" before "make" ?

Configure usually creates the Makefile based on the platform and the C compiler installed.

If needed, you can try editing the Makefile and ensure it uses the ANSI/C compiler.

Sundar

Learn What to do ,How to do and more importantly When to do ?
A. Clay Stephenson
Acclaimed Contributor

Re: error when do make on lzib

Your $(CC) within the makefile (or one of its includes) is somehow defined to be the bundled c compiler rather than the ansi C compiler. The bundled C compiler is /usr/ccs/bin/cc whereas the ansi c compiler is /opt/ansi/bin/cc. It make be that the path to the bundled version appears earlier in the PATH setting or you make have an incorrect symbolic link in /usr/bin. /usr/bin/cc should be a soft link to /opt/ansi/bin/cc.

Although you don't appear to have syntax problems in the makefile, be aware when you make changes that make is one of the very few UNIX utilities that cares about rather than spaces. Make sure that your commands within a rules set each start on a line with a leading .

If it ain't broke, I can fix that.