Displaying 20 results from an estimated 1100 matches similar to: "Problem compiling speex 1.1.4"
2004 Aug 06
1
Re: speex 1.1.4 compile fails/vq.h parse error
It's not really documented, but when you compile with --enable-sse, you
need to add -march=pentium3 to the compile switches. That's actually a
gcc requirement.
Jean-Marc
Le mer 21/01/2004 à 04:22, war a écrit :
> gcc-3.2.2 + slack 9 + p4 2.6ghz (has sse/2)
>
> ./configure --prefix=/app/speex-1.1.4 --enable-shared --enable-sse
> --with-ogg-dir=/app/libogg-1.1
>
2004 Aug 06
4
libspeex/SSE Intrinsics with GCC 3.3.x
When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be
added to the CFLAGS in libspeex/Makefile.
GCC 3.1.1 added a new option "-msse" (see
http://gcc.gnu.org/gcc-3.1/changes.html , specifically under "New
Targets and Target Specific Improvements") to enable SSE instructions
within the compiler's output (for appropriate architectures).
Compiling speex on
2004 Aug 06
0
libspeex/SSE Intrinsics with GCC 3.3.x
I'm aware of the problem, but I don't know how to get autoconf to handle
that properly. If someone knows how to make that work with autoconf even
with non-gcc compilers and with default CFLAGS, I'm interested.
Jean-Marc
Le jeu 01/04/2004 à 17:21, Michael T. Dean a écrit :
> When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be
> added to the CFLAGS in
2004 Aug 06
3
libspeex/SSE Intrinsics with GCC 3.3.x
Here is code to add to configure.in to do what you want. It preserves
CFLAGS and uses that var to hold the sse enable flags. You can subset this
under the exisiting AC_ARG for sse or just make it do it all the time. If
you notice the i?86, that means any x86 platform target will have it
enabled. You can change that i686, but keep in mind that some distros
compile/target for i386 on the glibc
2004 Aug 06
1
Compile issue with gcc3.2
I've been able to get Speex to compile on gcc 2.95.3 with no problems. When using gcc 3.2 I get the following output:
gcc -DHAVE_DLFCN_H=1 -DHAVE_SYS_SOUNDCARD_H=1 -DHAVE_LIBOGG=1 -DHAVE_LIBM=1 -DVERSION=\"1.0beta1\" -I. -I. -march=pentium4 -mcpu=pentium4 -O3 -pipe -c high_lsp_tables.c -o high_lsp_tables.o
cb_search.c: In function `split_cb_search_shape_sign':
cb_search.c:500:
2004 Nov 30
1
Problem compiling speex 1.1.6
# make
make all-recursive
make[1]: Entering directory `/tmp/speex-1.1.6'
Making all in libspeex
make[2]: Entering directory `/tmp/speex-1.1.6/libspeex'
source='nb_celp.c' object='nb_celp.lo' libtool=yes \
depfile='.deps/nb_celp.Plo' tmpdepfile='.deps/nb_celp.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I.
2006 Apr 08
2
speex cvs: 'EncState' has no member named 'frame'
Trying to build today's svn on fc5, gcc-4.1.0,amd64:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include
-I.. -I/usr/include -O2 -fPIC -funswitch-loops
-ftree-loop-linear -march=k8 -ftree-vectorize -pipe
-mfpmath=sse -frename-registers -O3 -msse -MT nb_celp.lo -MD
-MP -MF .deps/nb_celp.Tpo -c nb_celp.c -fPIC -DPIC -o
.libs/nb_celp.o
nb_celp.c: In function 'nb_encode':
2004 Aug 06
2
Notes on 1.1.4 Windows. Testing of SSE Intrinics Code and others
Jean-Marc,
Are you sure that you don't need to add just -msse to enable the
intrinsics rather than a full fledged -march=pentium3? I did some playing
around and I can get intrinsics code to compile with -march=i686 -msse on
linux with that.
Check out:
2004 Aug 06
0
Speex 1.1.4 is out
A few things -
1. I think that run-time processor detection should not be included in Speex.
2. There a few ways of doing per-file compiling flags.
a. Make a new static library that is just the files that have the
SSE / Altivec code in them. You can then use target_CFLAGS in the
Makefile.am script to set what you need
b. Do tricks with file extensions. CFLAGS applies to
2004 Aug 06
0
libspeex/SSE Intrinsics with GCC 3.3.x
Actually, I prefer having the user explicitly specify --enable-sse
because you might want to compile for other machines than what you have.
Also, any idea what happens if the user already has CFLAGS=-O2 defined
(and you add -O3)? Last thing, how do you check whether gcc accepts
-msse?
Jean-Marc
Le ven 02/04/2004 à 00:40, Aron Rosenberg a écrit :
> Here is code to add to configure.in
2010 Jan 13
0
BUG for speex-1.2rc1
DEAR:
I SEEM A BUG FOR speex-1.2rc1.tar.gz ON BUILD IN USING IT.
PLEASE LOOK:
=====================================================================
make all-recursive
make[1]: Entering directory `/tmp/speex-1.2rc1'
Making all in libspeex
make[2]: Entering directory `/tmp/speex-1.2rc1/libspeex'
/bin/sh ../libtool --mode=link gcc -g -O2 -fvisibility=hidden -O3 -msse
-o testenc
2005 Feb 28
4
memory usage
On Mon, 2005-02-28 at 19:42 -0500, Jean-Marc Valin wrote:
> > jean-marc: i think we can remove spx_sig_t *orig.
> > but am not sure about exc2Buf. is it for extension?
>
> orig is already removed in SVN (which you should probably use). As for
> exc2, it can be removed, but I'm not sure if you can just use exc
> instead (maybe yes).
>
when removing "spx_sig_t
2005 Nov 18
1
how can i compile speex on Solaris 9 with gcc 3.4.2
...compile error messages
E4500:[root]:/smb/vlc/speex-1.0.5 6 > gcc -v
Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/specs
Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/l
d --disable-nls
Thread model: posix
gcc version 3.4.2
Making all in src
make[1]: Entering directory `/smb/vlc/speex-1.0.5/src'
if gcc -DPACKAGE_NAME=\"\"
2004 Aug 06
2
libspeex/SSE Intrinsics with GCC 3.3.x
On Fri, Apr 02, 2004 at 12:08:52AM -0500, Jean-Marc Valin wrote:
> I'm aware of the problem, but I don't know how to get autoconf to handle
> that properly. If someone knows how to make that work with autoconf even
> with non-gcc compilers and with default CFLAGS, I'm interested.
It's easy enough to test whether gcc will accept -msse and ifdef out the
intrinsics code
2011 Jun 17
1
speex on arm
Hi All,
I'm trying to build speex for the mini2440 board, with this toolchain: http://www.friendlyarm.net/dl.php?file=arm-linux-gcc-4.3.2.tgz
because speex is a dependency of the sip softphone 'linphone'.
The 'configure' string I'm using is this:
./configure --prefix=/usr --host=arm-linux --with-gnu-ld --disable-static --enable-fixed-point --enable-arm-asm
Other
2001 Apr 23
1
building libao under Debian
Here are some of my notes with building and using vorbis-tools-1.0beta4
under Debian Linux 2.2.
1) building libao:
make[3]: Leaving directory
`/home/jeremy/src/ogg/libao-0.6.0/src/plugins/alsa'
Making all in arts
make[3]: Entering directory
`/home/jeremy/src/ogg/libao-0.6.0/src/plugins/arts'
/bin/sh ../../../libtool --mode=compile gcc
-DPACKAGE=\"libao\"
2006 Jan 02
0
Speex 1.1.11.1 not work on symbian
Dear sirs,
Speex fails to link with my application on symbian, sdk versions 2nd edition
fp2 and fp3 with this errors:
..\..\..\SYMBIAN\8.0A\S60_2ND_FP2\EPOC32\RELEASE\ARMI\UREL\SPEEX.LIB(../../../SYMBIAN/8.0A/S60_2ND_FP2/EPOC32/BUILD/SRC/SPEEX/SYMBIAN/SPEEX/ARMI/UREL/SPEEX.o)(.text+0x158):Speex.c:
undefined reference to `floor'
2004 Aug 06
2
Notes on 1.1.4 Windows. Testing of SSE Intrinics Code and others
Jean-Marc,
Good catch on the debug mode. After compiling the same code in
release mode it does appear to be using all the registers correctly. Give
us a few days to integrate our run-time flags into 1.1.4 and I will let you
know how are testing turns out.
Aron Rosenberg
SightSpeed
At 08:54 PM 1/21/2004, you wrote:
> > 1. Compile Error with regular mode (FIXED_POINT undefined)
2013 Sep 15
2
PATCH: x86-64 support and SSE intrinscis code
Erik de Castro Lopo <mle+la at mega-nerd.com> wrote:
> The biggest of these tweaks weas to disable the intrinsics version
> fero FLAC__CPU_IA32 because I couldn't get this to compile on
> i386-linux (and we have the nasm versions). Still open to re-enabling
> this if someone can get it to work.
I know you're a skilled programmer, but... maybe you forgot to add -msse
2015 Nov 26
2
Test failed!!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Jesus,
Thanks for the report. As far as I can tell, what's happening is that
when intrinsics are enabled, we compile all tests with -msse4.1, even
when it's only run-time detected. In most cases, that doesn't cause
any issue, but sometimes the compiler will take the C code and
generate an SSEx instruction on its own. I think this is