Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 644592 - sys-libs/libomp-4.0.1 pre-merge checks fails
Summary: sys-libs/libomp-4.0.1 pre-merge checks fails
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: 2018-01-14 20:48 UTC by Reimundo Heluani
Modified: 2018-01-16 16:26 UTC (History)
1 user (show)

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


Attachments
output of emerge --info (emerge-info.txt,5.17 KB, text/plain)
2018-01-14 20:48 UTC, Reimundo Heluani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Reimundo Heluani 2018-01-14 20:48:10 UTC
Created attachment 514816 [details]
output of emerge --info

Trying to emerge a world update. My kernel build is out of source 

KBUILD_OUTPUT=/var/kernel-builds/4.12.5

Get the following error: 
>>> Running pre-merge checks for sys-libs/libomp-4.0.1
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Could not find a Makefile in the kernel source directory.
 * Please ensure that /usr/src/linux points to a complete set of Linux sources
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Unable to calculate Linux Kernel version for build, attempting to use running version
/home/portage/eclass/linux-info.eclass: line 386: value = (2 << 16) + (4 << 8) +  : syntax error: operand expected (error token is "+  ")
 * The ebuild phase 'pretend' 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.
Comment 1 Reimundo Heluani 2018-01-14 22:47:08 UTC
Perhaps I should file this agains the linux-info eclass?
Comment 2 Reimundo Heluani 2018-01-14 23:55:12 UTC
I apologize for the noise, it was a bad link within my build directory to the wrong source directory.
Comment 3 Jonas Stein gentoo-dev 2018-01-16 16:26:44 UTC
ok I close then