Re: Dealing with compile options that need parameters

To: nia <nia%NetBSD.org@localhost>
Subject: Re: Dealing with compile options that need parameters
From: Francisco J. Tsao Santín <tsao%disroot.org@localhost>
Date: Fri, 22 Jul 2022 16:42:19 +0200 (CEST)

On Fri, 22 Jul 2022, nia wrote:

> On Thu, Jul 21, 2022 at 06:03:05PM +0200, Francisco J. Tsao Santn wrote:
> > PPP_PATH=/usr/sbin/pppd
> 
> Unrelated nit, I suggest doing something like this:
> 
> .if ${OPSYS} == "NetBSD" && exists(/usr/sbin/pppd)
> PPP_PATH?=	/usr/sbin/pppd
> .else
> DEPENDS+=	pppd-[0-9]*:../../net/pppd
> PPP_PATH?=	${PREFIX}/sbin/pppd
> .endif

Thanks, I finally removed that options, but I take note for the future
:-)

-- 
Francisco J. Tsao Santín
http://gattaca.es
1024D/71CF4D62  42 F1 53 35 EF 98 98 8A FC 6C 56 B3 4C A7 7D FB

References:
- Dealing with compile options that need parameters
  - From: Francisco J. Tsao Santín
- Re: Dealing with compile options that need parameters
  - From: nia

Prev by Date: Re: How to build a package with OpenMP support
Next by Date: Re: 'state_not_recoverable' is not a member of 'std::errc' on clang build (was: clang-13.0.1nb1 build from pkgsrc 2022Q2 fails on NetBSD-9.2_STABLE (2022-07-01))
Previous by Thread: Re: Dealing with compile options that need parameters
Next by Thread: openfortivpn at wip repository
Indexes:

Home | Main Index | Thread Index | Old Index