#20002: bugs in vtk-devel Portfile on Tiger -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: dweber@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: Tiger darwin_8 | Port: vtk-devel -------------------------------+-------------------------------------------- Comment(by dweber@…): Hi Jonathan, I have no access to a Tiger platform to test any of these changes. Please advise on your solutions, if you find them to work on Tiger, so that I can then test those solutions for Leopard. There may be simple alternatives to the tar and ln bugs, but I'm not going to resolve this unless I have access to a Tiger platform. When debugging the install process, I often clean out the destroot entirely because of this error. My debug process looks something like: sudo port destroot vtk-devel +huge # examine build and destroot, revise Portfile as required sudo rm -rf ${workpath}/destroot sudo vim ${workpath}/.macports*.state # to remove destroot state sudo port -o -k -d destroot vtk-devel +huge The -o option avoids an entire rebuild just because the Portfile changed. Of course, if you change build settings or something, then you may want to rebuild. For the most part, the debug process has to tweak the destroot (vtk usually compiles OK). The -k option is just there to 'keep' the build. I leave it in the command line just in case I change the destroot to an install command (my macports config does a clean after an install). The parallel build option was explored. It does work sometimes, but it can fail for no reason sometimes. For the sake of reliability over speed, the option was omitted. Note that the macports config file must be modified from default settings for this take any effect anyway. Take care, Darren PS, Leaving this ticket open, pending further advice on a possible fix for Tiger. -- Ticket URL: <http://trac.macports.org/ticket/20002#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS