I registered on the list, thank you for the link.

apparently there is irc, but ive never really been to it. except maybe when testing the client to be found in contribs/extras, which has the aros channel as default afair.

ive heard of people getteing their help there, though.

dev ml is not very lively at the moment:
https://mail.aros.org/mailman/listinfo/aros-dev
apparently good part of communication happens privately. but id try to register if i was you.

The build I try to do is natively on the RPi, on ARM, for the hosted ARM AROS on the same machine. It is just a hello world application using the provided SDK.

As mentioned, the missing libraries can be found in <tt>Development/lib</tt> in the contrib package.

In the app development doc I found that using <tt>-nostdlib</tt> can be used to skip auto including a lot of libraries. However, trying <tt>-nostdlib</tt> results in:

<code>
pi@retropie:~/projects/aros/helloworld $ arm-aros-gcc -nostdlib main.c
/usr/bin/ld: unrecognised emulation mode: armelf_aros
Supported emulations: armelf_linux_eabi armelfb_linux_eabi
</code>

The linker supports the mentioned two emulations and the specs file <tt>lib/gcc-lib/specs</tt> file in the SDK mentions:

<code>
*link:
-m armelf_linux_eabi -L/usr/local/aros-sdk/arm-aros/lib
</code>

The <tt>armelf_aros</tt> comes from inside the <tt>arm-aros/lib/gcc-lib/collect-aros</tt> binary.

The two supported ones should be native armelf variants, I suspect the first is for little endian and the second for big endian (due to the b). The one it is looking for (armelf_aros) is that something related to a cross compiler?

If I link with the libraries, I get a warning about <tt>wchar_t</tt> being used inconsistently:

<code>
pi@retropie:~/projects/aros/helloworld $ arm-aros-gcc -L ~/aros/AROS-20180820-linux-armhf-contrib/Development/lib main.c
/usr/bin/ld: warning: /tmp/cc0LmHZZ.o uses 4-byte wchar_t yet the output is to use 1-byte wchar_t; use of wchar_t values across objects may fail
/usr/bin/ld: unrecognised emulation mode: armelf_aros
Supported emulations: armelf_linux_eabi armelfb_linux_eabi
</code>

It seems that I will not get much further with the SDK I downloaded, so the next thing to do is to get the real source tree and look into the issues.

You mentioned a source development list, is that the best way to communicate, or is there some slow pace chat channel or similar too?

also generally if you want to do something constructive for aros, best is imho to leave abi v0 behind and work on trunk (abi v1). even though there arent v1 nightlies for arm target, perhaps it compiles, and if not it needs to be fixed. from there on michal, who will certainly work out of v1 might need some help.

Quote:
you ae building am on arm, ie no cross compilation?
best is you propose your patch on dev ml.
remember we need to keem cross compilation on different arch as an option.

Quote:

these libs will be built if you build aros in bin/"target"/AROS/Developer/lib

Quote:
if you surf over to www.aros.org there is a list of topics listed at your left side under documentation/developers. Click (and read) all the links (and the links listed therein etc) to get yourself more educated.

Alternatively use the wikibook link here on this site (look to the left of your screen when reading this post and click on "AROS dev Docs", then select your topic of choice).


Quote:
svn account, ask on developers mailinglist for details if unclear.

Quote:

Either you compile inside aros (hosted on linux if you prefer) or you do it on the host (or any other system for that matter).

In case _inside_ AROS you can setup development by adding files from contribute archive and make sure everything is in place (paths etc)

In case cross-compiling (which effectively your output is showing) you can use the gimmearos script (after you've installed the minimal build requirements manually on your linux box).


At least you're trying instead of bickering so :thumbsup:

To get more familiar with my AROS installation on the RPi I decided to install the SDK and build a hello world. Is there some documentation on how to do this?

First I downloaded the ARM ABI-v0 developer tools from nightly (<tt>linux-armhf-sdk</tt>), but AROS-SDK-install demands an x86 gcc, which I obviously do not have as I am on ARM.

So I fixed the script (two simple changes). How can I contribute this back in the best way? Can I open a pull request using git somewhere?

With a fresh SDK I typed in a hello world program and tried to build it, which resulted in:

<code>
pi@retropie:~/projects/aros/helloworld $ arm-aros-gcc main.c
/usr/bin/ld: cannot find -lposixc
/usr/bin/ld: cannot find -lstdcio
/usr/bin/ld: cannot find -lstdc
/usr/bin/ld: cannot find -lcodesets
/usr/bin/ld: cannot find -lkeymap
/usr/bin/ld: cannot find -lexpansion
/usr/bin/ld: cannot find -lcommodities
/usr/bin/ld: cannot find -ldiskfont
/usr/bin/ld: cannot find -lasl
/usr/bin/ld: cannot find -lmuimaster
/usr/bin/ld: cannot find -ldatatypes
/usr/bin/ld: cannot find -lcybergraphics
/usr/bin/ld: cannot find -lworkbench
/usr/bin/ld: cannot find -licon
/usr/bin/ld: cannot find -lintuition
/usr/bin/ld: cannot find -lgadtools
/usr/bin/ld: cannot find -llayers
/usr/bin/ld: cannot find -laros
/usr/bin/ld: cannot find -lpartition
/usr/bin/ld: cannot find -liffparse
/usr/bin/ld: cannot find -lgraphics
/usr/bin/ld: cannot find -llocale
/usr/bin/ld: cannot find -ldos
/usr/bin/ld: cannot find -lutility
/usr/bin/ld: cannot find -loop
/usr/bin/ld: cannot find -lexec
/usr/bin/ld: cannot find -lautoinit
</code>

Looking into <tt>/usr/local/aros-sdk/arm-aros/lib</tt> and the missing libraries are not there. What is present seems to come from <tt>arm/lib</tt> in the SDK archive, and then some gcc stuff.

Where can I find or how do I build the missing libraries?