From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] texinfo: new host package
Date: Mon, 25 Mar 2013 00:00:14 +0100 [thread overview]
Message-ID: <20130325000014.49c13ea1@skate> (raw)
In-Reply-To: <1111501726.1967.1364165012922.JavaMail.root@mail>
Dear Vivien Didelot,
On Sun, 24 Mar 2013 18:43:32 -0400 (EDT), Vivien Didelot wrote:
> Just curious, isn't possible for the Crosstool-NG build to disable the
> doc, with something like Gustavo did here for GCC:
>
> http://git.buildroot.net/buildroot/commit/?id=62322acb2ce186d544ab21fe253ccc8561a68a48
Yes, it should be possible. Normally, we enabled the "Remove
documentation" option from Crosstool-NG, which should tell Crosstool-NG
to not build the documentation. But in practice, Crosstool-NG
configure script still wants a makeinfo program. Even if you fake it by
passing /bin/true as the makeinfo program, then the build process of
binutils fails during the construction of its info pages. So it looks
like Crosstool-NG does not disable entirely the generation of
documentation, or something else is going one.
Introducing this texinfo package is only a short-term solution, until
the proper way of disabling the documentation generation in
Crosstool-NG is found.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-24 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 22:29 [Buildroot] Crosstool-NG fix Thomas Petazzoni
2013-03-24 22:29 ` [Buildroot] [PATCH 1/2] texinfo: new host package Thomas Petazzoni
2013-03-24 22:43 ` Vivien Didelot
2013-03-24 23:00 ` Thomas Petazzoni [this message]
2013-03-24 22:29 ` [Buildroot] [PATCH 2/2] crosstool-ng: add missing dependencies Thomas Petazzoni
2013-03-24 22:32 ` [Buildroot] Crosstool-NG fix Peter Korsgaard
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=20130325000014.49c13ea1@skate \
--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 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.