From: Rich Felker <dalias@libc.org>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions
Date: Thu, 24 Oct 2024 09:11:42 -0400 [thread overview]
Message-ID: <20241024131141.GW10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <ZxjsGeXjnu6lY68X@probook>
On Wed, Oct 23, 2024 at 02:29:13PM +0200, J. Neuschäfer wrote:
> On Tue, Oct 22, 2024 at 05:52:22PM -0400, Rich Felker wrote:
> > On Wed, Oct 02, 2024 at 05:40:03PM +0200, J. Neuschäfer wrote:
> > > This patchset adds newer GCC versions to MCM. Patches are copied from
> > > GCC 11 and only very lightly modifed (which can be verified by diffing
> > > the patch directories).
> > >
> > > I haven't tested the resulting toolchains, so there might be some bugs
> > > lurking.
> >
> > Could you resend these as attachments instead of lkml-thread-style?
> > Something got messed up with the whitespace and git am is applying
> > them but giving results that have gratuitous whitespace diffs, and I'd
> > rather not track down whether any of that is breaking.
> >
> > Rich
>
> Here they are.
Weird, I'm still getting problems. git-am gives me:
.git/rebase-apply/patch:40: space before tab in indent.
"|fstack-protector-strong|fstack-protector-explicit" \
.git/rebase-apply/patch:88: space before tab in indent.
extra_headers="s390intrin.h htmintrin.h htmxlintrin.h vecintrin.h"
.git/rebase-apply/patch:89: space before tab in indent.
;;
.git/rebase-apply/patch:93: space before tab in indent.
cpu_type=sh
.git/rebase-apply/patch:94: space before tab in indent.
extra_options="${extra_options} fused-madd.opt"
warning: squelched 79 whitespace errors
warning: 84 lines add whitespace errors.
and the applied patches have context lines that should be an empty
line with the one-space diff prefix replaced to empty lines (no
leading diff space).
Can you verify whether this is expected or if something is getting
munged in the mail?
Rich
next prev parent reply other threads:[~2024-10-24 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 15:40 J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 1/3] add gcc 12.4 hash and patches J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 2/3] add gcc 13.3 " J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 3/3] add gcc 14.2 " J. Neuschäfer
2024-10-22 21:52 ` [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions Rich Felker
2024-10-23 12:29 ` J. Neuschäfer
2024-10-24 13:11 ` Rich Felker [this message]
2024-10-24 13:36 ` Rich Felker
2024-10-25 11:39 ` J. Neuschäfer
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=20241024131141.GW10433@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=j.neuschaefer@gmx.net \
--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).