Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Apache: Dev

problem with build on AIX 6.1

  

 
Apache dev RSS feed   Index | Next | Previous | View Threaded


mamfelt at gmail

Oct 6, 2009, 11:01 AM

Post #1 of 18 (1470 views)
Permalink
problem with build on AIX 6.1
Hello all,

I am trying to get a build made on AIX 6.1. And I suspect the problem I am
having is the "root" cause of the problems people are reporting regarding
can't make .so files when using AIX 6.1 (p.s. the quick fix is to compile on
AIX 5.3, it runs fine on AIX 6.1)

Standard process:
unpack archive,
./configure --prefix=/usr/local/apache2 \
--enable-module=so \
--enable-module=unique_id \
--enable-module=usertrack \
--enable-module=vhost_alias \
--enable-rewrite=shared \
--enable-speling=shared \
--enable-digest=shared \
--enable-cgi=shared \
--enable-headers=shared \
--enable-info=shared \
--enable-log_forensic=shared \
--enable-proxy=shared \
--enable-proxy-connect=shared \
--enable-proxy-ftp=shared \
--enable-proxy-http=shared \
--enable-proxy-ajp=shared \
--enable-proxy-balancer=shared \
--with-z=/data/prj/zlib-1.2.3
make

On AIX5.3 I have as result, among others:
# find modules -name '*.so'
modules/generators/.libs/mod_info.so
modules/generators/.libs/mod_cgi.so
modules/loggers/.libs/mod_log_forensic.so
modules/mappers/.libs/mod_speling.so
modules/mappers/.libs/mod_rewrite.so
modules/metadata/.libs/mod_headers.so
modules/proxy/.libs/mod_proxy.so
modules/proxy/.libs/mod_proxy_connect.so
modules/proxy/.libs/mod_proxy_ftp.so
modules/proxy/.libs/mod_proxy_http.so
modules/proxy/.libs/mod_proxy_scgi.so
modules/proxy/.libs/mod_proxy_ajp.so
modules/proxy/.libs/mod_proxy_balancer.so
=====
And...
# find modules -name '*.slo'
modules/generators/mod_cgi.slo
modules/generators/mod_info.slo
modules/loggers/mod_log_forensic.slo
modules/mappers/mod_rewrite.slo
modules/mappers/mod_speling.slo
modules/metadata/mod_headers.slo
modules/proxy/mod_proxy.slo
modules/proxy/ajp_header.slo
modules/proxy/mod_proxy_connect.slo
modules/proxy/mod_proxy_scgi.slo
modules/proxy/mod_proxy_ftp.slo
modules/proxy/ajp_utils.slo
modules/proxy/mod_proxy_ajp.slo
modules/proxy/proxy_util.slo
modules/proxy/ajp_msg.slo
modules/proxy/ajp_link.slo
modules/proxy/mod_proxy_http.slo
modules/proxy/mod_proxy_balancer.slo
++++++++++++++++++++++
On AIX 6.1 I have:
michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.so'
=================================================
michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.slo'
modules/generators/mod_info.slo
modules/generators/mod_cgi.slo
modules/loggers/mod_log_forensic.slo
modules/mappers/mod_speling.slo
modules/mappers/mod_rewrite.slo
modules/metadata/mod_headers.slo
modules/proxy/mod_proxy.slo
modules/proxy/proxy_util.slo
modules/proxy/mod_proxy_connect.slo
modules/proxy/mod_proxy_ftp.slo
modules/proxy/mod_proxy_http.slo
modules/proxy/mod_proxy_scgi.slo
modules/proxy/mod_proxy_ajp.slo
modules/proxy/ajp_header.slo
modules/proxy/ajp_link.slo
modules/proxy/ajp_msg.slo
modules/proxy/ajp_utils.slo
modules/proxy/mod_proxy_balancer.slo
++++++++++++++++++++++++++++++++++++
Suspecting it was libtool I downloaded, built and installed libtool 2.2.6a
and Python 2.6.3, ope did the following:
make distclean
./buildconf
./configure *** as above
make
=========
make ends with:
Making all in srclib
make[1]: Entering directory `/data/prj/http-2.2.14.bad/srclib'
Making all in apr
make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
make[3]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
make[3]: Nothing to be done for `local-all'.
make[3]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
Making all in apr-util
make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/prj/http-2.2.14.bad/srclib'
make: *** [all-recursive] Error 1
michael [at] x05:[/data/prj/http-2.2.14.bad]

Attached: the config.log from each directory/system

AIX 5.3 TL07, xlc v7 patched to July 2009
AIX 6.1 : 6100-03-01-0921 (TL 03), same compiler.
Attachments: config.aix61.log (57.1 KB)
  config.aix53.log (57.7 KB)
  config.aix61.libtool2.2.6.log (353 KB)


trawick at gmail

Oct 6, 2009, 11:16 AM

Post #2 of 18 (1434 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On Tue, Oct 6, 2009 at 2:05 PM, Michael Felt <mamfelt [at] gmail> wrote:

> forgot to mention: I have done
> export CC=xlc
> in the builds yesterday, so the libtool build should reflect that. The two
> builds I just did for this report I neither defined nor exported CC before
> running configure.
>
>
> On Tue, Oct 6, 2009 at 8:01 PM, Michael Felt <mamfelt [at] gmail> wrote:
>
>> Suspecting it was libtool I downloaded, built and installed libtool 2.2.6a
>> and Python 2.6.3, ope did the following:
>> make distclean
>> ./buildconf
>> ./configure *** as above
>> make
>>
>
Does that libtool handle aix 6? The libtool.m4 in my older libtool has lots
of stanzas with

aix4* | aix5*)

or similar. I'd change those to include aix6* and see if that helps.

I think apr_hints.m4 and APR's configure.in also need a change to handle
aix6*. I don't know about the various config.guess files.


mamfelt at gmail

Oct 6, 2009, 12:10 PM

Post #3 of 18 (1435 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
Jeff Trawick wrote:
> On Tue, Oct 6, 2009 at 2:05 PM, Michael Felt <mamfelt [at] gmail> wrote:
>
>
>> forgot to mention: I have done
>> export CC=xlc
>> in the builds yesterday, so the libtool build should reflect that. The two
>> builds I just did for this report I neither defined nor exported CC before
>> running configure.
>>
>>
>> On Tue, Oct 6, 2009 at 8:01 PM, Michael Felt <mamfelt [at] gmail> wrote:
>>
>>
>>> Suspecting it was libtool I downloaded, built and installed libtool 2.2.6a
>>> and Python 2.6.3, ope did the following:
>>> make distclean
>>> ./buildconf
>>> ./configure *** as above
>>> make
>>>
>>>
> Does that libtool handle aix 6? The libtool.m4 in my older libtool has lots
> of stanzas with
>
> aix4* | aix5*)
>
> or similar. I'd change those to include aix6* and see if that helps.
>
> I think apr_hints.m4 and APR's configure.in also need a change to handle
> aix6*. I don't know about the various config.guess files.
>
michael [at] x05:[/data/prj/http-2.2.14.bad/srclib/apr/build]grep -c aix
*.m4 | grep -v :0
apr_hints.m4:5
libtool.m4:53
ltdl.m4:2
Most of these are in the form:
aix[[4-9]]*)

I saw a few aix5 ones, no aix6 specific ones. So you may have a good
starting point.

in aclocal.m4 for libtool.m4 I did not find a specific aix6) switch
(also the aix[[4-9]]* format.

regading the new libtool - is it enough to jst run ./buildconf - are
there extra arguments I should be giving? Is there any logged output.

Are people interested in the src/apr/libtool that is generated? easy
enough to attach if someone can make some sense of them.


trawick at gmail

Oct 6, 2009, 12:22 PM

Post #4 of 18 (1438 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On Tue, Oct 6, 2009 at 3:10 PM, Michael Felt <mamfelt [at] gmail> wrote:

> Jeff Trawick wrote:
>
>> On Tue, Oct 6, 2009 at 2:05 PM, Michael Felt <mamfelt [at] gmail> wrote:
>>
>>
>>
>>> forgot to mention: I have done
>>> export CC=xlc
>>> in the builds yesterday, so the libtool build should reflect that. The
>>> two
>>> builds I just did for this report I neither defined nor exported CC
>>> before
>>> running configure.
>>>
>>>
>>> On Tue, Oct 6, 2009 at 8:01 PM, Michael Felt <mamfelt [at] gmail> wrote:
>>>
>>>
>>>
>>>> Suspecting it was libtool I downloaded, built and installed libtool
>>>> 2.2.6a
>>>> and Python 2.6.3, ope did the following:
>>>> make distclean
>>>> ./buildconf
>>>> ./configure *** as above
>>>> make
>>>>
>>>>
>>>>
>>> Does that libtool handle aix 6? The libtool.m4 in my older libtool has
>> lots
>> of stanzas with
>>
>> aix4* | aix5*)
>>
>> or similar. I'd change those to include aix6* and see if that helps.
>>
>> I think apr_hints.m4 and APR's configure.in also need a change to handle
>> aix6*. I don't know about the various config.guess files.
>>
>>
> michael [at] x05:[/data/prj/http-2.2.14.bad/srclib/apr/build]grep -c aix *.m4
> | grep -v :0
> apr_hints.m4:5
> libtool.m4:53
> ltdl.m4:2
> Most of these are in the form:
> aix[[4-9]]*)
>
> I saw a few aix5 ones, no aix6 specific ones. So you may have a good
> starting point.
>
> in aclocal.m4 for libtool.m4 I did not find a specific aix6) switch (also
> the aix[[4-9]]* format.
>
> regading the new libtool - is it enough to jst run ./buildconf - are there
> extra arguments I should be giving? Is there any logged output.
>

should be; confirm by looking in configure to see if the new stuff is in
there


>
> Are people interested in the src/apr/libtool that is generated? easy enough
> to attach if someone can make some sense of them.
>
>
Others can speak for themselves, but I think a hint that libtool may need to
look for aix6 is as far as we can take it. Check with the libtool folks or
comp.os.unix.aix for info about which level of libtool works well on on AIX
6.


rainer.jung at kippdata

Oct 6, 2009, 12:55 PM

Post #5 of 18 (1440 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On 06.10.2009 21:22, Jeff Trawick wrote:
> michael [at] x05:[/data/prj/http-2.2.14.bad/srclib/apr/build]grep -c aix
> *.m4 | grep -v :0
> apr_hints.m4:5
> libtool.m4:53
> ltdl.m4:2
> Most of these are in the form:
> aix[[4-9]]*)
>
> I saw a few aix5 ones, no aix6 specific ones. So you may have a good
> starting point.
>
> in aclocal.m4 for libtool.m4 I did not find a specific aix6) switch
> (also the aix[[4-9]]* format.
>
> regading the new libtool - is it enough to jst run ./buildconf - are
> there extra arguments I should be giving? Is there any logged output.
>
>
> should be; confirm by looking in configure to see if the new stuff is in
> there

I just checked the latest libtool 1.x (1.5.26) which only has aix[4-9]
patterns, nothing aix5 specific. Another source of trouble could be
autoconf (e.g. config.guess) and automake. Recent versions (2.64 resp.
1.10.2) seem to respect AIX 6 in their script.

I don't have an AIX system at hand at the moment, but last time I build
on AIX 6.1 I was astonished, that they used .a as a suffix for shared
libs. They have two types of shared libs, depending on when symbol
resolution is done.

My notes tell me, that at that time I changed the contents of libtool in
the following way:

hardcode_action=immediate -> hardcode_action=relink
hardcode_direct=yes -> hardcode_direct=no
hardcode_minus_L=no -> hardcode_minus_L=yes

I don't remember whether that was actually necessary.

Regards,

Rainer


mamfelt at gmail

Oct 6, 2009, 1:18 PM

Post #6 of 18 (1431 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
Rainer Jung wrote:
> On 06.10.2009 21:22, Jeff Trawick wrote:
>
>> michael [at] x05:[/data/prj/http-2.2.14.bad/srclib/apr/build]grep -c aix
>> *.m4 | grep -v :0
>> apr_hints.m4:5
>> libtool.m4:53
>> ltdl.m4:2
>> Most of these are in the form:
>> aix[[4-9]]*)
>>
>> I saw a few aix5 ones, no aix6 specific ones. So you may have a good
>> starting point.
>>
>> in aclocal.m4 for libtool.m4 I did not find a specific aix6) switch
>> (also the aix[[4-9]]* format.
>>
>> regading the new libtool - is it enough to jst run ./buildconf - are
>> there extra arguments I should be giving? Is there any logged output.
>>
>>
>> should be; confirm by looking in configure to see if the new stuff is in
>> there
>>
>
> I just checked the latest libtool 1.x (1.5.26) which only has aix[4-9]
> patterns, nothing aix5 specific. Another source of trouble could be
> autoconf (e.g. config.guess) and automake. Recent versions (2.64 resp.
> 1.10.2) seem to respect AIX 6 in their script.
>
> I don't have an AIX system at hand at the moment, but last time I build
> on AIX 6.1 I was astonished, that they used .a as a suffix for shared
> libs. They have two types of shared libs, depending on when symbol
> resolution is done.
>
> My notes tell me, that at that time I changed the contents of libtool in
> the following way:
>
> hardcode_action=immediate -> hardcode_action=relink
> hardcode_direct=yes -> hardcode_direct=no
> hardcode_minus_L=no -> hardcode_minus_L=yes
>
> I don't remember whether that was actually necessary.
>
> Regards,
>
> Rainer
>
I had autoconf 2.63 installed (I believe buildconf wanted at least
2.50). Automake I do not have installed, so I'll install that and try again.
Step 1 - unpack the archive again, and run buildconf. I'll capture the
output to nohup.out - and check in a configure (directory) for
additional logs.

I have a POWER4 (AIX 6.1) and and POWER5 (with ivm and partitions, AIX
6.1 and AIX 5.3) so I can test several setups in parallel. Just provide
simple instructions. the libtool people seem to have put great effort
into aix5 and ia64. And a lot of the code seems to be gcc related. I'll
look into getting two partitions (5.3 and 6.1) with a gcc compiler and
see how things run.
I know the xlC v7 compiler is oldish (withdrawn from support 30-09-09)
but it is what I have.

Suggestions welcome!

btw: I believe AIX documentation says they use .so for shared objects,
but also support .a as a shared object archive. And of course, the docs
I found are on my other computer - that I cannot access at the moment.
As I get further I'll be working on a FAQ for http://www.rootvg.net (I
am webmaster there, and I am working on this build for that portal.) btw
- my other goal is to build a binary distrubtion for AIX and publish it
via rootvg.net.


mamfelt at gmail

Oct 6, 2009, 1:53 PM

Post #7 of 18 (1429 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
Michael Felt wrote:
> Rainer Jung wrote:
>> On 06.10.2009 21:22, Jeff Trawick wrote:
>>
>>> michael [at] x05:[/data/prj/http-2.2.14.bad/srclib/apr/build]grep -c
>>> aix
>>> *.m4 | grep -v :0
>>> apr_hints.m4:5
>>> libtool.m4:53
>>> ltdl.m4:2
>>> Most of these are in the form:
>>> aix[[4-9]]*)
>>>
>>> I saw a few aix5 ones, no aix6 specific ones. So you may have a
>>> good
>>> starting point.
>>>
>>> in aclocal.m4 for libtool.m4 I did not find a specific aix6) switch
>>> (also the aix[[4-9]]* format.
>>>
>>> regading the new libtool - is it enough to jst run ./buildconf -
>>> are
>>> there extra arguments I should be giving? Is there any logged
>>> output.
>>>
>>>
>>> should be; confirm by looking in configure to see if the new stuff
>>> is in
>>> there
>>>
>>
>> I just checked the latest libtool 1.x (1.5.26) which only has aix[4-9]
>> patterns, nothing aix5 specific. Another source of trouble could be
>> autoconf (e.g. config.guess) and automake. Recent versions (2.64 resp.
>> 1.10.2) seem to respect AIX 6 in their script.
>>
>> I don't have an AIX system at hand at the moment, but last time I build
>> on AIX 6.1 I was astonished, that they used .a as a suffix for shared
>> libs. They have two types of shared libs, depending on when symbol
>> resolution is done.
>>
>> My notes tell me, that at that time I changed the contents of libtool in
>> the following way:
>>
>> hardcode_action=immediate -> hardcode_action=relink
>> hardcode_direct=yes -> hardcode_direct=no
>> hardcode_minus_L=no -> hardcode_minus_L=yes
>>
>> I don't remember whether that was actually necessary.
>>
>> Regards,
>>
>> Rainer
>>
> I had autoconf 2.63 installed (I believe buildconf wanted at least
> 2.50). Automake I do not have installed, so I'll install that and try
> again.
> Step 1 - unpack the archive again, and run buildconf. I'll capture the
> output to nohup.out - and check in a configure (directory) for
> additional logs.
>
> I have a POWER4 (AIX 6.1) and and POWER5 (with ivm and partitions, AIX
> 6.1 and AIX 5.3) so I can test several setups in parallel. Just
> provide simple instructions. the libtool people seem to have put great
> effort into aix5 and ia64. And a lot of the code seems to be gcc
> related. I'll look into getting two partitions (5.3 and 6.1) with a
> gcc compiler and see how things run.
> I know the xlC v7 compiler is oldish (withdrawn from support 30-09-09)
> but it is what I have.
>
> Suggestions welcome!
>
> btw: I believe AIX documentation says they use .so for shared objects,
> but also support .a as a shared object archive. And of course, the
> docs I found are on my other computer - that I cannot access at the
> moment. As I get further I'll be working on a FAQ for
> http://www.rootvg.net (I am webmaster there, and I am working on this
> build for that portal.) btw - my other goal is to build a binary
> distrubtion for AIX and publish it via rootvg.net.
michael [at] x05:[/data/prj]diff http*14/build http*14.bad/build
Only in http-2.2.14.bad/build: config_vars.mk
Only in http-2.2.14.bad/build: config_vars.sh
Common subdirectories: httpd-2.2.14/build/pkg and http-2.2.14.bad/build/pkg
Common subdirectories: httpd-2.2.14/build/rpm and http-2.2.14.bad/build/rpm
Only in http-2.2.14.bad/build: rules.mk
Common subdirectories: httpd-2.2.14/build/win32 and
http-2.2.14.bad/build/win32

michael [at] x05:[/data/prj]ls -l http*14*/configure
-rwxr-xr-x 1 michael www 654523 Oct 05 20:38
http-2.2.14.bad/configure
-rwxr-xr-x 1 michael www 654523 Oct 06 20:50
httpd-2.2.14/configure

So, the configure file are the same, but having automake installed seems
to influenced the contents of the build directory at least.
Next, the configure.log


mamfelt at gmail

Oct 6, 2009, 2:24 PM

Post #8 of 18 (1435 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On Tue, Oct 6, 2009 at 10:53 PM, Michael Felt <mamfelt [at] gmail> wrote:

> Michael Felt wrote:
>
>> Rainer Jung wrote:
>>
>>> On 06.10.2009 21:22, Jeff Trawick wrote:
>>>
>>>
>>>> michael [at] x05:[/data/prj/http-2.2.14.bad/srclib/apr/build]grep -c aix
>>>> *.m4 | grep -v :0
>>>> apr_hints.m4:5
>>>> libtool.m4:53
>>>> ltdl.m4:2
>>>> Most of these are in the form:
>>>> aix[[4-9]]*)
>>>>
>>>> I saw a few aix5 ones, no aix6 specific ones. So you may have a good
>>>> starting point.
>>>>
>>>> in aclocal.m4 for libtool.m4 I did not find a specific aix6) switch
>>>> (also the aix[[4-9]]* format.
>>>>
>>>> regading the new libtool - is it enough to jst run ./buildconf - are
>>>> there extra arguments I should be giving? Is there any logged output.
>>>>
>>>>
>>>> should be; confirm by looking in configure to see if the new stuff is in
>>>> there
>>>>
>>>>
>>>
>>> I just checked the latest libtool 1.x (1.5.26) which only has aix[4-9]
>>> patterns, nothing aix5 specific. Another source of trouble could be
>>> autoconf (e.g. config.guess) and automake. Recent versions (2.64 resp.
>>> 1.10.2) seem to respect AIX 6 in their script.
>>>
>>> I don't have an AIX system at hand at the moment, but last time I build
>>> on AIX 6.1 I was astonished, that they used .a as a suffix for shared
>>> libs. They have two types of shared libs, depending on when symbol
>>> resolution is done.
>>>
>>> My notes tell me, that at that time I changed the contents of libtool in
>>> the following way:
>>>
>>> hardcode_action=immediate -> hardcode_action=relink
>>> hardcode_direct=yes -> hardcode_direct=no
>>> hardcode_minus_L=no -> hardcode_minus_L=yes
>>>
>>> I don't remember whether that was actually necessary.
>>>
>>> Regards,
>>>
>>> Rainer
>>>
>>>
>> I had autoconf 2.63 installed (I believe buildconf wanted at least 2.50).
>> Automake I do not have installed, so I'll install that and try again.
>> Step 1 - unpack the archive again, and run buildconf. I'll capture the
>> output to nohup.out - and check in a configure (directory) for additional
>> logs.
>>
>> I have a POWER4 (AIX 6.1) and and POWER5 (with ivm and partitions, AIX 6.1
>> and AIX 5.3) so I can test several setups in parallel. Just provide simple
>> instructions. the libtool people seem to have put great effort into aix5 and
>> ia64. And a lot of the code seems to be gcc related. I'll look into getting
>> two partitions (5.3 and 6.1) with a gcc compiler and see how things run.
>> I know the xlC v7 compiler is oldish (withdrawn from support 30-09-09) but
>> it is what I have.
>>
>> Suggestions welcome!
>>
>> btw: I believe AIX documentation says they use .so for shared objects, but
>> also support .a as a shared object archive. And of course, the docs I found
>> are on my other computer - that I cannot access at the moment. As I get
>> further I'll be working on a FAQ for http://www.rootvg.net (I am
>> webmaster there, and I am working on this build for that portal.) btw - my
>> other goal is to build a binary distrubtion for AIX and publish it via
>> rootvg.net.
>>
> michael [at] x05:[/data/prj]diff http*14/build http*14.bad/build
> Only in http-2.2.14.bad/build: config_vars.mk
> Only in http-2.2.14.bad/build: config_vars.sh
> Common subdirectories: httpd-2.2.14/build/pkg and http-2.2.14.bad/build/pkg
> Common subdirectories: httpd-2.2.14/build/rpm and http-2.2.14.bad/build/rpm
> Only in http-2.2.14.bad/build: rules.mk
> Common subdirectories: httpd-2.2.14/build/win32 and
> http-2.2.14.bad/build/win32
>
> michael [at] x05:[/data/prj]ls -l http*14*/configure
> -rwxr-xr-x 1 michael www 654523 Oct 05 20:38
> http-2.2.14.bad/configure
> -rwxr-xr-x 1 michael www 654523 Oct 06 20:50
> httpd-2.2.14/configure
>
> So, the configure file are the same, but having automake installed seems to
> influenced the contents of the build directory at least.
> Next, the configure.log
>
> michael [at] x05:[/data/prj/httpd-2.2.14]grep "\./configure\[" nohup.conf*
./configure[4131]: ./srclib/apr-util/apu-1-config: not found
./configure[4147]: ./srclib/apr-util/apu-1-config: not found
./configure[4148]: ./srclib/apr-util/apu-1-config: not found
./configure[4149]: ./srclib/apr-util/apu-1-config: not found
./configure[5725]: ./srclib/apr-util/apu-1-config: not found
./configure[5863]: 6000-ibm-aix: bad number
./configure[21518]: ./srclib/apr-util/apu-1-config: not found
./configure[21519]: ./srclib/apr-util/apu-1-config: not found
michael [at] x05:[/data/prj/httpd-2.2.14]cd ..
michael [at] x05:[/data/prj]r ls
ls -l http*14*/config*.log
-rw------- 1 michael www 361544 Oct 05 21:22
http-2.2.14.bad/config.log
-rw------- 1 michael www 360251 Oct 06 21:15
httpd-2.2.14/config.log

The make job seems to proceed, but ends the same as yesterday...
....
nawk -f /data/prj/httpd-2.2.14/srclib/apr/build/make_exports.awk
/data/prj/httpd-2.2.14/srclib/apr/include/apr_allocator.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_atomic.h /data/pr
j/httpd-2.2.14/srclib/apr/include/apr_dso.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_env.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_errno.h
/data/prj/httpd-2.2.14/srclib/apr/in
clude/apr_file_info.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_file_io.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_fnmatch.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_genera
l.h /data/prj/httpd-2.2.14/srclib/apr/include/apr_getopt.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_global_mutex.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_hash.h /data/prj/htt
pd-2.2.14/srclib/apr/include/apr_inherit.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_lib.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_mmap.h
/data/prj/httpd-2.2.14/srclib/apr/incl
ude/apr_network_io.h /data/prj/httpd-2.2.14/srclib/apr/include/apr_poll.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_pools.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_portable.h /
data/prj/httpd-2.2.14/srclib/apr/include/apr_proc_mutex.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_random.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_ring.h /data/prj/httpd-2.2.
14/srclib/apr/include/apr_shm.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_signal.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_strings.h
/data/prj/httpd-2.2.14/srclib/apr/include/a
pr_support.h /data/prj/httpd-2.2.14/srclib/apr/include/apr_tables.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_thread_cond.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_thread_mutex
.h /data/prj/httpd-2.2.14/srclib/apr/include/apr_thread_proc.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_thread_rwlock.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_time.h /data/pr
j/httpd-2.2.14/srclib/apr/include/apr_user.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_version.h
/data/prj/httpd-2.2.14/srclib/apr/include/apr_want.h > exports.c
xlc -E -DHAVE_CONFIG_H -U__STR__ -D_THREAD_SAFE -D_LARGEFILE64_SOURCE
-I./include -I/data/prj/httpd-2.2.14/srclib/apr/include/arch/unix
-I./include/arch/unix -I/data/prj/httpd-2.2.14/s
rclib/apr/include/arch/unix -I/data/prj/httpd-2.2.14/srclib/apr/include
export_vars.c | sed -e 's/^\#[^!]*//' | sed -e '/^$/d' >> apr.exp
xlc -E -DHAVE_CONFIG_H -U__STR__ -D_THREAD_SAFE -D_LARGEFILE64_SOURCE
-I./include -I/data/prj/httpd-2.2.14/srclib/apr/include/arch/unix
-I./include/arch/unix -I/data/prj/httpd-2.2.14/s
rclib/apr/include/arch/unix -I/data/prj/httpd-2.2.14/srclib/apr/include
exports.c | grep "ap_hack_" | sed -e 's/^.*[)]\(.*\);$/\1/' >> apr.exp
xlc -E -DHAVE_CONFIG_H -U__STR__ -D_THREAD_SAFE -D_LARGEFILE64_SOURCE
-I./include -I/data/prj/httpd-2.2.14/srclib/apr/include/arch/unix
-I./include/arch/unix -I/data/prj/httpd-2.2.14/s
rclib/apr/include/arch/unix -I/data/prj/httpd-2.2.14/srclib/apr/include
export_vars.c | sed -e 's/^\#[^!]*//' | sed -e '/^$/d' >> apr.exp
sed 's,^\(location=\).*$,\1installed,' < apr-1-config > apr-config.out
sed 's,^\(apr_build.*=\).*$,\1/usr/local/apache2/build,' < build/
apr_rules.mk > build/apr_rules.out
make[3]: Leaving directory `/data/prj/httpd-2.2.14/srclib/apr'
make[2]: Leaving directory `/data/prj/httpd-2.2.14/srclib/apr'
Making all in apr-util
make[2]: Entering directory `/data/prj/httpd-2.2.14/srclib/apr-util'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/data/prj/httpd-2.2.14/srclib/apr-util'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/prj/httpd-2.2.14/srclib'
make: *** [all-recursive] Error 1

In short, the build fails. No clue what is wrong.


rainer.jung at kippdata

Oct 6, 2009, 4:00 PM

Post #9 of 18 (1424 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On 06.10.2009 20:01, Michael Felt wrote:
> Hello all,
>
> I am trying to get a build made on AIX 6.1. And I suspect the problem I
> am having is the "root" cause of the problems people are reporting
> regarding can't make .so files when using AIX 6.1 (p.s. the quick fix is
> to compile on AIX 5.3, it runs fine on AIX 6.1)
>
> Standard process:
> unpack archive,
> ./configure --prefix=/usr/local/apache2 \
> --enable-module=so \
> --enable-module=unique_id \
> --enable-module=usertrack \
> --enable-module=vhost_alias \
> --enable-rewrite=shared \
> --enable-speling=shared \
> --enable-digest=shared \
> --enable-cgi=shared \
> --enable-headers=shared \
> --enable-info=shared \
> --enable-log_forensic=shared \
> --enable-proxy=shared \
> --enable-proxy-connect=shared \
> --enable-proxy-ftp=shared \
> --enable-proxy-http=shared \
> --enable-proxy-ajp=shared \
> --enable-proxy-balancer=shared \
> --with-z=/data/prj/zlib-1.2.3
> make
>
> On AIX5.3 I have as result, among others:
> # find modules -name '*.so'
> modules/generators/.libs/mod_info.so
> modules/generators/.libs/mod_cgi.so
> modules/loggers/.libs/mod_log_forensic.so
> modules/mappers/.libs/mod_speling.so
> modules/mappers/.libs/mod_rewrite.so
> modules/metadata/.libs/mod_headers.so
> modules/proxy/.libs/mod_proxy.so
> modules/proxy/.libs/mod_proxy_connect.so
> modules/proxy/.libs/mod_proxy_ftp.so
> modules/proxy/.libs/mod_proxy_http.so
> modules/proxy/.libs/mod_proxy_scgi.so
> modules/proxy/.libs/mod_proxy_ajp.so
> modules/proxy/.libs/mod_proxy_balancer.so
> =====
> And...
> # find modules -name '*.slo'
> modules/generators/mod_cgi.slo
> modules/generators/mod_info.slo
> modules/loggers/mod_log_forensic.slo
> modules/mappers/mod_rewrite.slo
> modules/mappers/mod_speling.slo
> modules/metadata/mod_headers.slo
> modules/proxy/mod_proxy.slo
> modules/proxy/ajp_header.slo
> modules/proxy/mod_proxy_connect.slo
> modules/proxy/mod_proxy_scgi.slo
> modules/proxy/mod_proxy_ftp.slo
> modules/proxy/ajp_utils.slo
> modules/proxy/mod_proxy_ajp.slo
> modules/proxy/proxy_util.slo
> modules/proxy/ajp_msg.slo
> modules/proxy/ajp_link.slo
> modules/proxy/mod_proxy_http.slo
> modules/proxy/mod_proxy_balancer.slo
> ++++++++++++++++++++++
> On AIX 6.1 I have:
> michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.so'
> =================================================
> michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.slo'
> modules/generators/mod_info.slo
> modules/generators/mod_cgi.slo
> modules/loggers/mod_log_forensic.slo
> modules/mappers/mod_speling.slo
> modules/mappers/mod_rewrite.slo
> modules/metadata/mod_headers.slo
> modules/proxy/mod_proxy.slo
> modules/proxy/proxy_util.slo
> modules/proxy/mod_proxy_connect.slo
> modules/proxy/mod_proxy_ftp.slo
> modules/proxy/mod_proxy_http.slo
> modules/proxy/mod_proxy_scgi.slo
> modules/proxy/mod_proxy_ajp.slo
> modules/proxy/ajp_header.slo
> modules/proxy/ajp_link.slo
> modules/proxy/ajp_msg.slo
> modules/proxy/ajp_utils.slo
> modules/proxy/mod_proxy_balancer.slo
> ++++++++++++++++++++++++++++++++++++
> Suspecting it was libtool I downloaded, built and installed libtool
> 2.2.6a and Python 2.6.3, ope did the following:
> make distclean
> ./buildconf
> ./configure *** as above
> make
> =========
> make ends with:
> Making all in srclib
> make[1]: Entering directory `/data/prj/http-2.2.14.bad/srclib'
> Making all in apr
> make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
> make[3]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
> make[3]: Nothing to be done for `local-all'.
> make[3]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
> make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
> Making all in apr-util
> make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
> make[2]: *** No rule to make target `all'. Stop.
> make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/data/prj/http-2.2.14.bad/srclib'
> make: *** [all-recursive] Error 1
> michael [at] x05:[/data/prj/http-2.2.14.bad]
>
> Attached: the config.log from each directory/system
>
> AIX 5.3 TL07, xlc v7 patched to July 2009
> AIX 6.1 : 6100-03-01-0921 (TL 03), same compiler.

I wouldn't use libtool 2.

So lets assume you have autoconf 2.64 and libtool 1.5.26. I assume both
tools are in your PATH and correctly installed.

Running buildconf for httpd 2.2.14 on my system (not AIX, it's Solaris)
gives:

% ./buildconf
found apr source: srclib/apr
found apr-util source: srclib/apr-util
rebuilding srclib/apr/configure
buildconf: checking installation...
buildconf: python version 2.5.1 (ok)
buildconf: autoconf version 2.64 (ok)
buildconf: libtool version 1.5.26 (ok)
Copying libtool helper files ...
buildconf: Using libtool.m4 at /some/path/share/aclocal/libtool.m4.
Creating include/arch/unix/apr_private.h.in ...
Creating configure ...
Generating 'make' outputs ...
rebuilding rpm spec file
rebuilding srclib/apr-util/configure

Looking for apr source in /test/httpd-2.2.14.buildconf/srclib/apr
Creating include/private/apu_config.h ...
Creating configure ...
Generating 'make' outputs ...
Invoking xml/expat/buildconf.sh ...
Copying libtool helper files ...
Incorporating /some/path/share/aclocal/libtool.m4 into aclocal.m4 ...
Creating config.h.in ...
autoheader: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for
`config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a
template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced,
see the
autoheader: WARNING: documentation.
Creating configure ...
rebuilding rpm spec file
copying build files
rebuilding srclib/pcre/configure
rebuilding include/ap_config_auto.h.in
rebuilding configure
rebuilding rpm spec file
fixing timestamps for mod_ssl sources


Running buildconf updates the following files in the httpd tree on my
system:

httpd-2.2.14/srclib/apr/build/libtool.m4
httpd-2.2.14/srclib/apr/configure
httpd-2.2.14/srclib/apr-util/xml/expat/aclocal.m4
httpd-2.2.14/srclib/apr-util/xml/expat/config.h.in
httpd-2.2.14/srclib/apr-util/xml/expat/configure

All other files stay the same (some have a newer timestamp, but the
contents do not change). What about that on your system?

The changes to the m4 and configure file pretty minor and are only
related to the Apple Darwin platform.

The change to config.h.in in srclib/apr-util is also small and
neglectable. So I think libtool and the autotools were pretty recent on
the system on which Graham prepared the 2.2.14 release. It seems no need
to actually run buildconf.

What is not very recent is two build files, namely config.sub and
config.guess. They originate from automake and you can copy them over
from automake 1.10.2. Whereas config.sub doesn't seem to have AIX
related changes, config.guess does:

534c548
< *:AIX:*:[45])
---
> *:AIX:*:[456])

All copies of the files in the four directories

build
srclib/apr/build
srclib/apr-util/build
srclib/apr-util/xml/expat/conftools

should be fixed. What is the output, when calling the original
config.guess, and what is the output of the fixed one?

Now try again and post again the contents of config.log and the full
output of your configure and make invocation.

Regards,

Rainer


mamfelt at gmail

Oct 6, 2009, 11:11 PM

Post #10 of 18 (1409 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
Rainer Jung wrote:
> On 06.10.2009 20:01, Michael Felt wrote:
>
>> Hello all,
>>
>> I am trying to get a build made on AIX 6.1. And I suspect the problem I
>> am having is the "root" cause of the problems people are reporting
>> regarding can't make .so files when using AIX 6.1 (p.s. the quick fix is
>> to compile on AIX 5.3, it runs fine on AIX 6.1)
>>
>> Standard process:
>> unpack archive,
>> ./configure --prefix=/usr/local/apache2 \
>> --enable-module=so \
>> --enable-module=unique_id \
>> --enable-module=usertrack \
>> --enable-module=vhost_alias \
>> --enable-rewrite=shared \
>> --enable-speling=shared \
>> --enable-digest=shared \
>> --enable-cgi=shared \
>> --enable-headers=shared \
>> --enable-info=shared \
>> --enable-log_forensic=shared \
>> --enable-proxy=shared \
>> --enable-proxy-connect=shared \
>> --enable-proxy-ftp=shared \
>> --enable-proxy-http=shared \
>> --enable-proxy-ajp=shared \
>> --enable-proxy-balancer=shared \
>> --with-z=/data/prj/zlib-1.2.3
>> make
>>
>> On AIX5.3 I have as result, among others:
>> # find modules -name '*.so'
>> modules/generators/.libs/mod_info.so
>> modules/generators/.libs/mod_cgi.so
>> modules/loggers/.libs/mod_log_forensic.so
>> modules/mappers/.libs/mod_speling.so
>> modules/mappers/.libs/mod_rewrite.so
>> modules/metadata/.libs/mod_headers.so
>> modules/proxy/.libs/mod_proxy.so
>> modules/proxy/.libs/mod_proxy_connect.so
>> modules/proxy/.libs/mod_proxy_ftp.so
>> modules/proxy/.libs/mod_proxy_http.so
>> modules/proxy/.libs/mod_proxy_scgi.so
>> modules/proxy/.libs/mod_proxy_ajp.so
>> modules/proxy/.libs/mod_proxy_balancer.so
>> =====
>> And...
>> # find modules -name '*.slo'
>> modules/generators/mod_cgi.slo
>> modules/generators/mod_info.slo
>> modules/loggers/mod_log_forensic.slo
>> modules/mappers/mod_rewrite.slo
>> modules/mappers/mod_speling.slo
>> modules/metadata/mod_headers.slo
>> modules/proxy/mod_proxy.slo
>> modules/proxy/ajp_header.slo
>> modules/proxy/mod_proxy_connect.slo
>> modules/proxy/mod_proxy_scgi.slo
>> modules/proxy/mod_proxy_ftp.slo
>> modules/proxy/ajp_utils.slo
>> modules/proxy/mod_proxy_ajp.slo
>> modules/proxy/proxy_util.slo
>> modules/proxy/ajp_msg.slo
>> modules/proxy/ajp_link.slo
>> modules/proxy/mod_proxy_http.slo
>> modules/proxy/mod_proxy_balancer.slo
>> ++++++++++++++++++++++
>> On AIX 6.1 I have:
>> michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.so'
>> =================================================
>> michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.slo'
>> modules/generators/mod_info.slo
>> modules/generators/mod_cgi.slo
>> modules/loggers/mod_log_forensic.slo
>> modules/mappers/mod_speling.slo
>> modules/mappers/mod_rewrite.slo
>> modules/metadata/mod_headers.slo
>> modules/proxy/mod_proxy.slo
>> modules/proxy/proxy_util.slo
>> modules/proxy/mod_proxy_connect.slo
>> modules/proxy/mod_proxy_ftp.slo
>> modules/proxy/mod_proxy_http.slo
>> modules/proxy/mod_proxy_scgi.slo
>> modules/proxy/mod_proxy_ajp.slo
>> modules/proxy/ajp_header.slo
>> modules/proxy/ajp_link.slo
>> modules/proxy/ajp_msg.slo
>> modules/proxy/ajp_utils.slo
>> modules/proxy/mod_proxy_balancer.slo
>> ++++++++++++++++++++++++++++++++++++
>> Suspecting it was libtool I downloaded, built and installed libtool
>> 2.2.6a and Python 2.6.3, ope did the following:
>> make distclean
>> ./buildconf
>> ./configure *** as above
>> make
>> =========
>> make ends with:
>> Making all in srclib
>> make[1]: Entering directory `/data/prj/http-2.2.14.bad/srclib'
>> Making all in apr
>> make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
>> make[3]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
>> make[3]: Nothing to be done for `local-all'.
>> make[3]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
>> make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
>> Making all in apr-util
>> make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
>> make[2]: *** No rule to make target `all'. Stop.
>> make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/data/prj/http-2.2.14.bad/srclib'
>> make: *** [all-recursive] Error 1
>> michael [at] x05:[/data/prj/http-2.2.14.bad]
>>
>> Attached: the config.log from each directory/system
>>
>> AIX 5.3 TL07, xlc v7 patched to July 2009
>> AIX 6.1 : 6100-03-01-0921 (TL 03), same compiler.
>>
>
> I wouldn't use libtool 2.
>
> So lets assume you have autoconf 2.64 and libtool 1.5.26. I assume both
> tools are in your PATH and correctly installed.
>
> Running buildconf for httpd 2.2.14 on my system (not AIX, it's Solaris)
> gives:
>
> % ./buildconf
> found apr source: srclib/apr
> found apr-util source: srclib/apr-util
> rebuilding srclib/apr/configure
> buildconf: checking installation...
> buildconf: python version 2.5.1 (ok)
> buildconf: autoconf version 2.64 (ok)
> buildconf: libtool version 1.5.26 (ok)
> Copying libtool helper files ...
> buildconf: Using libtool.m4 at /some/path/share/aclocal/libtool.m4.
> Creating include/arch/unix/apr_private.h.in ...
> Creating configure ...
> Generating 'make' outputs ...
> rebuilding rpm spec file
> rebuilding srclib/apr-util/configure
>
> Looking for apr source in /test/httpd-2.2.14.buildconf/srclib/apr
> Creating include/private/apu_config.h ...
> Creating configure ...
> Generating 'make' outputs ...
> Invoking xml/expat/buildconf.sh ...
> Copying libtool helper files ...
> Incorporating /some/path/share/aclocal/libtool.m4 into aclocal.m4 ...
> Creating config.h.in ...
> autoheader: WARNING: Using auxiliary files such as `acconfig.h',
> `config.h.bot'
> autoheader: WARNING: and `config.h.top', to define templates for
> `config.h.in'
> autoheader: WARNING: is deprecated and discouraged.
> autoheader:
> autoheader: WARNING: Using the third argument of `AC_DEFINE' and
> autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a
> template without
> autoheader: WARNING: `acconfig.h':
> autoheader:
> autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
> autoheader: [Define if a function `main' is needed.])
> autoheader:
> autoheader: WARNING: More sophisticated templates can also be produced,
> see the
> autoheader: WARNING: documentation.
> Creating configure ...
> rebuilding rpm spec file
> copying build files
> rebuilding srclib/pcre/configure
> rebuilding include/ap_config_auto.h.in
> rebuilding configure
> rebuilding rpm spec file
> fixing timestamps for mod_ssl sources
>
>
> Running buildconf updates the following files in the httpd tree on my
> system:
>
> httpd-2.2.14/srclib/apr/build/libtool.m4
> httpd-2.2.14/srclib/apr/configure
> httpd-2.2.14/srclib/apr-util/xml/expat/aclocal.m4
> httpd-2.2.14/srclib/apr-util/xml/expat/config.h.in
> httpd-2.2.14/srclib/apr-util/xml/expat/configure
>
> All other files stay the same (some have a newer timestamp, but the
> contents do not change). What about that on your system?
>
> The changes to the m4 and configure file pretty minor and are only
> related to the Apple Darwin platform.
>
> The change to config.h.in in srclib/apr-util is also small and
> neglectable. So I think libtool and the autotools were pretty recent on
> the system on which Graham prepared the 2.2.14 release. It seems no need
> to actually run buildconf.
>
> What is not very recent is two build files, namely config.sub and
> config.guess. They originate from automake and you can copy them over
> from automake 1.10.2. Whereas config.sub doesn't seem to have AIX
> related changes, config.guess does:
>
> 534c548
> < *:AIX:*:[45])
> ---
>
>> *:AIX:*:[456])
>>
>
> All copies of the files in the four directories
>
> build
> srclib/apr/build
> srclib/apr-util/build
> srclib/apr-util/xml/expat/conftools
>
> should be fixed. What is the output, when calling the original
> config.guess, and what is the output of the fixed one?
>
> Now try again and post again the contents of config.log and the full
> output of your configure and make invocation.
>
> Regards,
>
> Rainer
>
thanks. The buildconf output is similiar, and the config.guess file is
missing the 456 string. After work I'll get the rest done.


nikke at acc

Oct 7, 2009, 4:03 AM

Post #11 of 18 (1412 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On Tue, 6 Oct 2009, Michael Felt wrote:

>> I don't have an AIX system at hand at the moment, but last time I build
>> on AIX 6.1 I was astonished, that they used .a as a suffix for shared
>> libs. They have two types of shared libs, depending on when symbol
>> resolution is done.

<snip>

> btw: I believe AIX documentation says they use .so for shared objects, but
> also support .a as a shared object archive. And of course, the docs I found
> are on my other computer - that I cannot access at the moment. As I get
> further I'll be working on a FAQ for http://www.rootvg.net (I am webmaster
> there, and I am working on this build for that portal.) btw - my other goal
> is to build a binary distrubtion for AIX and publish it via rootvg.net.

AIX uses COFF, and thus behaves differently than most ELF-based unix
dialects out there.

Default for AIX is to use .a for all kinds of libs IIRC.

.so is used when you have compiled with -brtl to do runtime symbol
resolution ELF-style (ie, satisfying dependencies of linked-in
libraries can be done by linking your main binary with the missing
library). Hmm, "man ld" has some ramblings about dynamic vs shared
mode too, so see that manpage for the complete picture.

In any case, this hasn't changed between AIX5 and AIX6, so a fresh
AIX6-aware libtool should be all that's needed.

/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke [at] acc
---------------------------------------------------------------------------
Dangerous Job #?: Klingon Dentist
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


mamfelt at gmail

Oct 7, 2009, 7:27 AM

Post #12 of 18 (1403 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
You sound much better versed than I. However, next week when I am back I'll
go thru my "obscure" and see if I can find anything to help me understand.
Someone in IBM probably had a reason for being different (i.e. COFF versus
ELF). I just hope to understand it well enough to be able to be able to get
builds to build easily.

Would you care to comment on a preference for CC definition when using XL
compilers. I am leaning towards xlc.

On Wed, Oct 7, 2009 at 1:03 PM, Niklas Edmundsson <nikke [at] acc> wrote:

> On Tue, 6 Oct 2009, Michael Felt wrote:
>
> I don't have an AIX system at hand at the moment, but last time I build
>>> on AIX 6.1 I was astonished, that they used .a as a suffix for shared
>>> libs. They have two types of shared libs, depending on when symbol
>>> resolution is done.
>>>
>>
> <snip>
>
> btw: I believe AIX documentation says they use .so for shared objects, but
>> also support .a as a shared object archive. And of course, the docs I found
>> are on my other computer - that I cannot access at the moment. As I get
>> further I'll be working on a FAQ for http://www.rootvg.net (I am
>> webmaster there, and I am working on this build for that portal.) btw - my
>> other goal is to build a binary distrubtion for AIX and publish it via
>> rootvg.net.
>>
>
> AIX uses COFF, and thus behaves differently than most ELF-based unix
> dialects out there.
>
> Default for AIX is to use .a for all kinds of libs IIRC.
>
> .so is used when you have compiled with -brtl to do runtime symbol
> resolution ELF-style (ie, satisfying dependencies of linked-in libraries can
> be done by linking your main binary with the missing library). Hmm, "man ld"
> has some ramblings about dynamic vs shared mode too, so see that manpage for
> the complete picture.
>
> In any case, this hasn't changed between AIX5 and AIX6, so a fresh
> AIX6-aware libtool should be all that's needed.
>
> /Nikke
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke [at] acc
> ---------------------------------------------------------------------------
> Dangerous Job #?: Klingon Dentist
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>


trawick at gmail

Oct 7, 2009, 7:34 AM

Post #13 of 18 (1410 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On Wed, Oct 7, 2009 at 10:27 AM, Michael Felt <mamfelt [at] gmail> wrote:
> You sound much better versed than I. However, next week when I am back I'll
> go thru my "obscure" and see if I can find anything to help me understand.
> Someone in IBM probably had a reason for being different (i.e. COFF versus
> ELF). I just hope to understand it well enough to be able to be able to get
> builds to build easily.

(butting in; I was once versed enough)

COFF vs. ELF doesn't matter

statically resolving all symbols vs. dynamically resolving symbols
does matter for some code (e.g., mod_perl for Apache); thus, -brtl is
important; APR's apr_hints.m4 adds it to LDFLAGS for modern AIX

IIRC, when libtool sees -brtl it names shared libraries .so instead of .a

> Would you care to comment on a preference for CC definition when using XL
> compilers. I am leaning towards xlc.

CC=xlc_r gets you the appropriate reentrant flags


mamfelt at gmail

Oct 7, 2009, 7:49 AM

Post #14 of 18 (1402 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
I have differences in the following files, and all related to Darwin it
seems:
httpd-2.2.14a/srclib/apr/configure
httpd-2.2.14a/srclib/apr/build/libtool.m4
httpd-2.2.14a/srclib/apr-util/xml/expat/aclocal.m4
httpd-2.2.14a/srclib/apr-util/xml/expat/configure

What I also notice is that config.guess is not the same in the 4 locations.
Probably not a issue with current problem, but just thought I mention it for
completeness.

262158 44 -rwx------ 1 michael www 44208 Oct 7 06:02
./build/config.guess
264234 44 -rwx------ 1 michael www 44208 Aug 7 2006
./srclib/apr/build/config.guess
303593 44 -rwx------ 1 michael www 44208 Aug 7 2006
./srclib/apr-util/build/config.guess
303794 39 -rwx------ 1 michael www 39110 Nov 24 2004
./srclib/apr-util/xml/expat/conftools/config.guess

The config.log files follow shortly.

On Wed, Oct 7, 2009 at 1:00 AM, Rainer Jung <rainer.jung [at] kippdata> wrote:

> On 06.10.2009 20:01, Michael Felt wrote:
> > Hello all,
> >
> > I am trying to get a build made on AIX 6.1. And I suspect the problem I
> > am having is the "root" cause of the problems people are reporting
> > regarding can't make .so files when using AIX 6.1 (p.s. the quick fix is
> > to compile on AIX 5.3, it runs fine on AIX 6.1)
> >
> > Standard process:
> > unpack archive,
> > ./configure --prefix=/usr/local/apache2 \
> > --enable-module=so \
> > --enable-module=unique_id \
> > --enable-module=usertrack \
> > --enable-module=vhost_alias \
> > --enable-rewrite=shared \
> > --enable-speling=shared \
> > --enable-digest=shared \
> > --enable-cgi=shared \
> > --enable-headers=shared \
> > --enable-info=shared \
> > --enable-log_forensic=shared \
> > --enable-proxy=shared \
> > --enable-proxy-connect=shared \
> > --enable-proxy-ftp=shared \
> > --enable-proxy-http=shared \
> > --enable-proxy-ajp=shared \
> > --enable-proxy-balancer=shared \
> > --with-z=/data/prj/zlib-1.2.3
> > make
> >
> > On AIX5.3 I have as result, among others:
> > # find modules -name '*.so'
> > modules/generators/.libs/mod_info.so
> > modules/generators/.libs/mod_cgi.so
> > modules/loggers/.libs/mod_log_forensic.so
> > modules/mappers/.libs/mod_speling.so
> > modules/mappers/.libs/mod_rewrite.so
> > modules/metadata/.libs/mod_headers.so
> > modules/proxy/.libs/mod_proxy.so
> > modules/proxy/.libs/mod_proxy_connect.so
> > modules/proxy/.libs/mod_proxy_ftp.so
> > modules/proxy/.libs/mod_proxy_http.so
> > modules/proxy/.libs/mod_proxy_scgi.so
> > modules/proxy/.libs/mod_proxy_ajp.so
> > modules/proxy/.libs/mod_proxy_balancer.so
> > =====
> > And...
> > # find modules -name '*.slo'
> > modules/generators/mod_cgi.slo
> > modules/generators/mod_info.slo
> > modules/loggers/mod_log_forensic.slo
> > modules/mappers/mod_rewrite.slo
> > modules/mappers/mod_speling.slo
> > modules/metadata/mod_headers.slo
> > modules/proxy/mod_proxy.slo
> > modules/proxy/ajp_header.slo
> > modules/proxy/mod_proxy_connect.slo
> > modules/proxy/mod_proxy_scgi.slo
> > modules/proxy/mod_proxy_ftp.slo
> > modules/proxy/ajp_utils.slo
> > modules/proxy/mod_proxy_ajp.slo
> > modules/proxy/proxy_util.slo
> > modules/proxy/ajp_msg.slo
> > modules/proxy/ajp_link.slo
> > modules/proxy/mod_proxy_http.slo
> > modules/proxy/mod_proxy_balancer.slo
> > ++++++++++++++++++++++
> > On AIX 6.1 I have:
> > michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.so'
> > =================================================
> > michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.slo'
> > modules/generators/mod_info.slo
> > modules/generators/mod_cgi.slo
> > modules/loggers/mod_log_forensic.slo
> > modules/mappers/mod_speling.slo
> > modules/mappers/mod_rewrite.slo
> > modules/metadata/mod_headers.slo
> > modules/proxy/mod_proxy.slo
> > modules/proxy/proxy_util.slo
> > modules/proxy/mod_proxy_connect.slo
> > modules/proxy/mod_proxy_ftp.slo
> > modules/proxy/mod_proxy_http.slo
> > modules/proxy/mod_proxy_scgi.slo
> > modules/proxy/mod_proxy_ajp.slo
> > modules/proxy/ajp_header.slo
> > modules/proxy/ajp_link.slo
> > modules/proxy/ajp_msg.slo
> > modules/proxy/ajp_utils.slo
> > modules/proxy/mod_proxy_balancer.slo
> > ++++++++++++++++++++++++++++++++++++
> > Suspecting it was libtool I downloaded, built and installed libtool
> > 2.2.6a and Python 2.6.3, ope did the following:
> > make distclean
> > ./buildconf
> > ./configure *** as above
> > make
> > =========
> > make ends with:
> > Making all in srclib
> > make[1]: Entering directory `/data/prj/http-2.2.14.bad/srclib'
> > Making all in apr
> > make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > make[3]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > make[3]: Nothing to be done for `local-all'.
> > make[3]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > Making all in apr-util
> > make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
> > make[2]: *** No rule to make target `all'. Stop.
> > make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/data/prj/http-2.2.14.bad/srclib'
> > make: *** [all-recursive] Error 1
> > michael [at] x05:[/data/prj/http-2.2.14.bad]
> >
> > Attached: the config.log from each directory/system
> >
> > AIX 5.3 TL07, xlc v7 patched to July 2009
> > AIX 6.1 : 6100-03-01-0921 (TL 03), same compiler.
>
> I wouldn't use libtool 2.
>
> So lets assume you have autoconf 2.64 and libtool 1.5.26. I assume both
> tools are in your PATH and correctly installed.
>
> Running buildconf for httpd 2.2.14 on my system (not AIX, it's Solaris)
> gives:
>
> % ./buildconf
> found apr source: srclib/apr
> found apr-util source: srclib/apr-util
> rebuilding srclib/apr/configure
> buildconf: checking installation...
> buildconf: python version 2.5.1 (ok)
> buildconf: autoconf version 2.64 (ok)
> buildconf: libtool version 1.5.26 (ok)
> Copying libtool helper files ...
> buildconf: Using libtool.m4 at /some/path/share/aclocal/libtool.m4.
> Creating include/arch/unix/apr_private.h.in ...
> Creating configure ...
> Generating 'make' outputs ...
> rebuilding rpm spec file
> rebuilding srclib/apr-util/configure
>
> Looking for apr source in /test/httpd-2.2.14.buildconf/srclib/apr
> Creating include/private/apu_config.h ...
> Creating configure ...
> Generating 'make' outputs ...
> Invoking xml/expat/buildconf.sh ...
> Copying libtool helper files ...
> Incorporating /some/path/share/aclocal/libtool.m4 into aclocal.m4 ...
> Creating config.h.in ...
> autoheader: WARNING: Using auxiliary files such as `acconfig.h',
> `config.h.bot'
> autoheader: WARNING: and `config.h.top', to define templates for
> `config.h.in'
> autoheader: WARNING: is deprecated and discouraged.
> autoheader:
> autoheader: WARNING: Using the third argument of `AC_DEFINE' and
> autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a
> template without
> autoheader: WARNING: `acconfig.h':
> autoheader:
> autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
> autoheader: [Define if a function `main' is needed.])
> autoheader:
> autoheader: WARNING: More sophisticated templates can also be produced,
> see the
> autoheader: WARNING: documentation.
> Creating configure ...
> rebuilding rpm spec file
> copying build files
> rebuilding srclib/pcre/configure
> rebuilding include/ap_config_auto.h.in
> rebuilding configure
> rebuilding rpm spec file
> fixing timestamps for mod_ssl sources
>
>
> Running buildconf updates the following files in the httpd tree on my
> system:
>
> httpd-2.2.14/srclib/apr/build/libtool.m4
> httpd-2.2.14/srclib/apr/configure
> httpd-2.2.14/srclib/apr-util/xml/expat/aclocal.m4
> httpd-2.2.14/srclib/apr-util/xml/expat/config.h.in
> httpd-2.2.14/srclib/apr-util/xml/expat/configure
>
> All other files stay the same (some have a newer timestamp, but the
> contents do not change). What about that on your system?
>
> The changes to the m4 and configure file pretty minor and are only
> related to the Apple Darwin platform.
>
> The change to config.h.in in srclib/apr-util is also small and
> neglectable. So I think libtool and the autotools were pretty recent on
> the system on which Graham prepared the 2.2.14 release. It seems no need
> to actually run buildconf.
>
> What is not very recent is two build files, namely config.sub and
> config.guess. They originate from automake and you can copy them over
> from automake 1.10.2. Whereas config.sub doesn't seem to have AIX
> related changes, config.guess does:
>
> 534c548
> < *:AIX:*:[45])
> ---
> > *:AIX:*:[456])
>
> All copies of the files in the four directories
>
> build
> srclib/apr/build
> srclib/apr-util/build
> srclib/apr-util/xml/expat/conftools
>
> should be fixed. What is the output, when calling the original
> config.guess, and what is the output of the fixed one?
>
> Now try again and post again the contents of config.log and the full
> output of your configure and make invocation.
>
> Regards,
>
> Rainer
>


mamfelt at gmail

Oct 7, 2009, 7:52 AM

Post #15 of 18 (1407 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
I had, as an experiment tried xlC and a LDFLAG I had been using for php
builds (-blibpath:xxx) was not accepted as an argument. I'll try xlc and
xlc_r and see if I can spot differences.

On Wed, Oct 7, 2009 at 4:34 PM, Jeff Trawick <trawick [at] gmail> wrote:

> On Wed, Oct 7, 2009 at 10:27 AM, Michael Felt <mamfelt [at] gmail> wrote:
> > You sound much better versed than I. However, next week when I am back
> I'll
> > go thru my "obscure" and see if I can find anything to help me
> understand.
> > Someone in IBM probably had a reason for being different (i.e. COFF
> versus
> > ELF). I just hope to understand it well enough to be able to be able to
> get
> > builds to build easily.
>
> (butting in; I was once versed enough)
>
> COFF vs. ELF doesn't matter
>
> statically resolving all symbols vs. dynamically resolving symbols
> does matter for some code (e.g., mod_perl for Apache); thus, -brtl is
> important; APR's apr_hints.m4 adds it to LDFLAGS for modern AIX
>
> IIRC, when libtool sees -brtl it names shared libraries .so instead of .a
>
> > Would you care to comment on a preference for CC definition when using XL
> > compilers. I am leaning towards xlc.
>
> CC=xlc_r gets you the appropriate reentrant flags
>


mamfelt at gmail

Oct 7, 2009, 8:33 AM

Post #16 of 18 (1415 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
Rainer - give the man a cigar - or would you prefer a beer, or some other
beverage!

Replacing config.guess seems to fix it all.

==============
michael [at] x05:[/data/prj/httpd-2.2.14]./httpd -t
[Wed Oct 07 15:31:52 2009] [warn] module headers_module is already loaded,
skipping
Syntax OK
michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.so'
modules/generators/.libs/mod_info.so
modules/generators/.libs/mod_cgi.so
modules/loggers/.libs/mod_log_forensic.so
modules/mappers/.libs/mod_speling.so
modules/mappers/.libs/mod_rewrite.so
modules/metadata/.libs/mod_headers.so
modules/proxy/.libs/mod_proxy.so
modules/proxy/.libs/mod_proxy_connect.so
modules/proxy/.libs/mod_proxy_ftp.so
modules/proxy/.libs/mod_proxy_http.so
modules/proxy/.libs/mod_proxy_scgi.so
modules/proxy/.libs/mod_proxy_ajp.so
modules/proxy/.libs/mod_proxy_balancer.so
================================

So, this is probably the fix for
https://issues.apache.org/bugzilla/show_bug.cgi?id=47692

Thanks Rainer - great call!

On Wed, Oct 7, 2009 at 1:00 AM, Rainer Jung <rainer.jung [at] kippdata> wrote:

> On 06.10.2009 20:01, Michael Felt wrote:
> > Hello all,
> >
> > I am trying to get a build made on AIX 6.1. And I suspect the problem I
> > am having is the "root" cause of the problems people are reporting
> > regarding can't make .so files when using AIX 6.1 (p.s. the quick fix is
> > to compile on AIX 5.3, it runs fine on AIX 6.1)
> >
> > Standard process:
> > unpack archive,
> > ./configure --prefix=/usr/local/apache2 \
> > --enable-module=so \
> > --enable-module=unique_id \
> > --enable-module=usertrack \
> > --enable-module=vhost_alias \
> > --enable-rewrite=shared \
> > --enable-speling=shared \
> > --enable-digest=shared \
> > --enable-cgi=shared \
> > --enable-headers=shared \
> > --enable-info=shared \
> > --enable-log_forensic=shared \
> > --enable-proxy=shared \
> > --enable-proxy-connect=shared \
> > --enable-proxy-ftp=shared \
> > --enable-proxy-http=shared \
> > --enable-proxy-ajp=shared \
> > --enable-proxy-balancer=shared \
> > --with-z=/data/prj/zlib-1.2.3
> > make
> >
> > On AIX5.3 I have as result, among others:
> > # find modules -name '*.so'
> > modules/generators/.libs/mod_info.so
> > modules/generators/.libs/mod_cgi.so
> > modules/loggers/.libs/mod_log_forensic.so
> > modules/mappers/.libs/mod_speling.so
> > modules/mappers/.libs/mod_rewrite.so
> > modules/metadata/.libs/mod_headers.so
> > modules/proxy/.libs/mod_proxy.so
> > modules/proxy/.libs/mod_proxy_connect.so
> > modules/proxy/.libs/mod_proxy_ftp.so
> > modules/proxy/.libs/mod_proxy_http.so
> > modules/proxy/.libs/mod_proxy_scgi.so
> > modules/proxy/.libs/mod_proxy_ajp.so
> > modules/proxy/.libs/mod_proxy_balancer.so
> > =====
> > And...
> > # find modules -name '*.slo'
> > modules/generators/mod_cgi.slo
> > modules/generators/mod_info.slo
> > modules/loggers/mod_log_forensic.slo
> > modules/mappers/mod_rewrite.slo
> > modules/mappers/mod_speling.slo
> > modules/metadata/mod_headers.slo
> > modules/proxy/mod_proxy.slo
> > modules/proxy/ajp_header.slo
> > modules/proxy/mod_proxy_connect.slo
> > modules/proxy/mod_proxy_scgi.slo
> > modules/proxy/mod_proxy_ftp.slo
> > modules/proxy/ajp_utils.slo
> > modules/proxy/mod_proxy_ajp.slo
> > modules/proxy/proxy_util.slo
> > modules/proxy/ajp_msg.slo
> > modules/proxy/ajp_link.slo
> > modules/proxy/mod_proxy_http.slo
> > modules/proxy/mod_proxy_balancer.slo
> > ++++++++++++++++++++++
> > On AIX 6.1 I have:
> > michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.so'
> > =================================================
> > michael [at] x05:[/data/prj/httpd-2.2.14]find modules -name '*.slo'
> > modules/generators/mod_info.slo
> > modules/generators/mod_cgi.slo
> > modules/loggers/mod_log_forensic.slo
> > modules/mappers/mod_speling.slo
> > modules/mappers/mod_rewrite.slo
> > modules/metadata/mod_headers.slo
> > modules/proxy/mod_proxy.slo
> > modules/proxy/proxy_util.slo
> > modules/proxy/mod_proxy_connect.slo
> > modules/proxy/mod_proxy_ftp.slo
> > modules/proxy/mod_proxy_http.slo
> > modules/proxy/mod_proxy_scgi.slo
> > modules/proxy/mod_proxy_ajp.slo
> > modules/proxy/ajp_header.slo
> > modules/proxy/ajp_link.slo
> > modules/proxy/ajp_msg.slo
> > modules/proxy/ajp_utils.slo
> > modules/proxy/mod_proxy_balancer.slo
> > ++++++++++++++++++++++++++++++++++++
> > Suspecting it was libtool I downloaded, built and installed libtool
> > 2.2.6a and Python 2.6.3, ope did the following:
> > make distclean
> > ./buildconf
> > ./configure *** as above
> > make
> > =========
> > make ends with:
> > Making all in srclib
> > make[1]: Entering directory `/data/prj/http-2.2.14.bad/srclib'
> > Making all in apr
> > make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > make[3]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > make[3]: Nothing to be done for `local-all'.
> > make[3]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr'
> > Making all in apr-util
> > make[2]: Entering directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
> > make[2]: *** No rule to make target `all'. Stop.
> > make[2]: Leaving directory `/data/prj/http-2.2.14.bad/srclib/apr-util'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/data/prj/http-2.2.14.bad/srclib'
> > make: *** [all-recursive] Error 1
> > michael [at] x05:[/data/prj/http-2.2.14.bad]
> >
> > Attached: the config.log from each directory/system
> >
> > AIX 5.3 TL07, xlc v7 patched to July 2009
> > AIX 6.1 : 6100-03-01-0921 (TL 03), same compiler.
>
> I wouldn't use libtool 2.
>
> So lets assume you have autoconf 2.64 and libtool 1.5.26. I assume both
> tools are in your PATH and correctly installed.
>
> Running buildconf for httpd 2.2.14 on my system (not AIX, it's Solaris)
> gives:
>
> % ./buildconf
> found apr source: srclib/apr
> found apr-util source: srclib/apr-util
> rebuilding srclib/apr/configure
> buildconf: checking installation...
> buildconf: python version 2.5.1 (ok)
> buildconf: autoconf version 2.64 (ok)
> buildconf: libtool version 1.5.26 (ok)
> Copying libtool helper files ...
> buildconf: Using libtool.m4 at /some/path/share/aclocal/libtool.m4.
> Creating include/arch/unix/apr_private.h.in ...
> Creating configure ...
> Generating 'make' outputs ...
> rebuilding rpm spec file
> rebuilding srclib/apr-util/configure
>
> Looking for apr source in /test/httpd-2.2.14.buildconf/srclib/apr
> Creating include/private/apu_config.h ...
> Creating configure ...
> Generating 'make' outputs ...
> Invoking xml/expat/buildconf.sh ...
> Copying libtool helper files ...
> Incorporating /some/path/share/aclocal/libtool.m4 into aclocal.m4 ...
> Creating config.h.in ...
> autoheader: WARNING: Using auxiliary files such as `acconfig.h',
> `config.h.bot'
> autoheader: WARNING: and `config.h.top', to define templates for
> `config.h.in'
> autoheader: WARNING: is deprecated and discouraged.
> autoheader:
> autoheader: WARNING: Using the third argument of `AC_DEFINE' and
> autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a
> template without
> autoheader: WARNING: `acconfig.h':
> autoheader:
> autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
> autoheader: [Define if a function `main' is needed.])
> autoheader:
> autoheader: WARNING: More sophisticated templates can also be produced,
> see the
> autoheader: WARNING: documentation.
> Creating configure ...
> rebuilding rpm spec file
> copying build files
> rebuilding srclib/pcre/configure
> rebuilding include/ap_config_auto.h.in
> rebuilding configure
> rebuilding rpm spec file
> fixing timestamps for mod_ssl sources
>
>
> Running buildconf updates the following files in the httpd tree on my
> system:
>
> httpd-2.2.14/srclib/apr/build/libtool.m4
> httpd-2.2.14/srclib/apr/configure
> httpd-2.2.14/srclib/apr-util/xml/expat/aclocal.m4
> httpd-2.2.14/srclib/apr-util/xml/expat/config.h.in
> httpd-2.2.14/srclib/apr-util/xml/expat/configure
>
> All other files stay the same (some have a newer timestamp, but the
> contents do not change). What about that on your system?
>
> The changes to the m4 and configure file pretty minor and are only
> related to the Apple Darwin platform.
>
> The change to config.h.in in srclib/apr-util is also small and
> neglectable. So I think libtool and the autotools were pretty recent on
> the system on which Graham prepared the 2.2.14 release. It seems no need
> to actually run buildconf.
>
> What is not very recent is two build files, namely config.sub and
> config.guess. They originate from automake and you can copy them over
> from automake 1.10.2. Whereas config.sub doesn't seem to have AIX
> related changes, config.guess does:
>
> 534c548
> < *:AIX:*:[45])
> ---
> > *:AIX:*:[456])
>
> All copies of the files in the four directories
>
> build
> srclib/apr/build
> srclib/apr-util/build
> srclib/apr-util/xml/expat/conftools
>
> should be fixed. What is the output, when calling the original
> config.guess, and what is the output of the fixed one?
>
> Now try again and post again the contents of config.log and the full
> output of your configure and make invocation.
>
> Regards,
>
> Rainer
>


nikke at acc

Oct 12, 2009, 5:00 AM

Post #17 of 18 (1349 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
On Wed, 7 Oct 2009, Michael Felt wrote:

> Would you care to comment on a preference for CC definition when using XL
> compilers. I am leaning towards xlc.

I've had a long standing problem with CC=xlc optimizing away some
crucial part of the accept-loop in httpd, so it wouldn't process
connections. The workaround has been to use CC=cc. Haven't tried
CC=xlc or xlc_r with the recent patchsets of xlc/vac 9/10 though, so
this might just be me emitting stale noise. You'll notice if you hit
this issue ;)

And yes, everything Jeff stated is of course correct.

/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke [at] acc
---------------------------------------------------------------------------
RETIREMENT: When you stop living at work and start working at life.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


mamfelt at gmail

Oct 12, 2009, 9:21 AM

Post #18 of 18 (1327 views)
Permalink
Re: problem with build on AIX 6.1 [In reply to]
You mean it would not accept any connections, or just some?

On Mon, Oct 12, 2009 at 2:00 PM, Niklas Edmundsson <nikke [at] acc> wrote:

> On Wed, 7 Oct 2009, Michael Felt wrote:
>
> Would you care to comment on a preference for CC definition when using XL
>> compilers. I am leaning towards xlc.
>>
>
> I've had a long standing problem with CC=xlc optimizing away some crucial
> part of the accept-loop in httpd, so it wouldn't process connections. The
> workaround has been to use CC=cc. Haven't tried CC=xlc or xlc_r with the
> recent patchsets of xlc/vac 9/10 though, so this might just be me emitting
> stale noise. You'll notice if you hit this issue ;)
>
> And yes, everything Jeff stated is of course correct.
>
> /Nikke
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke [at] acc
> ---------------------------------------------------------------------------
> RETIREMENT: When you stop living at work and start working at life.
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>

Apache dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.