AROS Vanilla x86-64

[miker1264]

miker should you need it, my version of AROS One v11 Hosted Linux works fine, to run it you just need to run the  file "AROSBootstrap"

Could you send me a PM with a download link?

I would like to try it.

Now I have my Build System (cross compiler) setup in Ubuntu 20.04 on the same VM as my Test System for ABIv11. That makes things so much easier and quicker.

The beauty of Ubuntu on VMWare is that I can simply drag-n-drop directly to and from Windows into the VM. I can use the Linux File Manager to quickly move files around and editing in VS Code then dropping it into Linux is a breeze!

I have lots of compiling to do. 

[AMIGASYSTEM]

I will compress the folder and attach you AROS One 64 v11, I can also attach it here, maybe it can be useful to other users.

Question, I tried to compileu V11 your source "IconClone_02-03-23.c", I didn't get any error, but if I try to run "IconClone", I get the message "file not executable", where I am wrong ?

[miker1264]

I will compress the folder and attach you AROS One 64 v11, I can also attach it here, maybe it can be useful to other users.

Question, I tried to compileu V11 your source "IconClone_02-03-23.c", I didn't get any error, but if I try to run "IconClone", I get the message "file not executable", where I am wrong ?

Me too. I thought gcc was broken. 

So I compiled it with the Build System and it works fine. I will post the ABIv11 version & upload it to AROS Archives.

The shell version of gcc on x86-64 still has some issues.

But for really small source files it may be ok.

If you provide a download link I would like to try your x86-64.

[AMIGASYSTEM]

As soon as I finish uploading to Google Drive I will attach here the link of AROS One 64 Hosted Linux.

However I don't think the problem is the AROS 64 v11 GCC, I tried to compile "IconClone_02-03-23.c" also on AROS One ABIv0 and I get the same error "file not executable"

I suppose there is something in your source that is not supported by the AROS GCC, or some component is missing or needs to be replaced in "Development"

[miker1264]

As soon as I finish uploading to Google Drive I will attach here the link of AROS One 64 Hosted Linux.

However I don't think the problem is the AROS 64 v11 GCC, I tried to compile "IconClone_02-03-23.c" also on AROS One ABIv0 and I get the same error "file not executable"

I suppose there is something in your source that is not supported by the AROS GCC, or some component is missing or needs to be replaced in "Development"

I compiled IconClone_02-18-23.c with gcc in IcarosDesktop x86. It compiled and worked fine on AROS One x86.

But maybe there is something in it that isn't compatible with other gcc installations. I will try to investigate the issue.

[AMIGASYSTEM]

Have you used the GCC AROS ? what is Build System ?

[miker1264]

Have you used the GCC AROS ? what is Build System ?

The Build System is the gcc cross compiler on Ubuntu. It compiles AROS source code using Linux tools. That's the easiest way to compile complex programs like MultiView, LunaPaint, FileMaster & others. It can do small apps also.

The Build System is a larger version of gcc in a shell. It's what the AROS server uses to compile AROS. It's what deadwood uses to compile his new releases for AROS.

[AMIGASYSTEM]

On what version of Icaros what version of GCC did you use to compile, I would like to do some verification

[miker1264]

On what version of Icaros what version of GCC did you use to compile, I would like to do some verification

It was IcarosDesktop 2.2.8 x86. Using gcc in a shell. IcarosDesktop uses Magellan. Not sure if that is a factor.

[AMIGASYSTEM]

I don't think it depends on Magellan, but on a different version of GCC, IcarosDesktop 2.2.8 surely has an old version of GCC, Icaros 2.3 included GCC v4.6.4

[miker1264]

I don't think it depends on Magellan, but on a different version of GCC, IcarosDesktop 2.2.8 surely has an old version of GCC, Icaros 2.3 included GCC v4.6.4

I was using IcarosDesktop 2.2.8 Hosted on Linux.

I believe the Build System for ABIv11 uses gcc 6.5.0 also. I don't believe the gcc version has much to do with the issue.

It may be an issue with x86 Native vs Hosted just like ABIv11 Native & Hosted for gcc. One works & one doesn't.

Maybe if you copy the Development directory from Icaros 2.2.8 directly into one of your AROS One x86 test system you can test the older gcc in a shell. If it does not work then something else is wrong. If it does work then newer gcc has issues with Native vs. Hosted & x86 vs x86-64.

By simple comparison the startup-sequence is different on Icaros than it is on ABIv11.  The Package-Startup on Icaros does not include the assigns for Development directory. Those are located in Startup-sequence near the bottom. On ABIv11 the assign for Development is in Package-Startup.

One last thing then you can do your testing. The difference between a simple source code file & a complex one is not the lines of code or the size in kb. It is the number of includes. For example IconSplit uses no libraries other than studio.h, string.h & the other std library. It has 1500 lines of code but it compiles easily & it works. IconClone however has several system libraries such as IFFParse, Cybergfx, Datatypes, DOS, Exec, Icon & a few others. Maybe gcc has a problem finding the resources the application needs to run.

[AMIGASYSTEM]

I don't think it's a Hosted version problem, since the GCC of v11 hosted Linux gives the same error on your IconClone source, I ask deadwood to do a check to see where the problem lies.

[Amiwell]

Miker Odyssey could be the first application to work on for porting

[miker1264]

I don't think it's a Hosted version problem, since the GCC of v11 hosted Linux gives the same error on your IconClone source, I ask deadwood to do a check to see where the problem lies.

I can't seem to identify the problem with gcc in the shell not working correctly for every source code file. Some work and some don't.

Until it works perfectly I will use the Build System to compile x86-64 binaries. Here are a few small programs. IconClone (without icon), InfoInfo (cli only), & IconSplit (cli only).

InfoInfo reads an Amiga Classic Icon & gives information in the shell. IconSplit with split an Amiga Classic Icon & save ILBM images in Ram Disk. We know what IconClone does.

[Amiwell]

thanks