From: Hari Sandanagobalane <hariharans@picochip.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: disable libiberty for picochip build.
Date: Tue, 04 Jan 2011 09:50:00 -0000 [thread overview]
Message-ID: <4D22EA28.3000308@picochip.com> (raw)
In-Reply-To: <20110102164020.GK10951@gmx.de>
Thanks a bunch, Ralf.
Cheers
Hari
On 02/01/11 16:40, Ralf Wildenhues wrote:
> * Hari Sandanagobalane wrote on Thu, Dec 23, 2010 at 05:11:31PM CET:
>> On 23/12/10 10:39, Ralf Wildenhues wrote:
>>> * Hari Sandanagobalane wrote on Wed, Dec 22, 2010 at 11:35:14AM CET:
>>>> I have now committed (168165) the following change in mainline to disable
>>>> libiberty for picochip builds. Thanks
>>>
>>> This patch is missing the regeneration of the generated configure
>>> script. Also, toplevel needs to be synced to the src repository.
>>> Please ping me if you need someone to do the latter for you.
>
>> I have regenerated the configure script and checked the change in.
>> Would you be able to tell me what you mean by the
>> "synced to the src repository"?
>
> That is described at
> <http://gcc.gnu.org/codingconventions.html#upstream> and
> <http://sourceware.org/cgi-bin/cvsweb.cgi/src/MAINTAINERS?rev=1.36&content-type=text/x-cvsweb-markup&cvsroot=src>
> and is about files shared between GCC, binutils, gdb, and other
> packages.
>
>> If you can do it, that is great. But, i would like to know what
>> steps i missed so i do it right the next time!
>
> If you don't have write access to the src CVS repository, please mention
> that you need somebody to sync for you.
>
> FYI, I'm committing as below to src.
>
> In your commit log entries, please put two spaces between name and email
> address.
>
> Thanks,
> Ralf
>
> 2011-01-02 Ralf Wildenhues<Ralf.Wildenhues@gmx.de>
>
> Sync from GCC:
> 2010-12-22 Hariharan Sandanagobalane<hariharan@picochip.com>
>
> * configure.ac: (picochip): Disable libiberty.
> * configure: Regenerate.
>
> Index: configure.ac
> ===================================================================
> RCS file: /cvs/src/src/configure.ac,v
> retrieving revision 1.122
> diff -u -r1.122 configure.ac
> --- configure.ac 10 Dec 2010 14:50:10 -0000 1.122
> +++ configure.ac 2 Jan 2011 16:35:50 -0000
> @@ -916,6 +916,9 @@
> mt-*-*)
> noconfigdirs="$noconfigdirs sim"
> ;;
> + picochip-*-*)
> + noconfigdirs="$noconfigdirs target-libiberty"
> + ;;
> powerpc-*-aix*)
> # copied from rs6000-*-* entry
> noconfigdirs="$noconfigdirs gprof target-libgloss target-libssp target-newlib ${libgcj}"
>
prev parent reply other threads:[~2011-01-04 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 12:17 Hari Sandanagobalane
2010-12-23 12:58 ` Ralf Wildenhues
2010-12-23 16:31 ` Hari Sandanagobalane
2011-01-02 16:44 ` Ralf Wildenhues
2011-01-02 16:47 ` H.J. Lu
2011-01-02 17:18 ` Ralf Wildenhues
2011-01-04 9:50 ` Hari Sandanagobalane [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=4D22EA28.3000308@picochip.com \
--to=hariharans@picochip.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
/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).