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, 22 Oct 2015 09:40:43 +0200 [thread overview]
Message-ID: <20151022074039.GA609@omega> (raw)
In-Reply-To: <CAMyOCn_uhTiEoZvxLmOhObtWThhxo7R_S0zeoCbHwpf7D8p8CQ@mail.gmail.com>
Hi,
On Thu, Oct 22, 2015 at 08:43:43AM +0200, Wim Vinckier wrote:
> Hi,
>
> On 21 October 2015 at 19:08, Alexander Aring <alex.aring@gmail.com> wrote:
> > Hi,
> >
> > On Wed, Oct 21, 2015 at 03:58:55PM +0200, Wim Vinckier wrote:
> >> Hi,
> >>
> >> Did you found a solution for this? It seems like I'm having the same
> >> problem. :-(
> >>
> >
> > I didn't find a solution. For me, the issue is gone since the last
> > system upgrade. I don't have the issue anymore and don't know why I had
> > it.
> >
> > Maybe try a system upgrade.
> >
> > - Alex
>
> I'm currently building mine on a virtual box with the latest debian7
> but I think I have a debian8 lying around. I'll try that one and hope
> it will work.
>
> Thanks for the answer.
>
mhh, I thought you are on a bleeding edge distribution like me. So I
think a system upgrade should not solve this issue.
I also migrate to 2015.09.0, maybe this helps. I think not because when
I had this error I already tried to use different ptxdist version
without success.
It need to be something with a special "software" enviornment. Okay then
I would say a software upgrade could help, but debian is so stable. :-/
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-10-22 7:40 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 [this message]
2015-10-23 14:54 ` Wim Vinckier
2015-10-29 8:26 ` Alexander Aring
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=20151022074039.GA609@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