All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gstreamer: gst-ffmpeg: fix build issues for libav
Date: Tue, 07 Aug 2012 13:00:10 -0400	[thread overview]
Message-ID: <5021499A.60008@gmail.com> (raw)
In-Reply-To: <50213316.8080503@windriver.com>

On 07/08/2012 11:24 AM, Yao Zhao wrote:
>>> 1.The included libav configure is not generated by autotools
>>>    patch use-correct-toolchain.patch patched its configure to
>>> use correct toolchain wrapper.
>> Why are you patching the toolchain instead of passing the correct parameters
>> to configure (--enable-cross-compile, --cross-prefix-..., etc)?
> in the configure,
> ar_default="${cross_prefix}${ar_default}"
> cc_default="${cross_prefix}${cc_default}"
> nm_default="${cross_prefix}${nm_default}"
> pkg_config_default="${cross_prefix}${pkg_config_default}"
> ranlib="${cross_prefix}${ranlib}"
> 
> cc_default is the gcc so cc_default will be for example: 
> powerpc-xxx-gcc, it won't use the toolcain wrapper.
> 
> I will try whether command line will solve these too.

Perhaps you are looking for --cc=<something>?

Same thing can be done with --ld, and pals if you desire.

Remember to set --arch, maybe --cpu and --target-os too, as well as --enable-cross-compile.

>>> 3.detect whether toolchain supports altivec, if not then add
>>> disable-altivec to libav's configure line or configure will fail
>> Wrong fix.
>>
>> http://git.libav.org/?p=libav.git;a=blob;f=configure;h=b139008d2b1aa5faea3f33c2a1922d0e1cb1fa5c;hb=HEAD#l2318
>>
>> It should be fixed by passing the proper CPU to libav's configure as an argument.
> 
>          e500v2)
>              cpuflags="-mcpu=8548 -mhard-float -mfloat-gprs=double"
>              disable altivec
>          ;;
>          e500)
>              cpuflags="-mcpu=8540 -mhard-float"
>              disable altivec
>          ;;
> 
> I am fixing for e500mc which is not a case here and I am not sure what 
> exactly the cpuflags should be.
> Any idea?

http://lists.libav.org/pipermail/libav-devel/2012-August/032990.html

Working on it.

- Derek



  reply	other threads:[~2012-08-07 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 21:15 [PATCH] gstreamer: gst-ffmpeg: fix build issues for libav Yao Zhao
2012-08-04 18:57 ` Derek Buitenhuis
2012-08-05 11:52   ` Koen Kooi
2012-08-05 16:27     ` Derek Buitenhuis
2012-08-05 17:31       ` Koen Kooi
2012-08-05 19:11         ` Khem Raj
2012-08-05 22:16           ` Derek Buitenhuis
2012-08-07 15:24   ` Yao Zhao
2012-08-07 17:00     ` Derek Buitenhuis [this message]
2012-08-07 20:06       ` Derek Buitenhuis

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=5021499A.60008@gmail.com \
    --to=derek.buitenhuis@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.