[gccsdk] Autobuilder libglib2.0-0
beeb at woosh.co.nz
Tue Feb 4 18:17:39 PST 2014
In message <4c62ebd453.Jo at hobbes.bass-software.com>
John Tytgat <John.Tytgat at aaug.net> wrote:
> 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
> > #CC=$HOST_CC CXX=$HOST_CXX ./configure --prefix=$GCCSDK_INSTALL_CROSS
> > #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).
By 'this' I assume you mean a whole native libglib2.0-0, that
appears to be what is happening anyway.
I improved things by using
first but further down run into more problems with ffi,
I assume at this point the Autobuilders libffi and headers
shouldn't be used, and could it be left out if the purpose is
only to get a glib-genmarshal executable? that would simplify
> After that the RISC OS libglib build will be done, at that point
> glib-genmarshal is used.
Thats odd, I wonder how I managed to build the RISC OS variant of
However, I'll concentrate on getting the native part finishing.
Originally it was not finding libffi, then the export lines helped.
The autobuilder package is patching version
OK but not new versions.
My native linux will have latest versions of everything which
may be a complication.
Thanks Ron M.
More information about the gcc