From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] [RFC] Improve speex's buildsystem
Date: Sun, 8 Apr 2012 10:59:45 +0200 [thread overview]
Message-ID: <201204081059.45239.jbe@pengutronix.de> (raw)
In-Reply-To: <20120408074216.GB13585@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
Michael Olbrich wrote:
> On Fri, Apr 06, 2012 at 01:08:53PM +0200, Juergen Beisert wrote:
> > Please find below a patch to improve 'speex' buildsystem in various ways.
> > 'speex' comes with many hardware related switches. And as it is a
> > user-land component, sharing the settings in a PTXdist project based on
> > more than one platform with different architectures is (currently)
> > impossible.
> >
> > Also the current rule file is broken, as it depends on a few platform
> > settings which are no longer available since ages.
> >
> > This patch adds some auto-scripts (thanks to Uwe) that are able to read
> > back the important settings from the toolchain. And the result will
> > configure 'speex' automagically in accordance to the architecture's
> > features.
> >
> > These auto-scripts could also be used in other packages, that need
> > architecture specific configuration. And since the use of these
> > auto-scripts depends on an autogen step, PTXdist could provide these
> > auto-scripts as a generic part, instead of patching them into each
> > package (like it is done in this example).
> >
> > Comments are welcome.
>
> When I try to apply this I get an error:
>
> Applying: Improve speex's buildsystem
> fatal: corrupt patch at line 942
> [...]
> +-echo "You don't seem to have the development package for libogg (libogg-devel) installed. Only the Speex library (libspeex) will be built (no
> encoder/decoder executable)"
> [...]
Hmm, all lines are correct, but not this one (and two others). Don't know why.
I will re-send it again as an attachment this time.
(And the broken lines are always broken in column 144...)
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
[-- Attachment #2: Improve_speexs_buildsystem.diff.bz2 --]
[-- Type: application/x-bzip2, Size: 10482 bytes --]
[-- Attachment #3: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-04-08 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 11:08 Juergen Beisert
2012-04-08 7:42 ` Michael Olbrich
2012-04-08 7:47 ` Wolfram Sang
2012-04-08 7:56 ` Michael Olbrich
2012-04-08 8:59 ` Juergen Beisert [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=201204081059.45239.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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