From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cannot find LILO
Date: Sun, 04 Apr 2021 08:34:57 +0100 [thread overview]
Message-ID: <5700080.lOV4Wx5bFT@peak> (raw)
In-Reply-To: <CAJnmqwZRRVbg08t_hQ3mj12snERD6v3_=imBGH62KjHNYUEjWA@mail.gmail.com>
On Friday, 2 April 2021 17:29:25 BST konsolebox wrote:
> Your ARCH is set to i386 most likely. Maybe it's a CHOST configuration
> issue.
No, it isn't either of those. Nothing has changed between this kernel and
others. Oddly, 'make install' works if I chroot into this system from, e.g., a
rescue CD, just not natively.
I tried to install a new system, but some packages refuse to build so I've
restored the original system for now.
Still no idea what's wrong. Does anyone else suffer inexplicable things going
bump in the night at irregular intervals? My jaundiced eye is glaring at my
EFI BIOS, which I'm loath to tinker with.
--
Regards,
Peter.
next prev parent reply other threads:[~2021-04-04 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 13:37 [gentoo-user] Cannot find LILO Peter Humphrey
2021-04-02 16:29 ` konsolebox
2021-04-04 7:34 ` Peter Humphrey [this message]
2021-04-04 16:17 ` konsolebox
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=5700080.lOV4Wx5bFT@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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