From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] No .h dependency in Makeifle
Date: Wed, 4 Mar 2020 08:22:56 -0500 [thread overview]
Message-ID: <20200304132256.GR11469@brightrain.aerifal.cx> (raw)
In-Reply-To: <4526bf84ddc8e3cf1bf9ae8cb78bc345e543@guerrillamail.com>
On Wed, Mar 04, 2020 at 12:06:50PM +0000, khvluu+8f5rqrzfwl55o@guerrillamail.com wrote:
> Makefile is efficient and short.
>
> But maybe a comment is necessary, that no .h dependency was (auto) generated.
>
> Thus, modifying stdio.h for example will not trigger any build.
This was largely set aside because, for the most part, dependency on
the public (as opposed to internal) headers is not desirable. They are
defining a stable ABI boundary, so changes to them should just be
additions that don't affect existing code, and the code generated
"should not" change as a result of changes to the headers.
In reality, of course, there are some minor ways changes do affect
codegen in ways we want to test (and benefit from) -- for example,
changes to better macro versions of some functions, or bug fixes for
wrong macro definitions (happened for ioctls, fcntl numbers, etc. on
some archs). So I've somewhat wanted to add dependency generation. I'm
just not very familiar with the tooling to do it.
Rich
prev parent reply other threads:[~2020-03-04 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 12:06 khvluu+8f5rqrzfwl55o
2020-03-04 13:22 ` Rich Felker [this message]
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=20200304132256.GR11469@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).