[odb-users] GCC Headers on MacOS X

[Lukas Obermann]

Hi Boris,

thank you for the feedback. I have to admit that I was expecting that it
will not be that easy :)

I will try now to use the pre-built odb for windows, mac and linux and will
have to see if I need to compile it myself for ARM and Android, but at
least there I will have easier control over the gcc in the cross-compile
environment (I hope ;) )

Unfortunately for Mac I can not use homebrew or macports atm.

Thanks for now, I may get back later if needed ;)

Lukas


Boris Kolpackov <boris at codesynthesis.com> schrieb am Do., 22. Sep. 2016 um
03:18 Uhr:

> Hi Lukas,
>
> Lukas Obermann <obermann.lukas at gmail.com> writes:
>
> > I am trying to build ODB on a Mac. I am integrating it into a existing
> > build system, so I do want to avoid using the pre-built versions and get
> > the build running, as it will also be build on Windows and Linux (will
> test
> > those next).
>
> I must warn you, Windows will be really hard (as in "patching GCC" hard).
>
>
> > Executing a gcc --version gives me following:
> >
> > $ gcc --version
> > Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
> > --with-gxx-include-dir=/usr/include/c++/4.2.1
> > Apple LLVM version 7.3.0 (clang-703.0.31)
> > Target: x86_64-apple-darwin15.6.0
> > Thread model: posix
> > InstalledDir:
> >
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>
> This is actually not GCC, it is Apple's Clang pretending to be GCC.
>
> To build ODB from source on Mac OS you will need to build GCC with plugin
> support enabled (--enable-plugin configure option). You could also try
> GCC from homebrew though I am not sure if it's built with plugins enabled
> these days.
>
> Boris
>