Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 588112 - Compilation failure - same result on x86 and amd64 installs while using Gentoo Livecd 2014 as install environment
Summary: Compilation failure - same result on x86 and amd64 installs while using Gento...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-05 22:23 UTC by John Stein
Modified: 2016-07-09 04:34 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
compiler output (compileOutput,513 bytes, text/plain)
2016-07-06 17:22 UTC, John Stein
Details
First gentoo-sources log. Two were created for the same build. (genSourceBuildLogPart1.tar.gz,630.65 KB, application/gzip)
2016-07-06 17:56 UTC, John Stein
Details
Second part of log (genSourceBuildLogPart2.tar.gz,304.27 KB, application/gzip)
2016-07-06 17:57 UTC, John Stein
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Stein 2016-07-05 22:23:59 UTC
Failure occurs very soon after compilation begins with the first error of:
"bin/sh: bc: command not found" followed by:
"Kbuild:66: recipe for target 'include/generated/timeconst.h' failed", etc.

* Log is attached.

* I've tried first with x86 install while using my 64 bit cpu and the x86 tarball  and # make && make modules_install but same error.

* Next I tried an x86_64 install along with the appropriate tarball - same error.

* Tried changing the kernel .config to a default config using # make defconfig - same error.

* All the above install cases used a Funtoo host while installing.

* So next, I tried using Gentoo Livecd 2014 install host but - same error.
Comment 1 Brian Evans (RETIRED) gentoo-dev 2016-07-06 12:39:13 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?
Comment 2 John Stein 2016-07-06 17:22:08 UTC
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?
Comment 3 Adam Feldman gentoo-dev 2016-07-06 17:28:01 UTC
(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
Comment 4 John Stein 2016-07-06 17:40:20 UTC
* 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.
Comment 5 John Stein 2016-07-06 17:56:29 UTC
Created attachment 439896 [details]
First gentoo-sources log. Two were created for the same build.
Comment 6 John Stein 2016-07-06 17:57:16 UTC
Created attachment 439898 [details]
Second part of log
Comment 7 Brian Evans (RETIRED) gentoo-dev 2016-07-06 18:06:42 UTC
You have USE="build" enabled on gentoo-sources and possibly globally.. don't do that.
Comment 8 Brian Evans (RETIRED) gentoo-dev 2016-07-06 18:08:20 UTC
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
Comment 9 John Stein 2016-07-09 04:34:56 UTC
(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