All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Kamel Bouhara <kamel.bouhara@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/usbguard: fix build without asciidoc
Date: Tue, 08 Nov 2022 20:36:21 +0100	[thread overview]
Message-ID: <87zgd1i6h6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221026201736.327835-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Wed, 26 Oct 2022 22:17:36 +0200")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > Set ac_cv_prog_A2X to disable build of documentation and avoid the
 > following build failure without a working a2x raised since at least bump
 > to version 1.1.1 in commit ad21d84a589458fd4542993912891daa503d72dd:

 > a2x -v -f manpage doc/man/usbguard.1.adoc -D ./$(dirname doc/man/usbguard.1.roff)
 > a2x -v -f manpage doc/man/usbguard-dbus.8.adoc -D ./$(dirname doc/man/usbguard-dbus.8.roff)
 > /nvmedata/autobuild/instance-5/output-1/host/bin/python3: Error while
 > finding module specification for 'asciidoc.a2x' (ModuleNotFoundError:
 > No module named 'asciidoc')

 > Fixes:
 >  - http://autobuild.buildroot.org/results/e41950f3cd4bd83d9b067af498757cb9d2f207ef

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2022.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-11-08 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 20:17 [Buildroot] [PATCH 1/1] package/usbguard: fix build without asciidoc Fabrice Fontaine
2022-10-27  6:49 ` Thomas Petazzoni via buildroot
2022-11-08 19:36 ` Peter Korsgaard [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=87zgd1i6h6.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=kamel.bouhara@gmail.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 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.