I'm trying to go round the horn again to build curl (and libcurl) for
our population of Unix systems. Out the gate, I ran into trouble on
our HP-UX Itanium development system. I'm curious if anyone can provide
further info on building on HP-UX Itanium systems.

----- with gcc -----

On the first ./configure attempt, it found gcc and failed the make
attempt, seemingly in the same manner as reported here:
http://curl.haxx.se/mail/archive-2006-02/0016.html

>make
No suffix list.
Making all in lib
         make all-am
         /bin/sh ../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I../include/curl -I../include -I../include -I../lib
  -I../lib -DBUILDING_LIBCURL -DCURL_HIDDEN_SYMBOLS
-fvisibility=hidden -O2 -Wno-system-headers -MT libcurl_la-file.lo -MD
-MP -MF .deps/libcurl_la-file.Tpo -c -o libcurl_la-file.lo `test -f
'file.c' || echo './'`file.c
libtool: compile: gcc -DHAVE_CONFIG_H -I../include/curl -I../include
-I../include -I../lib -I../lib -DBUILDING_LIBCURL -DCURL_HIDDEN_SYMBOLS
-fvisibility=hidden -O2 -Wno-system-headers -MT libcurl_la-file.lo -MD
-MP -MF .deps/libcurl_la-file.Tpo -c file.c -fPIC -DPIC -o
.libs/libcurl_la-file.o
In file included from ../include/curl/curl.h:78,
                  from cookie.h:26,
                  from urldata.h:79,
                  from file.c:52:
/usr/include/sys/socket.h:535: error: static declaration of 'sendfile'
follows non-static declaration
/usr/include/sys/socket.h:506: error: previous declaration of 'sendfile'
was here
/usr/include/sys/socket.h:536: error: static declaration of 'sendpath'
follows non-static declaration
/usr/include/sys/socket.h:508: error: previous declaration of 'sendpath'
was here
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.

It was suggested that the poster try to build another network app and he
tried putty with CFLAGS = -D_XOPEN_SOURCE_EXTENDED and
ULDFLAGS = -lxnet and it built, but bombed when executed. I see no
further mention of this in terms of work-arounds.

Taking the hint from above, I re-ran using:
CFLAGS="-D_XOPEN_SOURCE_EXTENDED" ./configure and I seem to have gotten
a working curl build. I wonder if configure should always set this
flag for HP-UX systems? It (or something better) would aim for maximum
portability on this platform. Is there a place where all these

This warning seems strange. Why set CPPFLAGS for a c program?:
configure:3645: using CFLAGS: -D_XOPEN_SOURCE_EXTENDED
configure:3651: CFLAGS note: CFLAGS should only be used to specify C
compiler flags, not macro definitions. Use CPPFLAGS for:
  -D_XOPEN_SOURCE_EXTENDED

make test was even happy, although the output was littered with stty and
kill messages, plus this burp in test 1528:

test 1526...OK (896 out of 936, remaining: 00:24)
test 1527...OK (897 out of 936, remaining: 00:24)
test 1528...OK (898 out of 936, remaining: 00:23)
   File "./http_pipe.py", line 398
     except RequestTooLargeError as e:
                                  ^
SyntaxError: invalid syntax
RUN: failed to start the HTTP3 server
== Contents of files in the log/ dir after test 1900
test 2000...stty: : Not a typewriter
OK (903 out of 936, remaining: 00:20)
test 2001...stty: : Not a typewriter
OK (904 out of 936, remaining: 00:19)
test 2002...stty: : Not a typewriter
OK (905 out of 936, remaining: 00:19)
test 2003...stty: : Not a typewriter
stty: : Not a typewriter
OK (906 out of 936, remaining: 00:18)
sh: 1646 Killed
sh: 23912 Killed
sh: 27734 Killed
sh: 28273 Killed
sh: 28746 Killed
TESTDONE: 728 tests out of 728 reported OK: 100%
TESTDONE: 944 tests were considered during 564 seconds.

----- with cc ------

Ultimately, I probably want to use the native compiler.
HP aC++/ANSI C B3910B A.06.10 [Mar 22 2006]

CC=cc ./configure

Dies on:
checking if compiler halts on compilation errors... yes
checking if compiler halts on negative sized arrays... yes
checking if compiler halts on function prototype mismatch... no
configure: error: compiler does not halt on function prototype mismatch.

just like:
http://curl.haxx.se/mail/lib-2013-09/0081.html

http://curl.haxx.se/mail/lib-2013-09/0081.html from that thread says:
"You can easily just comment out CURL_CHECK_COMPILER_PROTOTYPE_MISMATCH
from configure.ac, re-run autoconf and then run configure again and that
failure shouldn't bother you."

I found and commented out the prototype check in configure.ac, but could
not get autoconf to run right:

>autoconf configure.ac
interpreter "/usr/local/bin/perl" not found
/usr/local/bin/autoconf[271]: /usr/local/bin/autom4te: not found.

On this system, perl is in /usr/bin. (I don't know if that's normal, I
did not set the system up.)

I'm going to put this aside for a while, but wanted to note it.

Rich

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-07-09