Re: [gccsdk] Autobuilder libglib2.0-0

In message <4c62ebd453.Jo@hobbes.bass-software.com>
John Tytgat <John.Tytgat@aaug.net> wrote:

> In message <18f0e7d453.beeb@ron1954.woosh.co.nz>
> Ron <beeb@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
export LIBFFI-CFLAGS=-I/usr/include/i386-linux-gnu
export LIBFFI_LIBS=-L/usr/lib/i386-linux-gnu/libffi.so.6
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
the job.

> 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
libglib2.0-0 now
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
glib2.0_2.33.12+really2.32.4.orig.tar.xz
OK but not new versions.
My native linux will have latest versions of everything which
may be a complication.

Thanks Ron M.

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK