nvalid parameter
combination for AltiVec intrinsic
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator an
.
It is an issue with altivec implementation on ppc64el, which actually
needs to be corrected.
The definitive fix would be to write ppc64el altivec code, which is not
a quick job. Just as it was done for supercollider, disabling altivec
for ppc64el at least allows it to build.
That is in the patch attached
y 17 23:11:19 2016 +0100
>
> debian/rules: disabled altivec/vsx for ppc64el
>
> since the package does not support the usage for now
>
> patch by Fernando Seiti Furusato,
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766630
>
> diff --git a/debian/changelog
Your message dated Fri, 21 Aug 2015 13:34:34 +
with message-id e1zsmso-00015o...@franck.debian.org
and subject line Bug#796269: Removed package(s) from unstable
has caused the Debian Bug report #729332,
regarding libpostproc: FTBFS on powerpcspe because of AltiVec assumption
to be marked
Source: supercollider
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
The package fails to build from source on ppc64el because the usage of altivec
is not implemented for the architecture.
So, the workaround was to disable it for ppc64el
Maintainer,
The package fails to build from source on ppc64el because the usage of
altivec is not implemented for the architecture.
So, the workaround was to disable it for ppc64el.
What does usage of altivec is not implemented? In supecollider, or
in the compiler?
In any case, perhaps
Hi Felipe. Thank you for your very quick response.
What does usage of altivec is not implemented? In supecollider, or
in the compiler?
In supercollider.
In any case, perhaps the solution is to disable supernova in ppc64el
as well instead of adding custom flags.
Simply disabling
is that in ppc64el the default compile flags include -mvsx
-which also implies altivec support, so just disabling supernova
doesn't work, the compiler will still try to build the altivec stuff.
Doing a simple :
$ gcc -dM -E - /dev/null|grep ALTIVEC
#define __ALTIVEC__ 1
#define __APPLE_ALTIVEC__ 1
it for ppc64el did not do the work (completely), but
you can test it if you want =)
The problem is that in ppc64el the default compile flags include -mvsx
-which also implies altivec support, so just disabling supernova
doesn't work, the compiler will still try to build the altivec stuff
On Fri, 24 Oct 2014 12:13:16 -0300
Felipe Sateler fsate...@debian.org wrote:
I had a few questions regarding the patch for enabling altivec on
ppc32, I'll repeat them here:
I'm very ignorant on altivec (or simd in general), but I try to
understand the patch anyway. This patch seems
On Fri, Oct 24, 2014 at 12:27 PM, Konstantinos Margaritis
mar...@freevec.org wrote:
On Fri, 24 Oct 2014 12:13:16 -0300
Felipe Sateler fsate...@debian.org wrote:
I had a few questions regarding the patch for enabling altivec on
ppc32, I'll repeat them here:
I'm very ignorant on altivec
-maltivec and -mabi=altivec wholesale to supercollider (in
d/rules), not the vector attribute replacing code.
I am thinking the same as Felipe here.
Best
Dan
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http
Your message dated Mon, 21 Apr 2014 10:08:47 +
with message-id e1wcb9b-0002ww...@franck.debian.org
and subject line Bug#732159: Removed package(s) from unstable
has caused the Debian Bug report #410962,
regarding [PowerPC] mplayer doesn't work on G3 macs because of altivec
instructions
Your message dated Mon, 21 Apr 2014 10:08:47 +
with message-id e1wcb9b-0002ww...@franck.debian.org
and subject line Bug#732159: Removed package(s) from unstable
has caused the Debian Bug report #410962,
regarding [PowerPC] mplayer doesn't work on G3 macs because of altivec
instructions
Your message dated Mon, 21 Apr 2014 10:08:47 +
with message-id e1wcb9b-0002ww...@franck.debian.org
and subject line Bug#732159: Removed package(s) from unstable
has caused the Debian Bug report #410962,
regarding [PowerPC] mplayer doesn't work on G3 macs because of altivec
instructions
Your message dated Mon, 21 Apr 2014 10:08:47 +
with message-id e1wcb9b-0002ww...@franck.debian.org
and subject line Bug#732159: Removed package(s) from unstable
has caused the Debian Bug report #410962,
regarding [PowerPC] mplayer doesn't work on G3 macs because of altivec
instructions
Your message dated Fri, 23 Nov 2012 21:17:31 +
with message-id e1tc0ct-0001be...@franck.debian.org
and subject line Bug#627197: fixed in mplayer2 2.0-665-gb5349bb-2
has caused the Debian Bug report #627197,
regarding mplayer2 dies with signal 4 (illegal instruction) on an
Altivec-enabled
Package: mplayer2
Followup-For: Bug #627197
On Apr 02 2012, Rogério Brito wrote:
Package: mplayer2
Version: 2.0-426-gc32b3ed-2
Followup-For: Bug #627197
Just for the record, I am also getting this signal 4 thing on an iBook G3
(which doesn't have altivec):
(...)
I just recompiled
Hi,
I notice in recent changelog of VLC that apparently it is now built with
altivec on PowerPC, as a fix for bug#660936.
Is that ok? I mean, do we no longer support non-altivec PowerPC
machines, or is it somehow ensured that only an Altivec plugin is
affected, not all code?
For 32 bit x86
Am Sonntag, den 26.02.2012, 15:50 +0100 schrieb Jonas Smedegaard:
Hi,
I notice in recent changelog of VLC that apparently it is now built with
altivec on PowerPC, as a fix for bug#660936.
No, the bug was, that -maltivec wasn't passed to one plugin. I checked
the log of 1.1.13
On 12-02-26 at 03:57pm, Benjamin Drung wrote:
Am Sonntag, den 26.02.2012, 15:50 +0100 schrieb Jonas Smedegaard:
Hi,
I notice in recent changelog of VLC that apparently it is now built
with altivec on PowerPC, as a fix for bug#660936.
No, the bug was, that -maltivec wasn't passed
instruction is the one that is making it die,
but this is somewhat surprising: I would expect this to happen with an
Altivec binary being run on a non-Altivec enabled processor (e.g., my iBook
G3), but not in this case.
Of course, I can give further details, but as I said in another e-mail, I am
busy
22 matches
Mail list logo
