Opened 16 years ago
Closed 14 years ago
#16405 closed defect (worksforme)
pike make fails errors
Reported by: | warren@… | Owned by: | exodusd@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: | pike |
Description (last modified by jmroot (Joshua Root))
install pike fails with this message ("std instruction ... _ALL option" segment repeated many times repeated many times):
tmp-add_n.s:99:std instruction is only for 64-bit implementations (not allowed without -force_cpusubtype_ALL option) make[3]: *** [add_n.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [configure] Error 1 Error: Status 1 encountered during processing.
install command was sudo port install pike +pcre +image +ttf +svg
I can get this far installing pike normally without resorting to macports but do not have the skill and knowledge to get around this and had hoped your build system would have done that for me. This is a G5 machine running 10.5.4 PPC
Change History (6)
comment:1 follow-up: 2 Changed 16 years ago by blb@…
Owner: | changed from macports-tickets@… to exodusd@… |
---|
comment:2 follow-up: 3 Changed 16 years ago by warren@…
Replying to blb@…:
Assigning to maintainer.
Thank you for your response. I'm sorry for being so stupid.... I am new to macports. The universal variant installed fine. I didn't think to try this until much later. Is there some documentation that I overlooked which would have pointed me to this at the start? Because I'm behind the times, I still think of Universal as meaning both PPC and Intel versions while a non-Universal build will be just the PPC version. Would it hold true, then, that I should select the universal variant wherever it is available to ensure a successful build on a G5 10.5 PPC?
comment:3 Changed 16 years ago by jmroot (Joshua Root)
Replying to warren@…:
Would it hold true, then, that I should select the universal variant wherever it is available to ensure a successful build on a G5 10.5 PPC?
No. If the port doesn't build without +universal, there's something wrong with it.
comment:5 Changed 14 years ago by jmroot (Joshua Root)
Description: | modified (diff) |
---|---|
Keywords: | pike failed build removed |
Port: | pike added |
comment:6 Changed 14 years ago by jmroot (Joshua Root)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I can't reproduce this on a G5 running the current versions of Leopard, Xcode and MacPorts.
Assigning to maintainer.