From: Kai Peter <kp@lists.openqmail.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
Date: Thu, 07 Dec 2017 13:04:08 +0100 [thread overview]
Message-ID: <ecdf2071574f873405215ad3d11019e7@lists.gentoo.org> (raw)
In-Reply-To: <2212379.l0OfTGrFQ4@peak>
On 2017-12-06 13:28, Peter Humphrey wrote:
> On Sunday, 3 December 2017 15:12:21 GMT Mick wrote:
>> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
>> > On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
>> > > I'm getting this error after I changed my profile as per
>> > > '2017-11-30-new-17-
>> > >
>> > > profiles' news item:
>> > > >>> Compiling source in
>> > > >>> /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
>> >
>> > [...]
>> >
>> > > However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
>> > > (mostly) stable system. This may save time for others who come across
>> > > the same problem.
>> > sys-boot/grub-0.97-r17
>> > It has. Thanks Mick.
>>
>> Unfortunately, an older system with only 50MB /boot partition did not
>> have enough space to allow sys-boot/grub-0.97-r17 to install all its
>> files and fs drivers. I ended up restoring /boot from a back up.
>> YMMV.
>
> I spoke too soon, too. Sys-boot/grub-0.97-r17 compiled and installed
> all
> right, as a package, but when I went to install it to the MBR I got an
> error
> complaining of a mismatch or corruption in stage X. The wording was
> something like that, and I forget the value of X. There was no mention
> of
> disk space, and the boot partition is 2GB, so I think it's something
> else.
>
> Installing sys-boot/grub-static-0.97-r12 instead went smoothly, so I've
> left
> it like that for the moment.
>
> Does the team think I should go back to grub-0.97-r17, take proper
> records
> and file a bug report?
I question if this makes sense for a masked ebuild.
I'm curious about what was discussed until now. The issue seems to be
quite simple to solve.
The build fails but portage/gcc does give clear info in this case: the
option "-nopie" have to be changed to "-no-pie". This option is set in
860_all_grub-0.97-pie.patch. Here is a diff:
--- a/860_all_grub-0.97-pie.patch 2012-05-31 01:00:13.000000000
+0200
+++ b/860_all_grub-0.97-pie.patch 2017-12-07 11:28:57.536089642
+0100
@@ -17,8 +17,8 @@
+ grub_cv_cc_fpie=no)
+ ])
+ if test "x$grub_cv_cc_fpie" = xyes; then
-+ STAGE1_CFLAGS="$STAGE1_CFLAGS -nopie"
-+ STAGE2_CFLAGS="$STAGE2_CFLAGS -nopie"
++ STAGE1_CFLAGS="$STAGE1_CFLAGS -no-pie"
++ STAGE2_CFLAGS="$STAGE2_CFLAGS -no-pie"
+ fi
fi
fi
Maybe the easiest way is to create a new grub-patches package, but there
are other ways to change this too. I'm expected the upstream will change
this soon - within the remaining 5 weeks ;-).
Another thing is I question that grub-legacy have to be rebuild at all.
I'm pretty sure it is save to remove it from the world file or comment
it out.
Anyhow, upgrading to grub2 is IMHO the right way. There are some
examples given in parallel threads how to write a grub.cfg by hand - and
keep it simple :-). Then nothing else then the grub2 binary and
grub2-install is required usually.
Kai
--
Sent with eQmail-1.10
next prev parent reply other threads:[~2017-12-07 12:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 12:30 [gentoo-user] grub-0.97-r16 and profile 17.0 change Mick
2017-12-02 21:28 ` [gentoo-user] " Ian Zimmerman
2017-12-02 23:28 ` Mick
2017-12-03 2:11 ` Adam Carter
2017-12-02 23:33 ` Michael Orlitzky
2017-12-03 1:07 ` Heiko Baums
2017-12-03 1:14 ` Michael Orlitzky
2017-12-03 2:18 ` Ian Zimmerman
2017-12-03 2:27 ` Michael Orlitzky
2017-12-03 10:57 ` [gentoo-user] " Peter Humphrey
2017-12-03 15:12 ` Mick
2017-12-05 1:54 ` Daniel Frey
2017-12-05 2:13 ` Daniel Frey
2017-12-05 2:15 ` Michael Orlitzky
2017-12-05 3:39 ` Daniel Frey
2017-12-05 10:15 ` Peter Humphrey
2017-12-05 10:44 ` Tom H
2017-12-05 7:06 ` [gentoo-user] " Ian Zimmerman
2017-12-05 2:20 ` [gentoo-user] " wabe
2017-12-05 10:11 ` Mick
2017-12-05 10:21 ` Raffaele Belardi
2017-12-05 12:48 ` Mick
2017-12-06 1:58 ` wabe
2017-12-06 12:28 ` Peter Humphrey
2017-12-07 12:04 ` Kai Peter [this message]
2017-12-07 14:22 ` Peter Humphrey
2017-12-07 15:06 ` Helmut Jarausch
2017-12-07 16:51 ` Kai Peter
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=ecdf2071574f873405215ad3d11019e7@lists.gentoo.org \
--to=kp@lists.openqmail.org \
--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