Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Add gcc version and tclibc to build summary
Date: Wed, 22 Jun 2016 10:05:06 -0700	[thread overview]
Message-ID: <576AC542.9020709@gmail.com> (raw)
In-Reply-To: <9FC96606-1A87-49F3-8A49-F692CDF8C2AA@gmail.com>



On 06/22/2016 09:52 AM, Khem Raj wrote:
> 
>> On Jun 22, 2016, at 8:29 AM, Armin Kuster <akuster808@gmail.com> wrote:
>>
>> Since there are two gcc versions supported and any number of tcglibc,
>> it would be nice to know which ones are being used.
>> Add those to the build summary.
>>
>> Build summary
>> TCLIBC            = “glibc"
> 
> libc is evident from TARGET_SYS

TARGET_SYS="x86_64-oe-linux", this is not the my intent.


The intent is to track which libc is being used. I changed TCLIBC =
"musl" local.conf and now build summary show.

TCLIBC            = "musl"
GCC_VERSION       = "6.1"

Is there a clearer / better way to display this?

- armin
> 
>> GCC_VERSION       = "6.1"
>>
>> Not sure if the gcc version bit is best practice.
>>
>> Armin Kuster (2):
>>  build summary: add gcc version being used.
>>  build summary: add TCLIBC being used
>>
>> meta/classes/base.bbclass | 2 ++
>> meta/conf/bitbake.conf    | 2 +-
>> 2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> --
>> 2.3.5
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 


  reply	other threads:[~2016-06-22 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 15:29 [PATCH 0/2] Add gcc version and tclibc to build summary Armin Kuster
2016-06-22 15:29 ` [PATCH 1/2] build summary: add gcc version being used Armin Kuster
2016-07-20 14:41   ` akuster808
2016-07-20 14:53     ` Richard Purdie
2016-06-22 15:29 ` [PATCH 2/2] build summary: add TCLIBC " Armin Kuster
2016-06-22 16:52 ` [PATCH 0/2] Add gcc version and tclibc to build summary Khem Raj
2016-06-22 17:05   ` akuster808 [this message]
2016-06-22 17:21     ` Khem Raj
2016-06-25 15:30       ` akuster808
     [not found]         ` <CAMKF1srkQ00SZVk2T3tp-o=ZBO8Xstv6JmZthksCE=geBfw1jw@mail.gmail.com>
     [not found]           ` <CAMKF1spToGmm0bLgqWu51bBKx6-NuN0ru9LAnEq7P3egKC5B2Q@mail.gmail.com>
2016-06-25 15:45             ` Khem Raj

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=576AC542.9020709@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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