public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Szabat" <michal611@interia.pl>
To: Linux-omap-open-source@linux.omap.com
Subject: encoder audio or speech for omap5912
Date: Thu, 27 Apr 2006 15:44:40 +0200	[thread overview]
Message-ID: <001201c66a00$bf2cb400$0301a8c0@hydra> (raw)

Hello. 

I want encode wav to mp3 on omap5912. I try to compiled lame3.96.1 with toolchain3.4.1 with options 
CC=arm-linux-gcc ./configure --target=arm-linux --host=arm-linux --prefix=/root/lame. 
This compiled properly, but not works.  

/ # lame
LAME version 3.96.1 (http://lame.sourceforge.net/)

usage: lame [options] <infile> [outfile]

    <infile> and/or <outfile> can be "-", which means stdin/stdout.

Try:
     "lame --help"           for general usage information
 or:
     "lame --preset help"    for information on suggested predefined settings
 or:
     "lame --longhelp"
  or "lame -?"              for a complete options list
/home # lame xp.wav xp.mp3
Segmentation fault.

I think that the problem maybe with this(configure warning)

checking for IEEE854 compliant 80 bit floats... configure: WARNING: can't check for IEEE854 compliant 80 bit floats

checking for ieee754_float64_t... no
checking for ieee754_float32_t... no
configure: WARNING:
  **************************************************************************
  *                                                                        *
  * You are cross compiling:                                               *
  *   - I did not have a change to determine                               *
  *     + the size of:                                                     *
  *       - short                                                          *
  *       - unsigned short                                                 *
  *       - int                                                            *
  *       - unsigned int                                                   *
  *       - long                                                           *
  *       - unsigned long                                                  *
  *       - float                                                          *
  *       - double                                                         *
  *       - long double                                                    *
  *     + the endianess of the system                                      *
  *   - You have to provide appropriate defines for them in config.h, e.g. *
  *     + define SIZEOF_SHORT to 2 if the size of a short is 2             *
  *     + define WORDS_BIGENDIAN if your system is a big endian system     *
  *                                                                        *
  **************************************************************************

Anyone could help me with this. It not must be lame encoder. I tried with bladeenc and speex.

             reply	other threads:[~2006-04-27 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 13:44 Michał Szabat [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-06 11:59 encoder audio or speech for omap5912 K S Shankar
2006-10-06 15:03 ` Dirk Behme

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='001201c66a00$bf2cb400$0301a8c0@hydra' \
    --to=michal611@interia.pl \
    --cc=Linux-omap-open-source@linux.omap.com \
    /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