Hi!
On 02/03/13 18:13, Reinhard Tartler wrote:
> On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge wrote:
>> I had a second look at this, and it turned out that it's actually a bug
>> in upstream's configure.
>
> Your patch does not apply to current libav.org master. However, I have
> found this up
Sorry for the delay getting back to you.
On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge wrote:
> I had a second look at this, and it turned out that it's actually a bug
> in upstream's configure.
Your patch does not apply to current libav.org master. However, I have
found this upstream patch tha
On Wed, Feb 27, 2013 at 5:53 PM, Roland Stigge wrote:
> Hi Reinhard,
>
> On 02/27/2013 05:47 PM, Reinhard Tartler wrote:
>> On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge wrote:
>>> Hi Reinhard,
>>> On 02/27/2013 02:57 PM, Reinhard Tartler wrote:
I don't understand this. Why does gcc on powe
Hi Reinhard,
On 02/27/2013 05:47 PM, Reinhard Tartler wrote:
> On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge wrote:
>> Hi Reinhard,
>> On 02/27/2013 02:57 PM, Reinhard Tartler wrote:
>>> I don't understand this. Why does gcc on powerpcspe enable altivec by
>>> default? If powerpcspe ships a gcc
On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge wrote:
> Hi Reinhard,
>
> On 02/27/2013 02:57 PM, Reinhard Tartler wrote:
>> I don't understand this. Why does gcc on powerpcspe enable altivec by
>> default? If powerpcspe ships a gcc that has broken default settings,
>> then this should be fixed fir
Hi Reinhard,
On 02/27/2013 02:57 PM, Reinhard Tartler wrote:
> I don't understand this. Why does gcc on powerpcspe enable altivec by
> default? If powerpcspe ships a gcc that has broken default settings,
> then this should be fixed first.
I had a second look at this, and it turned out that it's a
On Tue, Feb 26, 2013 at 10:32 PM, Roland Stigge wrote:
>> OTOH, I wonder why the gcc and the toolchain on this port do not set
>> the proper default flags by themselves. Since
>> http://wiki.debian.org/PowerPCSPEPort does not clarify this either,
>> can you perhaps jump in here?
>
> ...however, -
On Tue, Feb 26, 2013 at 10:45 PM, Roland Stigge wrote:
> On 26/02/13 19:32, Reinhard Tartler wrote:
>> TBH, I do not feel comfortable with maintaining this patch outside of
>> libav, escp. since upstream already does take care about unusual
>> environments. The libav packaging is already complicat
On 26/02/13 19:32, Reinhard Tartler wrote:
> TBH, I do not feel comfortable with maintaining this patch outside of
> libav, escp. since upstream already does take care about unusual
> environments. The libav packaging is already complicated enough.
> Therefore, I would like to ask you to reconsider
On 26/02/13 22:32, Roland Stigge wrote:
> On 26/02/13 19:43, Reinhard Tartler wrote:
>> On Tue, Feb 26, 2013 at 4:36 PM, Roland Stigge wrote:
>>
>>> The attached patch fixes this by assing support for powerpcspe in the Debian
>>> packaging, but omitting Altivec (not available on powerpcspe) in thi
On 26/02/13 19:43, Reinhard Tartler wrote:
> On Tue, Feb 26, 2013 at 4:36 PM, Roland Stigge wrote:
>
>> The attached patch fixes this by assing support for powerpcspe in the Debian
>> packaging, but omitting Altivec (not available on powerpcspe) in this case.
>
> I think a better solution would
On Tue, Feb 26, 2013 at 4:36 PM, Roland Stigge wrote:
> The attached patch fixes this by assing support for powerpcspe in the Debian
> packaging, but omitting Altivec (not available on powerpcspe) in this case.
I think a better solution would be to pass "-cpu=e500v2" to the
configure switch inst
On Tue, Feb 26, 2013 at 5:56 PM, Roland Stigge wrote:
> Hi,
>
> On 02/26/2013 05:42 PM, Reinhard Tartler wrote:
>> Thank you for the patch. I really think that upstream would be very
>> happy to include changes to configure that would make those switches
>> unnecessary. Would you be willing to sen
Hi,
On 02/26/2013 05:42 PM, Reinhard Tartler wrote:
> Thank you for the patch. I really think that upstream would be very
> happy to include changes to configure that would make those switches
> unnecessary. Would you be willing to send a patch against configure
> upstream?
Yes, that would be pos
On Tue, Feb 26, 2013 at 4:36 PM, Roland Stigge wrote:
> libav FTBFS on powerpcspe[1] like this:
>
> [...]
> dh_testdir
> mkdir -p debian-static
> cd debian-static && CFLAGS="-fstack-protector --param=ssp-buffer-size=4
> -Wformat -Werror=format-security" CPPFLAGS="-D_FORTIFY_SOURCE=2"
> LDFLAGS="
Source: libav
Version: 6:0.8.5-1
Severity: wishlist
Tags: patch sid
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe
Hi,
libav FTBFS on powerpcspe[1] like this:
[...]
dh_testdir
mkdir -p debian-static
cd debian-static && CFLAGS="-fstack-protector --param=ssp-buffer-size=4
-Wformat -We
16 matches
Mail list logo
