Re: pkg/48961 (make update from lang/g95 breaks blas, lapack, numpy, etc.)

[David Holland <dholland%eecs.harvard.edu@localhost>]

The following reply was made to PR pkg/48961; it has been noted by GNATS.

From: David Holland <dholland%eecs.harvard.edu@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/48961 (make update from lang/g95 breaks blas, lapack, numpy, etc.)
Date: Thu, 22 Jan 2015 19:02:09 -0500

 On Thu, Jan 22, 2015 at 10:30:01PM +0000, David Holland wrote:
  >  It seems to be that when building via make update, g95 isn't found.
  >  Diffing work directories that did and did not configure properly
  >  reveals the following bits of interest. (The various *makevars files
  >  all have the same diff.)
  >  
  >  I'm sure this is because the make update is *from* lang/g95; but so
  >  far I don't have any idea why.
 
 Now I do. The problem is this clause at the beginning of g95.mk:
 
 .if !empty(PKGPATH:Mlang/g95) || !empty(PKGPATH:Mdevel/patch) || \
     !empty(PKGPATH:Mdevel/libtool-base)
 IGNORE_G95=	yes
 MAKEFLAGS+=	IGNORE_G95=yes
 .endif
 
 make update passes MAKEFLAGS when building depending packages, so
 IGNORE_G95 gets passed along and messes up their builds.
 
 I suppose it needs to be in MAKEFLAGS when building depends to avoid
 potential cycles; but does anything G95 depends on use FORTRAN? My
 guess would be no and that it's therefore not needed...
 
 -- 
    - David A. Holland / dholland%eecs.harvard.edu@localhost