Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (hermes.apache.org: 217.155.92.109 is neither permitted
 nor denied by domain of ben@algroup.co.uk)
Message-ID: <41D6CB90.6060309@algroup.co.uk>
Date: Sat, 01 Jan 2005 16:10:56 +0000
From: Ben Laurie <ben@algroup.co.uk>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Stas Bekman <stas@stason.org>
Cc: APR Development <dev@apr.apache.org>
Subject: Re: how do I know if libapr was built with --enable-pool-debug or
 other opts?
References: <41D5E65A.5030102@stason.org>
In-Reply-To: <41D5E65A.5030102@stason.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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