head	1.2;
access;
symbols
	RELEASE_4_8_0:1.1
	RELEASE_5_0_0:1.1
	RELEASE_4_7_0:1.1
	RELEASE_4_6_2:1.1
	RELEASE_4_6_1:1.1
	RELEASE_4_6_0:1.1;
locks; strict;
comment	@# @;


1.2
date	2003.04.24.11.17.56;	author sobomax;	state dead;
branches;
next	1.1;

1.1
date	2002.04.16.17.54.35;	author sobomax;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Upgrade to 20021101 release (aka 1.0), which fixes compilation on
recent FreeBSD versions and allows to remove all of the gcc 3.x
fixes. sscli now supports Darwin/ppc, so that it might be possible
to port it to FreeBSD/ppc once it is available.
@
text
@
$FreeBSD: ports/lang/cli/files/patch-tools::cppmunge::makefile,v 1.1 2002/04/16 17:54:35 sobomax Exp $

--- tools/cppmunge/makefile.orig	Fri Mar 22 03:49:22 2002
+++ tools/cppmunge/makefile	Wed Apr 10 12:10:29 2002
@@@@ -17,7 +17,8 @@@@
 # makefile for cppmunge
 # ============================================================================
 
-CFLAGS = -g -Wall -O2
+CFLAGS ?= -g -Wall -O2
+CFLAGS += -fno-builtin -fno-exceptions -fno-rtti
 TARGET_NAME = $(TARGETCOMPLUS)/cppmunge
 
 SOURCES=cppmunge.c
@


1.1
log
@- Clean-up build system a bit;
- fix remaining two places where CFLAGS weren't respected;
- use cpio(1) to copy hierarchies instead of tar(1), so that it is possible
  to build the port as ordinary user, but still have installed files be
  owned by root;
- use slightly different solution for the problem with 777 permissions on
  directories created during the build. Instead of harcoding resulting
  prmission apply umask(2) to all mode arguments of [f]chmod() calls.
  Since Rotor has no notion of file-level security anyway this should be
  an optimal way to fix the problem.

Submitted by:	Patrick Backlund <pbacklun@@cc.hut.fi> (cpio fix)
		sobomax (the rest)
@
text
@d2 1
a2 1
$FreeBSD$
@

