Summary: | app-shells/sash: CFLAGS are ignored | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Diego Elio Pettenò (RETIRED)
2008-10-05 20:43:00 UTC
post information on why you think it isnt respecting flags. looks like it works to me and it's been that way for a long time. if you're just writing a script, you need to review the output to avoid a shit ton of false positives which just wastes other people's time. Hrm, I found the problem: my script assumes that CFLAGS gets set during src_compile, while here they are hardset during src_unpack(). I'd debate that I'm still correct here since after an ebuild $foo unpack I wouldt expect my CFLAGS to be respected again, but I admit it's semantic at this point. no, flag setting in src_unpack is valid and fully supported if you do it in src_compile, then you cannot repeat the step with the same result if something like "append-flags" were used ... you'd keep appending the value over and over |