virtuoso: Could not start virtuoso within 600 seconds

[macports@…]

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

[macports@…]

Log file for virtuoso build

[neverpanic (Clemens Lang)]

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.

[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.

[nerdling (Jeremy Lavergne)]

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).

[neverpanic (Clemens Lang)]

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.

[nerdling (Jeremy Lavergne)]

Replying to 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.

[macports@…]

Replying to 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

[pixilla (Bradley Giesbrecht)]

Replying to macports@…:

Replying to 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)

[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.

[nerdling (Jeremy Lavergne)]

Disabled in r90991.