Re: [gccsdk] OSLib cross-build fail

In message <20120601101010.GE4665@chiark.greenend.org.uk>
Theo Markettos <theo@markettos.org.uk> wrote:

> [...]
> I can see why this is happening; in AOF mode DefMod2 is compiling a command
> line that includes 'gcc' but that's picking up the system gcc not the cross
> compiler. It appears the paths from ro-make aren't getting through - if I
> change the DefMod2 source to call arm-riscos-unknown-gcc instead, it can't
> find it.
>
> I don't fully understand how passing through path variables works... any
> suggestions?

The AOF version OSLib is supposed to be built with GCCSDK 3.4.x as this
is an AOF based release. The ELF version OSLib should be built with
GCCSDK 4.x. Cfr. !OSLib/!Readme.

It is true that with GCCSDK 4.x you now can use AsAsm to assemble the
DefMod2 generated assembler files to AOF object files but you will be
missing the AOF library creation tool and also will be unable to compile
the C sources to AOF object files (OSLibSupport).

John.
--
John Tytgat, in his comfy chair at home BASS
John.Tytgat@aaug.net ARM powered, RISC OS driven

_______________________________________________
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