From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/avahi
Date: Wed, 27 Aug 2008 10:15:59 +0200 [thread overview]
Message-ID: <20080827081559.GA25436@mx.loc> (raw)
In-Reply-To: <20080827072921.BE910F8014@busybox.net>
On Wed, Aug 27, 2008 at 12:29:21AM -0700, jacmet at uclibc.org wrote:
>Author: jacmet
>Date: 2008-08-27 00:29:20 -0700 (Wed, 27 Aug 2008)
>New Revision: 23235
>Modified: trunk/buildroot/package/avahi/avahi.mk
>===================================================================
>--- trunk/buildroot/package/avahi/avahi.mk 2008-08-27 07:29:16 UTC (rev 23234)
>+++ trunk/buildroot/package/avahi/avahi.mk 2008-08-27 07:29:20 UTC (rev 23235)
>@@ -142,7 +142,7 @@
> touch $@
>
> $(AVAHI_DIR)/.compiled: $(AVAHI_DIR)/.configured
>- $(MAKE) -C $(AVAHI_DIR)
>+ $(MAKE) -C $(AVAHI_DIR) $(if $(BR2_ENABLE_LOCALE),LIBS=-lintl)
> touch $@
>
> $(AVAHI_DIR)/.installed: $(AVAHI_DIR)/.compiled
>@@ -180,7 +180,7 @@
> $(TARGET_DIR)/usr/sbin/avahi-daemon
> $(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $@
>
>-avahi: uclibc libdaemon $(AVAHI_TARGETS)
>+avahi: uclibc libdaemon $(AVAHI_TARGETS) $(if $(BR2_ENABLE_LOCALE),gettext libintl)
are you sure that the order is correct? Getting this proper for toplevel
parallel make would be fun:
# make sure to set JLEVEL=1
$ make oldconfig
$ rm -rf {toolchain,build,project}_*
$ make -j avahi
next prev parent reply other threads:[~2008-08-27 8:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 7:29 [Buildroot] svn commit: trunk/buildroot/package/avahi jacmet at uclibc.org
2008-08-27 8:15 ` Bernhard Reutner-Fischer [this message]
2008-08-27 8:28 ` Peter Korsgaard
-- 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-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-31 14:28 jacmet at uclibc.org
2008-04-04 1:52 ` Hebbar
2008-04-04 7:31 ` Peter Korsgaard
2008-04-04 8:28 ` Gururaja Hebbar K R
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=20080827081559.GA25436@mx.loc \
--to=rep.dot.nop@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.