virtuoso-6.1.1 Building seems to get stuck

[lang@…]

The kde ports now depend on virtuoso, so I's like to build it. If I try to build virtuoso on a MacBook Pro (Intel, Mac OS X Version 10.5, Xcode version 3.1), at some point it seems to get stuck: Seemingly no progress within hours (days) but almost full cpu load. Below I pasted a snippet of the debug log (the 'final' lines); I produced this log quite recently, but there would be no further progress if I had waited longer. Obviously there is an error because some file or directory ist not found, but I am not expert enough to see what is going on here and how to fix the problem.

=====================================================================
=  TUTORIAL VAD create
=  Wed Jul 7 16:49:34 CEST 2010
=====================================================================

Stop database with raw_exit
# isql localhost:1111 dba dba "EXEC=raw_exit();" VERBOSE=OFF PROMPT=OFF ERRORS=STDOUT
Virtuoso.ini creation...
Starting virtuoso

Waiting virtuoso start on port 1111...
PASSED: virtuoso successfully started on port 1111
PASSED: load dev.sql
PASSED: TUT_generate_files('/vad_files/vsp/tutorial')
tar (child): /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virtuoso/work/virtuoso-opensource-6.1.1/binsrc/samples/IBuySpy/ibuyspy_mono_virtuoso_client.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
mv: rename PortalCS to /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virtuoso/work/virtuoso-opensource-6.1.1/binsrc/tutorial/vad_files/vsp/PortalCS: No such file or directory
VAD Tutorial sticker make_tutorial_fs_vad.xml creation...
VAD Tutorial sticker make_tutorial_dav_vad.xml creation...

[ryandesign@…]

Please attach the MacPorts log file for virtuoso. It should be in some subdirectory of /opt/local/var/macports/logs.

[lang@…]

Replying to ryandesign@…:

Please attach the MacPorts log file for virtuoso. It should be in some subdirectory of /opt/local/var/macports/logs.

I did so. I took a look at the file: It ends with

:info:build =====================================================================
:info:build =  COMPLETED VAD PACKAGING
:info:build =  Thu Jul 8 11:41:29 CEST 2010
:info:build =====================================================================
:info:build 
:info:build Making all in tutorial
:info:build Making all in .
:info:build PATH="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virtuoso/work/virtuoso-opensource-6.1.1/binsrc/virtuoso:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virt

I did not truncate the final line...

The debug log said

=====================================================================
=  COMPLETED VAD PACKAGING
=  Thu Jul 8 11:41:29 CEST 2010
=====================================================================

Making all in tutorial
Making all in .
PATH="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virtuoso/work/virtuoso-opensource-6.1.1/binsrc/virtuoso:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virtuoso/work/virtuoso-opensource-6.1.1/binsrc/tests:.:$PATH" PORT=1111 HOME="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_virtuoso/work/virtuoso-opensource-6.1.1" HOST=localhost sh ./make_vad.sh

=====================================================================
=  TUTORIAL VAD create
=  Thu Jul 8 11:41:29 CEST 2010
=====================================================================
<... the same as I already pasted above ...>

[snc@…]

The pegged CPU load is likely virtuoso-t building things as it appears to bootstrap. I'll time how long it takes to build for me on various configurations (there's a new version out I'm testing).

[snc@…]

The new version took about 30 minutes on a single-core processor. Updated in r69587.

[lang@…]

Replying to snc@…:

The new version took about 30 minutes on a single-core processor. Updated in r69587.

Thank you for handling the problem! I am afraid that the problem still persists for me. After about three hours of building virtuoso, the debug log reached

=====================================================================
=  TUTORIAL VAD create
=  Tue Jul 13 12:26:24 CEST 2010
=====================================================================

Stop database with raw_exit
# isql localhost:1111 dba dba "EXEC=raw_exit();" VERBOSE=OFF PROMPT=OFF ERRORS=STDOUT
Virtuoso.ini creation...
Starting virtuoso

Waiting virtuoso start on port 1111...
PASSED: virtuoso successfully started on port 1111
PASSED: load dev.sql
PASSED: TUT_generate_files('/vad_files/vsp/tutorial')
VAD Tutorial sticker make_tutorial_fs_vad.xml creation...
VAD Tutorial sticker make_tutorial_dav_vad.xml creation...

I stopped building after about 12 hours (again the full cpu load for hours). I will attach the log file. I will also ask a collegue who could reproduce the problem on his MacBook if he can reproduce it one more.

[juaurib@…]

Hello

I had the same problem. After a bit of searching I realised that the Sophos antivirus was doing a InterCheck that was using all CPU during the virtuoso tests. After disabling the antivirus, I had to manually kill a process that was hanging called "virtuoso+wait" and after that it finished building virtuoso. Don't know if this is a problem related to the virus checks or what but in the end it finished. Cheers

[lang@…]

Replying to juaurib@…:

Hello

I had the same problem. After a bit of searching I realised that the Sophos antivirus was doing a InterCheck that was using all CPU during the virtuoso tests. After disabling the antivirus, I had to manually kill a process that was hanging called "virtuoso+wait" and after that it finished building virtuoso. Don't know if this is a problem related to the virus checks or what but in the end it finished. Cheers

Thank you for the hint, it worked for me as well! So from this point of view the problem is fixed (but I cannot alter the status of the ticket).

[snc@…]

Duplicate #29584

[egall@…]

Cc Me!