[MacPorts] #38267: v8 @3.17.6 +universal needs its configure.universal_args nuked
#38267: v8 @3.17.6 +universal needs its configure.universal_args nuked ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: haspatch | Port: v8 ----------------------+-------------------------------- Its configure script doesn't recognize the `--disable-dependency-tracking` flag. -- Ticket URL: <https://trac.macports.org/ticket/38267> MacPorts <http://www.macports.org/> Ports system for OS X
#38267: v8 @3.17.6 +universal needs its configure.universal_args nuked ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: v8 | ----------------------+-------------------------------- Comment (by ryandesign@…): Please just write: {{{ configure.universal_args-delete --disable-dependency-tracking }}} like other ports do. It doesn't need to go inside the universal variant; I don't think any other ports do that. -- Ticket URL: <https://trac.macports.org/ticket/38267#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#38267: v8 @3.17.6 +universal needs its configure.universal_args nuked ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: haspatch Port: v8 | ----------------------+-------------------------------- Changes (by cal@…): * status: new => closed * resolution: => fixed Comment: Fixed in r103654. What's the benefit of this flag anyway? Should we remove it in base? -- Ticket URL: <https://trac.macports.org/ticket/38267#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38267: v8 @3.17.6 +universal needs its configure.universal_args nuked ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: haspatch Port: v8 | ----------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:2 cal@…]:
What's the benefit of this flag anyway?
http://www.gnu.org/software/automake/manual/html_node/Dependency- Tracking.html -- Ticket URL: <https://trac.macports.org/ticket/38267#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38267: v8 @3.17.6 +universal needs its configure.universal_args nuked ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: haspatch Port: v8 | ----------------------+-------------------------------- Comment (by egall@…): Replying to [comment:3 larryv@…]:
Replying to [comment:2 cal@…]:
What's the benefit of this flag anyway? Should we remove it in base?
http://www.gnu.org/software/automake/manual/html_node/Dependency- Tracking.html
So in other words we could remove it from everything that does'''n't''' use `automake`? -- Ticket URL: <https://trac.macports.org/ticket/38267#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38267: v8 @3.17.6 +universal needs its configure.universal_args nuked ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: haspatch Port: v8 | ----------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:4 egall@…]:
So in other words we could remove it from everything that does'''n't''' use `automake`?
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. 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. -- Ticket URL: <https://trac.macports.org/ticket/38267#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts