I demand that Reinhard Tartler may or may not have written...

> On Fri, Jun 02, 2006 at 10:10:01PM +0100, Darren Salt wrote:
>> The .diff.gz, .dsc etc. for 1.1.1-1.2 are at
>>   <URL:http://zap.tartarus.org/~ds/debian/>

> Btw, why aren't you in Uploaders: and prepare a new maintainer upload? 

Siggi - any objections?

> I took your source package and gave it the version 1.1.1-2. I sucessfully
> built it on amd64, but got no sound at all (but might be chroot related, so
> I'm not sure).

Bind-mounting /dev should fix that :-)

(I can test on amd64 here, as it happens, and I've had no problems with
sound during my normal use of gxine.)

> I tried to build it on tbm's mips machine as well, and it still FTBFS. I
> attached the build log to this mail. It seems that the inline problems have
> been solved, but now there is another problem.

  h264.c:5659: sorry, unimplemented: inlining failed in call to 
'compute_mb_neighboors': function body not available
  h264.c:5718: sorry, unimplemented: called from here

Which is weird, because I don't recall it falling over on that one here...
hmm, the difference seems to be the optimisation level, at least on i386: -O2
provokes this, -O3 doesn't.

Basically, if you see any more of these, comment out or remove the 'inline'
in the offending function declaration.


--- ./src/libffmpeg/libavcodec/h264.c~  2006-06-03 14:21:41.000000000 +0100
+++ ./src/libffmpeg/libavcodec/h264.c   2006-06-03 14:21:41.000000000 +0100
@@ -5655,7 +5655,7 @@
     return 0;
 }
 
-void inline compute_mb_neighboors(H264Context *h)
+static void /*inline*/ compute_mb_neighboors(H264Context *h)
 {
     MpegEncContext * const s = &h->s;
     const int mb_xy  = s->mb_x + s->mb_y*s->mb_stride;

-- 
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy less and make it last longer.         INDUSTRY CAUSES GLOBAL WARMING.

Bugs do not exist. Programs merely have undocumented features.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to