This is the mail archive of the
mailing list for the binutils project.
Re: [PATCH] Disable all target libraries if not building gcc
- From: Joseph Myers <joseph at codesourcery dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 16 Mar 2015 23:41:41 +0000
- Subject: Re: [PATCH] Disable all target libraries if not building gcc
- Authentication-results: sourceware.org; auth=none
- References: <20150313200654 dot GA32326 at intel dot com> <alpine dot DEB dot 2 dot 10 dot 1503162247470 dot 30120 at digraph dot polyomino dot org dot uk> <CAMe9rOquPr5VeJKQhyLX32JmBxj1bW1ub49m6-M-Rbruaj=XXg at mail dot gmail dot com>
On Mon, 16 Mar 2015, H.J. Lu wrote:
> On Mon, Mar 16, 2015 at 3:50 PM, Joseph Myers <email@example.com> wrote:
> > On Fri, 13 Mar 2015, H.J. Lu wrote:
> >> I am working on SHF_COMPRESSED support:
> >> http://www.sco.com/developers/gabi/latest/ch4.sheader.html
> >> I will import zlib from GCC source tree into binutils-gdb tree. But zlib
> >> failed to build as a target library in binutils-gdb. There is no need to
> >> build target libraries if not building gcc. OK for master?
> > This is definitely wrong. newlib / libgloss is a target library that
> > certainly makes sense to build separately from GCC, and the toplevel
> > configure / build code should be identical in all three repositories (GCC,
> > binutils-gdb, newlib-cygwin).
> We need to work out something to avoid building target libraries
> in binutils.
I suggest not building zlib as a target library unless libgcj is also
being built as a target library, given that there should be no need to
built it as a target library in isolation.
It can be useful to build even GCC's target libraries when not building
GCC (for example, rebuilding them with different optimization options
using an installed compiler) - for libraries that don't use the host-side
tm.h (all except libgcc and libobjc, I think), this is practical.
Joseph S. Myers