Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Documentation question
Date: Wed, 9 Dec 2009 21:11:46 +0000 (UTC)	[thread overview]
Message-ID: <hfp3qi$e30$1@ger.gmane.org> (raw)
In-Reply-To: hfp1uh$6fk$1@ger.gmane.org

On 2009-12-09, Grant Edwards <grant.b.edwards@gmail.com> wrote:

> I've been reading the "buildroot usage and documentation"
> document over the past couple days, and in order to not be a
> complete leech, I'm fixing various minor problems (typos,
> spelling, punctuation, usage, grammar, etc.) and will submmit a
> patch when I've finished.
>
> However, I've run across one paragraph where I think the actual
> content could use a tweak, and I thought I should ask about it
> before making a change.

Another question on content -- the doc says

  Buildroot optionally honors some environment variables that
  are passed to make:
  
    HOSTCXX, the host C++ compiler to use
    HOSTCC, the host C compiler to use
    UCLIBC_CONFIG_FILE [...]

From what I've been able to figure out, honoring those is not
an option.  Aren't they're always honored?  If honoring those
is optional, how/where is that option configured?

-- 
Grant Edwards                   grante             Yow! An Italian is COMBING
                                  at               his hair in suburban DES
                               visi.com            MOINES!

  reply	other threads:[~2009-12-09 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 20:39 [Buildroot] Documentation question Grant Edwards
2009-12-09 21:11 ` Grant Edwards [this message]
2009-12-09 22:32 ` Michael S. Zick
2009-12-09 22:54   ` Grant Edwards
2009-12-09 23:07     ` Michael S. Zick

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='hfp3qi$e30$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.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