[MacPorts] #33042: Cannot install virtuoso ("shell command failed")
#33042: Cannot install virtuoso ("shell command failed") --------------------------------------------+------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: virtuoso, digikam | Port: virtuoso --------------------------------------------+------------------------------- I cannot build virtuoso 6.1.4. the install comand stoos with "Error: Target org.macports.build returned: shell command failed (see log for details)" The log files says at some stage: "***FAILED: Could not start virtuoso within 600 seconds" Log file attached. PS: I have switched the firewall off and restarted my machine. PPS: I want to install virtuoso as dependency to digiKam. My system: MacBook Pro, Mac OSX 10.7.2, Macports 2.0.3 -- Ticket URL: <https://trac.macports.org/ticket/33042> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Changes (by ryandesign@…): * keywords: virtuoso, digikam => * owner: macports-tickets@… => snc@… Old description:
I cannot build virtuoso 6.1.4. the install comand stoos with "Error: Target org.macports.build returned: shell command failed (see log for details)" The log files says at some stage: "***FAILED: Could not start virtuoso within 600 seconds" Log file attached.
PS: I have switched the firewall off and restarted my machine.
PPS: I want to install virtuoso as dependency to digiKam.
My system: MacBook Pro, Mac OSX 10.7.2, Macports 2.0.3
New description: I cannot build virtuoso 6.1.4. the install comand stoos with {{{ "Error: Target org.macports.build returned: shell command failed (see log for details)" }}} The log files says at some stage: {{{ "***FAILED: Could not start virtuoso within 600 seconds" }}} Log file attached. PS: I have switched the firewall off and restarted my machine. PPS: I want to install virtuoso as dependency to digiKam. My system: [[br]] MacBook Pro, Mac OSX 10.7.2, Macports 2.0.3 -- -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by cal@…): This has happened to me before, too, although it failed for me because I was building virtuoso unattended and could not press the allow button when the firewall asked me to. IMHO, these tests should be disabled or made optional. -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by macports@…): Well, I have tried it three times: Once with firewall and unattended, then with firewall and attended (then the connection allow message came up and i was able to allow it but i wasn't sure whether i missed another message) and finally with firewall switched off+restart. still it always failed. Is this server start up test necessary at build time? I want to build virtuoso only for digikam and it might be much easier to allow a connection at use time in case it is actually needed. Without knowing much about the virtuoso project I also vote for taking out the start-up test. -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by snc@…): Well if virtuoso can't start when being built, it certainly can't start when you're running anything that would use it. Since all sorts of other KDE packages rely on virtuoso, should we disable these tests just so you can use one app? I'm not sure. In the mean time, consider putting this in the configure.args: `--disable- all-vads`. Let me know if that's helpful and I can add it as a variant (-kitchensink). -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by cal@…): Consider the buildbot, too. There's nobody there to press the "allow" button on the buildbot, and I wouldn't be surprised if the build failed there because of that. -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by snc@…): Replying to [comment:5 cal@…]:
Consider the buildbot, too. There's nobody there to press the "allow" button on the buildbot, and I wouldn't be surprised if the build failed there because of that.
Doubt we have antivirus/firewall running on the buildbot. -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by macports@…): Replying to [comment:4 snc@…]:
In the mean time, consider putting this in the configure.args: `--disable-all-vads`. Let me know if that's helpful and I can add it as a variant (-kitchensink).
Sorry to bother, but where do I find the configure.args? Is there a config file I can edit? And where in the system sits it? Thanks, Leo -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by pixilla@…): Replying to [comment:7 macports@…]:
Replying to [comment:4 snc@…]:
In the mean time, consider putting this in the configure.args: `--disable-all-vads`. Let me know if that's helpful and I can add it as a variant (-kitchensink).
Sorry to bother, but where do I find the configure.args? Is there a config file I can edit? And where in the system sits it?
Thanks, Leo
Here are some commands that can help: {{{ $ man port $ man portfile $ port dir virtuoso $ port file virtuoso $ port ed virtuoso }}} and just doit: {{{ $ sudo sh -c 'echo "configure.args-append --disable-all-vads" >> '$(port file virtuoso) }}} -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds --------------------------------------------+------------------------------- Reporter: macports@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: virtuoso --------------------------------------------+------------------------------- Comment(by macports@…): Thanks, pixilla, it worked! and as a result digikam builds now, too. So, putting `--disable-all-vads` in the config is a work around. thanks again. -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33042: virtuoso: Could not start virtuoso within 600 seconds ---------------------------------------------+------------------------------ Reporter: macports@… | Owner: snc@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: fixed | Keywords: Port: virtuoso | ---------------------------------------------+------------------------------ Changes (by snc@…): * status: new => closed * resolution: => fixed Comment: Disabled in r90991. -- Ticket URL: <https://trac.macports.org/ticket/33042#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts