This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Running ranlib after installation - okay or not?


> 
> This is a multi-part message in MIME format.
> --------------070507080009000805030905
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This patch always does a chmod 644 on static libraries prior to running
> ranlib, so the ranlib will not fail due to lack of permssions.
> 
> The libtool bits are already in upstream libtool.
> 
> Tested by running make install and visually checking the log to make sure
> that there was a chmod before every ranlib.
> 
> There are a bunch of separate ChangeLog entries, because each file touched
> is in a different dir.
> 
> Why does classpath have its own libtool?
Because classpath is in an almost direct import from upstream.
There are a few changes to the sources but not a lot.
If you want to see what get changed from the upstream see
libjava/HACKING.

The libtool in classpath is not used while build libgcj.  It is
used while building classpath when it is built seperately.

-- Pinski


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]