fatal error: config.h: No such file or directory
Bruce Korb
bkorb@gnu.org
Tue Dec 23 21:54:00 GMT 2014
On 12/23/14 09:07, Aldy Hernandez wrote:
> Andrew Haley <aph@redhat.com> 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
>> supported.
>
> 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?
More information about the Gcc
mailing list