httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gustavo A. Baratto" <gbara...@superb.net>
Subject Re: [users@httpd] different configure options under the same source tree.
Date Thu, 29 Jul 2004 19:48:52 GMT
Thanks for the tip, but unfortunately this wont work for me as I can't do a "make clean"...
Once the source is compiled, I can't delete it, because I might need to run "make install"
in different server. Before you ask why:
We have many different sets of servers. Each set needs different configure options, as they
do different things. We may add a new server to the set at anytime (or maybe rebuild an existing
server if the HD fails), so, I don't want to compile everything again and waste time and CPU
on my build server if that was already done. I just want to nsf mount the source tree directory
and do a "make install" or a "make install SET1" where SET1 is the binary compiled with the
configure options for the set 1.

I know I could create packages after I compile the source for each set, but it is veeeeery
time consuming, and I found that "make install" serves me much better.

Thanks Brian ;)

    
  ----- Original Message ----- 
  From: Brian Quinn 
  To: users@httpd.apache.org 
  Sent: Thursday, July 29, 2004 12:23 PM
  Subject: Re: [users@httpd] different configure options under the same source tree.


  I have ONE source of apache, then in another directory i have all my scripts, like www.sh,
hcrs.sh, map.sh, etc.  Each one of those is a different physical server, so each one needs
it's own config options, and i just stick it all in the script.  just do a "make clean" before
the --config




  At 12:15 PM 7/29/2004, you wrote:

    Hi all,
     
    I don't know if this is an apache or autoconf/automake question, but since my goal is
to compile apache, here is goes...
     
    I want to build many different apache binaries (with different configure options), under
the same source tree... is it possible?
     
    What I am doing now is to download the source, unpack the source in different directories,
and for each directory I compile apache with different configure options. But I think this
is a waste of space.
     
    Any ideas?
     
    Thanks!
Mime
View raw message