From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] dbus-1.1.1 is always rebuilt on "make"
Date: Thu, 10 Jul 2008 15:58:02 +0200 [thread overview]
Message-ID: <4876156A.4050200@atmel.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It looks like dbus is always rebuilt.
make -d -n dbus shows: (In Swedish :-)
++++++++++++++++++++++++++
...
M?ste ?terskapa m?let "".
M?lfilen "libxml2-install-staging" ?terskapades.
F?rdigst?llde de n?dv?ndiga f?ruts?ttningarna f?r m?lfilen
"/home/ulf/projects/Buildroot/20080707/buildroot-avr32/build_avr32/dbus-1.1.1/.configured".
Den n?dv?ndiga f?ruts?ttningen
"/home/ulf/projects/Buildroot/20080707/buildroot-avr32/build_avr32/dbus-1.1.1/.unpacked"
?r ?ldre ?n m?let
"/home/ulf/projects/Buildroot/20080707/buildroot-avr32/build_avr32/dbus-1.1.1/.configured".
Den n?dv?ndiga f?ruts?ttningen "libxml2-install-staging" f?r m?let
"/home/ulf/projects/Buildroot/20080707/buildroot-avr32/build_avr32/dbus-1.1.1/.configured"
finns inte.
M?ste ?terskapa m?let
"/home/ulf/projects/Buildroot/20080707/buildroot-avr32/build_avr32/dbus-1.1.1/.configured".
...
- ----------------------------
Basically "dbus-1.1.1/.configured" depends on "libxml2-install-staging"
which does not exist,
Make cannot find an implicit rule for libxml2-install-staging.
The rule to create dbus-1.1.1/.configured is therefore run, and the
rest of the dbus targets are then run as well.
I tried
.PHONY: libxml2-install-staging
but this does not seem to work.
Any ideas?
BR
Ulf Samuelsson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIdhVqAyRRH5cXxqwRApVzAJsG9nBNFYS1BnLrz1NqQvxd53ByOACdHjl6
yp4Q4mo0hgOso6QinswyVe4=
=7PXW
-----END PGP SIGNATURE-----
next reply other threads:[~2008-07-10 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 13:58 Ulf Samuelsson [this message]
2008-07-10 14:21 ` [Buildroot] dbus-1.1.1 is always rebuilt on "make" Peter Korsgaard
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=4876156A.4050200@atmel.com \
--to=ulf.samuelsson@atmel.com \
--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