From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kconfig-frontends-3.6.0-0 released
Date: Sun, 13 Jan 2013 22:58:44 +0100 [thread overview]
Message-ID: <201301132258.45084.yann.morin.1998@free.fr> (raw)
In-Reply-To: <alpine.LNX.2.01.1301132204090.9693@nerf07.vanv.qr>
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-01-13 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 15:55 Yann E. MORIN
2013-01-12 17:25 ` Jan Engelhardt
2013-01-13 18:59 ` Yann E. MORIN
2013-01-13 21:09 ` Jan Engelhardt
2013-01-13 21:58 ` Yann E. MORIN [this message]
2013-01-13 22:37 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201301132258.45084.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=jengelh@inai.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®