AROS 68k updates from ApollOS repository

[deadwood]

@Gundam

I'm not currently looking into specific binary compatibility issues for m68k. Probably best would be to approach Apollo OS team about this.

[AMIGASYSTEM]

@deadwood

However ApolloOS is another world, it doesn't use Wanderer, many system applications are not native AROS but OS3, they use their own KickStart.

Basically if you start ApolloOS with your ROM, the few remaining native AROS applications on ApolloOS don't work, they require the posixc.library and the stdc.library

[OlafS3]

That can you basically also say for my distribution, I also use not wanderer and many applications are OS3. The main branch also benefitted from bugfixes like the fix of the lowlevel library. The same is true in the other direction too of course.

[AMIGASYSTEM]

Yes, but this will increase incompatibility between systems and there will no longer be an AROS standard.

As I've said many times, if I'm going to use a system with old OS3 applications, it's better to use a native OS3, mixed systems lead nowhere and only create incompatibility, if you want to grow you have to cut out the past.

[OlafS3]

Yes, but this will increase incompatibility between systems and there will no longer be an AROS standard.

As I've said many times, if I'm going to use a system with old OS3 applications, it's better to use a native OS3, mixed systems lead nowhere and only create incompatibility, if you want to grow you have to cut out the past.

 

*sigh*

I am tired from the discussions outside now they start here too. Amiga the new religion 

let people do what they want. Simple as that

[AMIGASYSTEM]

I don't like to make controversy, I just said what "I" think, everyone is free to choose and say his thought!

I have my A4000/060 in my garage together with all my other Amigas, I have used them for 30 years, now it's time to grow up with AROS I just want to

[deadwood]

@deadwood

However ApolloOS is another world, it doesn't use Wanderer, many system applications are not native AROS but OS3, they use their own KickStart.

Basically if you start ApolloOS with your ROM, the few remaining native AROS applications on ApolloOS don't work, they require the posixc.library and the stdc.library

I directed Gundam to Apollo OS team, because I believe they have greater incentive to fix these kind of incompatibility issues. Once the fix is done, I will port it back to my repository so the benefit is there.

[AMIGASYSTEM]

Thanks, hopefully it will be solved, it's not the only OS3 software to have that problem on AROS 68k, AmigaAMP for example after playing an mp3 can't be closed! the latest version of AmigaAMP just ran sends  crashes WinUAE.

[Amiwell]

works on winuae but I can't on janus-uae

[Gundam]

@Deadwood:

When trying to run RexxMast (in contrib here: http://www.aros.org/nightly1.php), in YOUR aros 68k distribution, it says it requires posixc.library, but your aros68k distro does not have posixc.library.

You should compile rexxmast and regina.library without that dependancy, so that it can be used in your distribution.

[deadwood]

That's a good point. I made a note of that and will take care of this once I do major work with core targets. For the time being, you can copy missing libraries from the nightly you mentioned.

[AMIGASYSTEM]

@deadwood

As mentioned on another post, on Wanderer there are problems to run an application when using the CLI parameter in the Tooltype, in my opinion it is a very important problem.

In practice if you want to run an executable from icon with CLI parameter, the executable doesn't execute any parameters included in the config file.

To check the problem just run the application TKUnpacker.

TKUnpacker allows with a Click to automatically unzip an Archive, on OS3 when you click on an Archive file a request asks where to unzip the archive, on Wanderer instead the request asks the path of the Archive file, if executed you get the error Unknow format or file not found - Ram", practically the archive is not found!

I attach screenshots exhaustive, the problem should also be present on AROS x86

[deadwood]

In practice if you want to run an executable from icon with CLI parameter, the executable doesn't execute any parameters included in the config file.

What do you mean by "config file"? Can you be more specific what config file you are referring to and what is contains? I'm not familiar with functionality you described.

[AMIGASYSTEM]

TKUnpacker as soon as it runs looks for and executes its configuration file located in the ENV "TKUnpacker.config".

Wanderer doesn't seem to know how to interpret the script, on OS 3 everything works normally

This problem happened to me also with other applications that work from Workbench through the "CLI" parameter.

[deadwood]

Ok, bug report created: https://github.com/deadw00d/AROS/issues/64