From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Arnaud Charlet <charlet@adacore.com>,
Rafael Espindola <espindola@google.com>,
Basile STARYNKEVITCH <basile@starynkevitch.net>,
GCC Mailing List <gcc@gcc.gnu.org>,
Diego Novillo <dnovillo@google.com>
Subject: Re: plugin issues to fix (or document) before 4.5 release
Date: Thu, 03 Dec 2009 22:12:00 -0000 [thread overview]
Message-ID: <4B183B92.5050107@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0912032101180.12495@digraph.polyomino.org.uk>
Joseph S. Myers wrote:
> On Thu, 3 Dec 2009, Arnaud Charlet wrote:
>
>>> Are rpaths as portable as shared libraries or do we support a host
>>> architecture that has shared libraries but no equivalent to rpath?
>> Windows (mingw) comes to mind at least.
>
> If the hypothetical libiberty.dll were only used by cc1 etc. (not by the
> driver), putting it in the same directory as cc1, libexecsubdir, where
> Windows would expect to find it, should work to allow separate copies for
> each GCC install. Though I prefer the --whole-archive approach (with a
> fallback of adding references to libiberty symbols or extracting the .o
> files if we wish to support plugins on hosts without --whole-archive or
> equivalent).
Has anyone tested plugins on windows yet? (I haven't, but I'll find some
time to give it a bit of basic testing during stage 4.)
cheers,
DaveK
next prev parent reply other threads:[~2009-12-03 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 6:05 Basile STARYNKEVITCH
2009-12-02 22:17 ` Rafael Espindola
2009-12-03 7:37 ` Arnaud Charlet
2009-12-03 8:42 ` Dave Korn
2009-12-03 21:03 ` Joseph S. Myers
2009-12-03 22:12 ` Dave Korn [this message]
2009-12-03 22:16 ` Kai Tietz
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=4B183B92.5050107@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=basile@starynkevitch.net \
--cc=charlet@adacore.com \
--cc=dnovillo@google.com \
--cc=espindola@google.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).