All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mjpegtools: fix build on powerpc without altivec
Date: Thu, 23 Aug 2018 13:43:53 +0200	[thread overview]
Message-ID: <20180823134353.5c76e7b6@windsurf> (raw)
In-Reply-To: <20180822203008.3249-1-fontaine.fabrice@gmail.com>

Hello,

On Wed, 22 Aug 2018 22:30:08 +0200, Fabrice Fontaine wrote:
> mpjegtools fails to build on powerpc without altivec:
> 
> build_sub44_mests.c: In function 'build_sub44_mests_altivec':
> build_sub44_mests.c:268:9: internal compiler error: Segmentation fault
>      vr1 = vec_ld(rowstride, (unsigned char*)s44blk);
> 
> It seems mpjegtools is wrongly detecting altivec support:
> configure:   - PowerPC Optimizations:
> configure:     - AltiVec enabled             : true
> 
> Fix this by adding BR2_PACKAGE_MJPEGTOOLS_SIMD_SUPPORT and setting
> --enable-simd-accel / --disable-simd-accel
> 
> Fixes:
>  - http://autobuild.buildroot.net/results/c9464712f43efb8954fd2e5460126ad193660353
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

I've applied to master, but it would have be nicer to figure out why
the Altivec detection doesn't work properly. But OK, that's good enough
for Buildroot with --enable/disable-simd-accel.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-08-23 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 20:30 [Buildroot] [PATCH 1/1] mjpegtools: fix build on powerpc without altivec Fabrice Fontaine
2018-08-22 20:54 ` Yann E. MORIN
2018-08-23 11:43 ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180823134353.5c76e7b6@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.