Date: Wed, 16 Dec 1998 13:46:44 -0800 (PST) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: mike@smith.net.au (Mike Smith) Cc: bdodson@beowulf.utmb.edu, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: sysinstall Message-ID: <199812162146.NAA75754@troutmask.apl.washington.edu> In-Reply-To: <199812161708.JAA00347@dingo.cdrom.com> from Mike Smith at "Dec 16, 1998 9: 8:51 am"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Mike Smith: > > Mike Smith writes: > > > Can you clarify for us why having g77 in the base system, rather than > > > an easily-installable and easily-upgradeable port would be worthwhile? > > > > > > Our current drive is to increase, not decrease, the modularity of the > > > system where possible; an addition like this would have to have a > > > compelling justification that was key to the system's functionality to > > > be considered. > > > > I'm absolutely sympathetic with a desire for modularity. The > > problem is specific to g77 (and, possibly, to other of the > > optional gnu compilers). You can't just install g77; you have to > > take, at least, a custom version of gcc along with it. That > > means that you have to juggle your path in order to pick up the > > correct versions of everything. Let me point out that people > > using this compiler are not likely to be as knowledgable as your > > ordinary "hackers" subscriber. I have had success getting things > > done in spite of this behavior, but it is a royal PITA. Not to > > mention the possible differences in code generation between the > > system gcc and the g77-specific gcc. > > I beg to differ; if you look at the current g77 port, it contains two > files: bin/g77 and libexec/f771. With the port's bin directory on your > path, 'g77' suffices to compile Fortran code as expected, and there are > no other changes to the compilation of other code. No path juggling is > required, nor anything that is beyond anyone that is already using any > other port. lang/g77 is version 0.5.19.1 The current version is 0.5.23 with 0.5.24 in the pipeline. Unfortunately, g77 as a frontend to th FSF backend has some knowledge of the backend, and g77+0.5.23 may only work with gcc+2.8.x. g77 no longer uses libf2c as its runtime library. You need to include the new libg77 in your path. [snippage] > I can't bear witness to this; I've deployed the 'g77' port for a number > of customers now with no effort whatsoever, usually just pkg_adding the > package and then forgetting about it. Tell your customers to run "finger -l fortran@gnu.org | more" > The port *is* currently marked > BROKEN, which would indicate that it's crying out for a Fortran-using > maintainer to step in and fix it, but there's nothing fundamentally > wrong with it in its current organisation AFAICT. > finger -l fortran@gnu.org | more Seek to BETA. - Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812162146.NAA75754>