From owner-freebsd-ports Sun Jan 14 6:49: 5 2001 Delivered-To: freebsd-ports@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id AF2C537B400 for ; Sun, 14 Jan 2001 06:48:47 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14HoSc-00034m-00; Sun, 14 Jan 2001 15:48:46 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id f0EEfeg16794 for freebsd-ports@freebsd.org; Sun, 14 Jan 2001 15:41:40 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: How can I make GNU configure respect $CFLAGS? Date: Sun, 14 Jan 2001 14:41:39 +0000 (UTC) Message-ID: <93sdr3$g1p$1@kemoauc.mips.inka.de> References: <20010113204921.A54960@cae88-102-101.sc.rr.com> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Donald J . Maddox wrote: > TSIA... I would like to make a port of a program that uses a GNU > configure script. Problem is, it is bound and determined to set > $CFLAGS (or actually $CXXFLAGS in this case) to '-g -O2', no matter > what. Surely some of you experienced porters out there have run > into this one before... Normally, configure picks up CFLAGS/CXXFLAGS from the environment, where bsd.port.mk places them automatically for the configure target. There are however some broken configure scripts out there, partly accidental, partly intentional (-Oinfinite -ftruly-bizarre). In that case you need to patch the configure script, or better (and more easily) configure.in. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message