On Wed, Jun 4, 2014 at 4:18 PM, "René J.V. Bertin"
wrote:
>
> On Jun 04, 2014, at 20:21, Eric Gallager wrote:
>
> > Wow, that looks a lot simpler than I thought that it would be... I was
> expecting something like this would have to be fixed upstream by gcc,
> because that is how they handle the
On Jun 04, 2014, at 20:21, Eric Gallager wrote:
> Wow, that looks a lot simpler than I thought that it would be... I was
> expecting something like this would have to be fixed upstream by gcc, because
> that is how they handle the GNU vs. NeXT Objective C runtime issues, but if
> all it takes
Wow, that looks a lot simpler than I thought that it would be... I was
expecting something like this would have to be fixed upstream by gcc,
because that is how they handle the GNU vs. NeXT Objective C runtime
issues, but if all it takes in this case is this script, it seems like just
using this sc
Hi all,
A long long time ago I had started discussing (well, complaining
might be more appropriate :-) about the fact that I could no
longer use g++ to compile my project, because Boost.Python was
compiled with clang++'s libc++.
Well, since then I managed to wrap a dirty script, g++-libc++,
which
