new build system configure step - a small suggestion
maurizio.cimadamore at oracle.com
Tue May 28 11:50:59 UTC 2013
On 28/05/13 12:47, Erik Joelsson wrote:
> This has been brought up before and is a good idea. At least the
> headers could be checked for in one go. The compiler is needed to
> check for headers, so that would need to be a separate run.
Makes sense. Thanks!
> Creating bug JDK-8015483 to track the suggestion.
> On 2013-05-28 13:36, Maurizio Cimadamore wrote:
>> 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
>> *) 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