All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: michael.opdenacker@rootcommit.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 2/5] alsa-utils: upgrade 1.2.14 -> 1.2.15
Date: Mon, 22 Dec 2025 17:32:59 +0000 (UTC)	[thread overview]
Message-ID: <d600fe11-1a72-4c29-8896-995f4f44f4f8@rootcommit.com> (raw)
In-Reply-To: <CANNYZj9BS-ztuQd5txArSADdp7T_PZG=UuQTrknv0qNXcspOKA@mail.gmail.com>

Hi Alex

On 12/22/25 18:24, Alexander Kanavin wrote:
> On Wed, 17 Dec 2025 at 17:05, Michael Opdenacker via
> lists.openembedded.org
> <michael.opdenacker=rootcommit.com@lists.openembedded.org> wrote:
>
>>   # On build machines with python-docutils (not python3-docutils !!) installed
>>   # rst2man (not rst2man.py) is detected and compile fails with
>>   # | make[1]: *** No rule to make target 'alsaucm.1', needed by 'all-am'.  Stop.
>>   # Avoid this by disabling expicitly
>> -EXTRA_OECONF = "--disable-rst2man"
>> +# EXTRA_OECONF = "--disable-rst2man"
> Hello Michael,
>
> is this commented out by mistake? Either you need to explain why
> --disable-rst2man is not needed anymore (and remove the comments
> above), or not do it.


Thanks for the review!

Oops, my mistake, I tested whether the setting was still needed or not, 
and then forgot about it.

I'd rather address this in a separate commit, because my machine doesn't 
have the issue.
Cheers
Michael.


-- 
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/



  reply	other threads:[~2025-12-22 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 16:05 [PATCH v2 0/5] ALSA 1.2.15 updates michael.opdenacker
2025-12-17 16:05 ` [PATCH v2 3/5] alsa-tools: upgrade 1.2.14 -> 1.2.15 michael.opdenacker
2025-12-17 16:05 ` [PATCH v2 1/5] alsa-lib: " michael.opdenacker
2025-12-17 16:05 ` [PATCH v2 2/5] alsa-utils: " michael.opdenacker
2025-12-22 17:24   ` [OE-core] " Alexander Kanavin
2025-12-22 17:32     ` Michael Opdenacker [this message]
2025-12-17 16:05 ` [PATCH v2 5/5] maintainers.inc: update e-mail address michael.opdenacker
2025-12-17 16:05 ` [PATCH v2 4/5] alsa-ucm-conf: upgrade 1.2.14 -> 1.2.15 michael.opdenacker

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=d600fe11-1a72-4c29-8896-995f4f44f4f8@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.