Browsing this Thread:
1 Anonymous Users
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Not too shy to talk
 
|
Quote:
Yep. I had to sed lines 4 to 47 or so from the diff and changed the linefeeds. Quote: perhaps thats the reason why your build broke. Yes exactly that was the reason. Yesterdays checkout didn't have that issue. Quote: but for what i see todays nightlies compiled fine, so it must have been resolved. I haven't updated yet. My last checkout is 3-4 hours ago. The thing is: So much has changed within the 14 years that I last compiled AROS from source. Every now and then - over the years - I ended up grabbing one nightly ISO that I ran in qemu. Just playing with the demos like Flamme, Tunnel, Fire etc. The past couple of days is basicly the first time (when I first started solving the Fedora 29 compile issues) that I compiled AROS from sources again. All I can say so far is: "Where to start ? I need months to find a path here". So much has changed. So much got added. AROS matured. What you people have here is a gold mine of an OS.
Posted on: 2018/9/16 20:38
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
Quote:
as you may have noticed in another thread, yannick sources fetched from his repo for ports/contribs has had changed line ending convention which resulted in pathes not being applied. perhaps thats the reason why your build broke. things like that happen time to time. but for what i see todays nightlies compiled fine, so it must have been resolved.
Posted on: 2018/9/16 20:27
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
What I noticed so far with Fedora 29 (x86_64) is this:
When I build AROS (V1) together with contrib, ports and so on, then I usually run make, make contrib, make ports, make distfiles. In the morning I wake up and receive an ISO image that only contains around ~200mb of files. I was quite irritated that stuff, that I recognized that should be there, were missing. The past 2 days I've been working on extending my buildscript (the one linked some pages before) and noticed that a few things were not compiling. AROS usually compiles through. But contrib and ports break half apart. This leads to the fact that the resulting ISO image was missing plenty of things. Sometimes files can't be grabbed from the internet because of stale sites or sites are down. I (works for me TM) was able to cover all the build fail issues that I found - and managed that, AROS, contrib and ports are compiling without any errors (as of SVN from today). Again: On my system :) The script got also extended in a way that, in case of a stale or down site that the script retries building (and re-grabbing the stuff). After compiling I ended up in a roughly ~12gb AROS directoy (where I compile in) and an AROS bin dir that is around ~1.8gb in size. I believe, once make distfiles ends up creating an ISO image, that the ISO will be around the same size (still waiting for the process to finish). (deleted: look at the latest in further comments)
Posted on: 2018/9/16 20:14
Edited by oGALAXYo on 2018/9/18 18:03:06
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Home away from home
|
as i already said you can at least propose patches. myself i am probably supposed to break even more, if let loose without oversight. therefore im relying on educated opinion.
Posted on: 2018/9/15 16:24
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Home away from home
|
as i already said you can at least propose patches. myself i am probably supposed to break even more, if let loose without oversight. therefore im relying on educated opinion.
Posted on: 2018/9/15 16:24
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Quote:
I think I will blow up more than I would fix :) I had access to CVS/SVN around 14 years ago but asked Aaron to close it down. Quote:
There is another issue if you want to correctly compile "contrib" including all the compiler stuff under Fedora 29 (maybe other newer distros as well). The program icu4c fails building. I already covered that issue in a patch and will provide an updated version of my build script that includes this patch once I ran through a couple of tests. Compiling takes ages here and a shitload of changes happened over the past 14 years. Some of the informations online is not aligned to the actual situation within the code anymore.
Posted on: 2018/9/15 12:52
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Hello, Sorry for my very late respond. I had to do a totally new Linux installation due to other issues (I've done more sudoing than understanding...) You should really get the svn access and join the effort IMHO. Thanks for looking into the issue!
Posted on: 2018/8/24 14:03
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Ok I think I was able to catch all build issues related to Fedora 28/29/...
1) The libc.a issue. Even if the default installation of Fedora installs a libc_nonshared.a, then copying libc_nonshared.a to bin/pc-i386/gen/lib as libc.a indeed helps but is not the right solution. The right solution would be to dnf install glibc-static.i686 (as well as glibc-static for x86_64). They don't interfer each other and also provide a correct version of libc.a in /lib/ and /lib64/. I have tested this (... and that's what took me so long to respond. My hardware isn't the fastest and compiling takes most of the time). 2) The grub2 issues. The grub2 issues are in reality 3 different issues. 2 of them I already covered earlier. a) The issue with missing symbols after linking because include files were missing. The new host glib2 (as explained earlier) stripped out some stuff in new headerfiles. b) The alignment of structures that cause the grub2 build to fail. Grub2 in Aros seem to be slightly outdated and hasn't received all the necessary changes to fit actual Linux systems. The changes - 3 actually - are added in the patch. c) As explained one comment earlier. When compiling the x86_64 version of Aros, I received following error (which doesn't happen with the 32bit build) ../grub-mkimage: error: relocation 0x4 is not implemented yet. make[1]: *** [mmakefile:801: grub2-efi-iso-setup] Error 1 The fix that I pointed at at savannah was indeed right. I was only to tired to properly apply it. This has been covered now and the patch works. I gave everything another night and had AROS and the iso files build for pc-i386 and pc-x86_64. The compilation finished early this morning and I received 2 iso files. Both are working. No compiling or linking issues. I also updated my own buildscript that I created during this process and I like to leave it that way until something new appeared. The buildscript also includes the patch (base64 encoded, so I can encapsulate it in the buildscript). The patch will of course be applied and saved as real readable textfile and everyone can verify its contents). Hope I could help those using Fedora or similar RPM based actual distros from being able to build Aros again. Please find the buildscript attached to this comment. (deleted: look at the latest in further comments)
Posted on: 2018/8/21 8:50
Edited by oGALAXYo on 2018/9/18 18:02:14
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Compiling Aros 64bit seem to work but compiling grub2 for 64bit ended up with this:
../grub-mkimage: error: relocation 0x4 is not implemented yet. make[1]: *** [mmakefile:801: grub2-efi-iso-setup] Error 1 Quick google leads to binutils changes of the host system that causes grub2 issues: https://patchwork.openembedded.org/patch/152725/ Close at the bottom the fix... http://git.savannah.gnu.org/cgit/grub.git/commit/util?id=842c390469e2c2e10b5aa36700324cd3bde25875 Edit: Applied first part of above patch from savannah and gave it a shot. Same issues... Did not work... Going to bed now :)
Posted on: 2018/8/18 21:02
Edited by oGALAXYo on 2018/8/18 21:23:49
|
|||
|
||||
|
Re: Unable to link i386 bootstrap on Fedora 28
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Sure... I only tested this on my environment which is the upcoming version of Fedora 29. But since someone else had the same issues on Fedora 28, this then caught my attention.
If there is another solution then go for it. But from what I saw only gcc get's bootstrapped and glibc (from what I figured out quickly) doesn't. So it relies on the hosts glibc or the crosscompiled glibc of the host system. Therefore you rely on an ongoing changing glibc version which - from what I am aware of - stripped some symbols out to other include files as the ones that are in my patch. I saw someone on the net that some other distros (Linux ones) solved this by altering the configure file, so the correct includes can be found. #ifdef'ing the *.c or *.h files. A qick google lead me to this: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1722955 The grub2 build perfectly here and the iso was generated and ran without issues under qemu...
Posted on: 2018/8/18 20:36
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
