On Sep 17, 2012, at 00:34, Frank J. R. Hanstick wrote:
When upgrading outdated, I ran into this error:\
I don't see an actual error message in the output you posted. Perhaps the real
error is earlier.
What do you need gcc42 for? It's very old; we're planning to delete it soon:
Is this another manifestation of the current problem with ld64?
Greg Shenaut
On Sep 17, 2012, at 6:06 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 17, 2012, at 00:34, Frank J. R. Hanstick wrote:
When upgrading outdated, I ran into this error:\
I don't see an actual error
On Sep 17, 2012, at 08:21, Gregory Shenaut wrote:
On Sep 17, 2012, at 6:06 AM, Ryan Schmidt wrote:
I don't see an actual error message in the output you posted. Perhaps the
real error is earlier.
What do you need gcc42 for? It's very old; we're planning to delete it soon:
Hello,
I am not sure what it is needed for these days, It was originally
installed to build ports requiring a more upgraded version of gcc 4.2
than that supported by Apple (that was a long time ago) and it has
been maintained since? If only the development gcc 4.2.1 is used by
MacPorts,
Hello,
When upgrading outdated, I ran into this error:\
:info:build /opt/local/bin/ranlib: file: .libs/
libgfortran.a(all_l16.o) has no symbols
:info:build /opt/local/bin/ranlib: file: .libs/
libgfortran.a(any_l16.o) has no symbols
:info:build /opt/local/bin/ranlib: file: .libs/
