This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Running ranlib after installation - okay or not?
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Peter O'Gorman <peter at pogma dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 24 Sep 2005 19:40:16 +0200 (CEST)
- Subject: Re: Running ranlib after installation - okay or not?
- References: <Pine.BSF.4.62.0508311718400.22973@pulcherrima.dbai.tuwien.ac.at><431AA840.6010203@pogma.com>
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.
Gerald