Bug 19193 - Update textproc/jade to C{XX,}FLAGS safe status
Summary: Update textproc/jade to C{XX,}FLAGS safe status
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-06-11 06:20 UTC by lioux
Modified: 2001-01-28 18:38 UTC (History)
0 users

See Also:

Attachments
file.diff (978 bytes, patch)
2000-06-11 06:20 UTC, lioux 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description lioux 2000-06-11 06:20:01 UTC 
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
Comment 1 Akinori MUSHA freebsd_committer freebsd_triage 2000-06-11 09:07:49 UTC 
Responsible Changed
From-To: freebsd-ports->jfieber

Over to Maintainer.
Comment 2 Will Andrews freebsd_committer freebsd_triage 2001-01-27 05:47:41 UTC 
Responsible Changed
From-To: jfieber->freebsd-ports

Return responsibility to general ports team.
Comment 3 FUJISHIMA Satsuki freebsd_committer freebsd_triage 2001-01-28 18:38:17 UTC 
State Changed
From-To: open->closed

Committed, thanks.