Opened 10 years ago
Last modified 6 months ago
#46890 new defect
vtk @6.1.0 build fails on G4, Leopard
Reported by: | zzanderr | Owned by: | stromnov (Andrey Stromnov) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | leopard powerpc | Cc: | cooljeanius (Eric Gallager), Dave-Allured (Dave Allured) |
Port: | vtk |
Description
The log file is attached. Directly before the first error is the line
:info:build cc1plus: error: /usr/lib/libIOKit.dylib: not a directory
My first thought was that I was in deep trouble...what happened to libIOKit.dylib??!! Why is this machine even running? Heart in throat, I determined that, indeed, libIOKit.dylib was in /usr/lib. I re-read the log's error lines more carefully and was struck by the words "not a directory". Well, of course not....
I decided that I was taunting fortune attempting an upgrade to a new major version while still on a PPC. So back to vtk5.
Out of curiousity, I read the port files for both versions and found the block:
if {${os.major} <= 10} { configure.args-append \ -DIOKit:FILEPATH=/System/Library/Frameworks/IOKit.framework }
in vtk5's Portfile. I edited vtk's (@6.1.0) Portfile, restarted the build and went to bed. This morning, a pleasant surprise--vtk had built! (I really wasn't expecting this to work, and I give full credit to the author(s) of vtk5's portfile.)
Do note, that I have not tested vtk yet, but I suppose this is a step forward.
Attachments (1)
Change History (7)
Changed 10 years ago by zzanderr
Attachment: | vtk_main.log.bz2 added |
---|
comment:1 Changed 10 years ago by zzanderr
comment:2 Changed 10 years ago by mf2k (Frank Schima)
Cc: | stromnov@… removed |
---|---|
Keywords: | leopard powerpc added |
Owner: | changed from macports-tickets@… to stromnov@… |
Port: | @6.1.0 removed |
comment:3 Changed 2 years ago by cooljeanius (Eric Gallager)
Cc: | cooljeanius added |
---|
comment:4 follow-up: 5 Changed 6 months ago by barracuda156
Upstream got upset that it worked for someone and they took care to have it broken for sure, hardcoding the target to 10.7.
comment:5 Changed 6 months ago by cooljeanius (Eric Gallager)
Replying to barracuda156:
Upstream got upset that it worked for someone and they took care to have it broken for sure, hardcoding the target to 10.7.
Link to where this happened?
comment:6 Changed 6 months ago by Dave-Allured (Dave Allured)
Cc: | Dave-Allured added |
---|
Will send log for successful build on request. It's big.