From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] glibc: Don't create object file from gcc test.
Date: Sat, 8 Jul 2023 09:02:43 +0200 [thread overview]
Message-ID: <20230708070243.2205254-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230707093619.3823719-1-christian.melki@t2data.com>
Thanks, applied as 0e19d21aaeadeee351ec41a3be1bffb71bf15eec.
Michael
[sent from post-receive hook]
On Sat, 08 Jul 2023 09:02:43 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> The test was creating a file named "-.o" in my workdir.
> We don't want the output. Use -fsyntax-only.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230707093619.3823719-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/glibc.make b/rules/glibc.make
> index a550f4b9206a..e3b3574ccf0b 100644
> --- a/rules/glibc.make
> +++ b/rules/glibc.make
> @@ -31,7 +31,7 @@ $(STATEDIR)/glibc.prepare:
> ifdef PTXCONF_GLIBC_Y2038
> @echo Checking Y2038 support...
> @echo 'static_assert(sizeof(time_t) == 8, "y2038");' | \
> - $(CROSS_CC) -c -x c -include sys/types.h -include assert.h - &>/dev/null || \
> + $(CROSS_CC) -c -x c -fsyntax-only -include sys/types.h -include assert.h - &>/dev/null || \
> ptxd_bailout "PTXCONF_GLIBC_Y2038 is enabled but the toolchain has no Y2038 support!"
> endif
> @$(call touch)
prev parent reply other threads:[~2023-07-08 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 9:36 [ptxdist] [PATCH v2] " Christian Melki
2023-07-08 7:02 ` Michael Olbrich [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=20230708070243.2205254-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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