From: Michael Hope <michael.hope@linaro.org>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org, patches@linaro.org
Subject: Re: [PATCH] scripts: add support for building manuals
Date: Thu, 17 Nov 2011 00:03:00 -0000 [thread overview]
Message-ID: <CANLjY-=b7ba65LXUD5ZpqHS7Tt3SRvKHRWiWks41sPAiDpTu0g@mail.gmail.com> (raw)
In-Reply-To: <201111170050.17759.yann.morin.1998@anciens.enib.fr>
On Thu, Nov 17, 2011 at 12:50 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> Michael, All,
>
> On Thursday 17 November 2011 00:29:37 Michael Hope wrote:
>> On Thu, Nov 17, 2011 at 12:04 PM, Yann E. MORIN
>> <yann.morin.1998@anciens.enib.fr> wrote:
>> > On my machine (Debian squeeze, amd64), the build freezes after some errors:
> [--SNIP--]
>> Out of interest, what is your pkgversion? And does it have an @ in it?
>
> Yes, it does.
>
>> @ is the texinfo command character and can wreck havoc if it's not escaped.
>
> Ah, this explains it, then.
It's a tricky one to fix. I sent a fix to EGLIBC a month ago, but
then found the same problem exists in binutils, gcc, and gdb and
pretty much anything else sourceware based. See:
http://www.eglibc.org/archives/patches/msg01014.html
A work-around is to change the development hg pkgversion format to
something without an @. I quite like the Debian style:
1.1.13+hg12345.
-- Michael
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-11-17 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 21:08 Michael Hope
2011-11-15 23:52 ` Yann E. MORIN
2011-11-16 23:05 ` Yann E. MORIN
2011-11-16 23:30 ` Michael Hope
2011-11-16 23:50 ` Yann E. MORIN
2011-11-17 0:03 ` Michael Hope [this message]
2011-11-17 0:14 ` 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='CANLjY-=b7ba65LXUD5ZpqHS7Tt3SRvKHRWiWks41sPAiDpTu0g@mail.gmail.com' \
--to=michael.hope@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=patches@linaro.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).