[MacPorts] #16405: pike make fails errors
#16405: pike make fails errors ----------------------------------+----------------------------------------- Reporter: warren@warrensweb.us | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: pike failed build | ----------------------------------+----------------------------------------- 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 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 Error: Status 1 encountered during processing. -- Ticket URL: <http://trac.macports.org/ticket/16405> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16405: pike make fails errors -----------------------------------+---------------------------------------- Reporter: warren@warrensweb.us | Owner: exodusd@gmx.de Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: pike failed build -----------------------------------+---------------------------------------- Changes (by blb@macports.org): * owner: macports-tickets@lists.macosforge.org => exodusd@gmx.de Comment: Assigning to maintainer. -- Ticket URL: <http://trac.macports.org/ticket/16405#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16405: pike make fails errors -----------------------------------+---------------------------------------- Reporter: warren@warrensweb.us | Owner: exodusd@gmx.de Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: pike failed build -----------------------------------+---------------------------------------- Comment(by warren@warrensweb.us): Replying to [comment:1 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? -- Ticket URL: <http://trac.macports.org/ticket/16405#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16405: pike make fails errors -----------------------------------+---------------------------------------- Reporter: warren@warrensweb.us | Owner: exodusd@gmx.de Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: pike failed build -----------------------------------+---------------------------------------- Comment(by jmr@macports.org): Replying to [comment:2 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. -- Ticket URL: <http://trac.macports.org/ticket/16405#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16405: pike make fails errors ----------------------------------+----------------------------------------- Reporter: warren@… | Owner: exodusd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | Port: pike ----------------------------------+----------------------------------------- Changes (by jmr@…): * keywords: pike failed build => * port: => pike Old description:
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
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
Error: Status 1 encountered during processing.
New description: 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 -- -- Ticket URL: <https://trac.macports.org/ticket/16405#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16405: pike make fails errors -----------------------------------+---------------------------------------- Reporter: warren@… | Owner: exodusd@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: worksforme | Keywords: Port: pike | -----------------------------------+---------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => worksforme Comment: I can't reproduce this on a G5 running the current versions of Leopard, Xcode and MacPorts. -- Ticket URL: <https://trac.macports.org/ticket/16405#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts