From: Pavel Roskin <proski@gnu.org>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] mpg123 build issues
Date: Fri, 15 Dec 2006 02:40:58 -0500 [thread overview]
Message-ID: <1166168458.2220.24.camel@dv> (raw)
In-Reply-To: <20061214160303.GA2577@aon.at>
On Thu, 2006-12-14 at 17:03 +0100, Bernhard Fischer wrote:
> >> May i ask you to verify that a) an mpg123 bug exists in the
> >> bug-database and if so b) incooperate possible additional fixes?
> >
> >I couldn't find any.
Actually, I sent a patch that upgrades mpg123 to the latest version that
uses an Autoconf generated configure script. It's much better than to
tweak makefiles not to ignore our variables. Unfortunately, I was asked
additional questions that I didn't have time to answer.
The current version is 0.61. My old patch doesn't apply anymore.
Here's the thread in case anyone wants to continue my effort:
http://buildroot.uclibc.org/lists/buildroot/2006-November/thread.html#626
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-12-15 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 15:02 [Buildroot] [patch] mpg123 build issues Ulrich Hecht
2006-12-14 15:29 ` Bernhard Fischer
[not found] ` <200612141653.07781.uli@suse.de>
2006-12-14 16:03 ` Bernhard Fischer
2006-12-15 7:40 ` Pavel Roskin [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=1166168458.2220.24.camel@dv \
--to=proski@gnu.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 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.