Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 934476 - sys-devel/crossdev: glibc fails to compile on arm64
Summary: sys-devel/crossdev: glibc fails to compile on arm64
Status: RESOLVED DUPLICATE of bug 932250
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: ARM64 Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-17 19:40 UTC by Steven Christenson
Modified: 2024-06-18 16:18 UTC (History)
1 user (show)

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


Attachments
Portage Info (cross-i486-unknown-linux-gnu-info.log,15.68 KB, text/plain)
2024-06-17 19:40 UTC, Steven Christenson
Details
Glibc build log (cross-i486-unknown-linux-gnu-glibc.log,4.13 KB, text/plain)
2024-06-17 19:41 UTC, Steven Christenson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Christenson 2024-06-17 19:40:44 UTC
Created attachment 895983 [details]
Portage Info

When trying to setup a new crossdev target with either i486 or i686 glibc fails with a message saying the kernel-headers are too low. However checking the headers shows a kernel newer then 3.X. In the crossdev info it even mentions that the headers are [latest]. Trying to manually emerge glibc produces another error but I think this is due to not being able to setup the target yet. 

I have included both the build log and the info log when trying to build out a i486 target. 

NOTE: There is also this line in the build log that may be relvent to the issue. 

i486-unknown-linux-gnu-gcc: error: unrecognized command-line option ‘-mbranch-protection=none’; did you mean ‘-fcf-protection=none’
Comment 1 Steven Christenson 2024-06-17 19:41:11 UTC
Created attachment 895984 [details]
Glibc build log
Comment 2 Steven Christenson 2024-06-17 22:55:13 UTC
I was able to get the merge to complete by editing the ebuild for glibc. Crossdev profile just points to the main repo's ebuild for glibc. 

I commented out the arch check here and just forced it to use x86 configure options. I am unsure why emerge in crossdev is picking up the host system instead of using the target system arch when doing this check. But its probably due to the way this ebuild determines the architecture? 

    append-flags '-fcf-protection=none'
#   if ! use cet; then
#       if use amd64 || use x86; then
#           append-flags '-fcf-protection=none'
#       elif use arm64; then
#           append-flags '-mbranch-protection=none'
#       fi
#   fi
Comment 3 Mike Gilbert gentoo-dev 2024-06-18 16:18:49 UTC

*** This bug has been marked as a duplicate of bug 932250 ***