[Bug fortran/13082] Function entries and entries with alternate returns not implemented
--- Additional Comments From fca at mail dot cern dot ch 2005-04-08 07:14 --- Subject: Re: Function entries and entries with alternate returns not implemented Dear All, I think that the tone of the conversation is evolving in the wrong direction (I might have been partially responsible for it). Now the situation is the following: - There is a large community that needs FORTRAN (77 + 95). There is a widespread attitude that FORTRAN is dead. I do not agree, however, if it was true, the millions lines of legacy FORTRAN that people need are far from dead. - g77, after some pain and suffering, evolved to be a reasonable FORTRAN compiler. Now we suddenly (at least me) learn that it will not be maintained any more. Which means that it is dead. May be not yet, but it is clear that we cannot expect it to be around for a long time for Linux. For those using Mac's the situation is even more serious because Tiger will come out with gcc4. - We tried out the designed successor and found it very immature. In fact it is not even a proper FORTRAN compiler because it does not implement the standard. Then we started the usual interaction with the developers. And here things started to degrade. On one side we ignored how thin is this group of developers. So we were a bit demanding in our approach. On the other side the developers gave us the impression to not understand how serious the situation is for us. - The moral of the story is that the developers need some help, which I cannot provide, because I am not a compiler expert (!). However I imagine that there must be some people out there that have the knowledge and the ability to react to the save the gcc suite! cry. So I would suggest to activate our contacts and to find out if someone has the possibility to look into gFortran and provide some patches for the problems that are high priority for us. Of course this requires some good will from the developers to check and introduce these patches. - Last but not least I wonder if the g95 split is really definitive. The community would profit enormously from this split to be mended. My personal experience in this kind of business makes me rather pessimist. Let me know if it makes sense to you. Best regards, Federico On Fri, 8 Apr 2005, kargl at gcc dot gnu dot org wrote: --- Additional Comments From kargl at gcc dot gnu dot org 2005-04-08 01:21 --- (In reply to comment #25) I do not understand your tone. There is a compiler, g77, which works and implements at least the Fortran 77 standard. I don't see any reason why it should be replaced in the distribution by a compiler which is not yet mature enough to implement the same standard. Are you aware of the fact that g77 *is completely* broken with respect to the gcc-4.x branch? There is no one who is going to fix the problem because the effort to fix g77 is estimated to be equilavent to implementing an actually F95 compiler. The attitude expressed in piss off the people who owe you nothing can be very bad for the future of Linux. I don't use linux. Never have, never will. I use FreeBSD on an AMD64 platform where there are no commercially available F95 compilers. I have zero compiler writing experience, yet you'll find that I've contributed 69 patches to make gfortran work. Those patches came about because I need a compiler, and I decided to contribute something to GCC other than whining and making disparaging remarks. I don't know about my fellow contributors, but I find that I have little motivation to continue to work on gfortran occur when indivudals come here to tell us that gfortran is useless. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13082
[Bug fortran/20587] gcc-4_0 from head does not build on Panther
--- Additional Comments From fca at mail dot cern dot ch 2005-03-23 15:08 --- Subject: Re: gcc-4_0 from head does not build on Panther Hello, this bug should be closed, it was my error and I apologise for that. I had the gnu intl lib in /usr/local/lib. Apparently configure was probing this one, finding the libintl_XXX entries. At link time it was the library in /sw/lib that was picked up. One may argue that there is some inconsistency in configure, but my system was a bit messy too. Best regards, Federico On Tue, 22 Mar 2005, Federico Carminati wrote: What kills the build is not the duplicate entry, but the fact that libintl_dgettext libintl_bindtextdomain are undefined. The reference is generated inside gcc, exactly in the file intl/libgnuintl.h at lines 142 and 265. On Mac gnu internationalisation routines are created without the libintl_ prefix. Somehow the configure should find this out and act correspondingly. Fed On Tue, 22 Mar 2005, pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-22 16:40 --- Just remove the intl library, or set the DYLD_LIBRARY_PATH to include /sw/lib. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20587
[Bug fortran/20587] gcc-4_0 from head does not build on Panther
--- Additional Comments From fca at mail dot cern dot ch 2005-03-22 16:51 --- Subject: Re: gcc-4_0 from head does not build on Panther What kills the build is not the duplicate entry, but the fact that libintl_dgettext libintl_bindtextdomain are undefined. The reference is generated inside gcc, exactly in the file intl/libgnuintl.h at lines 142 and 265. On Mac gnu internationalisation routines are created without the libintl_ prefix. Somehow the configure should find this out and act correspondingly. Fed On Tue, 22 Mar 2005, pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-22 16:40 --- Just remove the intl library, or set the DYLD_LIBRARY_PATH to include /sw/lib. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20587
[Bug fortran/20500] f95 build fails on MacOSX 10.4 Tiger
--- Additional Comments From fca at mail dot cern dot ch 2005-03-17 17:49 --- Subject: Re: f95 build fails on MacOSX 10.4 Tiger Hello, it is now failing with the following error. Any hint? Regards, Fed mkdir .libs /usr/local/gcc-4_0/build/gcc/xgcc -B/usr/local/gcc-4_0/build/gcc/ -B/usr/local/powerpc-apple-darwin8.0.0/bin/ -B/usr/local/powerpc-apple-darwin8.0.0/lib/ -isystem /usr/local/powerpc-apple-darwin8.0.0/include -isystem /usr/local/powerpc-apple-darwin8.0.0/sys-include -DHAVE_CONFIG_H -I. -I../../../libgfortran -I. -iquote../../../libgfortran/io -std=gnu99 -O2 -g -O2 -c ../../../libgfortran/runtime/environ.c -fno-common -DPIC -o .libs/environ.o In file included from ../../../libgfortran/runtime/environ.c:35: ../../../libgfortran/libgfortran.h:63: error: conflicting types for 'int8_t' /usr/include/ppc/types.h:72: error: previous declaration of 'int8_t' was here make[2]: *** [environ.lo] Error 1 make[1]: *** [all] Error 2 make: *** [all-target-libgfortran] Error 2 On Thu, 17 Mar 2005, Federico Carminati wrote: I was not complaining at all!! I know I am in uncharted land for the moment. It is churning away and I will let you know how it goes. Thanks for your help. Fed On Thu, 17 Mar 2005, pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-17 07:06 --- (In reply to comment #4) Subject: Re: f95 build fails on MacOSX 10.4 Tiger Hello, I rerun everything once more. The problem changed but now is reproducible. When you are in /usr/local/gcc-4_0/build/powerpc-apple-darwin8.0.0/ppc64/libgfortran Oh, well considering darwin 8.0 (aka Tiger) is no released yet, what do you expect. Anyways the correct way is to do --disable-multilib as you found out. There is no way around this right now and is the expected way. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20500
[Bug fortran/20500] f95 build fails on MacOSX 10.4 Tiger
--- Additional Comments From fca at mail dot cern dot ch 2005-03-16 18:54 --- Subject: Re: f95 build fails on MacOSX 10.4 Tiger Thanks a lot. It goes further and then it fails with make[4]: *** No rule to make target `all'. Stop. make[3]: *** [multi-do] Error 1 make[2]: *** [all-multi] Error 2 make[1]: *** [all] Error 2 make: *** [all-target-libgfortran] Error 2 Best regards, Federico On Wed, 16 Mar 2005, pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-16 17:59 --- Don't build in the source directory it is known to be broken. This is a dup of bug 17383. *** This bug has been marked as a duplicate of 17383 *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20500
[Bug fortran/20500] f95 build fails on MacOSX 10.4 Tiger
--- Additional Comments From fca at mail dot cern dot ch 2005-03-17 07:00 --- Subject: Re: f95 build fails on MacOSX 10.4 Tiger Hello, I rerun everything once more. The problem changed but now is reproducible. When you are in /usr/local/gcc-4_0/build/powerpc-apple-darwin8.0.0/ppc64/libgfortran the option --enable-multilib is on by default. The configure script checks that you can create an executable and run it. This works for the normal compilation, but not for the compilation with -m664. Trouble is that I do not have a ppc664 but a ppc750, so there may even be a mistake in identifying my cpu. In any case I am trying now with --disable-multilib, but it seems to me that there is something to be fixed. Best regards, Federico Carminati On Thu, 17 Mar 2005, pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-17 00:00 --- (In reply to comment #2) Subject: Re: f95 build fails on MacOSX 10.4 Tiger Thanks a lot. It goes further and then it fails with make[4]: *** No rule to make target `all'. Stop. make[3]: *** [multi-do] Error 1 make[2]: *** [all-multi] Error 2 make[1]: *** [all] Error 2 make: *** [all-target-libgfortran] Error 2 Read the instruction at http://gcc.gnu.org/install/ Also make sure that you downloaded all of the directories. You might need to do a download it again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20500
[Bug fortran/20500] f95 build fails on MacOSX 10.4 Tiger
--- Additional Comments From fca at mail dot cern dot ch 2005-03-17 07:09 --- Subject: Re: f95 build fails on MacOSX 10.4 Tiger I was not complaining at all!! I know I am in uncharted land for the moment. It is churning away and I will let you know how it goes. Thanks for your help. Fed On Thu, 17 Mar 2005, pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-17 07:06 --- (In reply to comment #4) Subject: Re: f95 build fails on MacOSX 10.4 Tiger Hello, I rerun everything once more. The problem changed but now is reproducible. When you are in /usr/local/gcc-4_0/build/powerpc-apple-darwin8.0.0/ppc64/libgfortran Oh, well considering darwin 8.0 (aka Tiger) is no released yet, what do you expect. Anyways the correct way is to do --disable-multilib as you found out. There is no way around this right now and is the expected way. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20500
