From: John Hubbard <jhubbard@nvidia.com>
To: Mirsad Todorovac <mtodorovac69@gmail.com>,
<linux-kselftest@vger.kernel.org>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Shuah Khan <shuah@kernel.org>, <linux-sgx@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Edward Liaw <edliaw@google.com>
Subject: Re: [PATCH v1 1/1] selftests/sgx: Fix the implicit declaration of asprintf() compiler error
Date: Fri, 10 May 2024 13:52:09 -0700 [thread overview]
Message-ID: <4dcd5fca-c200-42d1-a8f2-3045d5430fd6@nvidia.com> (raw)
In-Reply-To: <656c3b4a-0481-4634-9dd4-19bb9e4cd612@gmail.com>
On 5/10/24 1:37 PM, Mirsad Todorovac wrote:
...
> The fix defines __USE_GNU before including <stdio.h> in case it isn't already
> defined. After this intervention the module compiles OK.
Instead of interventions, I believe the standard way to do this is to simply
define _GNU_SOURCE before including the header file(s). For example, the
following also fixes the compilation failure on Ubuntu:
diff --git a/tools/testing/selftests/sgx/main.c b/tools/testing/selftests/sgx/main.c
index 9820b3809c69..bb6e795d06e2 100644
--- a/tools/testing/selftests/sgx/main.c
+++ b/tools/testing/selftests/sgx/main.c
@@ -1,6 +1,7 @@
// SPDX-License-Identifier: GPL-2.0
/* Copyright(c) 2016-20 Intel Corporation. */
+#define _GNU_SOURCE
#include <cpuid.h>
#include <elf.h>
#include <errno.h>
However, that's not required, because Edward Liaw is already on v4 of
a patchset[1] that fixes up the _GNU_SOURCE problem for all selftests.
[1] https://lore.kernel.org/all/20240510000842.410729-2-edliaw@google.com/
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2024-05-10 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:37 [PATCH v1 1/1] selftests/sgx: Fix the implicit declaration of asprintf() compiler error Mirsad Todorovac
2024-05-10 20:52 ` John Hubbard [this message]
2024-05-10 21:02 ` Mirsad Todorovac
2024-05-12 23:02 ` Jarkko Sakkinen
2024-05-13 9:43 ` Mirsad Todorovac
2024-05-13 11:20 ` Jarkko Sakkinen
2024-05-12 22:58 ` Jarkko Sakkinen
2024-05-12 22:48 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2024-05-10 20:46 Mirsad Todorovac
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=4dcd5fca-c200-42d1-a8f2-3045d5430fd6@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=dave.hansen@linux.intel.com \
--cc=edliaw@google.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mtodorovac69@gmail.com \
--cc=shuah@kernel.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.