From: Dennis S. <dm...@so...> - 2002-04-29 22:30:48
|
I've been trying to get ui 0.9.9 to build properly for a while, but with no luck. First is the same "finding the wrong version of XINE" problem as encountered by a number of others. Running ldconfig after installing lib 0.9.9 *does not* help. If I manually set LD_LIBRARY_PATH to include XINE I can configure successfully, but then when I try to make I get: /usr/bin/ld: cannot find -ltermcap collect2: ld returned 1 exit status when running "gcc ... libreadline.a". I've got termcap installed on my system, so I don't know why the problem occurs. I'm using Redhat 7.2+ various updates. I really like XINE, but at this point I'll probably just wait for somebody to generate an RPM so that I can try the latest without so many build hassles. - Dennis |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-04-29 22:42:10
|
Hi, Dennis Sosnoski wrote: > I've been trying to get ui 0.9.9 to build properly for a while, but with > no luck. First is the same "finding the wrong version of XINE" problem > as encountered by a number of others. Running ldconfig after installing > lib 0.9.9 *does not* help. If I manually set LD_LIBRARY_PATH to include > XINE I can configure successfully, but then when I try to make I get: > > /usr/bin/ld: cannot find -ltermcap > collect2: ld returned 1 exit status Are you sure you have libtermcap ? If you really have it, try this: GLOBAL_CFLAGS=/where/is/termcap/lib ./configure then try make again. Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: Dennis S. <dm...@so...> - 2002-04-30 00:39:15
|
I have libtermcap installed from RPM, not from source - is the source build needed? The library location is /lib/libtermcap.so.2; using either -L/lib or -L/lib/libtermcap.so.2 does not seem to effect the problem. - Dennis Daniel Caujolle-Bert wrote: > Hi, > > Dennis Sosnoski wrote: > >> I've been trying to get ui 0.9.9 to build properly for a while, but >> with no luck. First is the same "finding the wrong version of XINE" >> problem as encountered by a number of others. Running ldconfig after >> installing lib 0.9.9 *does not* help. If I manually set >> LD_LIBRARY_PATH to include XINE I can configure successfully, but >> then when I try to make I get: >> >> /usr/bin/ld: cannot find -ltermcap >> collect2: ld returned 1 exit status > > > Are you sure you have libtermcap ? If you really have it, > try this: > GLOBAL_CFLAGS=/where/is/termcap/lib ./configure > > then try make again. > > Cheers. |
From: Siggi L. <si...@us...> - 2002-04-30 06:21:39
|
On Mon, 29 Apr 2002, Dennis Sosnoski wrote: > I have libtermcap installed from RPM, not from source - is the source > build needed? The library location is /lib/libtermcap.so.2; using either > -L/lib or -L/lib/libtermcap.so.2 does not seem to effect the problem. That definitely makes the difference! Yes, you'll either have to install from source or install the libtermcap-devel (or whatever it's called exactly) package. Cheers, Siggi |
From: Dennis S. <dm...@so...> - 2002-04-30 19:20:15
|
That's great to know, but as it is now this is neither listed as a dependancy nor checked by configure. You might want to do one or the other to help others avoid this problem. - Dennis Siggi Langauf wrote: >On Mon, 29 Apr 2002, Dennis Sosnoski wrote: > >>I have libtermcap installed from RPM, not from source - is the source >>build needed? The library location is /lib/libtermcap.so.2; using either >>-L/lib or -L/lib/libtermcap.so.2 does not seem to effect the problem. >> > >That definitely makes the difference! >Yes, you'll either have to install from source or install the >libtermcap-devel (or whatever it's called exactly) package. > >Cheers, > Siggi > > |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-04-30 19:41:13
|
Hi, Dennis Sosnoski wrote: > That's great to know, but as it is now this is neither listed as a > dependancy nor checked by configure. You might want to do one or the > other to help others avoid this problem. I'm currently fighting with that, guess 0.9.10 will be fixed. Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-04-29 22:50:15
|
Ooch, seems tired: GLOBAL_CFLAGS=-L/where/is/termcap/lib ./configure is better ;-) Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: Siggi L. <si...@us...> - 2002-04-30 06:20:25
|
Hi, On Tue, 30 Apr 2002, Daniel Caujolle-Bert wrote: > =09GLOBAL_CFLAGS=3D-L/where/is/termcap/lib ./configure Hasn't G=FCnter changed that to "CFLAGS=3D..." lately? |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-05-02 07:28:56
|
Hi Siggi, Siggi Langauf wrote: > Hi, > > On Tue, 30 Apr 2002, Daniel Caujolle-Bert wrote: > > >> GLOBAL_CFLAGS=-L/where/is/termcap/lib ./configure > > > Hasn't Günter changed that to "CFLAGS=..." lately? No, just xine-lib. Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: <bar...@t-...> - 2002-05-02 09:03:56
|
Hi Daniel, On Tue, 30 Apr 2002, Daniel Caujolle-Bert wrote: > >>=09GLOBAL_CFLAGS=3D-L/where/is/termcap/lib ./configure > > > > > > Hasn't G=FCnter changed that to "CFLAGS=3D..." lately? > > =09No, just xine-lib. *aargh* ... does that mean xine-ui is _still_ using GLOBAL_CFLAGS?!? guenter -- time is a funny concept |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-05-02 12:30:51
|
Hi Guenter, Guenter Bartsch wrote: > Hi Daniel, > > On Tue, 30 Apr 2002, Daniel Caujolle-Bert wrote: > > >>>> GLOBAL_CFLAGS=-L/where/is/termcap/lib ./configure >>> >>> >>>Hasn't Günter changed that to "CFLAGS=..." lately? >> >> No, just xine-lib. > > > *aargh* ... does that mean xine-ui is _still_ using GLOBAL_CFLAGS?!? Exactly ;-) Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: <bar...@t-...> - 2002-05-02 19:28:19
|
Hi Daniel, On Thu, 2 May 2002, Daniel Caujolle-Bert wrote: > > *aargh* ... does that mean xine-ui is _still_ using GLOBAL_CFLAGS?!? > > Exactly ;-) hum - I guess standard-conforming CFLAGS handling and so-names will be top-priorities for 0.9.10 cheers, guenter -- time is a funny concept |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-05-02 20:04:02
|
Hi Guenter, Guenter Bartsch wrote: > Hi Daniel, > > On Thu, 2 May 2002, Daniel Caujolle-Bert wrote: > > >>>*aargh* ... does that mean xine-ui is _still_ using GLOBAL_CFLAGS?!? >> >> Exactly ;-) > > > hum - I guess standard-conforming CFLAGS handling and so-names will be > top-priorities for 0.9.10 GLOBAL_CFLAGS are gone now. Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: Siggi L. <si...@us...> - 2002-05-02 20:41:33
|
Hi folks, I guess it's time to make a list of "release critical stuff" for 0.9.10, so: On Thu, 2 May 2002, Guenter Bartsch wrote: > hum - I guess standard-conforming CFLAGS handling and so-names will be > top-priorities for 0.9.10 Yup, Daniel has done the CFLAGS, so I can do the SONAMEs. Can I safely assume that the API is stable now? Otherwise, I'd strongly recommend to open an "experimental" branch in CVS for any API changes in order to freeze the API for 1.0 now. (this is not quite a technical requirement but it will avoid ugly version races...) What else do we have? - VCD support has been reported to be broken (any more info on that?) - the missing DXR3 headers [fixed] - link plugins with correct libxine{,utils} even if 0.9.8 is installed (does xine do this currently for normal installs?) (hmmm, ist that already all of it?) Cheers, Siggi |
From: Daniel Caujolle-B. <seg...@cl...> - 2002-05-02 21:14:40
|
Hi, Siggi Langauf wrote: > Hi folks, > > I guess it's time to make a list of "release critical stuff" for 0.9.10, > so: > > On Thu, 2 May 2002, Guenter Bartsch wrote: > > >>hum - I guess standard-conforming CFLAGS handling and so-names will be >>top-priorities for 0.9.10 > > > Yup, Daniel has done the CFLAGS, so I can do the SONAMEs. > Can I safely assume that the API is stable now? Otherwise, I'd strongly > recommend to open an "experimental" branch in CVS for any API changes in > order to freeze the API for 1.0 now. > (this is not quite a technical requirement but it will avoid ugly > version races...) > > What else do we have? > > - VCD support has been reported to be broken (any more info on that?) > - the missing DXR3 headers [fixed] > - link plugins with correct libxine{,utils} even if 0.9.8 is installed > (does xine do this currently for normal installs?) At least on my system, latest installed libs are correctly linked to bins/plugins, even if an old xine-lib is installed. BTW, what about the uninstall problem you wrote about here, i want to reproduce (or maybe you have a nice log, like the debian package build you pointed out)?. > > (hmmm, ist that already all of it?) - found and fix the "no audio with mpeg1 after mpeg2 playback" bug. Cheers. -- 73's de Daniel, F1RMB. -=- Daniel Caujolle-Bert -=- seg...@cl... -=- -=- f1...@f1... (AMPR NET) -=- |
From: <bar...@t-...> - 2002-05-05 18:38:57
|
Hi folks, wow. the public libxine xine api state is much worse than I thought. I have been working on cleaning it up, but I'll need more time for this one. My goal is an interface which is consistent and also a true abstraction layer so it will be easy to use and also less-likely to break when there are changes in the xine engine. also, documentation is very important - but at this point there is hardly any and I must confess I don't remember the meaning of everything so I have to dig into the code to find out what it was good for. so, don't hold your breath for 0.9.10 - although I still expect it to be released some time this week cheers, guenter -- time is a funny concept |
From: Bartlomiej M. <fo...@kl...> - 2002-05-05 19:02:41
|
On Sunday 05 May 2002 20:38, Guenter Bartsch wrote: > Hi folks, > > wow. the public libxine xine api state is much worse than I thought. I > have been working on cleaning it up, but I'll need more time for this o= ne. > My goal is an interface which is consistent and also a true abstraction > layer so it will be easy to use and also less-likely to break when ther= e > are changes in the xine engine. > > also, documentation is very important - but at this point there is hard= ly > any and I must confess I don't remember the meaning of everything so I > have to dig into the code to find out what it was good for. > > so, don't hold your breath for 0.9.10 - although I still expect it to b= e > released some time this week That's fine for me:))) Just say - the docs changes will be huge one (re-translation will be need= ed)=20 or just correction and insertion of new features (so translation can be j= ust=20 updated)? Regards --=20 _4ever_ |
From: <bar...@t-...> - 2002-05-05 19:11:16
|
Hi, On Sun, 5 May 2002, Bartlomiej Muryn wrote: > > also, documentation is very important - but at this point there is hardly > > any and I must confess I don't remember the meaning of everything so I > > have to dig into the code to find out what it was good for. > That's fine for me:))) > Just say - the docs changes will be huge one (re-translation will be needed) > or just correction and insertion of new features (so translation can be just > updated)? erm - I didn't know header file comments are being translated ? cheers, guenter -- time is a funny concept |
From: Bartlomiej M. <fo...@kl...> - 2002-05-05 19:14:14
|
On Sunday 05 May 2002 21:10, Guenter Bartsch wrote: > Hi, > > On Sun, 5 May 2002, Bartlomiej Muryn wrote: > > > also, documentation is very important - but at this point there is > > > hardly any and I must confess I don't remember the meaning of > > > everything so I have to dig into the code to find out what it was g= ood > > > for. > > > > That's fine for me:))) > > Just say - the docs changes will be huge one (re-translation will be > > needed) or just correction and insertion of new features (so translat= ion > > can be just updated)? > > erm - I didn't know header file comments are being translated ? Sure - not:)! I thinked about end-user docs.. --=20 _4ever_ |
From: Morten N. <mo...@ni...> - 2002-05-05 19:14:24
|
Bartlomiej Muryn wrote: > On Sunday 05 May 2002 20:38, Guenter Bartsch wrote: > >>Hi folks, >> >>wow. the public libxine xine api state is much worse than I thought. I >>have been working on cleaning it up, but I'll need more time for this one. >>My goal is an interface which is consistent and also a true abstraction >>layer so it will be easy to use and also less-likely to break when there >>are changes in the xine engine. >> >>also, documentation is very important - but at this point there is hardly >>any and I must confess I don't remember the meaning of everything so I >>have to dig into the code to find out what it was good for. >> >>so, don't hold your breath for 0.9.10 - although I still expect it to be >>released some time this week > > That's fine for me:))) > Just say - the docs changes will be huge one (re-translation will be needed) > or just correction and insertion of new features (so translation can be just > updated)? > talking of next xine... I posted an url to a diff to get rid of most of the compiler warnings in xine-lib... I haven't heard any comments on it, and wondered if anyone have looked at it, or even applied it/checked it in? |
From: Siggi L. <si...@us...> - 2002-05-06 00:47:25
|
On Sun, 5 May 2002, Morten Nilsen wrote: > talking of next xine... I posted an url to a diff to get rid of most of > the compiler warnings in xine-lib... > I haven't heard any comments on it, and wondered if anyone have looked > at it, or even applied it/checked it in? I looked at it, it was too big for me to understand it immediately, so I moved on to other stuff... Still would be nice if there are no warnings ;-) Cheers, Siggi |
From: Brian J. C. <bc...@wp...> - 2002-05-02 21:26:19
|
> What else do we have? There was the issue with WINE headers not included with Xine being read and bombing out the compile. It never affected me, but someone mentioned it was fixed in CVS, I think. Brian J. Conway bc...@wp... "Any man who can drive safely while kissing a pretty girl is simply not giving the kiss the attention it deserves." - Albert Einstein |
From: <bar...@t-...> - 2002-05-02 21:50:16
|
Hi Siggi, On Thu, 2 May 2002, Siggi Langauf wrote: > > hum - I guess standard-conforming CFLAGS handling and so-names will be > > top-priorities for 0.9.10 > > Yup, Daniel has done the CFLAGS, so I can do the SONAMEs. very good. > Can I safely assume that the API is stable now? not yet, but I will do my best to review the api on saturday (sorry, only the weekend once again - university, university...). I expect only minor changes will be necessary, but I want to make sure I've reviewed it. Maybe also one small addition "select_video_channel()" will come in here. > Otherwise, I'd strongly recommend to open an "experimental" branch in > CVS for any API changes in order to freeze the API for 1.0 now. (this is > not quite a technical requirement but it will avoid ugly version > races...) I think as long as only functions/constants are added, i.e. backward(upward/downward ... I must confess I always confuse these)-compatible changes are done this shouldn't be a problem. > - VCD support has been reported to be broken (any more info on that?) humm ... hope I'll be able to check it on the weekend cheers, guenter |
From: Chris B. <re...@fu...> - 2002-05-03 02:24:41
|
On Thu, 2 May 2002, Siggi Langauf wrote: > Hi folks, > > I guess it's time to make a list of "release critical stuff" for 0.9.10, > so: > > > (hmmm, ist that already all of it?) > Well, one thing that I'd like to have fixed is the annoying behavior of both 0.9.8 and 0.9.9 where xine runs fine for root, but segfaults on initialization for all non-privledged users. This behavior is on a stock Slackware 8.0 system. |
From: <dp...@ds...> - 2002-05-03 03:25:54
|
On Thu, May 02, 2002 at 07:24:22PM -0700, Chris Bradford wrote: > Well, one thing that I'd like to have fixed is the annoying behavior of both > 0.9.8 and 0.9.9 where xine runs fine for root, but segfaults on > initialization for all non-privledged users. > > This behavior is on a stock Slackware 8.0 system. Can you use gdb or another debugger to provide a trace to show what's causing it? I use Xine on several systems, x86 and PPC, laptops and desktops, and have never encountered this behavior. -- Derrik Pates | Sysadmin, Douglas School | #linuxOS on EFnet dp...@ds... | District (dsdk12.net) | #linuxOS on OPN |