search for: lobogg

Displaying 6 results from an estimated 6 matches for "lobogg".

Did you mean: libogg
2009 Oct 21
3
Cross-compiling speex
Hi all, I'm cross-compiling speex for a GNU/Linux ARM target. I want to compile only the libraries, and not the speex executables. I don't have a libogg cross-compiled, and would prefer the need to have to set it up. Unfortunately: 1/ the speex executables depend on libogg header files, although, the speex executables are only compiled if the libogg header files are available 2/ the
2009 Oct 22
3
Cross-compiling speex
Hi Jean-Marc
2009 Oct 22
1
Cross-compiling speex
...libogg unconditionally. So we had to >> patch it to remove this check. I do not recall, whether this was somehow >> fixed or not. >> >> On Wed, Oct 21, 2009 at 15:19, Jean-Marc Valin >> <jean-marc.valin at usherbrooke.ca> wrote: >>> Try adding --without-lobogg to the configure script. Otherwise, just >>> ignore the error because the important part (libspeex/) has already been >>> built when the error is reported. >>> >>> ? ? ? ?Jean-Marc >>> >>> >>> >>> Ben Leslie a ?crit : >>&...
2008 Nov 03
0
No subject
configure *assumes* that you have libogg unconditionally. So we had to patch it to remove this check. I do not recall, whether this was somehow fixed or not. On Wed, Oct 21, 2009 at 15:19, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > Try adding --without-lobogg to the configure script. Otherwise, just > ignore the error because the important part (libspeex/) has already been > built when the error is reported. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0Jean-Marc > > > > Ben Leslie a =C3=A9crit : >> Hi all, >> >> I'm cross...
2009 Oct 21
0
Cross-compiling speex
Try adding --without-lobogg to the configure script. Otherwise, just ignore the error because the important part (libspeex/) has already been built when the error is reported. Jean-Marc Ben Leslie a ?crit : > Hi all, > > I'm cross-compiling speex for a GNU/Linux ARM target. > > I want to compile only...
2009 Oct 22
0
Cross-compiling speex
...*assumes* that you have libogg unconditionally. So we had to > patch it to remove this check. I do not recall, whether this was somehow > fixed or not. > > On Wed, Oct 21, 2009 at 15:19, Jean-Marc Valin > <jean-marc.valin at usherbrooke.ca> wrote: >> Try adding --without-lobogg to the configure script. Otherwise, just >> ignore the error because the important part (libspeex/) has already been >> built when the error is reported. >> >> Jean-Marc >> >> >> >> Ben Leslie a ?crit : >>> Hi all, >>> >&gt...