new build system configure step - a small suggestion

Maurizio Cimadamore maurizio.cimadamore at
Tue May 28 11:36:40 UTC 2013

as I recently went through the process of reinstalling my OS, I had to 
get the JDK build up and running again (with Ubuntu). As expected, 
configure kept failing because of missing libraries; I counted 4 failures:

*) build-essential missing (gcc, etc.)
*) X headers missing
*) cups headers missing
*) alsa headers missing

Since the output of the configure tool is already very good (i.e. it 
gives you the apt command needed to fetch missing stuff), wouldn't it be 
possible to somehow go through an entire scan of the system, and then 
report back a unique list of missing stuff instead of forcing users to 
do this trial and error approach?

Of course this is a very minor adjustment to an overall very 
user-friendly process; I only wanted to share my experience.


More information about the build-dev mailing list