Re: Running ranlib after installation - okay or not?

[Peter O'Gorman <peter at pogma dot com>]

Gerald Pfeifer wrote:
> On Sun, 4 Sep 2005, Peter O'Gorman wrote:
>
> > | We currently perform the following sequence of commands as part of the
> > | installation (-m 444 being the default on current FreeBSD systems).
> > I can not see where freebsd could be getting a -m 444 from. The libraries
> > are always installed with INSTALL_DATA and gcc's aclocal.m4 always sets that
> > to INSTALL_DATA='${INSTALL} -m 644' if it is otherwise unset.
> >
> > Do have an INSTALL_DATA var set in your environment?
>
>
> The FreeBSD ports system (/usr/share/mk/bsd.port.mk) indeed sets
>
>   INSTALL_DATA= \
>         ${INSTALL} ${COPY} ${_SHROWNGRP} -m ${SHAREMODE}
>
> and SHAREMODE is set to 444 (in /usr/share/mk/bsd.own.mk).
>
> Which does make sense, in general, but breaks ranlib without your fix.

I posted a patch that nobody has had time to look at for this, even if it is 
not acceptable (it would probably be better if it reset the permissions 
after calling ranlib) I'd appreciate some feedback :)

<http://gcc.gnu.org/ml/gcc-patches/2005-09/msg00201.html>

Peter