Yes, I know. We need a version for the gcc 9.2.0 version/branch, and the master 
one does not apply directly.

cheers Chris


> On 13 Oct 2019, at 5:30 pm, Jack Howarth <[email protected]> 
> wrote:
> 
> Chris,
>      FYI, this has already been committed upstream.
> 
> https://gcc.gnu.org/ml/gcc-cvs/2019-10/msg00148.html 
> <https://gcc.gnu.org/ml/gcc-cvs/2019-10/msg00148.html>
> 
>       Jack
> 
> On Sun, Oct 13, 2019 at 12:02 PM Chris Jones <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi,
> 
> Interesting thanks . Was wondering about something like this. Let me see 
> about porting it to the gcc9 build.
> 
> Chris
> 
>> On 13 Oct 2019, at 3:24 pm, Jack Howarth <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> 
>>    We might want to back port this patch into out gcc9 package in order to 
>> avoid hard coding the SDKROOT path in the compiler during the build.
>> 
>> [Darwin, committed] Pick up SDKROOT as the sysroot fallback. 
>> <https://gcc.gnu.org/ml/gcc-patches/2019-10/msg00251.html>
>> 
>>      Jack

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to