Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 452586 Details for
Bug 599124
sys-boot/refind-0.10.4-r1 : /.../environment:line <snip>: -march=native -O2 -pipe: attempted assignment to non-variable (error token is "=native -O2 -pipe")
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
sys-boot:refind-0.10.4-r1:20161106-212337.log
sys-boot:refind-0.10.4-r1:20161106-212337.log (text/plain), 1.88 KB, created by
Toralf Förster
on 2016-11-07 12:20:09 UTC
(
hide
)
Description:
sys-boot:refind-0.10.4-r1:20161106-212337.log
Filename:
MIME Type:
Creator:
Toralf Förster
Created:
2016-11-07 12:20:09 UTC
Size:
1.88 KB
patch
obsolete
> * Package: sys-boot/refind-0.10.4-r1 > * Repository: gentoo > * Maintainer: wraeth@gentoo.org sveyret@gmail.com,proxy-maint@gentoo.org > * USE: abi_x86_64 amd64 custom-cflags elibc_glibc ext2 ext4 iso9660 kernel_linux userland_GNU > * FEATURES: preserve-libs sandbox userpriv usersandbox >>>> Unpacking source... >>>> Unpacking refind-src-0.10.4.tar.gz to /var/tmp/portage/sys-boot/refind-0.10.4-r1/work >>>> Source unpacked in /var/tmp/portage/sys-boot/refind-0.10.4-r1/work >>>> Preparing source in /var/tmp/portage/sys-boot/refind-0.10.4-r1/work/refind-0.10.4 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/sys-boot/refind-0.10.4-r1/work/refind-0.10.4 ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/sys-boot/refind-0.10.4-r1/work/refind-0.10.4 ... >/var/tmp/portage/sys-boot/refind-0.10.4-r1/temp/environment: line 2519: -march=native -O2 -pipe: attempted assignment to non-variable (error token is "=native -O2 -pipe") > * The ebuild phase 'compile' has exited unexpectedly. This type of > * behavior is known to be triggered by things such as failed variable > * assignments (bug #190128) or bad substitution errors (bug #200313). > * Normally, before exiting, bash should have displayed an error message > * above. If bash did not produce an error message above, it's possible > * that the ebuild has called `exit` when it should have called `die` > * instead. This behavior may also be triggered by a corrupt bash binary or > * a hardware problem such as memory or cpu malfunction. If the problem is > * not reproducible or it appears to occur randomly, then it is likely to > * be triggered by a hardware problem. If you suspect a hardware problem > * then you should try some basic hardware diagnostics such as memtest. > * Please do not report this as a bug unless it is consistently > * reproducible and you are sure that your bash binary and hardware are > * functioning properly.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 599124
:
452584
| 452586