[asterisk-bugs] [Asterisk 0012197]: Make Menuselect bombs on a clean checkout or make dist-clean if configure not run.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12197 
====================================================================== 
Reported By:                juggie
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12197
Category:                   Core/BuildSystem
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 108031 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-12-2008 11:55 CDT
Last Modified:              03-12-2008 13:34 CDT
====================================================================== 
Summary:                    Make Menuselect bombs on a clean checkout or make
dist-clean if configure not run.
Description: 
As stated in subject, run make menuselect before a configure on a clean
checkout or a checkout that has just been cleaned with make dist-clean and
it will bomb out in a dramatic way.  (see attached file)

The end result however is not simply that you run ./configure, and then
run make menuselect because if you do that, you will notice that make menu
select now has every single option enabled and detected as available within
your system.  And of course running make will fail as you likely do not
have every single dependency.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 03-12-08 13:34  
---------------------------------------------------------------------- 
Okay, and if you look at the second last line, it tells you EXACTLY what
you should do.  I'm not sure what else you expect that we should do. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-12-08 13:34  Corydon76      Note Added: 0083839                          
======================================================================