From: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: linux-i2c <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [i2c-tools][PATCH] honor CROSS_COMPILE
Date: Sat, 08 Jan 2011 14:32:21 -0600 [thread overview]
Message-ID: <4D28C9D5.8050401@ti.com> (raw)
In-Reply-To: <20110108192345.GB4045-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Wolfram Sang wrote, on 01/08/2011 01:23 PM:
> Then again, the vast majority of userspace-projects do not use CROSS_COMPILE.
> Build systems like ptxdist and buildroot have done fine with overriding CC so
> far. I don't see much gain in that addition.
>
The same is true for CROSS_COMPILE as well.. since the patch does still
allow CC to be over-ridden (as was the previous behavior), why not add
CROSS_COMPILE as well considering folks who could be cross compiling
just i2ctools without using buildroot and the likes?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-01-08 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:01 [i2c-tools][PATCH] honor CROSS_COMPILE Nishanth Menon
[not found] ` <1294426874-24973-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2011-01-08 19:23 ` Wolfram Sang
[not found] ` <20110108192345.GB4045-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-01-08 20:32 ` Nishanth Menon [this message]
[not found] ` <4D28C9D5.8050401-l0cyMroinI0@public.gmane.org>
2011-01-08 21:01 ` Wolfram Sang
[not found] ` <20110108210130.GC4045-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-01-10 14:26 ` Jean Delvare
[not found] ` <20110110152608.536de8e7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-10 14:27 ` Nishanth Menon
[not found] ` <4D2B1768.5030303-l0cyMroinI0@public.gmane.org>
2011-01-10 14:44 ` Jean Delvare
[not found] ` <20110110154435.640c528b-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-10 14:46 ` Nishanth Menon
[not found] ` <4D2B1BDD.9070601-l0cyMroinI0@public.gmane.org>
2011-12-04 19:49 ` Jean Delvare
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=4D28C9D5.8050401@ti.com \
--to=nm-l0cymroini0@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
/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.