G77/mountain lion/xcode 4.6 help

  • Thread starter Thread starter zfisher
  • Start date Start date
AI Thread Summary
The discussion centers around the challenges faced while trying to compile code using g77 on a newly set up lab environment at UNC-CH, specifically on Mountain Lion 10.8.4. The user has successfully compiled code with gfortran but encounters errors when attempting to use g77, including warnings about macOS version compatibility and PIE (Position Independent Executable) issues. Despite acknowledging that g77 is outdated and ideally should not be used, the user is under pressure from the principal investigator and graduate students to make it work for legacy code. The user seeks assistance to resolve the compilation issues and is open to alternative support avenues. A suggestion is made to try running g77 with its full path to clarify the "no match" error encountered.
zfisher
Messages
1
Reaction score
0
First, let me state that I know g77 is no longer supported.

Second, I'm not a fortran developer, I'm simply trying to set up a lab for some grad students in the Geological Sciences department at UNC-CH.

I volunteered to help them set up there new lab with a brand new software image, including the following:

Mountain Lion 10.8.4
Xcode 4.6
Fink 0.35.1
gfortran 4.8.1 (downloaded from hpc.sourceforge.net)
g77 3.4.0 (also downloaded from hpc.sourceforge.net)
among others...

I can compile just fine with gfortran, but when I attempt to compile anything with g77 (even a simple hello.f) I receive the following error:

ld: warning: -macosx_version_min not specified, assuming 10.7
ld: warning: PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not allowed in code signed PIE, but used in __start from /usr/lib/crt1.o. To fix this warning, don't compile with -mdynamic-no-pic or link with -Wl,-no_pie

I've done a fair amount a research, but most solutions are to "stop using g77". And while I agree that that would be the ideal solution, the PI and grad students are adamant they need g77 to compile some of their older code.

FWIW, if I run: g77 hello.f [-no_pie] I receive the following response:
g77: no match.

Any help would be very much appreciated. If there is another/better avenue to request support, I'd be happy to follow those recommendations as well. I can't be the only person trying to get g77 to compile on a freshly installed copy of mountain lion, right?

Thanks so much in advance,
Zachary Fisher
Systems Administrator, UNC-Chapel Hill
 
Technology news on Phys.org
no match??

I've neither experience with g77 nor Mountain Lion, so I might not be much help, but one thing is not clear: why do you get a g77 "no match"? What happens when you run g77 with the full path (ie, /dir/to/g77 hello.f [...])?
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Thread 'Project Documentation'
Trying to package up a small bank account manager project that I have been tempering on for a while. One that is certainly worth something to me. Although I have created methods to whip up quick documents with all fields and properties. I would like something better to reference in order to express the mechanical functions. It is unclear to me about any standardized format for code documentation that exists. I have tried object orientated diagrams with shapes to try and express the...

Similar threads

Replies
1
Views
3K
Back
Top