David R. Morrison writes: > I suppose you are using the updated Developer Tools? There is a problem > with fort77 and the new tools. As it says on Fink's homepage, users > are advised not to update their developer tools, or if they do, to be > sure and run "sudo gcc_select 3" before using fink to compile packages. > > The problem with fort77 might actually lie in f2c, so you may need to go > back and recompile various things to get fort77 to work.
Yes, I did update my developer tools because there was no way to compile clisp with gcc 3.1. So my currently selected gcc compiler indeed is 3.3. Jeffrey S Whitaker writes: > > Pascal: If you installed the gcc3.3 update, "sudo /usr/sbin/gcc_select > 3.1" and rebuild f2c and fort77. If you haven't installed gcc 3.3, I have > no idea what's wrong. Ok, so some fink packages need 3.3, other need 3.1 (or is it 2.95.2?). Perhaps it would be possible for fink to select the right compiler for each package? > On Mon, 29 Sep 2003, Pascal Bourguignon wrote: > > > fort77 can't be compiled. > > > > Is there a way to know what package needs it? > > netcdf needs it. I don't think there are any others. I think it is the > f2c package that is broken by the gcc 3.3 update however, not fort77. -- __Pascal_Bourguignon__ http://www.informatimago.com/ Do not adjust your mind, there is a fault in reality. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
