From: Khem Raj <raj.khem@gmail.com>
To: Federico Pellegrin <fede@evolware.org>,
Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] util-linux and --enable-raw with recent kernels
Date: Tue, 12 Oct 2021 09:55:24 -0700 [thread overview]
Message-ID: <deee2a0d-5de0-d18b-3b95-2e3132c8915a@gmail.com> (raw)
In-Reply-To: <CAM6O0ZhZKspmeE02cgh1coOvjMUmhdUTMR8en3UbpJm3SL5fhA@mail.gmail.com>
On 10/12/21 9:27 AM, Federico Pellegrin wrote:
>
> Hello,
> Running on a quite recent kernel (5.14.10 from Fedora 34) I've came
> across a problem when building util-linux (2.35.2) native, namely in the
> configure phase:
>
> configure: error: raw selected, but required raw.h header file not available
>
you might want to use latest master, fix that you might find useful is
https://git.openembedded.org/openembedded-core/commit/?id=7f577c10913104860121f682b9b3754870c4db23
> After a bit or research I believe it is due to:
> https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1820154.html
> <https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1820154.html>
>
> Which is related to the change in the recent kernels here:
> https://github.com/torvalds/linux/commit/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093#diff-10d697dff14540ee1eb6539dcc53b2b88844b6187c1995c0698ba0936754304a
> <https://github.com/torvalds/linux/commit/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093#diff-10d697dff14540ee1eb6539dcc53b2b88844b6187c1995c0698ba0936754304a>
> where the raw.h file was indeed removed.
>
> As per first link it may not be obvious to fix, and don't see an
> upstream fix for it, but from the Yocto perspective my current
> workaround is basically just to remove "--enable-raw" from the
> EXTRA_OECONF to disable the raw feature.
>
> While the whole image seemed to build fine with this, I'm not very sure
> if that configuration option had a precise use (which maybe it's being
> skipping in my specific build) or not, so I wanted to ask the experts if
> there is any opinion on this and/or should I do a merge request that
> removes it to handle this problem, at least until there is a better
> solution upstream in util-linux?
>
> Many thanks,
> Federico
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> You automatically follow any topics you start or reply to.
> View/Reply Online (#55041): https://lists.yoctoproject.org/g/yocto/message/55041
> Mute This Topic: https://lists.yoctoproject.org/mt/86266370/1997914
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2021-10-12 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 16:27 util-linux and --enable-raw with recent kernels Federico Pellegrin
2021-10-12 16:55 ` Khem Raj [this message]
2021-10-13 3:01 ` [yocto] " Federico Pellegrin
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=deee2a0d-5de0-d18b-3b95-2e3132c8915a@gmail.com \
--to=raj.khem@gmail.com \
--cc=fede@evolware.org \
--cc=yocto@lists.yoctoproject.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 NNTP newsgroup(s).