From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm] libimxvpuapi_0.10.1 and waf: error: no such option: --disable-static
Date: Fri, 19 Feb 2016 14:10:07 +0100 [thread overview]
Message-ID: <56C7142F.4020800@pseudoterminal.org> (raw)
In-Reply-To: <CALbSrko-dNOxQtq-WKZie6TYkCnTB-37JiZFMYBGNeQPgv1_zA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5730 bytes --]
Actually, it already uses the waf bbclass:
inherit waf pkgconfig
On 2016-02-19 11:32, eien sakebe wrote:
> hello,
> Thank you for your feedback.
> Do you mean
> http://permalink.gmane.org/gmane.comp.handhelds.openembedded.core/76501 ?
> bcause it gives me annother issue | AttributeError: Values instance
> has no attribute 'enable_static'
>
>
> ERROR: libimxvpuapi-0.10.1-r0 do_configure: Function failed:
> do_configure (log file is located at
> /home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/temp/log.do_configure.15270)
> ERROR: Logfile of failure stored in:
> /home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/temp/log.do_configure.15270
> Log data follows:
> | DEBUG: Executing python function sysroot_cleansstate
> | DEBUG: Python function sysroot_cleansstate finished
> | DEBUG: Executing shell function do_configure
> | Setting top to :
> /home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git
> | Setting out to :
> /home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/build
> | Checking for 'gcc' (C compiler) :
> arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon
> -mfloat-abi=hard -mcpu=cortex-a9
> --sysroot=/home/mmuser/fsl-master-next-wayland/build/tmp/sysroots/imx6dlsabresd
> | Testing compiler flags -O2 -pipe -g -feliminate-unused-debug-types
> -fdebug-prefix-map=/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git=/usr/src/libimxvpuapi
> -fdebug-prefix-map=/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git=/usr/src/libimxvpuapi
> -fdebug-prefix-map=/home/mmuser/fsl-master-next-wayland/build/tmp/sysroots/x86_64-linux=
> -fdebug-prefix-map=/home/mmuser/fsl-master-next-wayland/build/tmp/sysroots/imx6dlsabresd=
> | Checking if building with these flags works : yes
> | Checking for compiler switch -O2 : yes
> | Checking for compiler switch -DPIC : yes
> | Checking for compiler switch -fPIC : yes
> | Checking for compiler switch -pedantic : yes
> | Checking for compiler switch -std=c99 : yes
> | Checking for compiler switch -Wall : yes
> | Checking for compiler switch -Wextra : yes
> | Traceback (most recent call last):
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/.waf-1.8.16-62b1bd1a26843637845309e604a98bca/waflib/Scripting.py",
> line 110, in waf_entry_point
> | run_commands()
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/.waf-1.8.16-62b1bd1a26843637845309e604a98bca/waflib/Scripting.py",
> line 171, in run_commands
> | ctx=run_command(cmd_name)
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/.waf-1.8.16-62b1bd1a26843637845309e604a98bca/waflib/Scripting.py",
> line 162, in run_command
> | ctx.execute()
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/.waf-1.8.16-62b1bd1a26843637845309e604a98bca/waflib/Configure.py",
> line 87, in execute
> | super(ConfigurationContext,self).execute()
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/.waf-1.8.16-62b1bd1a26843637845309e604a98bca/waflib/Context.py",
> line 93, in execute
> | self.recurse([os.path.dirname(g_module.root_path)])
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/.waf-1.8.16-62b1bd1a26843637845309e604a98bca/waflib/Context.py",
> line 134, in recurse
> | user_function(self)
> | File
> "/home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/git/wscript",
> line 80, in configure
> | conf.env['BUILD_STATIC'] = conf.options.enable_static
> | AttributeError: Values instance has no attribute 'enable_static'
> | WARNING: exit code 2 from a shell command.
> | ERROR: Function failed: do_configure (log file is located at
> /home/mmuser/fsl-master-next-wayland/build/tmp/work/imx6dlsabresd-poky-linux-gnueabi/libimxvpuapi/0.10.1-r0/temp/log.do_configure.15270)
> ERROR: Task 5
> (/home/mmuser/fsl-master-next-wayland/sources/meta-fsl-arm/recipes-multimedia/libimxvpuapi/libimxvpuapi_0.10.1.bb
> <http://libimxvpuapi_0.10.1.bb>, do_configure) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 432 tasks of which 430 didn't need to
> be rerun and 1 failed.
> NOTE: Writing buildhistory
> Waiting for 0 running tasks to finish:
>
>
> 2016-02-19 11:24 GMT+01:00 Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>>:
>
>
> On 19 February 2016 at 10:11, eien sakebe
> <eien.ni.sakebe@gmail.com <mailto:eien.ni.sakebe@gmail.com>> wrote:
>
> Building libimxvpu ersults on an waf: error: no such option:
> --disable-static
> anyone know how to fix it ?
>
>
> There's a patch on the oe-core list for the waf class that will
> solve this, assuming libimxvpu is using that. If it isn't then
> set DISABLE_STATIC="" in the recipe (or port it to use the waf class).
>
> Ross
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 8586 bytes --]
next prev parent reply other threads:[~2016-02-19 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 10:11 [meta-fsl-arm] libimxvpuapi_0.10.1 and waf: error: no such option: --disable-static eien sakebe
2016-02-19 10:24 ` Burton, Ross
2016-02-19 10:32 ` eien sakebe
2016-02-19 13:10 ` Carlos Rafael Giani [this message]
2016-02-19 13:25 ` eien sakebe
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=56C7142F.4020800@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.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.