public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Ying Huang <ying.huang@oss.cipunited.com>
Cc: "Andreas K. Huettel" <dilfridge@gentoo.org>,
	 Mark Wielaard <mark@klomp.org>,
	 Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	 Libc-alpha <libc-alpha@sourceware.org>,
	 yunqiang.su@oss.cipunited.com
Subject: Re: [PATCH v6] MIPS: Sync elf.h from binutils
Date: Mon, 24 Jul 2023 13:39:01 +0200	[thread overview]
Message-ID: <87wmyppmi2.fsf@oldenburg3.str.redhat.com> (raw)
In-Reply-To: <ZLvpaP6AK5jHbYda@aurel32.net> (Aurelien Jarno's message of "Sat, 22 Jul 2023 16:36:24 +0200")

* Aurelien Jarno:

> Hi,
>
> On 2023-07-22 13:02, Andreas K. Huettel via Libc-alpha wrote:
>> Am Samstag, 22. Juli 2023, 11:37:41 CEST schrieb Mark Wielaard:
>> > Hi,
>> > 
>> > On Tue, Jul 18, 2023 at 10:17:09AM +0800, Ying Huang wrote:
>> > > ping
>> > > 
>> > > Because I did not have commit permissions,  could you help commit?
>> > 
>> > I am happy to commit this for you. But even though it is a constants
>> > only patch at this point it should probably get an OK from Andreas,
>> > the release manager.
>> 
>> OK from me, looks well-separated enough.
>> Last feature add-on of the month. :o)
>> 
>
> Unfortunately this commit breaks building glibc on at list
> mips64el-linux-gnuabi64, unless --disable-werror is used, due to
> preprocessor redefinitions:

I was wondering if this is caught by build-many-glibcs.py, and it
actually is, on all MIPS targets.

We do not have a requirement to run build-many-glibcs.py (our
cross-building script); I merely wanted to check if there is a gap in
the tool that needs to be addressed.

Thanks,
Florian


  parent reply	other threads:[~2023-07-24 11:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  7:50 Ying Huang
2023-07-06 12:31 ` Mark Wielaard
2023-07-11  6:48 ` Ying Huang
2023-07-18  2:17   ` Ying Huang
2023-07-22  9:37     ` Mark Wielaard
2023-07-22 11:02       ` Andreas K. Huettel
2023-07-22 11:29         ` 黄莺
2023-07-22 12:28           ` Mark Wielaard
2023-07-22 14:36         ` Aurelien Jarno
2023-07-22 14:42           ` Andreas K. Huettel
2023-07-22 14:59             ` Mark Wielaard
2023-07-23  4:16               ` YunQiang Su
2023-08-06  8:52               ` Maciej W. Rozycki
2023-07-24 11:39           ` Florian Weimer [this message]
2023-07-24 18:04             ` Adhemerval Zanella Netto
2023-07-22 11:27       ` 黄莺

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=87wmyppmi2.fsf@oldenburg3.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dilfridge@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=ying.huang@oss.cipunited.com \
    --cc=yunqiang.su@oss.cipunited.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. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).