On 02/22/2016 11:52 AM, Bin.Cheng wrote:
Hi,
I still don't quite follow this method. If I pop up chroot
environment with new glibc, it's still possible that the new glibc
isn't compatible with the default gcc in chroot. Won't this a
chicken-egg problem because we want to build our gcc against n
On Mon, Feb 1, 2016 at 7:45 PM, Jeff Law wrote:
> On 02/01/2016 12:07 PM, Bin.Cheng wrote:
>>
>> On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab
>> wrote:
>>>
>>> "Bin.Cheng" writes:
>>>
Seems to me Andrew was right in comment of PR69559, that we simply
couldn't bootstrap GCC with sysro
On Mon, Feb 1, 2016 at 7:45 PM, Jeff Law wrote:
> On 02/01/2016 12:07 PM, Bin.Cheng wrote:
>>
>> On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab
>> wrote:
>>>
>>> "Bin.Cheng" writes:
>>>
Seems to me Andrew was right in comment of PR69559, that we simply
couldn't bootstrap GCC with sysro
On 02/01/2016 12:07 PM, Bin.Cheng wrote:
On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab wrote:
"Bin.Cheng" writes:
Seems to me Andrew was right in comment of PR69559, that we simply
couldn't bootstrap GCC with sysroot.
The main use of sysroot is to build a cross compiler, which you cannot
On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab wrote:
> "Bin.Cheng" writes:
>
>> Seems to me Andrew was right in comment of PR69559, that we simply
>> couldn't bootstrap GCC with sysroot.
>
> The main use of sysroot is to build a cross compiler, which you cannot
> bootstrap anyway.
>
>> My questi
"Bin.Cheng" writes:
> Seems to me Andrew was right in comment of PR69559, that we simply
> couldn't bootstrap GCC with sysroot.
The main use of sysroot is to build a cross compiler, which you cannot
bootstrap anyway.
> My question here is: If this is the case, how should I bootstrap a gcc
> aga
