Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot gcc 4.9.0 missing file
Date: Wed, 23 Apr 2014 15:30:24 -0300	[thread overview]
Message-ID: <535806C0.8030507@zacarias.com.ar> (raw)
In-Reply-To: <315218274.63625.1398277478747.JavaMail.root@storentr2>

On 04/23/2014 03:24 PM, Frederic MOURMANT wrote:

> Dear Gustavo,
> 
> The "[PATCH 1/2] toolchain: add gcc 4.9 series" is in error due to the
> missing file : <wordexp.h>
> 
> cf :  http://pastebin.com/nmDJEcRL

You missed a follow-up patch:
http://patchwork.ozlabs.org/patch/341419/
Next time please post to the list as well, there might be other people
wanting to know :)
Regards.

       reply	other threads:[~2014-04-23 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <315218274.63625.1398277478747.JavaMail.root@storentr2>
2014-04-23 18:30 ` Gustavo Zacarias [this message]
     [not found] <803911355.63694.1398280913367.JavaMail.root@storentr2>
2014-04-23 19:29 ` [Buildroot] buildroot gcc 4.9.0 missing file Gustavo Zacarias

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=535806C0.8030507@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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