From: Eric Christopher <echristo@apple.com>
To: Andreas Tobler <toa@pop.agri.ch>
Cc: bonzini@gnu.org, Mike Stump <mrs@apple.com>,
libtool@cwilson.fastmail.fm, Steve Ellcey <sje@cup.hp.com>,
jjohnstn@redhat.com, newlib@sourceware.org, aoliva@redhat.com,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org, Peter O'Gorman <peter@pogma.com>
Subject: Re: New libtool is in the GCC and Src trees.
Date: Fri, 25 May 2007 19:39:00 -0000 [thread overview]
Message-ID: <A5FD2753-7600-475B-9645-86B6438118FF@apple.com> (raw)
In-Reply-To: <465739FA.4060409@pop.agri.ch>
On May 25, 2007, at 12:33 PM, Andreas Tobler wrote:
> Paolo Bonzini wrote:
>>> /head/testbin-single/lib/libltdl.3.dylib -Wl,-
>>> compatibility_version -Wl,5 -Wl,-current_version -Wl,5.1
>>> /usr/bin/ld: unknown flag: -compatibility_version
>>> collect2: ld returned 1 exit status
>>>
>>> And Paolo, your suggestion doesn't work. Same error.
>>>
>>> So, do I follow correctly to put my patch into ltmain.sh on gcc?
>> Go ahead (gcc and src), remembering it is a temporary measure.
>
> Ok, done on gcc. Looking for a helper on src. Or is it time to
> request src access ?
I'll commit. Though if you'd like and have a need for src access
lemme know.
-eric
next prev parent reply other threads:[~2007-05-25 19:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 17:35 Steve Ellcey
2007-05-24 18:07 ` Steve Ellcey
2007-05-24 18:46 ` Steve Ellcey
2007-05-24 20:02 ` Andreas Tobler
2007-05-24 20:33 ` Steve Ellcey
2007-05-24 21:09 ` Andreas Tobler
2007-05-24 21:14 ` libtool
2007-05-24 22:13 ` Mike Stump
2007-05-25 17:38 ` Andreas Tobler
2007-05-25 17:43 ` Paolo Bonzini
2007-05-25 17:50 ` Eric Christopher
2007-05-25 19:33 ` Andreas Tobler
2007-05-25 19:39 ` Eric Christopher [this message]
2007-05-24 20:37 ` Mike Stump
2007-05-25 0:12 ` Andrew Pinski
2007-05-28 12:49 ` Andreas Schwab
2007-05-28 19:07 ` Charles Wilson
2007-05-29 1:25 ` Peter O'Gorman
2007-05-28 13:33 ` Andreas Schwab
[not found] <m3irah6d45.fsf@fleche.redhat.com>
2007-05-25 18:21 ` Steve Ellcey
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=A5FD2753-7600-475B-9645-86B6438118FF@apple.com \
--to=echristo@apple.com \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=libtool@cwilson.fastmail.fm \
--cc=mrs@apple.com \
--cc=newlib@sourceware.org \
--cc=peter@pogma.com \
--cc=sje@cup.hp.com \
--cc=toa@pop.agri.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