New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #29782 (closed defect: invalid)

Opened 2 years ago

Last modified 2 years ago

py27-numpy: ld: library not found for -lgfortran

Reported by: rrykim@… Owned by: ram@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: ryandesign@…
Port: py27-numpy

Description (last modified by ryandesign@…) (diff)

I'm using 2011 Macbook Pro (i5 2.3GHz) Xcode 3.2.6 installed.

py27-numpy failed to build with a message

Building py27-numpy
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for py27-numpy is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py27-numpy/main.log

Please see the attached file.

Attachments

main.log (43.2 KB) - added by rrykim@… 2 years ago.

Change History

Changed 2 years ago by rrykim@…

comment:1 Changed 2 years ago by ryandesign@…

  • Keywords py27-numpy removed
  • Owner changed from macports-tickets@… to ram@…
  • Description modified (diff)

Has duplicate #29781.

comment:2 Changed 2 years ago by ryandesign@…

  • Cc ryandesign@… added
  • Summary changed from py27-numpy build failure to py27-numpy: ld: library not found for -lgfortran

The relevant error seems to be:

ld: library not found for -lgfortran

libgfortran.dylib is supposed to be provided by the gcc port applicable to the gcc variant you selected. For example if you selected (or MacPorts automatically selected) the gcc44 variant, then it should be using the libgfortran.dylib in /opt/local/lib/gcc44.

What's peculiar about your log is that it shows it found and used /usr/bin/gfortran as the fortran compiler. Where did /usr/bin/gfortran come from? It is not a part of Mac OS X or Xcode and no MacPorts port provides it. You should remove it, and anything else that went along with it. Then clean py27-numpy and try again.

comment:3 Changed 2 years ago by ryandesign@…

Looks like a duplicate of #28966, also mentioned in #26719.

comment:4 Changed 2 years ago by rrykim@…

Removed gfortran as ryandesign suggested and it works. I am still curious about where the gfortran came from?

comment:5 Changed 2 years ago by ram@…

  • Status changed from new to closed
  • Resolution set to invalid

I've seen multiple instances of /usr/bin/gfortran causing problems and have no idea where it comes from. It would be useful to find where this is coming from...

Note: See TracTickets for help on using tickets.