From: "H. J. Lu" <hjl@lucon.org>
To: Andrew Haley <aph@redhat.com>
Cc: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PATCH: Build shared libraries with -Bsymbolic-functions
Date: Fri, 12 Jan 2007 14:40:00 -0000 [thread overview]
Message-ID: <20070112144003.GB4255@lucon.org> (raw)
In-Reply-To: <17831.31575.451392.28599@zebedee.pink>
On Fri, Jan 12, 2007 at 12:13:11PM +0000, Andrew Haley wrote:
> H. J. Lu writes:
> > On Thu, Jan 11, 2007 at 07:33:21PM +0100, Paolo Bonzini wrote:
> > >
> > > >config/
> > > >
> > > >2007-01-10 H.J. Lu <hongjiu.lu@intel.com>
> > > >
> > > > * ld-symbolic.m4: New.
> > >
> > > Please name the macro AC_LIB_PROG_LD_GNU_SYMBOLIC, or
> > > ACX_PROG_LD_GNU_SYMBOLIC.
> > >
> > > >libgfortran/
> > > >
> > > >2007-01-10 H.J. Lu <hongjiu.lu@intel.com>
> > > >
> > > > * aclocal.m4: Include ../config/lib-ld.m4 and
> > > > ../config/ld-symbolic.m4.
> > >
> > > Also, aclocal.m4 is automatically generated with "aclocal -I ../config"
> > > except in libjava.
> > >
> > > > * configure.ac: Use PROG_LD_GNU_SYMBOLIC. Set
> > > > libgcj_ld_symbolic to $SYMBOLIC_LDFLAGS if it isn't set.
> > >
> > > Please check if libgcj_ld_symbolic is now obsolete in
> > > libjava/configure.host.
> >
> > libjava will use -Bsymbolic on Linux, which is more aggresive than
> > -Bsymbol-functions.
>
> libjava doesn't use -Bsymbolic for all of its libraries, just for
> libgij, libjvm, and libawt. I'd use -Bsymbolic for libgcj as well,
> but (because of copy relocs) we'd have to compile all gcj executables
> -fpic.
>
> I presume your patch doesn't change this behaviour.
I didn't realized that. I will update my patch to build
libgcj with -Bsymbol-functions. You don't need to compile any
gcj executables with -fpic.
H.J.
prev parent reply other threads:[~2007-01-12 14:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17827.39608.578446.917969@zebedee.pink>
[not found] ` <20070109134100.GA17596@lucon.org>
[not found] ` <17827.40388.768818.387227@zebedee.pink>
[not found] ` <20070109135627.GA24284@lucon.org>
[not found] ` <17827.41041.498443.221842@zebedee.pink>
[not found] ` <20070109141819.GA4072@lucon.org>
[not found] ` <20070109174240.GA31750@lucon.org>
[not found] ` <20070109192047.GA32254@lucon.org>
[not found] ` <20070110142929.GA22520@lucon.org>
[not found] ` <m3tzyzqaha.fsf@localhost.localdomain>
2007-01-10 19:03 ` H. J. Lu
2007-01-10 22:49 ` H. J. Lu
2007-01-11 8:04 ` Paolo Bonzini
2007-01-11 18:15 ` H. J. Lu
2007-01-11 18:33 ` Paolo Bonzini
2007-01-11 20:09 ` H. J. Lu
2007-01-12 7:57 ` Paolo Bonzini
2007-01-12 14:39 ` H. J. Lu
2007-01-12 18:52 ` H. J. Lu
2007-01-13 13:48 ` Paolo Bonzini
2007-01-13 14:51 ` H. J. Lu
2007-01-13 17:12 ` Andrew Pinski
2007-01-13 17:32 ` H. J. Lu
2007-01-14 13:04 ` Andrew Haley
2007-01-14 15:46 ` H. J. Lu
2007-01-14 18:29 ` Andrew Pinski
2007-01-14 18:47 ` H. J. Lu
2007-01-31 22:20 ` H. J. Lu
2007-01-31 22:24 ` Andrew Pinski
2007-01-31 22:42 ` H. J. Lu
2007-02-10 23:28 ` H. J. Lu
2007-02-11 9:09 ` Andrew Pinski
2007-01-12 12:13 ` Andrew Haley
2007-01-12 14:40 ` H. J. Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070112144003.GB4255@lucon.org \
--to=hjl@lucon.org \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=paolo.bonzini@lu.unisi.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).