You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by Stas Bekman <st...@stason.org> on 2005/01/01 00:52:58 UTC
how do I know if libapr was built with --enable-pool-debug or other
opts?
How could I know whether libapr was built with a certain option on or off?
e.g. after building libapr with CPPFLAGS="-DAPR_BUCKET_DEBUG" and
--enable-pool-debug, I run:
% apr-config --cppflags
-DLINUX=2 -D_REENTRANT -DAPR_POOL_DEBUG=1 -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
so I can see -DAPR_BUCKET_DEBUG, but what about --enable-pool-debug? I
can't find an option to show me that.
Similar to httpd -V I want to be able to see what options a library was
compiled with, so when asking users to submit a bug report, we can
reproduce the same build. Instead asking users to manually paste their
build options, it'd be great to have the -config tool report those
automatically.
Thanks.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: how do I know if libapr was built with --enable-pool-debug or
other opts?
Posted by Stas Bekman <st...@stason.org>.
Ben Laurie wrote:
> Stas Bekman wrote:
>
>> How could I know whether libapr was built with a certain option on or
>> off?
>>
>> e.g. after building libapr with CPPFLAGS="-DAPR_BUCKET_DEBUG" and
>> --enable-pool-debug, I run:
>>
>> % apr-config --cppflags
>> -DLINUX=2 -D_REENTRANT -DAPR_POOL_DEBUG=1 -D_XOPEN_SOURCE=500
>> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
>>
>> so I can see -DAPR_BUCKET_DEBUG, but what about --enable-pool-debug? I
>> can't find an option to show me that.
>
>
> I'd note that you _can't_ see -DAPR_BUCKET_DEBUG - but you can see
> -DAPR_POOL_DEBUG :-)
doh, thanks Ben, a parsing problem. So why the second one is not there?
>> Similar to httpd -V I want to be able to see what options a library
>> was compiled with, so when asking users to submit a bug report, we can
>> reproduce the same build. Instead asking users to manually paste their
>> build options, it'd be great to have the -config tool report those
>> automatically.
>>
>> Thanks.
>>
>
>
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: how do I know if libapr was built with --enable-pool-debug or
other opts?
Posted by Ben Laurie <be...@algroup.co.uk>.
Stas Bekman wrote:
> How could I know whether libapr was built with a certain option on or off?
>
> e.g. after building libapr with CPPFLAGS="-DAPR_BUCKET_DEBUG" and
> --enable-pool-debug, I run:
>
> % apr-config --cppflags
> -DLINUX=2 -D_REENTRANT -DAPR_POOL_DEBUG=1 -D_XOPEN_SOURCE=500
> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
>
> so I can see -DAPR_BUCKET_DEBUG, but what about --enable-pool-debug? I
> can't find an option to show me that.
I'd note that you _can't_ see -DAPR_BUCKET_DEBUG - but you can see
-DAPR_POOL_DEBUG :-)
> Similar to httpd -V I want to be able to see what options a library was
> compiled with, so when asking users to submit a bug report, we can
> reproduce the same build. Instead asking users to manually paste their
> build options, it'd be great to have the -config tool report those
> automatically.
>
> Thanks.
>
--
http://www.apache-ssl.org/ben.html http://www.thebunker.net/
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff