From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] kconfig/lxdialog: get ncurses CFLAGS with pkg-config
Date: Sun, 26 Oct 2014 22:24:49 +0100 [thread overview]
Message-ID: <20141026222449.315ce1ff@free-electrons.com> (raw)
In-Reply-To: <CAEYzJUEV=Z5yb6+DS_vZ9NuOjtsTfX0KGU5jYFa8wjMRt=v8dw@mail.gmail.com>
Dear Bj?rn Forsman,
On Sun, 26 Oct 2014 22:16:33 +0100, Bj?rn Forsman wrote:
> I've tried to re-sync with linux 3.18-rc1. Without luck. Quite
> frustrating. Something is changed upstream and I don't (yet) manage to
> fill in the missing bits of Make code to have Buildroot's "make
> menuconfig" work with these changes.
Argh :/
At some point, Yann E. Morin was very active on the kbuild/kconfig code
in the upstream Linux kernel. Maybe he can help there?
> Would it be acceptable to add the patch posted in this thread directly
> to support/kconfig/patches/ instead?
Yes, it is acceptable. Especially if the patch description mentions
that it's already upstream, it will help when we'll bump the kconfig
code.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-26 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 13:17 [Buildroot] [PATCH 0/2] Portability fixes for "make menuconfig" Bjørn Forsman
2014-10-26 13:17 ` [Buildroot] [PATCH 1/2] kconfig/lxdialog: get ncurses CFLAGS with pkg-config Bjørn Forsman
2014-10-26 15:41 ` Thomas Petazzoni
2014-10-26 16:06 ` Bjørn Forsman
2014-10-26 21:16 ` Bjørn Forsman
2014-10-26 21:24 ` Thomas Petazzoni [this message]
2014-10-26 21:45 ` Bjørn Forsman
2014-11-05 7:10 ` Bjørn Forsman
2014-11-05 7:15 ` Thomas Petazzoni
2014-12-13 19:04 ` Bjørn Forsman
2015-01-02 16:01 ` Bjørn Forsman
2014-10-26 13:17 ` [Buildroot] [PATCH 2/2] Makefile: pass host PKG_CONFIG_PATH at "make menuconfig" time Bjørn Forsman
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=20141026222449.315ce1ff@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 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.