From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH 0/2] Fix incorrect stub warnings after generic refactor
Date: Mon, 19 Dec 2022 13:27:55 +0100 [thread overview]
Message-ID: <87y1r3fuic.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <dc265a5e-492c-828c-1988-41185f9f6b55@linaro.org> (Adhemerval Zanella Netto's message of "Mon, 19 Dec 2022 09:16:58 -0300")
* Adhemerval Zanella Netto:
> On 19/12/22 09:03, Florian Weimer wrote:
>> They cause link failures with -Wl,--fatal-warnings on aarch64.
>>
>
> Would be possible to use this option as default to catch such errors?
We'd have to make it conditional because tests for mktemp and the like
do result in warnings. We also do not have an inotify test, but in this
particular case, maybe the nscd build would have caught it.
Thanks,
Florian
prev parent reply other threads:[~2022-12-19 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 12:03 Florian Weimer
2022-12-19 12:03 ` [PATCH 1/2] Linux: Reflow and sort some Makefile variables Florian Weimer
2022-12-19 12:15 ` Adhemerval Zanella Netto
2022-12-19 12:03 ` [PATCH 2/2] Linux: Remove epoll_create, inotify_init from syscalls.list Florian Weimer
2022-12-19 12:16 ` Adhemerval Zanella Netto
2022-12-19 12:16 ` [PATCH 0/2] Fix incorrect stub warnings after generic refactor Adhemerval Zanella Netto
2022-12-19 12:27 ` Florian Weimer [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=87y1r3fuic.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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 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).