DO NOT REPLY [Bug 31453] New: - top level config.status does not capture the "configure" state properly.

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31453>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31453

top level config.status does not capture the "configure" state properly.

           Summary: top level config.status does not capture the "configure"
                    state properly.
           Product: Apache httpd-2.0
           Version: 2.0.51
          Platform: Other
        OS/Version: FreeBSD
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Build
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: alfred@freebsd.org


untar apache2
./configure
save the "config.status" file someplace.
remove apache2 source
untar again
run the config.status output from the previous ./configure run.
does not compile.

I think this is because there are sub-configure scripts that are being run that
the top level configure does not catch.

Shouldn't the top level configure catch all the data needed in config.status?

As a workaround I'm storing the arguments to the top level configure, but I just
assumed this would work.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org