From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/avahi
Date: Fri, 04 Apr 2008 09:31:58 +0200 [thread overview]
Message-ID: <87zlsavzwx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <16477104.post@talk.nabble.com> (Hebbar's message of "Thu\, 3 Apr 2008 18\:52\:35 -0700 \(PDT\)")
>>>>> "Hebbar" == Hebbar <gururajakr@sanyo.co.in> writes:
>>
>> Author: jacmet
>> Date: 2008-03-31 07:28:38 -0700 (Mon, 31 Mar 2008)
>> New Revision: 21594
>>
>> Log:
>> avahi: depend on dbus-daemon in staging_dir
>>
>> Depend on dbus-daemon in staging_dir instead of in target_dir as
>> fakeroot updates the timestamp on the target_dir version every time,
>> so the avahi makefile thinks it always needs to recompile avahi.
Hebbar> Hi jacmet,
Hebbar> Thanks for this info. i always wondered why libusb, ncurses ,
Hebbar> zlib used to run at the end everytime i give make world. when
Hebbar> i looked at the respective make file, i found that in
Hebbar> (package): option, respective target_dir lib files are
Hebbar> mentioned which rather should point to staging_dir/usr/lib
Hebbar> library files. kindly let me know if this is correct. if
Hebbar> correct, then i can send pacthes to change this.
Do you still have that problem now?
Hebbar> Regards
Hebbar> Gururaja
Hebbar> ncurses: $(TARGET_DIR)/lib/libncurses.so.$(NCURSES_VERSION)
Hebbar> zlib: uclibc $(TARGET_DIR)/usr/lib/libz.so.$(ZLIB_VERSION)
Hebbar> libusb: uclibc $(TARGET_DIR)/$(LIBUSB_BINARY)
No, this seems correct to me. We need the files installed in
TARGET_DIR, so they cannot depend on the files in STAGING_DIR.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-04 7:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 14:28 [Buildroot] svn commit: trunk/buildroot/package/avahi jacmet at uclibc.org
2008-04-04 1:52 ` Hebbar
2008-04-04 7:31 ` Peter Korsgaard [this message]
2008-04-04 8:28 ` Gururaja Hebbar K R
-- strict thread matches above, loose matches on Subject: below --
2009-01-28 15:12 jacmet at uclibc.org
2008-12-15 16:09 jacmet at uclibc.org
2008-12-04 16:13 egtvedt at uclibc.org
2008-10-01 10:28 egtvedt at uclibc.org
2008-08-31 20:23 jacmet at uclibc.org
2008-08-27 7:29 jacmet at uclibc.org
2008-08-27 8:15 ` Bernhard Reutner-Fischer
2008-08-27 8:28 ` Peter Korsgaard
2008-08-27 7:29 jacmet at uclibc.org
2008-08-04 19:08 jacmet at uclibc.org
2008-06-24 16:02 correa at uclibc.org
2008-06-13 14:19 jacmet at uclibc.org
2008-03-31 19:56 jacmet at uclibc.org
2008-03-31 19:43 jacmet at uclibc.org
2008-03-06 17:54 ninevoltz at uclibc.org
2008-01-26 7:56 thomasez at uclibc.org
2007-11-29 13:04 ulf at uclibc.org
2007-11-26 15:39 jacmet at uclibc.org
2007-11-26 13:02 jacmet at uclibc.org
2007-11-26 12:23 jacmet at uclibc.org
2007-11-23 15:45 jacmet at uclibc.org
2007-11-23 16:30 ` Ulf Samuelsson
2007-11-23 15:40 jacmet at uclibc.org
2007-11-23 13:24 jacmet at uclibc.org
2007-11-25 8:28 ` Ulf Samuelsson
2007-11-26 12:56 ` Peter Korsgaard
2007-09-03 9:02 jacmet at uclibc.org
2007-08-28 8:05 jacmet at uclibc.org
2007-08-01 15:52 ulf at uclibc.org
2007-07-23 15:00 ulf at uclibc.org
2007-07-23 14:53 ` Bernhard Fischer
2007-06-12 15:19 jacmet at uclibc.org
2007-05-15 9:45 jacmet at uclibc.org
2007-05-09 14:03 jacmet at uclibc.org
2007-05-09 13:38 jacmet at uclibc.org
2007-05-08 15:57 jacmet at uclibc.org
2007-01-22 18:15 andersen at uclibc.org
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=87zlsavzwx.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