From: Carlos O'Donell <carlos_odonell@mentor.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: [PATCH] Move definition of libgcc_s soname to shlib-versions
Date: Thu, 26 Apr 2012 14:37:00 -0000 [thread overview]
Message-ID: <4F995DB4.20006@mentor.com> (raw)
In-Reply-To: <20120426093925.74d6c2a5@spoyarek>
On 4/26/2012 12:09 AM, Siddhesh Poyarekar wrote:
> Hi,
>
> I just committed the change to move LIBGCC_S_SO soname definition from
> libgcc_s.h to shlib-versions into the core tree. Attached patch needs
> to be applied to the ports tree to allow m68k and hppa to build against
> the new changes.
>
> Regards,
> Siddhesh
>
> ChangeLog:
>
> 2012-04-26 Siddhesh Poyarekar <siddhesh@redhat.com>
>
> * sysdeps/hppa/libgcc_s.h: Remove.
> * sysdeps/hppa/shlib-versions: Add libgcc_s.
> * sysdeps/m68k/libgcc_s.h: Remove.
> * sysdeps/m68k/shlib-versions: Add libgcc_s.
Thanks, I'll get this checked in for hppa.
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026
prev parent reply other threads:[~2012-04-26 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 4:08 Siddhesh Poyarekar
2012-04-26 14:37 ` Carlos O'Donell [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=4F995DB4.20006@mentor.com \
--to=carlos_odonell@mentor.com \
--cc=libc-ports@sourceware.org \
--cc=siddhesh@redhat.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).