A1222 support in the SDK and problems

	Bottom Previous Topic Next Topic
Register To Post

« 1 2 (3)

FlynnTheAvatar

Re: A1222 support in the SDK and problems

Posted on: 6/29 13:45 #41

Just popping in

@Maijestro

The log file is in ffbuild/config.log.

That is not a standard location, normally it should be in the same directory where you ran configure.

Maijestro

Re: A1222 support in the SDK and problems

Posted on: 6/29 14:20 #42

Just can't stay away

@FlynnTheAvatar

Quote:

FlynnTheAvatar wrote:@Maijestro

The log file is in ffbuild/config.log.

That is not a standard location, normally it should be in the same directory where you ran configure.

Ok I tried again with version 6.1.1 of FFMPEG and get the following error message "Unknown OS 'amigaos'." probably I have to set a target.

But it doesn't matter at the moment as long as I can't build the compile with "SPE" optimizations at all. The normal compile would make no sense here as there is already a FFMPEG version 6.1.1 on Os4Depot.

log FFMPEG Build:


mktemp -u XXXXXX

configure[4590]: mktemp: not found

test_ld cc

test_cc

BEGIN /T/ffconf....1783026048/test.c

    1    int main(void){ return 0; }

END /T/ffconf....1783026048/test.c

gcc -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

gcc -o /T/ffconf....1783026048/test /T/ffconf....1783026048/test.o

check_cxxflags -std=c++11

test_cxx -std=c++11

BEGIN /T/ffconf....1783026048/test.cpp

    1    int x;

END /T/ffconf....1783026048/test.cpp

g++ -D_ISOC99_SOURCE -D__STDC_CONSTANT_MACROS -std=c++11 -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.cpp

test_cflags_cc -std=c11 ctype.h __STDC_VERSION__ >= 201112L

test_cc -std=c11

BEGIN /T/ffconf....1783026048/test.c

    1    #include <ctype.h>

    2    #if !(__STDC_VERSION__ >= 201112L)

    3    #error "unsatisfied condition: __STDC_VERSION__ >= 201112L"

    4    #endif

END /T/ffconf....1783026048/test.c

gcc -D_ISOC99_SOURCE -std=c11 -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

check_cppflags -D_FILE_OFFSET_BITS=64

test_cpp -D_FILE_OFFSET_BITS=64

BEGIN /T/ffconf....1783026048/test.c

    1    #include <stdlib.h>

END /T/ffconf....1783026048/test.c

gcc -D_ISOC99_SOURCE -std=c11 -D_FILE_OFFSET_BITS=64 -E -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

check_cppflags -D_LARGEFILE_SOURCE

test_cpp -D_LARGEFILE_SOURCE

BEGIN /T/ffconf....1783026048/test.c

    1    #include <stdlib.h>

END /T/ffconf....1783026048/test.c

gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -std=c11 -D_LARGEFILE_SOURCE -E -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

check_host_cflags -std=c99

test_host_cc -std=c99

BEGIN /T/ffconf....1783026048/test.c

    1    int x;

END /T/ffconf....1783026048/test.c

gcc -std=c99 -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

check_host_cflags -Wall

test_host_cc -Wall

BEGIN /T/ffconf....1783026048/test.c

    1    int x;

END /T/ffconf....1783026048/test.c

gcc -std=c99 -Wall -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

check_host_cflags -O3

test_host_cc -O3

BEGIN /T/ffconf....1783026048/test.c

    1    int x;

END /T/ffconf....1783026048/test.c

gcc -std=c99 -Wall -O3 -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

test_code cc  int test[2*(sizeof(void *) > 4) - 1]

test_cc

BEGIN /T/ffconf....1783026048/test.c

    1    int main(void) { int test[2*(sizeof(void *) > 4) - 1]; return 0; }

END /T/ffconf....1783026048/test.c

gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -std=c11 -c -o /T/ffconf....1783026048/test.o /T/ffconf....1783026048/test.c

/T/ffconf....1783026048/test.c: In function 'main':

/T/ffconf....1783026048/test.c:1:22: error: size of array 'test' is negative

 int main(void) { int test[2*(sizeof(void *) > 4) - 1]; return 0; }

                      ^~~~

Unknown OS 'amigaos'.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE

jabirulo

Re: A1222 support in the SDK and problems

Posted on: 6/29 16:16 #43

Just can't stay away

@Maijestro, but if you build "without SPE" it builds correctly?

if yes, the it's a matter to "find" the correct "switches/options". but no friggin' idea TBH.

Maijestro

Re: A1222 support in the SDK and problems

Posted on: 6/29 17:21 #44

Just can't stay away

@jabirulo

Quote:

jabirulo wrote:@Maijestro, but if you build "without SPE" it builds correctly?

if yes, the it's a matter to "find" the correct "switches/options". but no friggin' idea TBH.

Yes, I wanted to build it for testing purposes with a simple "./configure" without SPE optimized functions, but even that fails.

I'm also not sure if after ",/configure" further options like "-taget amigaos" or similar have to be specified.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE

LiveForIt

Re: A1222 support in the SDK and problems

Posted on: 6/29 18:19 #45

Home away from home

@Maijestro

Configure is Lnux sh script,
AmigaOS is barely an existing OS.
you might need to generate makefiles for linux
target or posix and modify the makefile and makefile.in etc script as needed.

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.

Maijestro

Re: A1222 support in the SDK and problems

Posted on: 6/29 20:34 #46

Just can't stay away

@all

Ok I give up, the best would probably be a cross compiler over Linux, but I only have the possibility to use MacOs, so I'm out for now.

If there is someone who could provide a clip4 version of FFMPEG including "SPE" optimization that would be excellent. If not it's ok and I'll use the things as they are available.

Thanks anyway everyone for the help.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE

jabirulo

Re: A1222 support in the SDK and problems

Posted on: 6/29 22:05 #47

Just can't stay away

@Maijestro
dont give up!!!
I know is a pita sometimes, but...

using crosscompiler (via docker or whatever):
./configure --host=ppc-amigaos --target=ppc-amigaos

https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=8122

smarkusg

Re: A1222 support in the SDK and problems

Posted on: 6/30 22:09 #48

Not too shy to talk

@Maijestro

Quote:

If there is someone who could provide a clip4 version of FFMPEG including "SPE" optimization that would be excellent. If not it's ok and I'll use the things as they are available.

I can build you ffplay under SPE with clib4 only with flags under CPU. I don't have access to the A1222 I am not able to make you other things under SPE and even check it.
The code generated under SPE will not work for me.

It is a pity that the A1222 has been announced for so many years, even some people had access to it and nobody was interested in its life after it was released.

arfcarl

Re: A1222 support in the SDK and problems

Posted on: 7/1 11:34 #49

Just popping in

@smarkusg

It’s released and sells a lot (multiple of tens, maybe hundreds). There’s definitely some interest.

flash

Re: A1222 support in the SDK and problems

Posted on: 7/1 13:08 #50

Just popping in

Someone has to release a new SDK with full support for A1222 to let new apps, and rebuild of the existing ones, to take advantage of new vector unit, reduce slow fpu emulation and avoid crashes/gurus/grim reapers.
I hope also to have full integration of afx clib in next release.

Memento audere semper!

Maijestro

Re: A1222 support in the SDK and problems

Posted on: 7/1 16:15 #51

Just can't stay away

@flash

Until recently I used AmigaOs4.1 exclusively on my MacStudio with Qemu and that was for almost 2 years before I bought the A1222. Many things work just as quickly as the experience I had with Qemu.

But of course there are also things that simply work worse, especially when they come into contact with emulation or software that is not compatible. Everything that is ported and used with Clib4 works really well.

I agree with you that a customized SDK for the A1222 will be essential, we should not forget that the A1222 may be the last PPC hardware released for AmigaOs4.1, so I think it is all the more important that the last platform should be supported, even if Tabor's actual call is unfounded. But like everything, it will take time, a lot of time....

So I accept things as they are and I knew there would be limitations anyway, but the box is still really fun.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE

Register To Post	« 1 2 (3)
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 3 ( 0 members and 3 Anonymous Users )