mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [linux-next-20250307] Build Failure
Date: Mon, 17 Mar 2025 11:06:13 +0100	[thread overview]
Message-ID: <ebc5d8c6-3c5c-4e6a-a218-9dddcdb4f8bc@csgroup.eu> (raw)
In-Reply-To: <25e5d468-6c40-40b7-a010-8c8018b6d228@linux.ibm.com>



Le 17/03/2025 à 08:27, Venkat Rao Bagalkote a écrit :
> 
> On 12/03/25 8:49 pm, Christophe Leroy wrote:
>>
>>
>> Le 12/03/2025 à 11:11, Venkat Rao Bagalkote a écrit :
>>>
>>> On 12/03/25 4:20 am, Christophe Leroy wrote:
>>>>
>>>>
>>>> Le 09/03/2025 à 13:38, Venkat Rao Bagalkote a écrit :
>>>>> Greetings!!,
>>>>>
>>>>> I see linux-next-20250307 fails to build on IBM Power9 and Power10 
>>>>> servers.
>>>>>
>>>>>
>>>>> Errors:
>>>>>
>>>>> In file included from ^[[01m^[[K<command-line>^[[m^[[K:
>>>>> ^[[01m^[[K./usr/include/cxl/features.h:11:10:^[[m^[[K 
>>>>> ^[[01;31m^[[Kfatal error: ^[[m^[[Kuuid/uuid.h: No such file or 
>>>>> directory
>>>>>     11 | #include ^[[01;31m^[[K<uuid/uuid.h>^[[m^[[K
>>>>>        |          ^[[01;31m^[[K^~~~~~~~~~~~~^[[m^[[K
>>>>
>>>> This is unreadable. Please avoid fancy colors that add escapes to 
>>>> logs. You can unset LANG environment var before building in order to 
>>>> get pastable stuff.
>>>>
>>
>> Allthought not really readable, it seems to mention that uuid/uuid.h 
>> is missing.
>>
>> Can you confirm that you have installed libuuid package in your 
>> system ? Maybe you also need some libuuid-dev packet to get headers ?
> 
> 
> Yeah uuid package is installed on my system. I am seeing this failure 
> only with build next-20250307.
> 
> Builds with before and after are compiling successfully.

Ok, so I understand from this that the problem is fixed and there is not 
further investigation required.

Thanks
Christophe

      reply	other threads:[~2025-03-17 10:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09 12:38 Venkat Rao Bagalkote
2025-03-11  4:23 ` Venkat Rao Bagalkote
2025-03-11  7:41   ` Nicolas Frattaroli
2025-03-11  8:47 ` Madhavan Srinivasan
2025-03-11  9:40   ` Madhavan Srinivasan
2025-03-11 22:50 ` Christophe Leroy
2025-03-12 10:11   ` Venkat Rao Bagalkote
2025-03-12 10:16     ` Christophe Leroy
2025-03-17  7:19       ` Venkat Rao Bagalkote
2025-03-12 15:19     ` Christophe Leroy
2025-03-17  7:27       ` Venkat Rao Bagalkote
2025-03-17 10:06         ` Christophe Leroy [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=ebc5d8c6-3c5c-4e6a-a218-9dddcdb4f8bc@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=sfr@canb.auug.org.au \
    --cc=venkat88@linux.ibm.com \
    /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

all inboxes | Powered by JetHome®