From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/binutils: fixes glibc build compiled with -Os on x86
Date: Sun, 13 Feb 2022 21:45:01 +0100 [thread overview]
Message-ID: <20220213214501.29dbc301@windsurf> (raw)
In-Reply-To: <Ygalu5jOo9skIxRc@waldemar-brodkorb.de>
On Fri, 11 Feb 2022 19:06:51 +0100
Waldemar Brodkorb <wbx@openadk.org> wrote:
> See here:
> https://sourceware.org/bugzilla/show_bug.cgi?id=28870
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Is this patch also needed for binutils 2.38 ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-13 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 18:06 [Buildroot] [PATCH 1/2] package/binutils: fixes glibc build compiled with -Os on x86 Waldemar Brodkorb
2022-02-13 20:45 ` Thomas Petazzoni via buildroot [this message]
2022-02-13 21:00 ` Thomas Petazzoni via buildroot
2022-02-14 21:06 ` 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=20220213214501.29dbc301@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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 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.