All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: GCC + Texinfo 5
Date: Wed, 27 Feb 2013 14:00:36 +0000	[thread overview]
Message-ID: <512E1184.1040202@communistcode.co.uk> (raw)
In-Reply-To: <512E10A8.2080407@communistcode.co.uk>

On 27/02/13 13:56, Jack Mitchell wrote:
> On 27/02/13 13:52, Jack Mitchell wrote:
>> On 27/02/13 13:46, Jack Mitchell wrote:
>>> As with the recent binutils texinfo5 compatibility I believe GCC now 
>>> also has the same failings, please see attached log.
>>>
>>> I've had a quick look for patches but I am not at all familiar with 
>>> the GCC development process and I came up empty handed.
>>>
>>> Cheers,
>>>
>>
>> Ok, one patch found, there seems to be some @anchor problems too; 
>> I'll see if I can dig anything up.
>>
>> http://lists.gnu.org/archive/html/bug-coreutils/2012-07/msg00045.html
>>
>
> Appologies, that isn't even for GCC :(
>

Ok, this is the patch; I'll look into trying to use it in the GCC 
recipes but they're pretty complicated...

http://patchwork.ozlabs.org/patch/222861/
-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2013-02-27 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 13:46 GCC + Texinfo 5 Jack Mitchell
2013-02-27 13:52 ` Jack Mitchell
2013-02-27 13:56   ` Jack Mitchell
2013-02-27 14:00     ` Jack Mitchell [this message]
2013-02-27 14:10       ` Jack Mitchell
2013-02-27 14:42         ` Khem Raj
2013-02-27 14:48           ` Jack Mitchell
2013-02-28  6:59             ` Khem Raj
2013-02-28  9:46               ` Jack Mitchell

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=512E1184.1040202@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.