#41149 closed defect (fixed)
vtk5: error: expected "FILENAME" or <FILENAME>
Reported by: | bricklemacho@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | mavericks | Cc: | oliverjhahn@…, bernard-giroux (Bernard Giroux), locober@…, ryandesign (Ryan Carsten Schmidt) |
Port: | vtk5 |
Description (last modified by mf2k (Frank Schima))
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.
Attachments (2)
Change History (15)
Changed 11 years ago by bricklemacho@…
comment:1 Changed 11 years ago by oliverjhahn@…
Cc: | oliverjhahn@… added |
---|
comment:2 Changed 11 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|---|
Port: | vtk5 added; VTK5 removed |
In the future, please use WikiFormatting.
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | bernard.giroux@… added |
---|---|
Keywords: | mavericks added |
Summary: | VTK5 Compile Problems → vtk5: error: expected "FILENAME" or <FILENAME> |
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...
comment:4 Changed 11 years ago by 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?
comment:5 Changed 11 years ago by bricklemacho@…
More for completness, freetype appears to be installed correctly as the the following ports on my machine, which have freetype as a dependency, all seem to build and function fine.
---> fontconfig @2.11.0_0 ---> cairo @1.12.16_1+x11 ---> gd2 @2.1.0_3+x11 ---> ghostscript @9.10_1+x11 ---> harfbuzz @0.9.23_0 ---> poppler @0.24.2_0 ---> Xft2 @2.3.1_0 ---> ffmpeg @2.1_0+gpl2 ---> librsvg @2.36.4_2 ---> py27-pil @1.1.7_6 ---> py27-matplotlib @1.3.0_0+tkinter ---> texlive-bin @2013_3+x11 ---> graphviz @2.34.0_0+pangocairo+x11 ---> ImageMagick @6.8.7-3_0+x11 ---> dvipng @1.14_7 ---> py27-matplotlib @1.3.0_0+latex+qt4 ---> libwmf @0.2.8.4_7 ---> gimp2 @2.8.6_3+help_browser+python27 ---> poppler @0.24.3_0 ---> gimp2 @2.8.8_0+help_browser+python27
So not sure why vtk5 is having a problem. Not sure what else to do/try. All that is seems left is fresh/clean/new install of Macports.
comment:7 follow-up: 8 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
comment:8 Changed 11 years ago by 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
comment:9 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Could you attach the new main.log file? The relevant portion is before the portion you pasted.
Changed 11 years ago by bernard-giroux (Bernard Giroux)
Attachment: | main.log.bz2 added |
---|
comment:10 Changed 11 years ago by 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.
comment:11 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Status: | new → assigned |
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.
comment:12 follow-up: 13 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Should be fixed in r112958.
Cc Me!