On Wed, Sep 2, 2009 at 09:59, Ryan Schmidt wrote:
> On Sep 2, 2009, at 11:56, Toby Peterson wrote:
>
>>> I don't know what dependency tracking does, but since the default is to
>>> enable it, I assume it's useful for something. Does anybody know what
>>> it's
>>> for or what consequences disabling
On Sep 2, 2009, at 11:56, Toby Peterson wrote:
I don't know what dependency tracking does, but since the default
is to
enable it, I assume it's useful for something. Does anybody know
what it's
for or what consequences disabling it could have?
The primary consequence is that builds would b
On Wed, Sep 2, 2009 at 02:16, Ryan Schmidt wrote:
> On Sep 2, 2009, at 03:39, Vincent Lefevre wrote:
>
>> The GNU Coding Standards don't mention --disable-dependency-tracking
>> because it is not an option universally recognized. In fact, this is
>> a specific option
On Sep 2, 2009, at 03:39, Vincent Lefevre wrote:
The GNU Coding Standards don't mention --disable-dependency-tracking
because it is not an option universally recognized. In fact, this is
a specific option defined by automake. Software not based on automake
probably don't have such
er, it's simply a difference in how optipng's
> configure script functions vs. how some other programs' configure
> scripts function. MacPorts has to have some sort of default
> behavior, and the default of including --disable-dependency-tracking
> reflected the best guess o
the --disable-dependency-tracking configure option with the
universal variant, even though this option is not standard:
http://www.gnu.org/prep/standards/standards.html#Configuration
Closes #21002.
As I recall, all versions of MacPorts that have had a universal
variant have added the --disable
