From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] autoreconf fails
Date: Fri, 17 Apr 2009 15:04:29 +0200 [thread overview]
Message-ID: <1239973469.6397.16.camel@sven> (raw)
In-Reply-To: <1239965054.6397.13.camel@sven>
Hi,
I found that my problems were caused by some custom packages in our tree
that had not been updated to use host-pkgconfig. After I fixed that and
started from a fresh tree, the problems were gone. Sometimes it is
really hard to determine the actual root of build problems. I apologize
for the noise I made...
Sven
prev parent reply other threads:[~2009-04-17 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 10:33 [Buildroot] autoreconf fails Sven Neumann
2009-04-17 10:44 ` Sven Neumann
2009-04-17 13:04 ` Sven Neumann [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=1239973469.6397.16.camel@sven \
--to=s.neumann@phase-zero.de \
--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