Summary: | net-irc/rhapsody-0.28b-r1 does not respect LDFLAGS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | CONFIRMED --- | ||
Severity: | QA | CC: | esigra, hwoarang, net-irc, sam |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 331933 | ||
Attachments: |
Build log
add LDFLAGS and CPPFLAGS to LOCALFLAGS |
Description
Diego Elio Pettenò (RETIRED)
![]() Created attachment 245676 [details]
Build log
Created attachment 245717 [details, diff]
add LDFLAGS and CPPFLAGS to LOCALFLAGS
rhapsody's buildsystem doesn't distinguish between different sorts of compiler flags, so a ``correct'' fix is to add LDFLAGS to the LOCALFLAGS variable.
Why are you using CPPFLAGS on LOCALFLAGS? Where does this variable come from and why do you need it? (In reply to comment #3) > Why are you using CPPFLAGS on LOCALFLAGS? Where does this variable come from > and why do you need it? CPPFLAGS is just another *FLAGS variable in the list of conventions all Makefiles should support. Or at least that's my understanding ;-). If you think it shouldn't be there and want me to roll another patch I can. tinderbox has reproduced this issue with version 0.28b - Updating summary. ci has reproduced this issue with version 0.28b-r1 - Updating summary. |