From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] Use sys-root rather than sysroot for the sysroot/staging_dir
Date: Tue, 25 Jan 2011 22:50:53 +0100 [thread overview]
Message-ID: <20110125225053.49f7660b@surf> (raw)
In-Reply-To: <201101252239.36666.yann.morin.1998@anciens.enib.fr>
On Tue, 25 Jan 2011 22:39:36 +0100
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> wrote:
> As Thomas said on IRC, I would suggest to revert this. Is there anything
> in BR that depends on the sysroot being named 'sysroot' or 'sys-root' at all,
> or was that just an eye-candy change? (genuine question)
Just for the record, my preference for "sysroot" instead of "sys-root"
is because all sysroot-related options in gcc use the "sysroot"
spelling and not "sys-root" :
-print-sysroot
-print-sysroot-headers-suffix
--sysroot
And all gcc documentation refers to it as the "sysroot" :
`-print-sysroot'
Print the target sysroot directory that will be used during
compilation. This is the target sysroot specified either at
configure time or using the `--sysroot' option, possibly with an
extra suffix that depends on compilation options. If no target
sysroot is specified, the option prints nothing.
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:[~2011-01-25 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 15:08 [Buildroot] [git commit master 1/1] Use sys-root rather than sysroot for the sysroot/staging_dir Peter Korsgaard
2011-01-25 21:39 ` Yann E. MORIN
2011-01-25 21:50 ` Thomas Petazzoni [this message]
2011-01-25 23:25 ` Yann E. MORIN
2011-01-25 21:51 ` 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=20110125225053.49f7660b@surf \
--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.