On Jun 25, 2016 8:30 AM, "akuster808" wrote:
>
>
>
> On 06/22/2016 10:21 AM, Khem Raj wrote:
> >
> >> On Jun 22, 2016, at 10:05 AM, akuster808 wrote:
> >>
> >>
> >>
> >> On 06/22/2016 09:52 AM, Khem Raj wrote:
> >>>
> On Jun 22, 2016, at 8:29 AM,
On 06/22/2016 10:21 AM, Khem Raj wrote:
>
>> On Jun 22, 2016, at 10:05 AM, akuster808 wrote:
>>
>>
>>
>> On 06/22/2016 09:52 AM, Khem Raj wrote:
>>>
On Jun 22, 2016, at 8:29 AM, Armin Kuster wrote:
Since there are two gcc versions
> On Jun 22, 2016, at 10:05 AM, akuster808 wrote:
>
>
>
> On 06/22/2016 09:52 AM, Khem Raj wrote:
>>
>>> On Jun 22, 2016, at 8:29 AM, Armin Kuster wrote:
>>>
>>> Since there are two gcc versions supported and any number of tcglibc,
>>> it would
On 06/22/2016 09:52 AM, Khem Raj wrote:
>
>> On Jun 22, 2016, at 8:29 AM, Armin Kuster 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
> On Jun 22, 2016, at 8:29 AM, Armin Kuster 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
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"
GCC_VERSION = "6.1"
Not sure if the gcc version bit is best practice.
Armin Kuster (2):