Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libtool: disable makeinfo
Date: Tue, 7 Jul 2015 09:22:14 +0200	[thread overview]
Message-ID: <20150707092214.30d13879@free-electrons.com> (raw)
In-Reply-To: <559AF52D.5090106@mind.be>

Arnout,

On Mon, 6 Jul 2015 23:37:49 +0200, Arnout Vandecappelle wrote:

>  BTW, Thomas, any idea why the autobuilders didn't catch this? Do the chroots
> have texinfo installed?

My chroot does not have texinfo installed:

test at build:~$ dpkg -l | grep texinfo
test at build:~$ which makeinfo
test at build:~$ 

This makeinfo thing is very mysterious to me. Sometimes it complains
it's missing, sometimes not. I've never been able to really understand
what happens.

I am wondering if some packages don't bundle the pre-generated
documentation in their tarball, but sometimes have the pre-generated
files with an older date than the source files, which causes the
documentation to be generated once again. But that's really just a
guess.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2015-07-07  7:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  1:14 [Buildroot] [PATCH 1/1] package/libtool: disable makeinfo Sam Bobroff
2015-07-03 16:07 ` Arnout Vandecappelle
2015-07-03 17:56 ` Yann E. MORIN
2015-07-04 10:45 ` Thomas Petazzoni
2015-07-06 21:37   ` Arnout Vandecappelle
2015-07-07  6:20     ` Peter Korsgaard
2015-07-07  7:22     ` Thomas Petazzoni [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=20150707092214.30d13879@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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