From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] problem with dbus.mk
Date: Fri, 20 Jun 2008 21:24:13 +0200 [thread overview]
Message-ID: <87tzfn29lu.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <46a136670806200815p7034b6c5y6dbe39035796af62@mail.gmail.com> (John Voltz's message of "Fri\, 20 Jun 2008 11\:15\:58 -0400")
>>>>> "John" == John Voltz <john.voltz@gmail.com> writes:
John> Hi,
John> I discovered a bit of a problem in dbus.mk.
John> DBUS_XML_DEP:=$(BUILD_DIR)/libxml2-2.6.29/.stamp_staging_installed
John> What happens when libxml2 has not been downloaded, extracted,
John> or built and you depend on .stamp_staging_installed?
Normally it would work just fine (we do this all the time), but
looking closer at it, the Makefile.autotools.in stuff is horribly
broken as it doesn't have proper dependencies listed.
It also looks like it would break badly for parallel builds (-j)
:/
John> Build failure. I would suggest a revert on dbus.mk.
I'll revert the libxml2 hunk. We really need to fixup the autotools
stuff or stop using it.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2008-06-20 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 15:15 [Buildroot] problem with dbus.mk John Voltz
2008-06-20 19:24 ` Peter Korsgaard [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=87tzfn29lu.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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