In message <37d474d553...@hobbes.bass-software.com>
John Tytgat wrote:
> In message <44a0fbd453.b...@ron1954.woosh.co.nz>
> Ron wrote:
>
> > In message <4c62ebd453...@hobbes.bass-software.com>
> > John Tytgat wrote:
> >
> > > In message <18f0e7d453.b...@ron1954.w
In message <44a0fbd453.b...@ron1954.woosh.co.nz>
Ron wrote:
> In message <4c62ebd453...@hobbes.bass-software.com>
> John Tytgat wrote:
>
> > In message <18f0e7d453.b...@ron1954.woosh.co.nz>
> > Ron wrote:
> >
> > > I had a problem where libffi was not linking whe
In message <44a0fbd453.b...@ron1954.woosh.co.nz>
Ron wrote:
> In message <4c62ebd453...@hobbes.bass-software.com>
> John Tytgat wrote:
>
> > In message <18f0e7d453.b...@ron1954.woosh.co.nz>
> > Ron wrote:
> >
> > > I had a problem where libffi was not linking whe
In message <4c62ebd453...@hobbes.bass-software.com>
John Tytgat wrote:
> In message <18f0e7d453.b...@ron1954.woosh.co.nz>
> Ron 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 nat
In message <18f0e7d453.b...@ron1954.woosh.co.nz>
Ron 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 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=$H
