From: Charles Wilson <libtool@cwilson.fastmail.fm>
To: Steve Ellcey <sje@cup.hp.com>
Cc: dave.korn@artimi.com, binutils@sourceware.org,
gcc-patches@gcc.gnu.org, gdb-patches@gcc.gnu.org,
newlib@sourceware.org, Ralf.Wildenhues@gmx.de,
aoliva@redhat.com, bonzini@gnu.org, fxcoudert@gmail.com,
schwab@suse.de
Subject: Re: Final(?) patch to update libtool in GCC and src trees
Date: Wed, 11 Apr 2007 02:38:00 -0000 [thread overview]
Message-ID: <461C49E6.6090706@cwilson.fastmail.fm> (raw)
In-Reply-To: <200704102006.NAA21177@hpsje.cup.hp.com>
Steve Ellcey wrote:
>> I appreciate the problem, but Cygwin can be a bit 'special' when it comes to
>> libtool; if it hasn't been done yet, can you possibly bear to hold off a bit
>> while I give it some hasty testing? (By 'a bit', I mean no more than say
>> 'overnight'). Sorry to be a pain :-/
>
> I can wait, especially since no one has given me the go ahead yet. :-)
> I know of no cygwin testing that has been done.
Sorry -- I was starting to do some testing, but got distracted by some
side issues:
(1) building libbfd/libopcodes as DLL on windows (with the new
libtool support). This is related to:
(2) using the new libtool to build libiberty
Warning on #2: I dug up an old (gcc-patches mailing list, circa Oct
2004) attempt at this, and used it with some limited success. However,
there are /issues/ with making libiberty into a libtoolized
"convenience" library. See this thread:
[RFC] New library "type" needed?
http://lists.gnu.org/archive/html/libtool/2007-03/msg00022.html
especially the final post:
Simultaneous pic and non-pic convenience libs [Was: [RFC] New library..]
http://lists.gnu.org/archive/html/libtool/2007-03/msg00038.html
I'll rip that failed experiment out of my tree and try again with just
Steve's patches; however I'd imagine Dave Korn will have results before
I do.
--
Chuck
next prev parent reply other threads:[~2007-04-11 2:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 18:25 Steve Ellcey
2007-04-10 18:42 ` Andrew Pinski
2007-04-10 20:04 ` Steve Ellcey
2007-04-10 20:02 ` Dave Korn
2007-04-10 20:07 ` Steve Ellcey
2007-04-10 20:58 ` Dave Korn
2007-04-11 1:13 ` Dave Korn
2007-04-11 7:36 ` Paolo Bonzini
2007-04-11 8:47 ` Andreas Schwab
2007-04-11 8:51 ` Paolo Bonzini
2007-04-11 8:57 ` Ralf Wildenhues
2007-04-11 8:59 ` Paolo Bonzini
2007-04-11 9:23 ` Dave Korn
2007-04-11 9:25 ` Paolo Bonzini
2007-04-11 10:00 ` Dave Korn
2007-04-11 10:19 ` Paolo Bonzini
2007-04-11 21:41 ` Christopher Faylor
2007-04-12 10:42 ` Dave Korn
2007-04-11 2:38 ` Charles Wilson [this message]
2007-04-12 6:36 ` Charles Wilson
2007-04-12 7:03 ` Paolo Bonzini
2007-04-12 15:13 ` Steve Ellcey
2007-04-12 18:02 ` Charles Wilson
2007-04-13 7:18 ` Paolo Bonzini
2007-04-13 17:27 ` Steve Ellcey
2007-04-13 18:05 ` Daniel Jacobowitz
2007-04-13 18:18 ` Paolo Bonzini
2007-04-13 18:27 ` Steve Ellcey
2007-04-13 18:38 ` Paolo Bonzini
2007-04-13 18:44 ` Steve Ellcey
2007-04-13 20:19 ` Charles Wilson
2007-04-13 18:24 ` Paolo Bonzini
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=461C49E6.6090706@cwilson.fastmail.fm \
--to=libtool@cwilson.fastmail.fm \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=dave.korn@artimi.com \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=newlib@sourceware.org \
--cc=schwab@suse.de \
--cc=sje@cup.hp.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