[users@httpd] how httpd was compiled

[Anurag Gujral <an...@yahoo.com>]

Hi  All,
       We are using httpd-2.0.59 to run a site.The persoon who compiled the httpd is no longer with the company.
Is it possible to know from compiled httpd  with what options it was compiled(sounds like a crazy question).
I was trying to debug a core dump, I compiled httpd-2.0.59 when I run gdb I get message that
core file and exe are not related.

Thats is why I wanted to know if there is way to find out how a particuar httpd was compiled.
Thanks 
Anurag


      

Re: [users@httpd] how httpd was compiled

[Anurag Gujral <an...@yahoo.com>]

________________________________

From: Sander Temme <sc...@apache.org>
To: users@httpd.apache.org
Sent: Sunday, November 30, 2008 6:24:11 PM
Subject: Re: [users@httpd] how httpd was compiled


Unfortunately it is not present.

If that isn't present, don't despair: a combination of httpd -l and the contents of the modules subdirectory will tell you what modules were enabled, and httpd -V will tell you some of the path prefix choices that were made.  Also, running ldd on the httpd binary and on the individual modules will tell you where Apache expects to find its libraries: that will allow you to recreate the --with-package=... parameters to configure

I will try this thanks.

Thanks & Regards,
Anurag

Most of the configure options have to do with turning modules on and off, so if you collect that information you're most of the way there.

Good luck,

S.

--Sander Temme
sctemme@apache.org
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF





On Nov 30, 2008, at 5:05 PM, Anurag Gujral wrote:

> Thats is why I wanted to know if there is way to find out how a particuar httpd was compiled.


If your installation is complete, you should find a file called config.nice in the build subdirectory.  It has the exact invocation of the configure script used to set up the build process.

That should allow you to recreate your compilation.


      

Re: [users@httpd] how httpd was compiled

[Sander Temme <sc...@apache.org>]

On Nov 30, 2008, at 5:05 PM, Anurag Gujral wrote:

> Thats is why I wanted to know if there is way to find out how a  
> particuar httpd was compiled.


If your installation is complete, you should find a file called  
config.nice in the build subdirectory.  It has the exact invocation of  
the configure script used to set up the build process.

That should allow you to recreate your compilation.

If that isn't present, don't despair: a combination of httpd -l and  
the contents of the modules subdirectory will tell you what modules  
were enabled, and httpd -V will tell you some of the path prefix  
choices that were made.  Also, running ldd on the httpd binary and on  
the individual modules will tell you where Apache expects to find its  
libraries: that will allow you to recreate the --with-package=...  
parameters to configure

Most of the configure options have to do with turning modules on and  
off, so if you collect that information you're most of the way there.

Good luck,

S.

-- 
Sander Temme
sctemme@apache.org
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

RE: [users@httpd] how httpd was compiled

[Rekha Rani <rr...@bdna.com>]

Try "apachectl -V"  command and there you might get what you looking
for.

 

 

________________________________

From: Anurag Gujral [mailto:anurag_gujral@yahoo.com] 
Sent: Sunday, November 30, 2008 5:05 PM
To: users@httpd.apache.org
Cc: Anurag Gujral
Subject: [users@httpd] how httpd was compiled

 

Hi  All,

       We are using httpd-2.0.59 to run a site.The persoon who compiled
the httpd is no longer with the company.

Is it possible to know from compiled httpd  with what options it was
compiled(sounds like a crazy question).

I was trying to debug a core dump, I compiled httpd-2.0.59 when I run
gdb I get message that

core file and exe are not related.

 

Thats is why I wanted to know if there is way to find out how a
particuar httpd was compiled.

Thanks 

Anurag 

--------------------------------------------------------

This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication may contain material protected by the attorney-client privilege. If you are not the intended recipient, be advised that any use, dissemination, forwarding, printing or copying is strictly prohibited. If you have received this email in error, please contact the sender and delete all copies.