Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 831704 - [guru] app-editors/mined-2015.25 does not respect CFLAGS
Summary: [guru] app-editors/mined-2015.25 does not respect CFLAGS
Status: RESOLVED FIXED
Alias: None
Product: GURU
Classification: Unclassified
Component: Package issues (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: alex
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: qa-guru
  Show dependency tree
 
Reported: 2022-01-21 08:13 UTC by Agostino Sarubbo
Modified: 2022-02-07 15:16 UTC (History)
1 user (show)

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


Attachments
build.log (build.log,69.70 KB, text/plain)
2022-01-21 08:13 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2022-01-21 08:13:49 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: app-editors/mined-2015.25 does not respect CFLAGS.
Discovered on: amd64 (internal ref: guru_ci)

NOTE:
To reproduce this issue you may want to add "-frecord-gcc-switches" to CFLAGS/CXXFLAGS/FFLAGS/FCFLAGS. If this is not something about c/c++ context see this bug as an hint to hide the QA warning (with QA_FLAGS_IGNORED) where is not possible to respect CFLAGS.
Comment 1 Agostino Sarubbo gentoo-dev 2022-01-21 08:13:52 UTC
Created attachment 762978 [details]
build.log

build log and emerge --info
Comment 2 alex 2022-02-03 15:09:13 UTC
OK, so the problem here was that the Makefile just called a script, apparently handwritten by upstream, that would set the CFLAGS then run the compilation process.
I've modified the ebuild to run this compilation process (the src/mkmined script) without editing the CFLAGS, and it's passed all of my sanity checks.
I've pushed the change, and once it's merged I'll close this bug as fixed, provided the issue doesn't still persist.
Comment 3 alex 2022-02-07 15:13:12 UTC
Fix pushed to the repository, no new issues, and I've solved the error, to the best of my knowledge, on my test machine.
Seems like a resolution if I've ever seen one.
Comment 4 alex 2022-02-07 15:16:09 UTC
I figure I'd best mention that it was commit ab5323899177ed87341c97b4a75f76a2781e5d10 that fixed this issue.