From: "Paul E. McKenney" <paulmck@kernel•org>
To: Dave Jiang <dave.jiang@intel•com>
Cc: linux-cxl@vger•kernel.org, dave@stgolabs•net,
jonathan.cameron@huawei•com, alison.schofield@intel•com,
vishal.l.verma@intel•com, ira.weiny@intel•com,
dan.j.williams@intel•com, gourry@gourry•net,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
sfr@canb•auug.org.au
Subject: Re: [BUG -next] ./usr/include/cxl/features.h:11:10: fatal error: uuid/uuid.h: No such file or directory
Date: Fri, 28 Mar 2025 13:45:42 -0700 [thread overview]
Message-ID: <52a34c97-88d2-415e-a899-6583ae3ba620@paulmck-laptop> (raw)
In-Reply-To: <14bfcfa0-5999-49e4-854e-ff8810d6df3c@intel.com>
On Fri, Mar 28, 2025 at 01:03:19PM -0700, Dave Jiang wrote:
>
>
> On 3/28/25 10:39 AM, Paul E. McKenney wrote:
> > Hello!
> >
> > In next-20250328 and next-20250327, allmodconfig builds get me:
> >
> > ./usr/include/cxl/features.h:11:10: fatal error: uuid/uuid.h: No such file or directory
> >
> > This file is apparently auto-generated, because when I change the #include
> > to the more likely linux/uuid.h, my changes are overwritten by the build.
> >
> > Gregory Price noted that something similar has happened recently and been fixed:
> >
> > https://lore.kernel.org/all/70ba4e80-53c4-4583-82f3-2851e0829aa6@linux.ibm.com/
> >
> > Perhaps someone unfixed it?
> >
> > Thanx, Paul
>
>
> I can't get the powerpc cross build to build to reproduce the issue from next-20250328. Does the change below address the issue for you?
>
> ---
> diff --git a/include/uapi/cxl/features.h b/include/uapi/cxl/features.h
> index d6db8984889f..691eeda9c892 100644
> --- a/include/uapi/cxl/features.h
> +++ b/include/uapi/cxl/features.h
> @@ -8,11 +8,7 @@
> #define _UAPI_CXL_FEATURES_H_
>
> #include <linux/types.h>
> -#ifndef __KERNEL__
> -#include <uuid/uuid.h>
> -#else
> #include <linux/uuid.h>
> -#endif
>
> /*
> * struct cxl_mbox_get_sup_feats_in - Get Supported Features input
Thank you, Dave!
Please note that I am reproducing this not on powerpc, but instead on
x86 with a simple allmodconfig build.
Making the above change got me this:
usr/include/cxl/features.h:59:9: error: unknown type name ‘uuid_t’
Thanx, Paul
next prev parent reply other threads:[~2025-03-28 20:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 17:39 [BUG -next] ./usr/include/cxl/features.h:11:10: fatal error: uuid/uuid.h: No such file or directory Paul E. McKenney
2025-03-28 20:03 ` Dave Jiang
2025-03-28 20:45 ` Paul E. McKenney [this message]
2025-03-28 21:22 ` Dave Jiang
2025-03-28 21:57 ` Paul E. McKenney
2025-03-28 23:26 ` Dan Williams
2025-03-28 23:58 ` Paul E. McKenney
2025-03-29 0:23 ` Dan Williams
2025-03-29 0:26 ` Dave Jiang
2025-03-31 13:24 ` Jason Gunthorpe
2025-03-31 16:48 ` Paul E. McKenney
2025-03-31 16:54 ` Dan Williams
2025-03-31 17:17 ` Jason Gunthorpe
2025-03-31 19:47 ` Dan Williams
2025-04-01 7:01 ` Venkat Rao Bagalkote
2025-04-01 14:08 ` Paul E. McKenney
2025-04-01 15:15 ` Dave Jiang
2025-04-02 0:07 ` Paul E. McKenney
2025-04-02 0:18 ` Dave Jiang
2025-04-02 0:47 ` Stephen Rothwell
2025-04-02 4:21 ` Paul E. McKenney
2025-04-02 6:27 ` Venkat Rao Bagalkote
2025-04-02 11:44 ` Jason Gunthorpe
2025-04-02 13:42 ` Venkat Rao Bagalkote
2025-04-02 17:20 ` Paul E. McKenney
2025-04-07 17:49 ` Jason Gunthorpe
2025-04-05 17:34 ` Palmer Dabbelt
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=52a34c97-88d2-415e-a899-6583ae3ba620@paulmck-laptop \
--to=paulmck@kernel$(echo .)org \
--cc=alison.schofield@intel$(echo .)com \
--cc=dan.j.williams@intel$(echo .)com \
--cc=dave.jiang@intel$(echo .)com \
--cc=dave@stgolabs$(echo .)net \
--cc=gourry@gourry$(echo .)net \
--cc=ira.weiny@intel$(echo .)com \
--cc=jonathan.cameron@huawei$(echo .)com \
--cc=linux-cxl@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vishal.l.verma@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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