Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 831330

Summary: cross-x86_64-linux-musl/gcc-11.2.0 - patching file gcc/config/i386/pmm_malloc.h fails
Product: Gentoo Linux Reporter: Bertrand Jacquin <bertrand>
Component: Current packagesAssignee: Cross compilation support <cross>
Status: RESOLVED INVALID    
Severity: normal CC: bertrand, jstein
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info
build.log

Description Bertrand Jacquin 2022-01-16 22:10:17 UTC
Hi,

cross-x86_64-linux-musl/gcc-11.2.0 fails to prepare() with USE=""cxx hardened jit lto nls nptl openmp (pie) (ssp) zstd":

 * Applying musl patches ...
 * Applying cpu_indicator.patch ...
patching file gcc/config/i386/i386-expand.c
Hunk #1 succeeded at 11063 (offset 122 lines).
patching file libgcc/config/i386/cpuinfo.c
Hunk #1 succeeded at 63 with fuzz 1 (offset -445 lines).                                                    [ ok ]
 * Applying gcc-pure64.patch ...                                                                            [ ok ]
 * Applying posix_memalign.patch ...                                                                        [ ok ]
 * Applying 0001-posix_memalign.patch ...
patching file gcc/config/i386/pmm_malloc.h
Hunk #1 FAILED at 27.
Hunk #2 FAILED at 42.
2 out of 2 hunks FAILED -- saving rejects to file gcc/config/i386/pmm_malloc.h.rej                          [ !! ]
 * ERROR: cross-x86_64-linux-musl/gcc-11.2.0::x-portage failed (prepare phase):
 *   patch -p1  failed with /etc/portage/patches/cross-x86_64-linux-musl/gcc/0001-posix_memalign.patch

Please find attached logs and emerge --info.

Reproducible: Always
Comment 1 Bertrand Jacquin 2022-01-16 22:10:41 UTC
Created attachment 762373 [details]
emerge --info
Comment 2 Bertrand Jacquin 2022-01-16 22:10:58 UTC
Created attachment 762374 [details]
build.log
Comment 3 Bertrand Jacquin 2022-01-16 22:13:54 UTC
This issue comes from a leftover local patch, resolving