From: Alexander Aring <alex.aring@gmail.com>
To: Wim Vinckier <wimpunk@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] External Kconfig menuconfig/nconfig failed
Date: Thu, 29 Oct 2015 09:26:08 +0100 [thread overview]
Message-ID: <20151029082606.GA3606@omega> (raw)
In-Reply-To: <CAMyOCn_dedvjZ0YpDRbYkwxCjvEH_OPLEDsLtX8_6DfWfhPbRQ@mail.gmail.com>
On Fri, Oct 23, 2015 at 04:54:34PM +0200, Wim Vinckier wrote:
...
>
> I actually fixed it by running `ptxdist clean host-ncurses` first. I
> saw scripts/kconfig/mconf was linked against that library so I thought
> I could give that idea a try. But now it compiles.
>
I guess I know what's happening here.
1. You have some pre compiled "scripts/kconfig/mconf".
2. Running system upgrade -> it updates something at libncurses (or
maybe other dependency, don't know it right now. When I had this
issue I downgrade libncurses and it doesn't solve the issue).
3. Then it doesn't works anymore. A recompile of "host-ncurses" and new
building/linking of "scripts/kconfig/mconf" helps.
This sounds like some real-host vs ptxdist-host issue. Something is
provided by ptxdist-host, but also uses parts from real-host.
But this always exists e.g. glibc.
Or maybe ptxdist used at "scripts/kconfig/mconf" from ptxdist-host while
building/linking. But the LD_PRELOAD_PATH, etc isn't right set when
calling "scripts/kconfig/mconf" so a real-host env will be used. I think
this is more likely.
Then I remember that a "ptxdist kernelconfig" doesn't work, but inside
the kernel source tree a "scripts/kconfig/mconf" worked. I think
"host-ncurses" should not link against "host-ncurses" to avoid such
issues. The internal "ptxdist menuconfig" works because it's linked
against "real-host" ncurses lib. (when you type make inside ptxdist
source).
So we should be sure that for Kconfig building/linking and execution
the "real-host" env is used, not anything from "ptxdist-host". Not
"ptxdist-host" because you don't want have linked binaries from
"ptxdist-host" in external source tree's.
This all occurs because our systems has updated some libaries which was
ncurses related, otherwise it looks that it was somehow compatible
together.
Anyway seems like a very rarely issue.
Thanks for providing a solution here.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-10-29 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 12:17 Alexander Aring
2015-10-21 13:58 ` Wim Vinckier
2015-10-21 17:08 ` Alexander Aring
2015-10-22 6:43 ` Wim Vinckier
2015-10-22 7:40 ` Alexander Aring
2015-10-23 14:54 ` Wim Vinckier
2015-10-29 8:26 ` Alexander Aring [this message]
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=20151029082606.GA3606@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
--cc=wimpunk@gmail.com \
/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