From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] libdaemon patch
Date: Thu, 2 Aug 2007 10:47:44 +0200 [thread overview]
Message-ID: <20070802084743.GJ11697@aon.at> (raw)
In-Reply-To: <1185995952.7651.94.camel@elrond.sweden.atmel.com>
On Wed, Aug 01, 2007 at 09:19:12PM +0200, Ulf Samuelsson wrote:
>libdaemon does not build properly, complaining about missing libtool
>and giving some hints what to do:
>Anyone can comment on the patch below?
First, why do you constantly add whitespace-damaged patches to
buildroot? Please don't do this.
The host system doesn't have to have autotools installed.
Providing a bz2'ed patch that holds the result of an autoreconf is the
proper thing to do.
>It at least allows libdaemon to complete the compile...
>
>Index: package/libdaemon/libdaemon.mk
>===================================================================
>--- package/libdaemon/libdaemon.mk (revision 19374)
>+++ package/libdaemon/libdaemon.mk (arbetskopia)
>@@ -29,7 +29,12 @@
> touch $(LIBDAEMON_DIR)/.unpacked
>
> $(LIBDAEMON_DIR)/.configured: $(LIBDAEMON_DIR)/.unpacked
>- (cd $(LIBDAEMON_DIR) && rm -rf config.cache && autoconf)
>+ (cd $(LIBDAEMON_DIR) ; \
>+ rm -rf config.cache ; \
>+ aclocal ; \
>+ autoconf; \
>+ automake; \
>+ autoheader)
> ( cd $(LIBDAEMON_DIR) && \
> $(TARGET_CONFIGURE_OPTS) \
> $(TARGET_CONFIGURE_ARGS) \
>
>
>Best Regards
>Ulf Samuelsson
>
>
>_______________________________________________
>buildroot mailing list
>buildroot at uclibc.org
>http://busybox.net/mailman/listinfo/buildroot
>
prev parent reply other threads:[~2007-08-02 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 19:19 [Buildroot] [RFC] libdaemon patch Ulf Samuelsson
2007-08-02 8:47 ` Bernhard Fischer [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=20070802084743.GJ11697@aon.at \
--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.