Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 612506 - dev-libs/concurrencykit-0.6.0: fatal error: gnu/stubs-64.h: No such file or directory
Summary: dev-libs/concurrencykit-0.6.0: fatal error: gnu/stubs-64.h: No such file or d...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tomáš Mózes
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-13 15:06 UTC by Alexandr Tiurin
Modified: 2017-03-14 18:20 UTC (History)
1 user (show)

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


Attachments
buildlog (dev-libs:concurrencykit-0.6.0:20170313-145555.log,29.10 KB, text/plain)
2017-03-13 15:07 UTC, Alexandr Tiurin
Details
emerge --info concurrencykit (emergeInfo_conkurrencykit,5.48 KB, text/plain)
2017-03-13 15:08 UTC, Alexandr Tiurin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Tiurin 2017-03-13 15:06:31 UTC
/usr/include/gnu/stubs.h:10:27: fatal error: gnu/stubs-64.h: No such file or directory


Reproducible: Always
Comment 1 Alexandr Tiurin 2017-03-13 15:07:08 UTC
Created attachment 466886 [details]
buildlog
Comment 2 Alexandr Tiurin 2017-03-13 15:08:15 UTC
Created attachment 466890 [details]
emerge --info concurrencykit
Comment 3 Arfrever Frehtes Taifersar Arahesis 2017-03-14 05:29:43 UTC
# qfile -Sv /usr/include/gnu/stubs*
sys-libs/glibc-2.25:2.2 (/usr/include/gnu/stubs-32.h)
sys-libs/glibc-2.25:2.2 (/usr/include/gnu/stubs-64.h)
sys-libs/glibc-2.25:2.2 (/usr/include/gnu/stubs.h)

So rebuild sys-libs/glibc.
Comment 4 Tomáš Mózes 2017-03-14 05:52:50 UTC
Hello,
this seems weird - that is a virtual machine detected as x86_64 but not 
having 64 bit headers, because it seems the building toolchain is 32 
bit.

./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu
...
PROFILE = x86_64

Is this a 32 or 64 bit system? Why do you have both x86 and ~amd64 in 
ACCEPT_KEYWORDS?

Maybe try to re-emerge linux-headers / glibc and then try again. 
Honestly, never seen such system :)
Comment 5 Alexandr Tiurin 2017-03-14 11:36:23 UTC
Oh, my mistake. Needs to have a rest:)
Comment 6 Tomáš Mózes 2017-03-14 12:50:05 UTC
(In reply to Alexandr Tiurin from comment #5)
> Oh, my mistake. Needs to have a rest:)

If you don't mind, share the resolution so we can all learn.
Comment 7 Alexandr Tiurin 2017-03-14 18:20:05 UTC
My build environment is x86. I forgot about that and worked with the environment as x86_64, added ACCEPT_KEYWORDS="~amd64" and  linux64 chroot .