Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 832740 - [guru] app-editors/mined-2015.25 does not respect LDFLAGS
Summary: [guru] app-editors/mined-2015.25 does not respect LDFLAGS
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-02-05 07:54 UTC by Agostino Sarubbo
Modified: 2022-03-16 19:39 UTC (History)
1 user (show)

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


Attachments
build.log (build.log,43.75 KB, text/plain)
2022-02-05 07:54 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-02-05 07:54:07 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

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

NOTE:
To reproduce this issue you may want to set LDFLAGS="${LDFLAGS} -Wl,--defsym=__gentoo_check_ldflags__=0". If this is not something about c/c++ context you may want to see this bug as an hint to hide the QA warning (with QA_FLAGS_IGNORED) where is not possible to respect LDFLAGS.
Comment 1 Agostino Sarubbo gentoo-dev 2022-02-05 07:54:09 UTC
Created attachment 764370 [details]
build.log

build log and emerge --info
Comment 2 alex 2022-02-20 04:29:22 UTC
A commit (503799036a7c56cacc33ad87c876141304362499) was just pushed that should fix this problem.
For the record, I really don't like using sed this much, and I'd prefer to just have a patch that I'd use, but I'm having errors with that that I can't seem to solve right now, so this should work until I can figure out what my problem is.
Comment 3 alex 2022-03-16 19:39:14 UTC
I could've sworn that I'd marked this as resolved, but apparently I didn't. That's my bad. The aforementioned commit seems to have held, and I haven't heard any new problems from it, so I'm marking this as fixed.