Bug 19193
| Summary: | Update textproc/jade to C{XX,}FLAGS safe status | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | lioux <lioux> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports (Nobody) <ports> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-ports->jfieber Over to Maintainer. Responsible Changed From-To: jfieber->freebsd-ports Return responsibility to general ports team. State Changed From-To: open->closed Committed, thanks. |
Updated textproc/jade to C{XX,}FLAGS safe status. Files removed: patches/patch-aa patch-aa is not necessary. "-O" is the default value for C{XX,}FLAGS. I've just built jade 2 times using very weird C{XX,}FLAGS values to be sure and it seems okay. Besides, CONFIGURE_ENV is unusual. Just let CXXFLAGS be CXXFLAGS, if the user has not set it, we do not unless it brakes the port not to. This way we respect make.conf choices and behave safely in possibly hostile enviroments (archs such as alpha). jade behaves just fine without these How-To-Repeat: n/a