> Hi Matthias,
>
> Cleaned up patchscript of obsolete items.
Thanks!
>
> Decided to leave the first line of the patchscript as is :
> _ output of "what /usr/bin/ld" seems too variable, even in format.
> _ too many ld's around, and not sure which ones exactly have the
> problem,
From what I fi
On 05 Jun 2008, at 16:05, Dominique Dhumieres wrote:
> Matthias,
>
> First, what /usr/bin/ld gives:
>
> /usr/bin/ld
> PROGRAM:ld PROJECT:ld64-77
> PROGRAM:ld PROJECT:ld64-77
>
> so I left the line "if [ `uname -r|sed 's,\..*,,'` = 9 ] ..." in
> PatchScript,
> but I have deleted th
Hi Dominique
> With these changes libxine1 rebuilt without problem.
thanks for testing. Could you please try again with the original .info
file?
the obsolete patches should have no effect, and the patch file I've
sent before is not used by libxine1.info.
Matthias
---
Matthias,
First, what /usr/bin/ld gives:
/usr/bin/ld
PROGRAM:ld PROJECT:ld64-77
PROGRAM:ld PROJECT:ld64-77
so I left the line "if [ `uname -r|sed 's,\..*,,'` = 9 ] ..." in PatchScript,
but I have deleted the lines you asked for in your other mail.
Second, I changed libxine1.pa
Hi again.
I've just successfully build libxine1-1.1.12-1 on an MacBook Pro.
The libxine1.info from CVS unstable actually doesn't use the
libxine1.patch I had provided.
It rather uses some regular expression fixing to get things going. I'l
try to look at those in detail.
From a first glance,
Hi Dominique (and other Intel users... :)
the compile errors comes from a part of xine which should have been
disabled by my libxine1.patch.
I've just realized that the patch in fink cvs is the one by the
initial xine 1.1.11 update and not mine.
can you try to use the attached libxine1.patc
Since I haven't had much to do with the new xine, thought I'd post
this here till I have time to look into it and get caught up.
---
TS
http://southofheaven.org/
Chaos is the beginning and end, try dealing with the rest.
Begin forwarded message:
> From: [EMAIL PROTECTED] (Dominique Dhumieres)
>
