From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: Michael Hope <michael.hope@linaro.org>
Cc: Zhenqiang Chen <zhenqiang.chen@linaro.org>, crossgcc@sourceware.org
Subject: Re: [PATCH] debug/gdb: add extra config for gdb cross
Date: Wed, 23 Nov 2011 21:22:00 -0000 [thread overview]
Message-ID: <201111232221.46437.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <CANLjY-nAdw7aZXiCd72TH4DJGF05wsZBbUBW2_mZ1ORqsx9xtA@mail.gmail.com>
Michael, Zhenqiang, All,
On Wednesday 23 November 2011 22:07:37 Michael Hope wrote:
> On Thu, Nov 24, 2011 at 12:40 AM, Zhenqiang Chen
> <zhenqiang.chen@linaro.org> wrote:
> > # HG changeset patch
> > # User Zhenqiang Chen <zhenqiang.chen@linaro.org>
> > # Date 1322025327 -28800
> > # Node ID e3a6a636cfa9013ddd0855ca9eb8d3a35dad3249
> > # Parent 2f4e3c312b659422e4a9950f13a0fc507b97c1fd
> > debug/gdb: add extra config for gdb cross.
> >
> > Signed-off-by: Zhenqiang Chen <zhenqiang.chen@linaro.org>
> >
> > diff --git a/config/debug/gdb.in.cross b/config/debug/gdb.in.cross
> > --- a/config/debug/gdb.in.cross
> > +++ b/config/debug/gdb.in.cross
> > @@ -39,4 +39,11 @@
> > have been reports of problems when linking gdb to the static
> > libpython.a. This should be fixed in gdb >=7.3. YMMV.
> >
> > +config GDB_CROSS_EXTRA_CONFIG_ARRAY
> > + string
> > + prompt "Extra config for gdb cross"
>
> Should this be "Cross-gdb extra config" to be consistent with the
> other arrays in binutils, glibc, and gcc?
Yes, I'll change here before committing.
> > + default ""
> > + help
> > + Extra flags to pass onto ./configure when configuring the gdb cross.
> > +
> > endif # GDB_CROSS
> > diff --git a/scripts/build/debug/300-gdb.sh b/scripts/build/debug/300-gdb.sh
> > --- a/scripts/build/debug/300-gdb.sh
> > +++ b/scripts/build/debug/300-gdb.sh
> > @@ -147,7 +147,8 @@
> > --with-sysroot="${CT_SYSROOT_DIR}" \
> > --with-expat=yes \
> > --disable-werror \
> > - "${cross_extra_config[@]}"
> > + "${cross_extra_config[@]}" \
>
> Huh. The trailing \ looks fine in Thunderbird but is one character
> short in gmail's view original.
I looked at the raw message, and somehow a leading space is added to every
lines that already start with a space.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-11-23 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 11:41 Zhenqiang Chen
2011-11-23 21:08 ` Michael Hope
2011-11-23 21:22 ` Yann E. MORIN [this message]
2011-11-23 22:59 ` Yann E. MORIN
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=201111232221.46437.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=michael.hope@linaro.org \
--cc=zhenqiang.chen@linaro.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).