[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mac OS X sscanf bug/feature?
From: |
Mike Miller |
Subject: |
Re: Mac OS X sscanf bug/feature? |
Date: |
Sun, 27 Mar 2016 09:35:01 -0700 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Sun, Mar 27, 2016 at 08:48:09 -0400, Ben Abbott wrote:
> Ok. Thanks. I’ve cc myself on the bug report.
You might also want to follow the upstream bug report.
https://llvm.org/bugs/show_bug.cgi?id=17782
I guess that some future version of libc++ will fix this. Until then, is
there a way for you to compile with Mac's clang compiler but with GCC's
libstdc++ instead of libc++? That works for me.
--
mike
- Mac OS X sscanf bug/feature?, Ben Abbott, 2016/03/26
- Re: Mac OS X sscanf bug/feature?, Doug Stewart, 2016/03/26
- Re: Mac OS X sscanf bug/feature?, Ben Abbott, 2016/03/26
- Re: Mac OS X sscanf bug/feature?, Mike Miller, 2016/03/26
- Re: Mac OS X sscanf bug/feature?, Ben Abbott, 2016/03/27
- Re: Mac OS X sscanf bug/feature?,
Mike Miller <=
- Re: Mac OS X sscanf bug/feature?, Ben Abbott, 2016/03/27
- Re: Mac OS X sscanf bug/feature?, Mike Miller, 2016/03/27
- Re: Mac OS X sscanf bug/feature?, Ben Abbott, 2016/03/27
- Re: Mac OS X sscanf bug/feature?, Mike Miller, 2016/03/27
- Re: Mac OS X sscanf bug/feature?, Ben Abbott, 2016/03/27
Re: Mac OS X sscanf bug/feature?, Carlo De Falco, 2016/03/27