Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Aug 2003 12:12:40 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        "Peter Ulrich Kruppa <root@pukruppa.de>" <root@pukruppa.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: make.conf question
Message-ID:  <20030826111240.GD37256@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <20030826124137.A41428@small.pukruppa.de>
References:  <20030826124137.A41428@small.pukruppa.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--fXStkuK2IQBfcDe+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 26, 2003 at 12:54:25PM +0200, Peter Ulrich Kruppa <root@pukrupp=
a.de> wrote:

> 1) Can I put any make option into make.conf that can be applied
>    to ports (like in 	make WITH_CALENDAR=3Dyes install clean    )
>    or is this restricted to system ressources?

Yes, you can put ports specific options into /etc/make.conf You can
also put a Makefile.inc into a specific port directory which will be
read in automatically -- I think there are a few ports that may happen
to overwrite that file, but they are few and far between.

See also /usr/local/etc/pkgtools.conf if you're a portupgrade(1) user.

> 2) If yes - would this be advisable? - Or is there a big chance
>    to produce some sort of mess?

No, this is what /etc/make.conf is designed to do.  Generally it will
work well, but occasional problems creep in.  Eg. if you put:

    A4=3DYES

into /etc/make.conf at the moment, then I believe that triggers a bug
in the print/ghostscript-gnu port which makes the build fall over at
unexpected moments (ports/54848).  Slightly inconvenient for the large
chunk of the world that uses metric paper sizes.

> 3) Is make.conf also applied to gmake (used by many ports)?

No, /etc/make.conf won't be read in by *any* of the Makefiles (gmake
or otherwise) that come with the source code of the port.  It's only
used by the Makefiles in the port directory, and it's up to them to
run the port's configure script with the required options or to apply
patches to the source code or do whatever else is required to achive
the desired result as indicated by the make options.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--fXStkuK2IQBfcDe+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/S0CodtESqEQa7a0RAjDdAJ9ofgpAADUtBA9Wn7uyZ64Ln238bACdG759
ze+J+3V0ted4+MAVG9KgAVA=
=w2Ua
-----END PGP SIGNATURE-----

--fXStkuK2IQBfcDe+--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030826111240.GD37256>