From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] ncurse address error
Date: Fri, 21 Mar 2008 11:30:33 +0100 [thread overview]
Message-ID: <01d701c88b3e$9b1336a0$ad289e86@LPSC0173W> (raw)
In-Reply-To: 47E27895.2000909@gnat.ca
> I provided a patch yesterday to fix this, but haven't seen/heard a
> response. Here it is again, since there are a handful of packages
> affected by it.
Thanks, I got your message after I posted my question, so it may have been
delayed.
I see that the svn repository of buildroot is updated daily, so as a general
rule how long before such a patch makes it into the tree ?
[...still fighting to get a first compile...]
--
Guillaume Dargaud
http://www.gdargaud.net/
next prev parent reply other threads:[~2008-03-21 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 10:57 [Buildroot] Buildroot compilation error Reinier Coetzer
2008-03-20 10:47 ` [Buildroot] ncurse address error Guillaume Dargaud
2008-03-20 14:45 ` Nathanael D. Noblet
2008-03-21 10:30 ` Guillaume Dargaud [this message]
2008-03-20 14:58 ` [Buildroot] Problem building busybox Guillaume Dargaud
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='01d701c88b3e$9b1336a0$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--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