All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: yocto@yoctoproject.org
Subject: Re: Alternative SDK installation directory working?
Date: Mon, 19 Nov 2012 16:21:30 +0200	[thread overview]
Message-ID: <50AA406A.60605@intel.com> (raw)
In-Reply-To: <20121119135023.5927D20032F@gemini.denx.de>



On 11/19/2012 03:50 PM, Wolfgang Denk wrote:
> Dear Laurentiu,
> 
> In message <50AA31D8.5020700@intel.com> you wrote:
>>
>>>> -> source /opt/poky-test/environment-setup-armv5te-poky-linux-gnueabi
>>>> -> ${TARGET_PREFIX}gcc -v -o /tmp/x /tmp/x.c
>>
>> Just do: $CC -o /tmp/x /tmp/x.c
>>
>> It should work.
>>
>> echo $CC
>> arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork
>> -mtune=arm926ej-s --sysroot=/tests/sdk/sysroots/armv5te-poky-linux-gnueabi
> 
> Argh... Isn't it somewhat ... unconventional (to avoid stonger words)
> to encode compiler options in a variable which is supposed to define
> the "Program for compiling C programs" ?
It is unconventional, I admit. Unfortunately, it's not clear to me why
this was done in the first place. I've just read the commit message for
these changes and it didn't make it clearer. Maybe Mark, who made these
changes, can give us a better answer.

> 
> Should such options not go to one of the *FLAGS variables instead?
I personally don't see any reason why they shouldn't.

Thanks,
Laurentiu
> 
> Best regards,
> 
> Wolfgang Denk
> 


  reply	other threads:[~2012-11-19 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 12:35 Alternative SDK installation directory working? Wolfgang Denk
2012-11-19 13:06 ` Jack Mitchell
2012-11-19 13:19   ` Laurentiu Palcu
2012-11-19 13:50     ` Wolfgang Denk
2012-11-19 14:21       ` Laurentiu Palcu [this message]
2012-11-19 13:46   ` Wolfgang Denk
2012-11-19 13:38 ` Eric Bénard

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=50AA406A.60605@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=wd@denx.de \
    --cc=yocto@yoctoproject.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.