Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#49766 - [hardening-wrapper] doesn't respect CC and CXX environment variables

Attached to Project: Community Packages
Opened by Matt (ilikenwf) - Sunday, 19 June 2016, 01:51 GMT
Last edited by Daniel Micay (thestinger) - Monday, 20 June 2016, 03:12 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

As hardening-wrapper is forced by default into our path, it forces us to use gcc6, which does not build certain applications. Handbrake git from the AUR is a good example.

I don't recall manually installing this package and so I assume it was installed by either an AUR package, or an upgrade, but even so, it seems to heavily break building with alternative compilers. I'm removing it for now, but think that the wrapper should be able to dynamically wrap compilers based on environment vars.
This task depends upon

Closed by  Daniel Micay (thestinger)
Monday, 20 June 2016, 03:12 GMT
Reason for closing:  Works for me
Comment by Matt (ilikenwf) - Sunday, 19 June 2016, 19:55 GMT
I realize that this was seen as a non-issue when I posted this to the github issue tracker, but because this package currently breaks building of certain packages like handbrake-cli-git, I thought it worth discussing. It seems some cmake and other packages directly use the user's profile and ignore CC and CXX, meaning that when one sets them, they are still disregarded when the wrapper is installed. As such, builds of specific applications like handbrake-cli-git are broken.
Comment by Daniel Micay (thestinger) - Monday, 20 June 2016, 03:12 GMT
As I already said when you filed this before, it does no such thing. It puts itself into PATH as a wrapper around GCC. It can not cause CC/CXX to be ignored, and it delegates to the next gcc binary in PATH. CC/CXX have no relevant to it. You could file a bug about the specific package that's broken, but by filing a bug about a specific problem that I know to not be a problem you're not going to get any result other than it being closed as invalid.

Loading...