Bug#2142: some small g77 problems
Dear me, First I sent a private message to the bug reporter,
thinking I'll send a decent followup later, then I wantend to
quicly give him some more info, and I sent it to the whole list!
Sorry for that, anyway, here is what I intend to say about
"the small problems":
*************
Hi,
Thanks very much for the bug-report.
I noticed myself one or two of your bugs, but I though I didn't
want to put out a new version before I knew people
were actually using it.
> From @mongo.pixar.com:debian-devel-request@Pixar.com Mon Jan 15 06:49:46 1996
> Old-Return-Path: <iwj10@cus.cam.ac.uk>
> Subject: Bug#2142: some small g77 problems
> Package: g77
> Version: 0.5.17
> Revision: 0
>
> * There are two (actually quite neat) typos in debian.control:
> Description: The GNU Frontran 77 compiler (ELF version).
> ^^^^^^^^
> Compiles Fortran 77. With this, you can debug frotran code with
> ^^^^^^^
> gdb, which isn't possible with f2c.
English spelling isnt' my strongest point. But thanks.
>
> * The documentation in /usr/doc/g77 should be gzipped, at least the file DOC
> which is over 100 kB big. This file, though ascii, looks a lot like it has
> been prepared using texinfo. Isn't there a way to get an .info file that
> could go into /usr/info?
I'll look into that. I searched for info files in the original package,
but I'll try to see if I find something again (or maybe make it)
>
> * g77 provides a libf2c lib, and so does the f2c package. I'm not sure
> whether they should `Conflict:'; they are in way complements and not
> substitutes as some code might prefer to be compiled with the one and not the
> other. Also, some packages now depend on f2c (octave does or could) so that
> they shouldn't conflict. I'm CCing this to the f2c maintainer who might want
> to comment.
In the (not yet included in the package) INSTALL file, it says
If you do have f2c on your system, you need to decide how users
of f2c will be affected by your installing g77. Since g77 is
currently designed to be object-code-compatible with f2c (with
very few, clear exceptions), users of f2c might want to combine
f2c-compiled object files with g77-compiled object files in a
single executable.
To do this, users of f2c should use the same copies of f2c.h and
libf2c.a that g77 uses (and that get built as part of g77).
This is why I installed the libf2c.a library.
I'll put the INSTALL file in the package, as it clearly seems neccecary!
But anyway, as I see it now, g77 needs libf2c, and, if I leave it out
I would have to make g77 depend on f2c, whitch I don't think is very
good eighter. So, I would like to hear the f2c's maintainer's thoughts about
this.
>
> * g77 contains /usr/bin/g++, as does gcc. Maybe g77.preinst should move an
> existinng g++ into some other name, and move it back in g77.postrm. This
> might require some more thought.
Not at all, it should be removed altoghter. This is just a plain error
on my side, not noticing that I put a g++ frontend in the package.
It has already been removed in my private version.
As it now has been proven that g77 has (at least) one user, I'll put
out a new, improved package today. (in about 12 hours from now).
--
joost witteveen
joost@rulcmc.leidenuniv.nl
joostje@dds.hacktic.nl
--
There's no substitute for reading README's.
(except for using Debian, and typing "dpkg -i package.deb").
>
>
> Anyway, thanks again for the comments,
>
> --
> joost witteveen
> joost@rulcmc.leidenuniv.nl
> joostje@dds.hacktic.nl
> --
> There's no substitute for reading README's.
> (except for using Debian, and typing "dpkg -i package.deb").
>
>
--
joost witteveen
joost@rulcmc.leidenuniv.nl
joostje@dds.hacktic.nl
--
There's no substitute for reading README's.
(except for using Debian, and typing "dpkg -i package.deb").
Reply to: