[gccsdk] Autobuilder libglib2.0-0

John Tytgat John.Tytgat at aaug.net
Tue Feb 4 15:20:14 PST 2014

In message <18f0e7d453.beeb at ron1954.woosh.co.nz>
          Ron <beeb at woosh.co.nz> wrote:

> I had a problem where libffi was not linking when trying to build
> libglib2.0-0
> After examining the make file I found plain native gcc was being
> used rather than arm-unknown-riscos-gcc.
> In the libglib2.0-0 setvars file I remarked out these lines.
> # build for local system to build local tools
> #make install
> #make clean
> And then libglib2.0-0 built successfully.
> Can someone explain the intention of the above or perhaps
> correct my misunderstanding.

In order to build libglib for RISC OS you need to have the glib-genmarshal
executable for your build machine.  That's why this gets first built
using your native gcc compiler and this gets then installed in
$GCCSDK_INSTALL_CROSS (where the RISC OS cross-compiler is installed).
After that the RISC OS libglib build will be done, at that point
glib-genmarshal is used.

That's on its own if perfectly fine.  Without further details I can't
see what your libffi problem would be.

John Tytgat, in his comfy chair at home
John.Tytgat at aaug.net

More information about the gcc mailing list