Summary: | sys-boot/grub-0.97-r12 compiled with sys-devel/gcc-4.7.3-r1 -msse2: crash at stage-1_5 and the system reboots in cycle | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Dubenetsky <ald> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ald, pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
Alex Dubenetsky
2013-10-05 10:04:20 UTC
Created attachment 360134 [details]
emerge --info
The last grub-0.97-r13 from slot 0 is also affected. The answer lies in the question here. This is (in a way) a dupe of bug 360513. Your CFLAGS don't make sense for a bootloader (frankly, if you can't rely just on march value, chances are there are other ebuilds that get broken with such). > Your CFLAGS don't make sense for a bootloader Actually, it does. To be exact - CPPFLAGS. I don't know if it's a feature - then ok. > (frankly, if you can't rely just on march value, chances are there are other ebuilds that get broken with such). Sorry, I don't quite understand what do you mean. If you talking about -march=native, it works for me for years. I added CPPFLAGS="-march=atom -pipe -g0" to /etc/portage/env/grub.conf. I feel like the bug is resolved and changing status so. |