Changes between Initial Version and Version 1 of Ticket #38267, comment 5


Ignore:
Timestamp:
Mar 4, 2013, 3:43:05 AM (11 years ago)
Author:
larryv (Lawrence Velázquez)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #38267, comment 5

    initial v1  
    22> So in other words we could remove it from everything that does'''n't''' use `automake`?
    33
    4 No. The flag is necessary for universal builds because automatic dependency generation cannot be done when targeting multiple architectures. I presume that the configure scripts that don’t accept the flag have dependency generation disabled by default.
     4No. The flag is necessary for universal builds because Clang and Apple’s GCC cannot automatically generate dependency information when targeting multiple architectures. I presume that the configure scripts that don’t accept the flag have dependency generation disabled by default, or don’t generate dependency information at all, or handle this in some other way.
    55
    6 In my experience, most configure scripts that don’t accept the flag just ignore it. Unless the flag actually causes problems with configure, I don’t see why we should bother dealing with it.
     6In my experience, most configure scripts that don’t accept the flag just ignore it. Given that there’s no good way to determine whether a particular build system requires the flag’s presence or absence, I don’t see how we could deal with it in base. And since only 103 out of 9126 portfiles mention the flag at all, I don’t see why we should bother.