Summary: | Compilation failure - same result on x86 and amd64 installs while using Gentoo Livecd 2014 as install environment | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Stein <aksornsri1> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | grknight |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
compiler output
First gentoo-sources log. Two were created for the same build. Second part of log |
Description
John Stein
2016-07-05 22:23:59 UTC
'bc' command is required for a kernel compilation. How did you obtain these kernel sources? 'emerge gentoo-sources' normally pulls in sys-devel/bc as a requirement before the sources are installed. Where is this log you mention? Why is this in SELinux component? Created attachment 439894 [details]
compiler output
I could upload my sys-kernel/gentoo-sources emerge log but there is a 1MB limit and the two files generated are 7.7MB and 4.2MB.
Sorry about sending this to you; I guess it should have been Current Packages.
Should I resubmit or can you forward this?
(In reply to John Stein from comment #2) > Created attachment 439894 [details] > compiler output > > I could upload my sys-kernel/gentoo-sources emerge log but there is a 1MB > limit and the two files generated are 7.7MB and 4.2MB. > > Sorry about sending this to you; I guess it should have been Current > Packages. > Should I resubmit or can you forward this? You can compress the build.log and attach that * The gentoo-sources were obtained from your servers: GENTOO_MIRRORS="http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/" and through repos.conf/gentoo.conf usage I suppose. Created attachment 439896 [details]
First gentoo-sources log. Two were created for the same build.
Created attachment 439898 [details]
Second part of log
You have USE="build" enabled on gentoo-sources and possibly globally.. don't do that. reasoning: $ equery u gentoo-sources [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for sys-kernel/gentoo-sources-4.4.6: U I - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1] + + experimental : Apply experimental patches; for more information, see "https://wiki.gentoo.org/wiki/Project:Kernel/Experimental". - - kdbus : Apply the kdbus patch. This also requires the "experimental" use flag. - - symlink : Force kernel ebuilds to automatically update the /usr/src/linux symlink (In reply to Brian Evans from comment #8) > reasoning: > $ equery u gentoo-sources > [ Legend : U - final flag setting for installation] > [ : I - package is installed with flag ] > [ Colors : set, unset ] > * Found these USE flags for sys-kernel/gentoo-sources-4.4.6: > U I > - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, > used for creating build images and the first half of bootstrapping [make > stage1] > + + experimental : Apply experimental patches; for more information, see > "https://wiki.gentoo.org/wiki/Project:Kernel/Experimental". > - - kdbus : Apply the kdbus patch. This also requires the > "experimental" use flag. > - - symlink : Force kernel ebuilds to automatically update the > /usr/src/linux symlink Yes, that did the trick. Thank you so much for your help as it was very appreciated. Take care, John Stein |