From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] texinfo: new host package
Date: Sun, 24 Mar 2013 18:43:32 -0400 (EDT) [thread overview]
Message-ID: <1111501726.1967.1364165012922.JavaMail.root@mail> (raw)
In-Reply-To: <1364164146-16517-2-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
> The makeinfo program from texinfo is needed to get Crosstool-NG to
> build properly a toolchain. Long term, it would be great if
> Crosstool-NG supported building without texinfo, simply by disabling
> the build of documentation.
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
Cheers,
Vivien
next prev parent reply other threads:[~2013-03-24 22:43 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 [this message]
2013-03-24 23:00 ` Thomas Petazzoni
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=1111501726.1967.1364165012922.JavaMail.root@mail \
--to=vivien.didelot@savoirfairelinux.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