A bootstrapped megatest directory enables more kinds of tests.
Let's look at these builds:
0) configure CC='gcc -Wall -Werror -fno-builtin' # as seen earlier
1) configure
2) configure -C
3) pre-seed config.cache with the file resulting from (2), then
configure -C
4) create a config.cache from
Ralf Wildenhues wrote:
> Maybe there should be a way to automatize the "disable the config-h
> module as long as one of the modules this package uses still guards
> config.h"; or simpler: exempt the config-h module from the ALL test
> for now.
Done.
2006-09-22 Bruno Haible <[EMAIL PROTECTED]>
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>> Have we decided that gnulib files don't need HAVE_CONFIG_H checks? If
>> so, maybe something should be added to the gnulib manual...
>
> IIRC there has been no decision to do so. Just a new module config-h
> which you can use. The only point of thi
Hello Simon,
* Simon Josefsson wrote on Fri, Sep 22, 2006 at 02:47:20PM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > - Failures that stem from the incomplete HAVE_CONFIG_H transition,
> > including but certainly not limited to these files:
> > base64.c, argp-help.c, xvasprintf.c,
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> - Failures that stem from the incomplete HAVE_CONFIG_H transition,
> including but certainly not limited to these files:
> base64.c, argp-help.c, xvasprintf.c, check-version.c, hmac-md5.c,
> memxor.c, hmac-sha1.c
What do you mean here? Do you m
