From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] libid3tag build broken: Please add zlib to dependency list
Date: Thu, 20 Sep 2007 08:28:47 +0200 [thread overview]
Message-ID: <1190269727.9021.23.camel@localhost.localdomain> (raw)
In-Reply-To: <145594.52785.qm@web62014.mail.re1.yahoo.com>
On Wed, 2007-09-19 at 22:50 -0700, Doug the RockRat wrote:
> The package/libid3tag/libid3tag.mk file needs zlib
> added to the dependency.
>
> Do you want a patch or is this good enough?
Attached a patch, I also cleaned up some rules and typos, so the library
is not rebuilt every time you build.
Diffed against the snapshot from 20070919.
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libid3tag-add-zlib-dependancy-and-fix-rules.patch
Type: text/x-patch
Size: 1900 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070920/5817279f/attachment.bin
next prev parent reply other threads:[~2007-09-20 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 5:50 [Buildroot] libid3tag build broken: Please add zlib to dependency list Doug the RockRat
2007-09-20 6:28 ` Hans-Christian Egtvedt [this message]
2007-09-20 9:45 ` Bernhard Fischer
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=1190269727.9021.23.camel@localhost.localdomain \
--to=hcegtvedt@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox