* Fabian Greffrath , 2010-05-19, 10:12:
I believe that bashisms are the only problems here. The bug didn't
trigger earlier, because dash didn't support LINENO and configure
scripts try to avoid such shells; as a result, the configure script was
effectively run by bash. However, LINENO has been im
Processing commands for cont...@bugs.debian.org:
> tags 582037 + patch
Bug #582037 [idjc] idjc: FTBFS error: ffmpeg/avcodec.h: No such file or
directory
Added tag(s) patch.
> thank
Stopping processing here.
Please contact me if you need assistance.
--
582037: http://bugs.debian.org/cgi-bin/bugr
tags 582037 + patch
thank
Am 18.05.2010 11:34, schrieb Jakub Wilk:
I believe that bashisms are the only problems here. The bug didn't
trigger earlier, because dash didn't support LINENO and configure
scripts try to avoid such shells; as a result, the configure script was
effectively run by bash.
Am 18.05.2010 10:58, schrieb Stefano Rivera:
I still get the faulty positive and build failure with the patch.
checking for avcodec.h in legacy ffmpeg directory... yes
checking for avcodec_decode_audio3 in -lavcodec... ffmpeg_avcodec.c:3:28:
error: ffmpeg/avcodec.h: No such file or directory
ff
* Fabian Greffrath , 2010-05-18, 10:28:
Seems to be a race condition in the check for the legacy avcodec
include file location. Please try the patch attached (which also
fixes a bashism BTW).
I believe that bashisms are the only problems here. The bug didn't
trigger earlier, because dash didn
Hi Reinhard (2010.05.18_11:01:08_+0200)
> did you really regenerate the configure script? It gets generated from
> configure.in, so you either have to apply it to both files, or make sure
> configure gets regenerated.
I trusted the build script to regenerate it for me, I didn't see that
the autore
Am 18.05.2010 10:59, schrieb Reinhard Tartler:
Okay, I agree that your patch look OK to me, although I don't understand
(yet) why it fixes the race. If it fixes it, let's integrate it.
It checks some return value before the compiler even finished
compiling (and failing on) the code.
did you
On Tue, May 18, 2010 at 10:58:54 (CEST), Stefano Rivera wrote:
> Hi Fabian (2010.05.18_10:54:44_+0200)
>> In the build log, the result of the check is already (faulty) positive
>
> I still get the faulty positive and build failure with the patch.
>
> checking for avcodec.h in legacy ffmpeg directo
Hi Fabian (2010.05.18_10:54:44_+0200)
> In the build log, the result of the check is already (faulty) positive
I still get the faulty positive and build failure with the patch.
checking for avcodec.h in legacy ffmpeg directory... yes
checking for avcodec_decode_audio3 in -lavcodec... ffmpeg_avcod
On Tue, May 18, 2010 at 10:54:44 (CEST), Fabian Greffrath wrote:
> Am 18.05.2010 10:35, schrieb Reinhard Tartler:
>> I don't understand the race here. What is running in paralell to the
>> configure script here?
>
> In the build log, the result of the check is already (faulty) positive
>
> c
Am 18.05.2010 10:35, schrieb Reinhard Tartler:
I don't understand the race here. What is running in paralell to the
configure script here?
In the build log, the result of the check is already (faulty) positive
checking for avcodec.h in legacy ffmpeg directory... yes
*before* the code
On Tue, May 18, 2010 at 10:28:49 (CEST), Fabian Greffrath wrote:
> Seems to be a race condition in the check for the legacy avcodec include
> file location. Please try the patch attached (which also fixes a bashism
> BTW).
--- idjc-0.8.2.orig/configure.in
+++ idjc-0.8.2/configure.in
@@ -48,8 +48,
Seems to be a race condition in the check for the legacy avcodec
include file location. Please try the patch attached (which also fixes
a bashism BTW).
--
Dipl.-Phys. Fabian Greffrath
Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150,
Hi Reinhard (2010.05.18_07:36:52_+0200)
> > Severity: important
> that would be severity serious.
Reportbug dropped it when I wasan't looking. I raised it manually,
afterwards.
> can you please clarify what is different on your system? perhaps a
> *full* buildlog would be helpful?
Pretty standar
On Mon, May 17, 2010 at 22:31:56 (CEST), Stefano Rivera wrote:
> Package: idjc
> Version: 0.8.2-2
> Severity: important
> Justification: fails to build from source
that would be severity serious.
> idjc appears to look for libavcodec headers in the wrong place.
>
> Interesting parts in the faile
Package: idjc
Version: 0.8.2-2
Severity: important
Justification: fails to build from source
idjc appears to look for libavcodec headers in the wrong place.
Interesting parts in the failed build log:
checking for avcodec.h in legacy ffmpeg directory... yes
checking for avcodec_decode_audio3 in -
16 matches
Mail list logo
