vtk5: error: expected "FILENAME" or <FILENAME>

[bricklemacho@…]

Trying to compile VTK5 on OS X Mavericks. Ticket #40901 applies a upstream patch. I have since tried the following:

sudo port clean vtk5
sudo port selfupdate
sudo port install vtk5 +python27 +qt4_mac

Seems to be getting errors VTK5.10.1/Utilities/vtkfreetype/src/base firectory (not sure) Log file attached.

Previously I built qt4-mac (Ticket #40852 fixed the qt4_mac issue). I downloaded the VTK5.10.1 source form Kitware and it builds without error on my machine.

[oliverjhahn@…]

Cc Me!

[mf2k (Frank Schima)]

In the future, please use WikiFormatting.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #41159.

I see lots of errors beginning with:

:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_vtk5/vtk5/work/VTK5.10.1/Utilities/vtkfreetype/src/base/ftpic.c:21:10: error: expected "FILENAME" or <FILENAME>
:info:build #include FT_INTERNAL_OBJECTS_H
:info:build          ^

Seems vtk5 is having trouble locating freetype...

[bricklemacho@…]

The strange thing is that when I download vtk5.10.1 source from kitware it builds fine.

tar -zxvf vtk-5.10.1.tar.gz
cd vtk5.10.1
cmake .
make

Is is something to do with paths? The kitware version building as normal user, and macports version is being built as a privileged user via sudo?

[bricklemacho@…]

Although I have followed the migrations steps, I am experiencing other strange port behaviour. I am at the frontier on my knowledge in fixing/diagnosing Macport issues, not sure what else to try. I am going to do a fresh/clean/new install of Macports, hopefully that sorts a few thing out (although others are reporting problems form clean install). Note to self, don't be in a rush to upgrade the OS. Can close this ticket if you like.

[locober@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

I was experiencing a different build failure with vtk5, which was fixed by r112944 (see #41142). Please wait 30 minutes then run "sudo port clean vtk5" and "sudo port selfupdate" and see if your build failures are fixed as well.

[bernard-giroux (Bernard Giroux)]

Replying to ryandesign@…:

I was experiencing a different build failure with vtk5, which was fixed by r112944 (see #41142). Please wait 30 minutes then run "sudo port clean vtk5" and "sudo port selfupdate" and see if your build failures are fixed as well.

Still no luck. I get the same message at the end of the log file:

:info:build [  6%] Built target vtksqlite
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_vtk5/vtk5/work/VTK5.10.1'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_vtk5/vtk5/work/VTK5.10.1'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_vtk5/vtk5/work/VTK5.10.1" && /usr/bin/make -j16 -w all 
:info:build Exit code: 2
:error:build org.macports.build for port vtk5 returned: command execution failed
:debug:build Error code: CHILDSTATUS 14675 2
:debug:build Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: targets not executed for vtk5: org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Please see the log file for port vtk5 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_vtk5/vtk5/main.log

[ryandesign (Ryan Carsten Schmidt)]

Could you attach the new main.log file? The relevant portion is before the portion you pasted.

[ryandesign (Ryan Carsten Schmidt)]

Ok, same error as before. Unfortunately I cannot reproduce it on my system and I don't know what else to suggest.

[ryandesign (Ryan Carsten Schmidt)]

I can reproduce it now. The problem is that the freetype port's /opt/local/include/ft2build.h file was being included instead of the older local copy being built by vtk5, causing the build failure. A local change I had made to MacPorts base (#40656) was correcting the problem. So until we commit that change to base and release a new version of base, we need a local fix in the vtk5 portfile.

[ryandesign (Ryan Carsten Schmidt)]

Should be fixed in r112958.

[bernard-giroux (Bernard Giroux)]

Replying to ryandesign@…:

Should be fixed in r112958.

Success! Many thanks