From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13576] Issues compiling buildroot for 5x86
Date: Wed, 10 Mar 2021 19:46:16 +0000 [thread overview]
Message-ID: <bug-13576-163-6eaJ0A4lbl@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13576-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13576
--- Comment #9 from ingineru_de_sistem at yahoo.com ---
(In reply to Peter Seiderer from comment #7)
About the grub issue:
For an older project of mine (reviving an old AMD Sempron laptop where the
original hdd had unrecoverable bad sectors), I tried Lubuntu 18.04 LTS with an
IDE44pin-to-SDCard convertor with a fairly new micro-SD card.
All went fine except for the part when booting it with grub would erase the
partition table at every boot from the hdd (well, sd-card+adapter).
After tons of Googling (can't remember the exact search terms) found that one
guy had replaced grub with lilo (which fortunately still comes as a Lubuntu
package at least in 18.04) and it worked. So I did the same (full install, add
the lilo package, purge grub, remove all grubby remnants, configure and run
lilo) and it worked fine.
For syslinux - if one wraps the linker in a shell file that adds
--allow-multiple-definition, all works fine. And it's even simpler than LILO
but it needs a FAT partition (no biggie), tested that one as well.
For the revival project at hand (ancient 32-bit 5*86 with an asterisk zap card)
I reused the ancient LILO which can load new kernels as well.
Still a lot to do (Asterisk+zaptel doesn't compile directly either from
buildroot on 586, GCC doesn't come at all with buildroot and GCC's
documentation is not very friendly as to what sources one needs to download to
do the whole bootstraping stuff) and since it's a pet low-priority project, it
will take a long while. If anything pops up in the mean time, I will let you
know.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-10 19:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 0:33 [Buildroot] [Bug 13576] New: Issues compiling buildroot for 5x86 bugzilla at busybox.net
2021-03-05 9:04 ` [Buildroot] [Bug 13576] " bugzilla at busybox.net
2021-03-05 22:35 ` bugzilla at busybox.net
2021-03-05 22:51 ` bugzilla at busybox.net
2021-03-05 23:29 ` bugzilla at busybox.net
2021-03-06 9:52 ` bugzilla at busybox.net
2021-03-06 11:31 ` bugzilla at busybox.net
2021-03-07 18:02 ` bugzilla at busybox.net
2021-03-07 18:12 ` bugzilla at busybox.net
2021-03-10 19:46 ` bugzilla at busybox.net [this message]
2021-03-10 19:50 ` bugzilla at busybox.net
2021-03-10 19:57 ` bugzilla at busybox.net
2021-03-10 22:47 ` bugzilla at busybox.net
2024-06-15 14:56 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13576-163-6eaJ0A4lbl@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox