On Wednesday, 28. August 2002 15:41, Igor Kolar wrote:
> It's nice to see xine's progressing and is soon to hit the 1.0
> release. For that, I'm only grateful, however, I would have a
> question on the libxine API.
> Version 0.9.13, downloaded from sourceforge.net, compiled without
> probems. xine-check gives no warnings, xine, on the other hand,
> yealds an error:
> $ xine [RET]
> xine: error while loading shared libraries: xine: undefined symbol:
> It seems loading libxine is about the first thing the xine binary
> (part of xine-ui; right) does, as running it with the -v (version)
> option produces the same result. So I went about searching the
> mailing lists as to what happened. xine-users registered some cases,
> but non offered a solution. Then I searched the xine-devel list.
> In an interesting thread, entitled "new public xine api", the
> following is
> said by Daniel Caujolle-Bert:
> > Hmmm, now that I think about it, we don't need most of this:
> > -/*
> > - * prepare and setup localization for xine-lib usage
> > - * this function should be called before xine_init()
> > - */
> > -char *xine_set_locale ();
> Gasp, let it there, this is optional.
> that would be URL:
> -> http://sourceforge.net/mailarchive/message.php?msg_id=1757545
> So what seems to have occured is an API-mismatch between xine-ui (the
> xine front end) and xine-lib (libxine). The latter seems to no longer
> contain the xine_set_locale() function, which in turn causes xine to
Have you checked out the new_api branch of cvs? The changes discussed
in the mail you've found only affect this branch. The head branch of
cvs, which you will checkout when you don't do anything special still
The new_api branch is a development version and does not work now.
* We used to try various strange things. Let's not.