Displaying 20 results from an estimated 100 matches similar to: "static lib"
2003 Jun 24
3
Compiling Asterisk under Yellow Dog
Hi,
I am trying to compile Asterisk under Yellow Dog 3.0 distributionn.
I am getting an error
gcc -shared -Xlinker -x -o codec_gsm.so codec_gsm.o -lgsm
/usr/bin/ld: cannot find -lgsm
May be I need packages that my distribution does not include?
What do I need to download to get it compiled?
Thanks
Serge
_________________________________________________________________
The new MSN 8: smart spam
2004 Aug 06
7
CVS changes
To all CVS users of ices 0.x:
I've just merged the ices-libshout_2 branch onto HEAD. Anyone using that branch
should switch back to HEAD to continue to get the latest updates.
This also means you now need the latest version of libshout2 from CVS in order
to build ices from CVS.
libshout2: :pserver:anoncvs@cvs.xiph.org:/usr/local/cvsroot libshout
ices:
2001 Jul 06
1
problem with vorbis autoconf stuff
It sets:
VORBIS_LIBS="$VORBIS_LIBDIR -lvorbis -lm"
VORBISFILE_LIBS="-lvorbisfile"
VORBISENC_LIBS="-lvorbisenc"
Shouldn't this be:
VORBIS_LIBS="$VORBIS_LIBDIR -lvorbis -lm"
VORBISFILE_LIBS="$VORBIS_LIBDIR -lvorbisfile"
VORBISENC_LIBS="$VORBIS_LIBDIR -lvorbisenc"
as libvorbisenc & libvorbis are also in the same
2010 May 20
3
GSM Problems
I've been trying to get wine to compile with GSM and haven't had any luck, I downloaded the most recent GSM library from http://www.quut.com/gsm/ and manually modified the Makefile to have it install to proper folders.. installed.. and heres proof that files are there in my /usr/lib folder!
Code:
-r--r--r-- 1 root root 53506 2010-05-14 01:40 /usr/lib/libgsm.a
lrwxrwxrwx 1 root root 11
2014 Aug 09
1
libvorbisfile dynamic linkage with pkg-config - inter-library dependencies?
Audacity is preparing to release version 2.0.6 shortly, so I have been
doing numerous test builds. Since the last Audacity release, my
development system (Gentoo Linux) has updated to libvorbis-1.3.4 and
libogg-1.3.1.
As a result (I think) of this, I now get link errors when
trying to compile Audacity against the system copies of libogg and
libvorbis (standard dynamic linkage to the system
2007 Mar 02
3
3.0.4 ACPI support and Opteron 2210 ?
Hello,
I originally posted this to xen-users, but someone suggested I post it here.
I am having ACPI problems on a PenguinComputing Altus1600 system.
It has 2x dual core Opteron 2210 processors.
The system boots with a standard Debian or Ubuntu SMP kernel, with ACPI
enabled. However the xen live cd, binary xen install, as well as my own custom
compile of xen 3.0.4 from source will not boot.
2000 Jul 25
2
Library issues (BOUNCE vorbis-dev@xiph.org: Non-member submission from [rob@emusic.com]) (fwd)
BTW, I need a volunteer to upgrade xiph.org to MailMan or the like. I'm
officially sick to death of majordomo.
(Or, if you want to code all the features I want in majordomo, that's fine too
;-) I'm a little bit out of time, see....
------- Forwarded Message
Sender: robert@emusic.com
I just brought the FreeAmp codebase up to speed with the latest Vorbis
source. In doing so,
2002 Sep 11
1
Compiling
I am trying to compile the example code for vorbis files and I am getting an
undefined reference, below is my Makefile, any ideas on what is wrong?
OBJS=ogg.o
ogg: $(OBJS)
cc -o ogg $(OBJS) -L/usr/local/lib -lm -lc -lvorbis
ogg.o: ogg.c
cc -I/usr/local/include -c ogg.c
clean:
rm -f $(OBJS)
<p>_________________________________________________________________
Join
2001 Jun 20
1
What makefile should we use ?
Hello,
I'm trying to write my own code for an oggplayer. Once i have my source
files, what kind of makefile should I use ? Or what commande line should i
give to the compiler ?
Thank you
ekine
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request@xiph.org'
2010 Sep 11
2
Re: Trouble with libgsm on Mac OS X 10.6.2
ralniv wrote:
> Below are my instructions for getting a libgsm friendly version of Wine compiled on SnowLeopard. I assume that you already have wine-devel installed and configured to your liking. I also assume that you use MacPorts for package management.
>
> [1] Uninstall wine-devel
>
> Code:
> sudo port uninstall wine-devel
>
>
>
> [2] Edit the portfile for
2003 Jan 05
2
VorbisFile library crashs.
Hello!
There is a problem with the VorbisFile library. It only works when I open an
OGG file for
the 1st time. After I closed the file and try to open another one or the
same it crashs. It seems it applies to the use of either ov_open or ov_test
functions or their combination.
I wrote a test app that illustrates the bug. It crashs with a message
"Unmapped memory exception". It's
2004 Aug 06
2
ices configure script
Hi,
I'm having difficulty getting ices 0.2.2 to see my lame install and my
perl install. The lame libraries (v3.91) are installed in:
/usr/local/lib/ with the header file at: /usr/local/include/lame/lame.h,
but when I run:
./configure --with-lame --with-lame-includes=/usr/local/include/lame/
--with-lame-libraries=/usr/local/
it says it can't find the lame libraries. ldconfig seems
2007 Mar 19
0
2 commits - configure.ac
configure.ac | 42 +++++++++++++++++++++++++++++++++---------
1 files changed, 33 insertions(+), 9 deletions(-)
New commits:
diff-tree 4b27c650286f819714b1fd9048385796037a516a (from parents)
Merge: deb389f11445d7d935e05ef44590507f0e64db84 00252e7f75acd6466c2ae7c6fc446f4741dab7a1
Author: Benjamin Otte <otte@gnome.org>
Date: Mon Mar 19 09:14:48 2007 +0100
Merge branch
2004 Aug 06
2
Lame, Bitrates, ReEncoding I
I'd like to use the Bitrate and Reencode features of ices and understand I
must recompile with lamelib.
However, it's Very Unclear where to begin here. This is noted in the
ices-0.2.3 INSTALL file:
I installed lame as a debian package so lame.h is in
/usr/include/lame/lame.h
and libmp3lame.a is in /usr/lib. configure finds everything automatically.
<p>I assume we
2004 Aug 06
6
more on building with lame
On Tuesday, 26 June 2001 at 11:02, Denys Sene dos Santos wrote:
>
> Lame3.88 has no reencoding.
> Because this, I used 3.86... but it needs to copy the libs manualy
> to the right places
Er, what version of ices are you running? ices 0.1.0 will not work
with 3.86. Lame 3.88 also builds much better.
> Why is the Lame/Ices/Icecast documentation so poor ???
Because
2004 Aug 06
2
Two Things: Python 2.1 & ices 0.2.2 / Multiple Streams
First off, I managed to build iceS 0.2.2 with Python 2.1, though I had to
add -lutil to the $LIBS definition whilst ./configure'ing. Otherwise,
configure won't find Py_Initialize
Secondly - multiple streams
I've added a second "stream" definition to my ices.conf, and both streams
show up as sources for icecast, (http://blah.com:8000/list.cgi), though
when i try to connect
2000 Dec 15
1
AIX + ogg123
Has anyone managed to get ogg123 to compile in AIX? I'm got an RS6k with a
PPC 604e, running AIX 4.3.3. I can get libogg, libvorbis, libao, oggenc
(so, everything _but_ ogg123) to compile just fine. I'm using gcc,
thankfully, and not the native IBM compilers. I believe the problem to be
with the linker. By default gcc for AIX doesn't use the GNU linker, but
the standard AIX
2001 Mar 13
1
Compiling vorbis-tools on NetBSD-1.5/i386
[This mail is a bit long: sorry.]
Hi,
I have been trying to compile vorbis-tools-1.0beta4 on NetBSD-1.5/i386,
and I get the following:
---------------------
Upon typing
./configure --prefix=/usr/pkg/ --with-ogg-prefix=/usr/pkg/
--with-vorbis-prefix=/usr/pkg/ --with-ao-prefix=/usr/pkg/
checking for Ogg... yes
checking for Vorbis... yes
checking for ao... no
*** Could not run
2006 Aug 18
6
Ogg Player Code
Hello,
In one of my recent assignments, I was asked to develop a ogg player.
I am not able to find the right repository of the source code. There are few repositories on vorbis but I am not clear which one is the right one for Windows environment.
If somebody has successfully compiled any ogg player ever, his ideas will be helpful to me.
In one of the code set, I was able to compile the
2007 Oct 25
0
[PATCH] Fix logic in mad detection
If neither --enable-mad nor --disable-mad was given, try to find mad.
If it wasn't found, warn the user, but don't fail.
If --enable-mad was given, fail if mad is not found. If --disable-mad
was given, don't warn the user, as the user already knows that mad won't
be enabled.
mad is not and should not be considered a hard requirement, as it's
absent in most distros due to