Re: Ports failing with bsd make

On Sunday, 2. January 2005 22:54, Kirill Ponomarew wrote:
> On Sun, Jan 02, 2005 at 10:50:33PM +0100, Michael Nottebrock wrote:
> > On Sunday, 2. January 2005 22:23, Kris Kennaway wrote:
> > > On Sun, Jan 02, 2005 at 09:17:44PM +0100, Michael Nottebrock wrote:
> > > > On recent -current, several ports are failing to build. Common
> > > > quality: They all use the system make rather than gmake.
> > > >
> > > > Examples: science/hdf, textproc/Wordnet, devel/qmake.
> > > >
> > > > The errors all look pretty similar:
> > > >
> > > > ===> mfhdf/nctest (all)
> > > > make: don't know how to make nctest.1. Stop
> > > > ...
> > > >
> > > > make: don't know how to make wn.1. Stop
> > > > ...
> > > >
> > > > make: don't know how to make qmake.1. Stop
> > > >
> > > > Looks like they're all failing while trying to generate manpages. Has
> > > > make become allergic to targets with a dot in them perhaps?
> > >
> > > Ruslan's NO_* change broke a lot of ports.  He's currently on vacation
> > > for a few days, but I expect he'll fix these when he gets back.  If
> > > you want to do it in the meantime (although we're in ports freeze
> > > anyway so this won't be committed until after), the port needs to set
> > > *both* NOMAN and NO_MAN (similarly for any other options like NOSHARED
> > > and NOPROFILE), for compatibility with both 6.x and older.
> >
> > Hm - none of those ports set either NO_MAN or NOMAN at the moment (and
> > isn't this a base-system switch?). Is my build environment wonky?
>
> They're defined in software makefiles.

LOL - I didn't think that the other common thing of those ports would matter 
here, but it actually does - they're all made by mi_at_ and he used a 
bsd.prog.mk-based custom build system for all of them, too.

I guess he got all the pointyhat mail already. :-)
-- 
   ,_,   | Michael Nottebrock               | lofi_at_freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org