Hi On Apr 22, 2008, at 3:09 AM, Jean-François Mertens wrote:
> Hi Matthias, > > Please post a full copy of your message on the tracker thread, + > your new info > and and patch files.. I did update my mail and tried to put it into the tracker in a structured way. > A side question in my mind is still why you need this disabling > which I didn't; would be nice > to clarify. What system do you have then? I remember you said you are using 10.4. This means you are using XCode 2.5. The linker with XCode 2.5 does not complain about absolute addressing code in shared libraries. The one from XCode 3.0 does. If you do a "what /usr/bin/ld", I get "PROGRAM:ld PROJECT:ld64-77". you should get an older revision number. also with the XCode from the iPhone SKD you'll get a newer version which also accepts the problematic asm code. > For caca, I've no problem, there is only one dependent pkg (gst- > plugins-good-0.10) besides > libxine itself, and it builds as well with the new libcaca as with > the old one. So, though I didn't > get yet an explicit approval from its maintainer to rev-up and > update deps, I hope I know > him sufficiently well to consider this as a tacit approval. > This will clear the way for libxine itself. good. > still t is probably safer for the future to prepare caca in a way > completely conformant with > fink's shlibs policy, so that in the future no upgrades have to be > done to dependent pkgs > when updating caca. what exactly should we do with caca then? > For libxine itself, true that the main problem I noticed was with > gxine (tried several versions_ > upper bound (0.5.11 ?): to stay compatible with the "non-pangocairo > branch"; though I had > the impression that the issue was that the configure script, when > checking for xine's version, > got confused by the "." in the third item (with 1.1.11.1) _ since > testing with [0-9]* or the like, > don't remember exactly_, and so would still have hoped that with > 1.1.12 this would be over ... > You seem to imply that not ... Too bad then.. I successfully compiled gxine (forgot if latest release or cvs) against an installed xine-lib. however, it did not work. > But anyway a clear upgrade strategy is still missing here, but > shouldn't be too hard to get.. > The essential remaining questions are, as you mention, as to an > upgrade strategy, which > is completely absent in the submission as it is. I've put a comment on the tracker item, but I guess this might be as well discussed on the list: to me, the simplest solution would be a libxine2 without paying to much attention to the 4 packages which depend on libxine1 and notify those maintainers that there's an updated libxine available. An update to the new xine-lib should be most interesting to the videocut package which sports a new maintstream version btw. amarok-engine-xine works with the new xine-lib, but there xine is only used for audio playback and there are not that many changes on that front (I guess). kmplayer worked with new xine-lib, gxine didn't want to show a video to me. There is the general problem of xine-frontends which come from the X11 community that they don't know how to use the mac os x video output and just assumes Xv with video overlay is working well, which is not the case on mac, as far as I know. I was thinking on a) packaging xine-ui to have at least a recent front- end even if its using X11 output and maybe to try to port it to use the mac os x video output which would lead to an X11-ish looking but powerful movieplayer. > > Pls redirect any replies rather to the thread > https://sourceforge.net/tracker/?func=detail&atid=414256&aid=1927452&group_id=17203 > to keep information together ... sorry. most facts are in the tracker. open discussion is here. regards, matthias ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel