Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 877245 - sys-devel/gcc-12.2.1_p20221008 fails to patch on Via
Summary: sys-devel/gcc-12.2.1_p20221008 fails to patch on Via
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: 2022-10-15 20:11 UTC by Thomas Capricelli
Modified: 2022-10-15 20:55 UTC (History)
1 user (show)

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


Attachments
/tmp/portage/sys-devel/gcc-12.2.1_p20221008/temp/build.log (build.log,3.63 KB, text/x-log)
2022-10-15 20:12 UTC, Thomas Capricelli
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Capricelli 2022-10-15 20:11:18 UTC
The core of the problem is there:

patching file config/cet.m4
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 155.
2 out of 2 hunks FAILED -- saving rejects to file config/cet.m4.rej
patching file libiberty/configure
Hunk #1 succeeded at 5430 (offset 34 lines).
Hunk #2 FAILED at 5460.
1 out of 2 hunks FAILED -- saving rejects to file libiberty/configure.rej
 [ !! ]


Reproducible: Always
Comment 1 Thomas Capricelli 2022-10-15 20:12:18 UTC
Created attachment 824327 [details]
/tmp/portage/sys-devel/gcc-12.2.1_p20221008/temp/build.log
Comment 2 Thomas Capricelli 2022-10-15 20:13:03 UTC
Ok, the system is extremely old, 32bits.

~ # cat /proc/cpuinfo 
processor       : 0
vendor_id       : CentaurHauls
cpu family      : 6
model           : 9
model name      : VIA Nehemiah
stepping        : 3
cpu MHz         :
Comment 3 Ionen Wolkens gentoo-dev 2022-10-15 20:16:01 UTC
This is your own patch which sounds obsolete, suggest cleaning:

 *   patch -p1  failed with /etc/portage/patches/sys-devel/gcc/fix-cet-detection-on-via.patch
Comment 4 Thomas Capricelli 2022-10-15 20:55:16 UTC
Oh.. indeed. I'm so sorry ! Will be way more careful next time.

It's not my patch, but a (temporary) workaround patch, probably found in some other ticket here on b.g.o.