Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#42883 closed defect (worksforme)

Problem installing py27-scipy

Reported by: david.robinson@… Owned by: seanfarley (Sean Farley)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: michaelld (Michael Dickens)
Port: py27-scipy

Description (last modified by ryandesign (Ryan Schmidt))

Can not seem to build py27-scipy - see below and attached for details

THIS IS WHAT I GET IN THE TERMINAL

Davids-MacBook-Air:~ PCUser$ sudo port install py27-scipy +gcc45
--->  Computing dependencies for py27-scipy
--->  Building py27-scipy
Error: org.macports.build for port py27-scipy returned: command execution failed
Please see the log file for port py27-scipy for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-scipy/py27-scipy/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port py27-scipy failed

Attachments (1)

main.log (75.1 KB) - added by david.robinson@… 7 years ago.

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by david.robinson@…

Attachment: main.log added

comment:1 Changed 7 years ago by ryandesign (Ryan Schmidt)

Cc: michaelld@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to sean@…
Port: py27-scipy added

Per our ticket filing guidelines, please remember to use WikiFormatting, to fill in the Port field, to Cc the maintainers of that port, and to clean and try again (this last step you should do now, and attach the new main.log file).

comment:2 Changed 7 years ago by michaelld (Michael Dickens)

Please try the following:

sudo port clean py27-scipy
sudo port selfupdate
sudo port install py27-scipy

and if that fails, then post the generated log file here.

Question: Why are you using GCC 4.5? Why not at least 4.7 if not 4.8? 4.5 is pretty old, and 4.8 is quite stable and usable. With current MacPorts, you can mix and match the +gcc4X variants between different ports if you want to; there's nothing wrong with installing this port with +gcc48 (which, by the way, is the default for most ports offering +gcc4X variants).

comment:3 Changed 7 years ago by michaelld (Michael Dickens)

Resolution: worksforme
Status: newclosed

The OP reported off-ticket that moving to +gcc48 worked. I tried building py27-scipy +gcc45, and that worked OK for me. So, I'm guessing this was a "cruft" issue that cleaning took care of. Thanks for reporting back! I'm closing this ticket as "works for me".

comment:4 Changed 7 years ago by michaelld (Michael Dickens)

Trac didn't send a "closing" email; hopefully it will with this change!

Note: See TracTickets for help on using tickets.