From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] build/advanced: add option to check for use of cdefs.h
Date: Sun, 4 Dec 2016 14:05:56 +0100 [thread overview]
Message-ID: <20161204130556.GA3433@free.fr> (raw)
In-Reply-To: <20161204135202.109c6480@free-electrons.com>
Thomas, All,
On 2016-12-04 13:52 +0100, Thomas Petazzoni spake thusly:
> On Sun, 4 Dec 2016 11:59:37 +0100, Yann E. MORIN wrote:
> > We want to catch programs that directly include sys/cdefs.h so that
> > we can fix them not to. So, we want to instrument sys/cdefs.h to emit
> > a warning when it is included.
>
> Thanks for working on this. However, I am still not convinced that we
> want to merge such an additional complexity (one new Config.in choice
> with three sub-options, two additional Config.in options), a cdefs.h
> wrapper for glibc/uclibc, etc.
>
> Do we really care about upstream packages using sys/cdefs.h? Is it
> really the most important battle to fight against upstream projects
> using sys/cdefs.h?
I don't really care. I did some cleanups and changes according to
comments to the previous, initial iteration, and just sent it to the
list for a final review before I delete it locally.
So, at least, it is in the list archives for posterity, in case we
want/need to revisit this later on.
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:[~2016-12-04 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 10:59 [Buildroot] [PATCH] build/advanced: add option to check for use of cdefs.h Yann E. MORIN
2016-12-04 12:52 ` Thomas Petazzoni
2016-12-04 13:05 ` Yann E. MORIN [this message]
2016-12-04 20:33 ` Arnout Vandecappelle
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=20161204130556.GA3433@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.