Quote:
No, the patch was not required for me on my system. I wonder how that's related to compiling gcc since it only does some small changes to the *.texi files which will only generate some documentation.

What exactly was the bug that you received before applying above patch ?

Hi oGALAXYo

Thanks for the script it's very good.

It worked for me using Fedora 28, but I had also to apply <a href="https://osmocom.org/attachments/2798/patch-gcc46-texi.diff">this</a> patch, documented <a href=""https://osmocom.org/issues/1916>here</a> during gcc compilation. It was not required for you?

Quote:
Fedora has always been some sort of exception. But they are one of the leading distros with huge influence.

yes, thats what im referring to. it seems there is more coming, therefore i advise keeping eye on there.

note, its contribution of someone else and in many cases i may not be up to date or informed enough to dependably forward the infos.

what concerns fedora and other bleeding edge distros, this has been discussed as a potential issue when choosing build environment, to refrain to stable ones, as best solution. aros may not always be able to in incorporate each and every possibility and adopt to every potential constellation, i fear.

Quote:

Thanks for the feedback. What build system are you eyeing at ? CMake ?

For the documentation update: Are you referring to this change ?

https://github.com/ezrec/AROS-mirror/commit/26b3106e37077abc6febf02a6457054470d990ca

The binutils and gcc situation on Fedora is always kinda tricky because they have the key developers for these tools and usually jump to bleeding edge. Same applies for the glibc developers. This makes it hard for Fedora users to get things as big as AROS compiled properly. It is also not possible to easily downgrade to older versions because of the lifetime (release cycle) of the distribution. They even added binary signature to their recent two (or latest) Fedora (upcoming) releases. Means 28 or 29.

What's interesting here are the --enable-lto flags. How experimental are they ? They can give some performance boost on compiled executables.

But things seem to be compiling and working. I had to re-create and re-apply the grub2 patches by patching the patch provided...

as i said id keep an eye whats being reported and talked on that aros section of slack and on the commits, since there are changes of build system underway, just yesterday i forwarded a docummentation update.

Thanks!

I decided to create an own thread for this because I don't wanted to hijack the other thread that covered a different issue (which was the reason that this script was created at all).

In case you run a recent version of Fedora or similar rpm based distribution (RHEL, CentOS and maybe SUSE), then this script may help you in getting AROS compiled.

The script is capable in building two kind of AROS versions. Either a self running 64bit version or a self running 32bit version.

The script checks out AROS (abi_v1), contrib, ports, documentation and binaries from the SVN, configures it and then starts building it. You end up - if successful - getting a fully bootable ISO image, that you can run native or by virtual machine.

This script is an alternative option to the gimmearos.sh script that comes shipped with AROS itself. But it contains some on the go patches, that addresses some compile issues that I came along with. They are most likely related to *bleeding edge* compiler and linker tools bundles by Fedora or changes to packaging of the files.

Either way! Please issue "aros.sh" for an overview of the options or "aros.sh -i" for an info about the recent changes.

Normal compile options that I prefer using is:

aros.sh -a32 *or*
aros.sh -a64

The script downloads and builds everything in the directory that you are in at the time of execution.

Please report issues and suggestions below. If I find time, I may try covering the issues.

Attach file:

---

Link only for registered users