From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] error in dgen?
Date: Thu, 27 Oct 2011 19:29:47 +0200 [thread overview]
Message-ID: <20111027172947.GK30634@pengutronix.de> (raw)
In-Reply-To: <201110070955.35851.tstone@iss.tu-darmstadt.de>
Hi,
On Fri, Oct 07, 2011 at 09:55:34AM +0200, Tim Sander wrote:
> > Just out of the blue i am having this error on a amd64 platform:
> >
> > ptxdist kernelconfig
> > ptxdist: Checking dependencies. This may take some seconds.
> >
> > error: error during generation of dependencies
> > (maybe amd64 executable on x86)
> >
> > ptxdist: error: error in dgen
> >
> > Any hints whats causing this?
> Accidentially i put a openssh.in and openssh.make into the root of ptxdist.
> This caused this error which was completly unhelpful in resolving this issue.
I found the problem:
We run "find some-dir -name *.in" for the autogenerated kconfig menus.
This happens in the current working dir and because it wasn't quoted
properly you go "find some-dir -name openssh.in" and most generated menus
are missing.
dgen parses the output of kconfig to set up the dependencies. With the
missing files kconfig fails. Unfortunately kcondig send the error message
to stdout (same as the dependency data) so it's not visible :-(
I've push a patch that qoutes "*.in" so this should not happen any more. I
have no idea how to get a better error message if kconfig fails for some
other reason.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2011-10-27 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 7:06 Tim Sander
2011-10-07 7:55 ` Tim Sander
2011-10-27 17:29 ` Michael Olbrich [this message]
2011-10-08 12:30 ` Robert Schwebel
2011-10-09 18:46 ` Tim Sander
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=20111027172947.GK30634@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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