Re: pkg/33632

[Tim Zingelman <tez%netbsd.org@localhost>]

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

From: Tim Zingelman <tez%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/33632
Date: Mon, 20 Jun 2011 16:33:39 -0500

 The initially reported problem seems to be resolved... however with
 sunpro compiler, automake14 seems to do the wrong thing for dependency
 generation.
 
 I have found that a workaround for this is to patch these files:
 
  work/w3c-libwww-5.4.0/modules/expat/xmltok/Makefile.am
  work/w3c-libwww-5.4.0/modules/expat/xmlparse/Makefile.am
  work/w3c-libwww-5.4.0/modules/md5/Makefile.am
  work/w3c-libwww-5.4.0/Library/src/SSL/Makefile.am
  work/w3c-libwww-5.4.0/Library/src/Makefile.am
  work/w3c-libwww-5.4.0/Library/Examples/Makefile.am
  work/w3c-libwww-5.4.0/Library/cvs2sql/Makefile.am
  work/w3c-libwww-5.4.0/PICS-client/src/Makefile.am
  work/w3c-libwww-5.4.0/Robot/src/Makefile.am
  work/w3c-libwww-5.4.0/LineMode/src/Makefile.am
  work/w3c-libwww-5.4.0/ComLine/src/Makefile.am
 
 in the package to add:
 
  AUTOMAKE_OPTIONS = no-dependencies
 
 at the top.  This allows the package to build using sunpro on solaris.
 
 Is this change ok for all compilers/systems or do we need to find a
 way to limit it to the sunpro compiler case?
 
 Is there any reasonable way to patch automake14 instead to do the
 right thing, or is that not worth the work since it is so old and used
 by so few packages?