Re: AROS SDK ABI v0, current status [Development (General)]

Forum Index

Board index » Development » Development (General) » AROS SDK ABI v0, current status

Browsing this Thread: 1 Anonymous Users

Bottom

Previous Topic

Next Topic Register To Post

« 1 (2)

jman

Re: AROS SDK ABI v0, current status

Home away from home

Quote:

deadwood wrote:
First wild guess would be to build outside of source tree. That is how I build it always.

Fantastic, it worked

Also, I had to install package libc-dev-i386, because I was missing stub-32.h header.
Ok, so for future reference the revised list of needed Ubuntu/Debian packages should be:

sudo apt-get install build-essential git automake autoconf netpbm python libc-dev-i386

Thanks

Posted on: 2016/1/17 22:26

deadwood

Re: AROS SDK ABI v0, current status

Home away from home

I don't recall seeing such problems before. What distro of Linux are you using? Is it 32 or 64 bit?

First wild guess would be to build outside of source tree. That is how I build it always.


Make a clear clone (building inside leaves trash) and execute:[code

$ mkdir somedir

$ ./../AROS/configure --target=linux-i386

$ make

Posted on: 2016/1/16 7:28

Krzysztof

"There is no such thing as software for free. If it is not the user who covers the cost of software creation with money, it is the developer who covers this cost with his own free time."

www.aros3d.org
www.twitter.com/ddeadwood

jman

Re: AROS SDK ABI v0, current status

Home away from home

Thanks for the answers, I could finally test a compilation but it fails here:


Compiling  asm.c...

asm.c: In function ?main?:

asm.c:44:5: error: ?size_t? undeclared (first use in this function)

asm.c:44:5: note: each undeclared identifier is reported only once for each function it appears in

mmakefile:92: recipe for target '/home/jman/aros/AROS-mirror/AROS/bin/linux-i386/gen/compiler/include/asm.s' failed

make[1]: *** [/home/jman/aros/AROS-mirror/AROS/bin/linux-i386/gen/compiler/include/asm.s] Error 1

[MMAKE] make --no-print-directory TOP=/home/jman/aros/AROS-mirror/AROS SRCDIR=/home/jman/aros/AROS-mirror/AROS CURDIR=compiler/include TARGET=includes-asm_h-i386 --file=mmakefile includes-asm_h-i386 failed: 512

[MMAKE] Error: Error while running make in compiler/include: No such file or directory

Makefile:53: recipe for target 'crosstools' failed

make: *** [crosstools] Error 10

here's what I did:


$ git clone https://github.com/ezrec/AROS-mirror.git

$ cd AROS-mirror

$ git checkout ABI_V0-on-trunk-20141231

$ cd AROS

$ ./configure --target=linux-i386

$ make

any idea?

EDIT: the compilation succeeds if I'm on branch ABI_V1

thanks

Posted on: 2016/1/15 22:56

deadwood

Re: AROS SDK ABI v0, current status

Home away from home

Quote:

jman wrote:

yes, one can build the tools and the includes files like you mention (i.e. compiling AROS from scratch) and that's how I always did before.
However I was wondering if the SDK distribution (packaged as AROS-YYYYMMDD-pc-i386-sdk.tar.bz2) was of any use, but I still notice a lot of missing files:

# dir created by SDK package
$ find /usr/local/aros-sdk/i386-aros/include/ | wc -l
1661

# dir created by compiling AROS sources
$ find AROS-20160109-source/bin/pc-i386/AROS/Development/include/ | wc -l
1718

I want to compile my hello world to check whether my dev environment is ok again.

Maybe the SDK distribution is not for what I thought it was (i.e. third party development)? If not, what is it for?

It is indeed for what you mentioned, but it is not maintained in a long it. It also still assumes using fake cross compiler. I know it is a shame we don't have this cleaned up :(

Quote:

jman wrote:
Also, is it still ok to compile AROS with "--target=pc-i386" in order to create the crosstools vor ABIv0?

Yes, but you need to be using this branch: ABI_V0-on-trunk-20141231

You now get read crosscompiler for C and C++

Quote:

jman wrote:
And finally: why the header "rt.h" is not generated anymore when I compile the crosstools from AROS sources?

This was removed as it was basically used in only one program in AROS. It was an old experiment that never took off.

Posted on: 2016/1/12 20:10

jman

Re: AROS SDK ABI v0, current status

Home away from home

Quote:

deadwood wrote:
Hi jman,

Can you explain what you mean by "SDK is not yet fixed and a lot of files are missing"? If you compile AROS from source you will not only get the includes but a working cross compiler as well. This is how I get the SDK for me.

yes, one can build the tools and the includes files like you mention (i.e. compiling AROS from scratch) and that's how I always did before.
However I was wondering if the SDK distribution (packaged as AROS-YYYYMMDD-pc-i386-sdk.tar.bz2) was of any use, but I still notice a lot of missing files:

# dir created by SDK package
$ find /usr/local/aros-sdk/i386-aros/include/ | wc -l
1661

# dir created by compiling AROS sources
$ find AROS-20160109-source/bin/pc-i386/AROS/Development/include/ | wc -l
1718

I want to compile my hello world to check whether my dev environment is ok again.

Maybe the SDK distribution is not for what I thought it was (i.e. third party development)? If not, what is it for?

Also, is it still ok to compile AROS with "--target=pc-i386" in order to create the crosstools vor ABIv0?

And finally: why the header "rt.h" is not generated anymore when I compile the crosstools from AROS sources?

Thanks

Posted on: 2016/1/11 23:53

deadwood

Re: AROS SDK ABI v0, current status

Home away from home

Hi jman,

Can you explain what you mean by "SDK is not yet fixed and a lot of files are missing"? If you compile AROS from source you will not only get the includes but a working cross compiler as well. This is how I get the SDK for me.

Posted on: 2016/1/11 6:06

jman

AROS SDK ABI v0, current status

Home away from home

hello,

after a long hiatus, I'm toying myself with the idea of getting in touch with AROS development again.

Since the "pc-i386-sdk" wasn't complete, in order to have a fully working AROS sdk last time I had to:
1) Download AROS sources
2) compile (and wait)
3) the SDK includes are available in "AROS-YYYYMMDD-source/bin/pc-i386/AROS/Development/include"

Apparently this situation seems unchanged, the SDK is not yet fixed and a lot of files are missing.

Is that correct or am I missing something?

Moreover the SDK is i386 only so imo the check in AROS-SDK-Install script about the CPU arch of the gcc available ($cc_cpu) isn't needed.

Thanks

Posted on: 2016/1/10 22:33