> Since PPC does not have clang, it will be bitten by this issue.
PPC does not have this issue. Many details in the referenced harfbuzz ticket.
Ken
Hi,
On 8/14/19 3:05 PM, Ryan Schmidt wrote:
I tried building with clang-3.7 but it doesn't work, because the port wants
then to issue -stdlib=macports-libstdc++, which clang 3.7 does not understand.
We didn't backport that feature to clang-3.7? I wonder why we didn't.
Clang-3.9 is no more
Hi all,
On 8/14/19 4:58 PM, Kenneth F. Cunningham wrote:
On 2019-08-14, at 7:52 AM, Kenneth F. Cunningham wrote:
/System/Library/Frameworks/Security.framework/Headers/SecKeychain.h:102:46:
error: shift expression '(1853123693 << 8)' overflows [-fpermissive]
kSecAuthenticationTypeNTLM
On 2019-08-14, at 7:52 AM, Kenneth F. Cunningham wrote:
>> /System/Library/Frameworks/Security.framework/Headers/SecKeychain.h:102:46:
>> error: shift expression '(1853123693 << 8)' overflows [-fpermissive]
>> kSecAuthenticationTypeNTLM = AUTH_TYPE_FIX_ ('ntlm'),
>
> I have
> /System/Library/Frameworks/Security.framework/Headers/SecKeychain.h:102:46:
> error: shift expression '(1853123693 << 8)' overflows [-fpermissive]
> kSecAuthenticationTypeNTLM = AUTH_TYPE_FIX_ ('ntlm'),
I have fixed this error on several occasions previously -- I believe by
> > I tried building with clang-3.7 but it doesn't work, because the port wants
> > then to issue -stdlib=macports-libstdc++, which clang 3.7 does not
> > understand.
>
> We didn't backport that feature to clang-3.7? I wonder why we didn't.
The supporting technology for macports-libstdc++ did
On Wed, 14 Aug 2019 at 15:05, Ryan Schmidt wrote:
> On Aug 14, 2019, at 02:14, Riccardo Mottola wrote:
>
> > I tried building with clang-3.7 but it doesn't work, because the port wants
> > then to issue -stdlib=macports-libstdc++, which clang 3.7 does not
> > understand.
>
> We didn't backport
On Aug 14, 2019, at 02:14, Riccardo Mottola wrote:
> as a dependency, harfbuzz is being installed on my 10.5 64bit system.
>
> The default picked up compiler is gcc6 and I get the following errors. I ask,
> because I have seen this errors in other builds and even some of my own code,
> it
