httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yann Ylavic <ylavic....@gmail.com>
Subject Re: nghttp2 warning - what is this?
Date Thu, 17 Sep 2015 11:26:48 GMT
Isn't mod_h2 removed from the list of "enable-mods-shared=all" already
when libh2 isn't available?
There is no point in enabling it in this case, so a warning about
disabling it automatically looks enough to me.

On Thu, Sep 17, 2015 at 10:27 AM, Stefan Eissing
<stefan.eissing@greenbytes.de> wrote:
> What do you propose? A better warning when libnghttp2 cannot be found at all? Anything
else?
>
>> Am 16.09.2015 um 18:42 schrieb Michael Felt <mamfelt@gmail.com>:
>>
>> well, correction on building nghttp. Seems it only expects to work in a GNU rte and
I do not have the time to verify an environment that will support "POSIX" and GNU requirements.
My experience is "small", i.e., not saying it cannot be done - but anytime I have tried to
build a library that insisted on gcc I could not get it to work reliably with packages built
using the IBM compiler and the default AIX libc (et al) .rte filesets. Basically, I need to
add all the libraries that gcc needs to compile something.
>>
>> Oh well. In any case, not tonight.
>>
>> (p.s. gcc 4.7.X implies a standard compiler might work - if I understand correctly
that there is a break with standard C starting with gcc 4.8)
>>
>> On Wed, Sep 16, 2015 at 6:31 PM, Michael Felt <mamfelt@gmail.com> wrote:
>> well, just built it again, with --enable-maintainer-mode added, so now have:
>>
>> It was created by configure, which was
>> generated by GNU Autoconf 2.69.  Invocation command line was
>>
>>   $ ./configure --enable-layout=AIX --with-apr=/opt/bin/apr-1-config --with-apr-util=/opt/bin/apu-1-config
--enable-mpms-shared=all --enable-mods-shared=all --disable-lua --enable-load-all-modules
--enable-maintainer-mode
>>
>> I guess it will "complain" if I try to do anything. re: SSL - it is special, especially
with the likes of libressl (aka "others" out there) - so maybe not the best test code - copying
the test for pcre may be better. That caught me asap when I first started.
>>
>> And I shall go look for the library and get it built. Thanks for your quick reply!
>>
>>
>>
>> Slightly off topic - not sure if relevent considering the -Werror changes (whatever
that is suppossed to mean in gcc land) here are the warning messages that are getting sent
by XLC to stderr (there are more/others going to stdout):
>>
>> "util_expr_eval.c", line 1767.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1768.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1769.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1771.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1772.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1773.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1774.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1775.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1776.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1777.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1778.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1779.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,char*)" is not allowed.
>> "util_expr_eval.c", line 1780.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,char*)" is not allowed.
>> "util_expr_eval.c", line 1781.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,char*)" is not allowed.
>> "util_expr_eval.c", line 1782.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1783.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1784.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1785.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1789.7: 1506-196 (W) Initialization between types "const
void* const" and "const char*(*)(struct {...}*,const void*,const struct apr_array_header_t*)"
is not allowed.
>> "util_expr_eval.c", line 1794.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1795.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1796.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1797.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1798.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1799.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1800.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1801.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1802.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1803.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1804.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1805.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1806.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1807.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1812.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1813.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1814.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*,const char*)" is not allowed.
>> "util_expr_eval.c", line 1815.7: 1506-196 (W) Initialization between types "const
void* const" and "int(*)(struct {...}*,const void*,const char*,const char*)" is not allowed.
>> make[2]: warning:  Clock skew detected.  Your build may be incomplete.
>> make[1]: warning:  Clock skew detected.  Your build may be incomplete.
>> "mod_include.c", line 722.26: 1506-068 (W) Operation between types "const void*"
and "const char*(*)(struct {...}*,const void*,const char*)" is not allowed.
>> "mod_headers.c", line 971.43: 1506-280 (W) Function argument assignment between types
"const void*" and "const char*(*)(struct request_rec*,char*)" is not allowed.
>> "ssl_engine_vars.c", line 161.26: 1506-068 (W) Operation between types "const void*"
and "const char*(*)(struct {...}*,const void*)" is not allowed.
>> "ssl_engine_vars.c", line 168.26: 1506-068 (W) Operation between types "const void*"
and "struct apr_array_header_t*(*)(struct {...}*,const void*,const char*)" is not allowed.
>>
>>
>>
>>
>>
>> On Wed, Sep 16, 2015 at 5:57 PM, Stefan Eissing <stefan.eissing@greenbytes.de>
wrote:
>> Hi,
>>
>> if you enable all modules, it will enable mod_h2 and that one needs libnghttp2. The
warning could be better, if this is missing, admittedly I just copied and modified mod_ssl's
test for openssl.
>>
>> //Stefan
>>
>>
>>
>> > Am 16.09.2015 um 17:51 schrieb Michael Felt <mamfelt@gmail.com>:
>> >
>> > Hello all,
>> >
>> > I have been ignoring building httpd-2.5.x and thought it was about time to start
taking notice. And I see a bunch of new messages - one of which may be a drift in time between
my AIX server and the NFS server I keep all the files on.
>> >
>> > But the first WARNING I saw was from nghttp2 - which perhaps I do not have at
all! Is this something extra, like pcre or apr that I need to have as a library first? If
so, the WARNING about it being too old is not correct - because I do not have it at all.
>> >
>> > However, if it is a module within httpd-2.5.x - how could it be too old when
I have just refreshed from the SVN repository?
>> >
>> > Snip....
>> >
>> > + ./configure
>> >                 --enable-layout=AIX
>> >                 --with-apr=/opt/bin/apr-1-config
>> >                 --with-apr-util=/opt/bin/apu-1-config
>> >                 --enable-mpms-shared=all
>> >                 --enable-mods-shared=all
>> >                 --disable-lua > build/aix/configure.out
>> > configure: WARNING: apr/apr-util is compiled without ldap support
>> > configure: WARNING: nghttp2 version is too old
>> > configure: WARNING: apr/apr-util is compiled without ldap support
>> > configure: WARNING: Your system does not support Journald.
>> > configure: WARNING: Your system does not support systemd.
>> > + make > build/aix/make.out
>> > make: Warning: File '/data/prj/apache/httpd/httpd-2.5.x/.deps' has modification
time 118 s in the future
>> >
>>
>>
>
> <green/>bytes GmbH
> Hafenweg 16, 48155 Münster, Germany
> Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
>
>
>

Mime
View raw message