mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Lukas Bulwahn <>
To: Rich Felker <>,
Cc: Lukas Bulwahn <>
Subject: [musl] [PATCH 0/2] Minor stylistic clean-up in musl Makefile
Date: Mon, 13 Mar 2023 06:17:03 +0100	[thread overview]
Message-ID: <> (raw)

Dear Rich,

while doing some investigation on which compiler flags are used in the musl
build, I noticed some inconvenience in my aggregation script and hence came
across two minor clean-up changes for the musl build that you may want to pick.

Both changes are purely stylistic for invoking the compiler and have no
effective change on the build output.


Lukas Bulwahn (2):
  avoid passing -fno-stack-protector twice for LDSO_OBJS
  drop adding -DCRT to CFLAGS in the Makefile

 Makefile | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)


             reply	other threads:[~2023-03-13  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  5:17 Lukas Bulwahn [this message]
2023-03-13  5:17 ` [musl] [PATCH 1/2] avoid passing -fno-stack-protector twice for LDSO_OBJS Lukas Bulwahn
2023-03-13  5:17 ` [musl] [PATCH 2/2] drop adding -DCRT to CFLAGS in the Makefile Lukas Bulwahn

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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

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).