[MacPorts] #42630: avahi @0.6.31_12: fails to configure
#42630: avahi @0.6.31_12: fails to configure -----------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: avahi -----------------------------+-------------------------------- I cannot update avahi because it fails on the configure step. I am running on OS X 10.8, MacPorts 2.2.1, Xcode 4.6.2, Build version 4H1003 main.log attached -- Ticket URL: <https://trac.macports.org/ticket/42630> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by cal@…): Is your `cairo` installed with the `+quartz` variant, like your `gtk2` is? -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): It is not! I thought it was, but the cairo @1.12.16_2+universal+x11, seems to have been installed at some point later ... petr% port installed gtk2 cairo The following ports are currently installed: cairo @1.12.16_2+quartz+x11 cairo @1.12.16_2+universal+x11 (active) cairo @1.12.16_2+x11 gtk2 @2.24.22_1+quartz (active) gtk2 @2.24.22_1+x11 So I probably need to fix this, but what will I break then? -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by cal@…): You can install `cairo +x11+quartz` (and even `+universal`, if you have to). That should fix it. -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:2 Peter.Danecek@…]:
It is not! I thought it was, but the cairo @1.12.16_2+universal+x11, seems to have been installed at some point later ... {{{ petr% port installed gtk2 cairo The following ports are currently installed: cairo @1.12.16_2+quartz+x11 cairo @1.12.16_2+universal+x11 (active) cairo @1.12.16_2+x11 gtk2 @2.24.22_1+quartz (active) gtk2 @2.24.22_1+x11 }}} So I probably need to fix this, but what will I break then?
Unlike most other things with both `+quartz` and `+x11` variants, cairo's `+quartz` and `+x11` variants can both be selected simultaneously. So I would not worry about it breaking anything. -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): I actually tried to reactivate cairo @1.12.16_2+quartz+x11. But `rev- upgrade` reverted the change, so I am now rebuilding with +universal, to see if this makes the trick. Anyway, if it is save to have +quartz+x11 variant, why not make it the default, so that is can serve almost all ports or does this involves too many dependencies? -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): Okay I build with cairo with +quartz+x11+universal variants and new also avahi builds fine. So basically it is only the depencency handling which might be somewhat cleaner. Thanks for helping with this! -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:7 Peter.Danecek@…]:
So basically it is only the depencency handling which might be somewhat cleaner.
Which in other words means using `require_active_variants` for cairo as well. Avahi already checks the variants of gtk2 with `require_active_variants`, so it should be easy just to do likewise with cairo. [[BR]] ^(Of course it would be easier if #126 ever gets fixed, but that looks like that will never happen...)
Thanks for helping with this!
You're welcome! -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): I realize the pixilla dropped maintainership. So what to do about this ticket? Anyone willing to commit the proposed change before this ticket is closed? -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#42630: avahi @0.6.31_12: fails to configure ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: avahi | ------------------------------+-------------------------------- Comment (by pixilla@…): Attaching a patch to the ticket will be helpful. -- Ticket URL: <https://trac.macports.org/ticket/42630#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts