From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] Makeconfig: Fix time64-compat.mk target
Date: Thu, 17 Jun 2021 16:19:21 +0530 [thread overview]
Message-ID: <1d4f4bad-935c-afab-a2bb-8aa88270d0bd@sourceware.org> (raw)
In-Reply-To: <53064b9e-cd0e-e594-2c6c-5a326ca1074a@linaro.org>
On 6/17/21 4:08 PM, Adhemerval Zanella wrote:
> Thanks for catching it. Out of curiosity, how do you trigger this issue?
> I am building it glibc and tests with this patch for some time and I didn't
> see it.
It happens all the time, just that it does not terminate the build and
hence would be nearly impossible to notice unless you read the full
build messages line by line. However, I have this curious habit of
running the build as `make -j16 > /dev/null` due to which only stderr
gets printed on the terminal. The bright red error from gcc complaining
about missing libc-modules.h was hard to miss :)
Siddhesh
prev parent reply other threads:[~2021-06-17 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 5:44 Siddhesh Poyarekar
2021-06-17 8:36 ` Andreas Schwab
2021-06-17 10:38 ` Adhemerval Zanella
2021-06-17 10:49 ` Siddhesh Poyarekar [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=1d4f4bad-935c-afab-a2bb-8aa88270d0bd@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--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).