On Wed, 19 Aug 1998, Zdenek Salvet wrote:

> Hello,
> 
> I have noticed  egcs-19980608 and f2c-19980516 use the same names
> for important files (the contents are different):
> /usr/pkg/bin/f77
> /usr/pkg/include/f2c.h
> /usr/pkg/lib/libf2c.a
> 
I agree that I would like to eliminate the conflict.

> I suggest to change the names 
> /usr/pkg/bin/f77 -> /usr/pkg/bin/f2c-f77 for f2c-* package
This one sounds good to me.  As far as I know the only other package this
will affect is scilab (and I haven't send-pr submitted it yet so I can fix
that).  I'll try to find some time in the next week or so to update the
f2c package.  

 > /usr/pkg/lib/libf2c.a ->
>    /usr/pkg/lib/gcc-lib/i386--netbsd/egcs-2.91.40/libf2c.a for egcs-19980516
> /usr/pkg/include/f2c.h -> /usr/pkg/lib/gcc-lib/include/f2c.h for egcs-19980516
I won't comment on this not being the egcs maintainer (or even a casual
egcs user).  Is there a reason that egcs has f2c.h and libf2c.a?  Does
this mean it also installs f2c?  If so, perhaps, egcs should not install
f2c or only do it as a "DEPEND" thing (so it causes the f2c package to
install).  


> PS. Please add -fPIC support to f2c-f77 of lang/f2c package,
ok.  Unless I get an email in the next few days saying why I shouldn't do
this when I update the f2c package, then I'll add it.
Not to ask a stupid question, but what exactly does that do?
"-fPIC  If supported for the target machine, emit position-
              independent  code,  suitable  for  dynamic linking,
              even if branches need large displacements."
I'm not sure I understand....

--Dan