From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libusb
Date: Fri, 13 Jun 2008 19:58:01 +1000 [thread overview]
Message-ID: <20080613095801.GA31077@cloud.net.au> (raw)
In-Reply-To: <48522AB7.9000501@gmail.com>
On Fri, Jun 13, 2008 at 08:07:19PM +1200, Matthew Dombroski wrote:
>
>> And now we're back to the original problem where libusb gets built over
>> and over again. Oh how I love autotools & our autotools packages..
I've got a fix, which I'll check in anyway.
> I have rewritten libusb.mk. I sent it to the buildroot mailing list
> about 2 weeks ago but never heard anything.
Sorry about that.. I don't remember seeing it.
> This time I'm sending a proper patch (although its bigger than the
> resulting libusb.mk).
> Can someone confirm that it works?
It looks ok, I will test it later (maybe Monday).
> -$(LIBUSB_DIR)/.configured: $(LIBUSB_DIR)/.unpacked
> - (cd $(LIBUSB_DIR); rm -rf config.cache; \
> - $(TARGET_CONFIGURE_OPTS) \
> - $(TARGET_CONFIGURE_ARGS) \
> - ac_cv_header_regex_h=no \
It looked to me like something important was lost in your patch (it
doesn't mention ac_cv_header_regex_h anywhere after patching), but
looking at libusb's configure script it doesn't seem to be used anyway.
> +$(LIBUSB_TARGET_INSTALL_TARGET): $(LIBUSB_TARGET_INSTALL_STAGING)
> + $(call MESSAGE,"Installing to target")
> -libusb: uclibc $(TARGET_DIR)/$(LIBUSB_BINARY)
> +$(LIBUSB_TARGET_UNINSTALL):
> + $(call MESSAGE,"Uninstalling")
Why the messages? Is this standard among our autotools-using packages?
thanks!
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-06-13 9:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 5:53 [Buildroot] svn commit: trunk/buildroot/package/libusb hamish at uclibc.org
2008-06-13 6:25 ` Hamish Moffatt
2008-06-13 8:07 ` Matthew Dombroski
2008-06-13 9:58 ` Hamish Moffatt [this message]
2008-06-13 10:11 ` Matthew Dombroski
-- strict thread matches above, loose matches on Subject: below --
2008-12-05 10:22 jacmet at uclibc.org
2008-12-05 10:42 ` Gaye Abdoulaye Walsimou
2008-12-08 21:08 ` Peter Korsgaard
2008-12-09 0:46 ` Hamish Moffatt
2008-06-13 8:47 jacmet at uclibc.org
2008-06-13 8:45 jacmet at uclibc.org
2008-06-13 10:02 ` Hamish Moffatt
2008-06-13 10:18 ` Peter Korsgaard
2008-05-28 6:54 hamish at uclibc.org
2008-05-28 2:12 hamish at uclibc.org
2008-03-27 13:00 jacmet at uclibc.org
2008-02-18 14:30 sjhill at uclibc.org
2008-02-15 14:06 jacmet at uclibc.org
2007-11-09 9:30 vanokuten at uclibc.org
2007-11-09 9:26 vanokuten at uclibc.org
2007-09-25 12:54 ulf at uclibc.org
2007-09-20 9:35 aldot at uclibc.org
2007-08-31 12:04 aldot at uclibc.org
2007-08-21 18:30 aldot at uclibc.org
2007-07-16 9:45 ulf at uclibc.org
2007-05-07 4:00 sjhill at uclibc.org
2007-05-07 9:41 ` Assen Stoyanov
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=20080613095801.GA31077@cloud.net.au \
--to=hamish@cloud.net.au \
--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.