Re: kconfig-frontends-3.6.0-0 released

From: Yann E. MORIN
Date: Sun Jan 13 2013 - 17:05:59 EST


Jan, All,

On Sunday 13 January 2013 Jan Engelhardt wrote:
> On Sunday 2013-01-13 19:59, Yann E. MORIN wrote:
> >> Not again. autoreconf has existed for so long, why are people still
> >> hand-coding the boilerplate?
[--SNIP--]
> >How does one autoreconf a 'foreign' package?
>
> Surely, just that:
> AM_INIT_AUTOMAKE([foreign])

Aha! :-)

Just one small nit left: autoreconf does not grok AC_CONFIG_MACRO_DIR and
does not create it, so aclocal complains. Easily worked around, though.

> >> >AC_HEADER_STDC
> >> >AC_HEADER_STDBOOL
> >> >AC_CHECK_HEADERS([ fcntl.h limits.h locale.h ])
> >> >AC_CHECK_HEADERS([ stdlib.h string.h sys/time.h unistd.h ])
[--SNIP--]
> >> All of this seems pointless because you never use the results
> >> (HAVE_FCNTL_H, HAVE_LIMITS_H, etc.)
[--SNIP--]
> >As I see it, the only action we could take is to bail out if any is missing.
> >Is this what you meant?
>
> You could do that, though I would simply direct users to read the compiler
> error message. That enhances (hopefully) both their knowledge on compiling,
> and reduces the walltime configure runs.

OK, sounds reasonable.

> If I understood right, kconfig-frontends is supposed to run on non-Linux too,
> and I have yet to see a modern platform that's missing any of the stdc
> functions like malloc and strchr.

Yes, this is reasonable too. I'll do that.

Thank you very much! :-)

Regards,
Yann E. MORIN.

--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/