Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 700746 - sys-fs/lxcfs fails emerge when cross compiling
Summary: sys-fs/lxcfs fails emerge when cross compiling
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Erik Mackdanz
Keywords: PATCH
Depends on:
Reported: 2019-11-20 04:20 UTC by Fergus Dall
Modified: 2019-11-20 13:10 UTC (History)
3 users (show)

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

Proposed patch (0001-sys-fs-lxcfs-Add-with-distro-gentoo-to-econf.patch,920 bytes, patch)
2019-11-20 04:37 UTC, Fergus Dall
Details | Diff
Proposed patch (with Signed-off-by line) (0001-sys-fs-lxcfs-Add-with-distro-gentoo-to-econf.patch,969 bytes, patch)
2019-11-20 04:45 UTC, Fergus Dall
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Fergus Dall 2019-11-20 04:20:04 UTC
Emerge fails during configure phase because the configure script tries to check the distribution it's running on, which is forbidden when cross-compiling. This can be fixed by adding "--with-distro=gentoo" to the econf command. I will attach a patch to this bug.

Reproducible: Always

Steps to Reproduce:
1. Set up a Chrome OS development environment, as per
2. Add the sys-fs/lxcfs to the overlay in //src/third-party/portage-stable
3. Run ./build_packaged --board tatl sys-fs/lxcfs
Actual Results:  
Emerging sys-fs/lxcfs fails during the configure phase with the following logs:

checking dependency style of x86_64-cros-linux-gnu-clang... (cached) none
checking for x86_64-cros-linux-gnu-clang option to accept ISO C99... none needed
checking for main in -lpthread... yes
checking pkg-config is at least version 0.9.0... yes
checking for FUSE... yes
checking for help2man... /usr/bin/help2man
checking host distribution... checking for /etc/redhat-release... configure: error: cannot check for file existence when cross compiling

I encountered this in the context of Chrome OS development, but the issue can probably be reproduced with a simpler set up
Comment 1 Fergus Dall 2019-11-20 04:37:15 UTC
Created attachment 596864 [details, diff]
Proposed patch
Comment 2 Fergus Dall 2019-11-20 04:45:51 UTC
Created attachment 596866 [details, diff]
Proposed patch (with Signed-off-by line)