This is the mail archive of the
mailing list for the GCC project.
Re: fatal error: config.h: No such file or directory
- From: Bruce Korb <bkorb at gnu dot org>
- To: aldyh at redhat dot com, Andrew Haley <aph at redhat dot com>
- Cc: GCC <gcc at gcc dot gnu dot org>
- Date: Tue, 23 Dec 2014 13:54:36 -0800
- Subject: Re: fatal error: config.h: No such file or directory
- Authentication-results: sourceware.org; auth=none
- References: <5496329E dot 8070106 at gnu dot org> <5496B069 dot 7070304 at redhat dot com> <87r3vql2gi dot fsf at reynosa dot quesejoda dot com>
- Reply-to: bkorb at gnu dot org
On 12/23/14 09:07, Aldy Hernandez wrote:
Andrew Haley <firstname.lastname@example.org> writes:
On 12/21/2014 02:38 AM, Bruce Korb wrote:
Shouldn't the configure step have made config.h?
It's probably because you are building in srcdir. That is not
Hmm, newbies run into this often enough that I wonder whether we should
just error out from the configuration stage.
Yeah, we newbies who've only been fiddling it for 15 years.
I think it a good idea. My script that does the configure & build
is much newer though. It's only about 5 years old.
Good error messages are really, really, really important --
especially if you are changing requirements. Someone from
the distant dusty past may wind up with a stubbed toe.
Oh, another point:
Some projects cannot be built with separate source/build directories
and some projects (like yours) cannot be build without separation.
So the real question is, Does it really save enough development effort
that it is not worth doing the "you can build it either way" way?