From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libid3tag
Date: Tue, 29 May 2007 07:55:28 -0700 (PDT) [thread overview]
Message-ID: <20070529145528.5920E48573@busybox.net> (raw)
Author: jacmet
Date: 2007-05-29 07:55:27 -0700 (Tue, 29 May 2007)
New Revision: 18700
Log:
libid3tag requires zlib. Noticed by Stuart Wood
Modified:
trunk/buildroot/package/libid3tag/Config.in
Changeset:
Modified: trunk/buildroot/package/libid3tag/Config.in
===================================================================
--- trunk/buildroot/package/libid3tag/Config.in 2007-05-27 22:03:58 UTC (rev 18699)
+++ trunk/buildroot/package/libid3tag/Config.in 2007-05-29 14:55:27 UTC (rev 18700)
@@ -1,6 +1,7 @@
config BR2_PACKAGE_LIBID3TAG
bool "libid3tag"
default n
+ select BR2_PACKAGE_ZLIB
help
ID3 tag reading library from the MAD project.
next reply other threads:[~2007-05-29 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 14:55 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-28 16:02 [Buildroot] svn commit: trunk/buildroot/package/libid3tag ulf at uclibc.org
2007-07-28 17:30 ulf at uclibc.org
2007-07-28 23:17 ulf at uclibc.org
2007-09-20 7:19 aldot 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=20070529145528.5920E48573@busybox.net \
--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