Displaying 2 results from an estimated 2 matches for "xiph_path_ogg2".
Did you mean:
xiph_path_ogg
2004 Aug 06
1
Configure can't fine ogg
looks like ogg2.m4 and ogg.m4 both exist in the m4 dir, but the AC macro
defined in both cases is XIPH_PATH_OGG, so my guess is that AC is picking
up ogg2.m4 first and using that incorrectly....
is there a reason the macro name in ogg2.m4 is XIPH_PATH_OGG and not
XIPH_PATH_OGG2 ?
oddsock
At 11:51 AM 5/26/2004, you wrote:
>On Wed, 2004-05-26 at 17:05, Jack Moffitt wrote:
> > > > checking for Ogg2... no
> > >
> > > Just to answer my own question, for the sake of the archive, it seems
> that
> > > Ogg development work in SVN is...
2004 Aug 06
2
Configure can't fine ogg
> > checking for Ogg2... no
>
> Just to answer my own question, for the sake of the archive, it seems that
> Ogg development work in SVN is actually in a module called ogg2, not in the
> ogg module, and it's this that icecast was looking for.
Why is icecast checking for unreleased Ogg code?
jack.
--- >8 ----
List archives: http://www.xiph.org/archives/
icecast