AROS ABIv11 Release Thread

[deadwood]

I see the problem with undefined symbols. This is something that should not be happening. I think you are right and extraction from archive somehow damaged the file.

[AMIGASYSTEM]

You should try using a different compressor that is supported well by all platforms, perhaps RAR or ZIP would be a good solution.

[Amiwell]

amifox of marcus alb42 works fine

[deadwood]

That's good development

[AMIGASYSTEM]

deadwood, I would like to report that with AROS ABIv11 the Network does not work with VMware !

[deadwood]

deadwood, I would like to report that with AROS ABIv11 the Network does not work with VMware !

I understand, that's possible. If VMWare has emulation of different network devices, you can try to see if all the drivers fail.

[AMIGASYSTEM]

I have already tried the various network devices without success, but AROS Network Prefs side, should I set a Device other than PCNet32.device?

[Amiwell]

That's good development

yes is possible try to compile more application for this architecture, finally we works fine.

[deadwood]

I have already tried the various network devices without success, but AROS Network Prefs side, should I set a Device other than PCNet32.device?

Well, yes. On AROS side you need to set the device that matches the virtual hardware. Try e1000.device if you have Intel PRO/1000 set on VM side.

[AMIGASYSTEM]

With 1000.device Network Preferences crashes, the PC I use withVMware has a "Gigabit Intel(R) 82567LF-3" as the Network Card

[Amiwell]

currently with the alpha 3 version I have encountered problems with ahi and DiskImageGui

[AMIGASYSTEM]

I see the problem with undefined symbols. This is something that should not be happening. I think you are right and extraction from archive somehow damaged the file.

After doing some tests, I think the problem is in the x86 Build, I installed "AROS One + ABIv11 Host Linux", and the GCC worked fine, and the source compilation also worked correctly, see screenshot.

Then I used the "same Development folder" on x86 and got the usual error

[Amiwell]

ok amigasystem

[deadwood]

Then I used the "same Development folder" on x86 and got the usual error

That's quite possible. Which driver are you using in your native installation? ide.device or ahci.device?

[AMIGASYSTEM]

My Native test was done only on VMWare ! the error happens even if you run GCC from the ISO, without the need to install it.