* Bitbake fails to create SDK meanwhile can create image
@ 2020-01-02 11:00 Ashish
2020-01-06 10:11 ` Ashish
2020-01-07 10:21 ` [poky] " Richard Purdie
0 siblings, 2 replies; 6+ messages in thread
From: Ashish @ 2020-01-02 11:00 UTC (permalink / raw)
To: poky
[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]
Hi All ,
bitbake -c populate_sdk <IMAGE> fails with below error :
| checking target system type... Invalid configuration `x86_64-build-config-policy-basicsdk-linux': more than four components
| configure: error: /bin/sh ../config.sub x86_64-build-config-policy-basicsdk-linux failed
But for same setup i am able to generate an working image using bitbake -k <IMAGE>
Here IMAGE = *images/armour-whiplash-image.bb* & DISTRO = conf/distro/build-config-policy-basic.conf
( both derived from qemux86-64 )
1) Can member please provide any pointer / debug step as why the *binutils-crosssdk* fails to compile
when SDK is created but compiles fine when image is created.
2) I even tried with cleanall option with binutils , but same behaviour .
Attached along is the log
Thanks
Ashish
[-- Attachment #1.2: Type: text/html, Size: 1073 bytes --]
[-- Attachment #2: log.do_configure.12246 --]
[-- Type: application/octet-stream, Size: 5817 bytes --]
DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common']
DEBUG: Executing shell function autotools_preconfigure
DEBUG: Shell function autotools_preconfigure finished
DEBUG: Executing python function autotools_aclocals
DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common']
DEBUG: Python function autotools_aclocals finished
DEBUG: Executing shell function do_configure
NOTE: Running ../configure --build=x86_64-linux --host=x86_64-linux --target=x86_64-build-config-policy-basicsdk-linux --prefix=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr --exec_prefix=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr --bindir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/bin/x86_64-build-config-policy-basicsdk-linux --sbindir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/bin/x86_64-build-config-policy-basicsdk-linux --libexecdir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/libexec/x86_64-build-config-policy-basicsdk-linux --datadir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/share --sysconfdir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/etc --sharedstatedir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/com --localstatedir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/var --libdir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/lib/x86_64-build-config-policy-basicsdk-linux --includedir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/include --oldincludedir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/include --infodir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/share/info --mandir=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot-native --program-prefix=x86_64-build-config-policy-basicsdk-linux- --disable-werror --enable-deterministic-archives --enable-plugins --enable-64-bit-bfd --with-sysroot=/home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/recipe-sysroot --disable-install-libbfd --enable-poison-system-directories --with-lib-path==/opt/build-config-policy-basic/1.0/sysroots/x86_64-build-config-policy-basicsdk-linux/lib:=/opt/build-config-policy-basic/1.0/sysroots/x86_64-build-config-policy-basicsdk-linux/usr/lib --disable-static --disable-nls
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... Invalid configuration `x86_64-build-config-policy-basicsdk-linux': more than four components
configure: error: /bin/sh ../config.sub x86_64-build-config-policy-basicsdk-linux failed
NOTE: The following config.log files may provide further information.
NOTE: /home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/git/build.x86_64-linux.x86_64-build-config-policy-basicsdk-linux/config.log
ERROR: configure failed
WARNING: /home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/temp/run.do_configure.12246:1 exit 1 from 'exit 1'
ERROR: Function failed: do_configure (log file is located at /home/ashish/Documents/linux-foundation-projects/yocto/build-armour/tmp/work/x86_64-linux/binutils-crosssdk-x86_64-build-config-policy-basicsdk-linux/2.32.0-r0/temp/log.do_configure.12246)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bitbake fails to create SDK meanwhile can create image
2020-01-02 11:00 Bitbake fails to create SDK meanwhile can create image Ashish
@ 2020-01-06 10:11 ` Ashish
2020-01-06 16:54 ` [poky] " Khem Raj
2020-01-07 10:21 ` [poky] " Richard Purdie
1 sibling, 1 reply; 6+ messages in thread
From: Ashish @ 2020-01-06 10:11 UTC (permalink / raw)
To: poky
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
Hi All ,
( Updating the thread just in case if any one else face similar issue )
1) Changing the distro file from "build-config-policy-basic" to "buildpolicy" this was based on below pointer from error log
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... *Invalid configuration `x86_64-build-config-policy-basicsdk-linux': more than four components*
2) Clean and build binutils package . Build the image .
3) Generate the SDK again , there is no error mentioned above .
Ashish .
[-- Attachment #2: Type: text/html, Size: 853 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [poky] Bitbake fails to create SDK meanwhile can create image
2020-01-06 10:11 ` Ashish
@ 2020-01-06 16:54 ` Khem Raj
2020-01-07 6:30 ` Ashish
0 siblings, 1 reply; 6+ messages in thread
From: Khem Raj @ 2020-01-06 16:54 UTC (permalink / raw)
To: Ashish; +Cc: poky
are you building out of master ? if so did this config work in past ?
I wonder if this started after this commit
https://git.openembedded.org/openembedded-core/commit/?id=66e4c638b942c9832da9e1d578aa03eeafae28db
can you test if this is the case.
On Mon, Jan 6, 2020 at 2:11 AM Ashish <ashish.emailaddress@gmail.com> wrote:
>
> Hi All ,
>
> ( Updating the thread just in case if any one else face similar issue )
>
> 1) Changing the distro file from "build-config-policy-basic" to "buildpolicy" this was based on below pointer from error log
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking target system type... Invalid configuration `x86_64-build-config-policy-basicsdk-linux': more than four components
>
> 2) Clean and build binutils package . Build the image .
>
> 3) Generate the SDK again , there is no error mentioned above .
>
> Ashish . -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#11885): https://lists.yoctoproject.org/g/poky/message/11885
> Mute This Topic: https://lists.yoctoproject.org/mt/69378078/1997914
> Group Owner: poky+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bitbake fails to create SDK meanwhile can create image
2020-01-06 16:54 ` [poky] " Khem Raj
@ 2020-01-07 6:30 ` Ashish
0 siblings, 0 replies; 6+ messages in thread
From: Ashish @ 2020-01-07 6:30 UTC (permalink / raw)
To: poky
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Hi Khem ,
- are you building out of master ? *( Yes)*
- if so did this config work in past ? *( This was the first iteration to get the SDK from custom named image file )*
- I wonder if this started after this commit *( NO )
* The said patch commit is not available on my yocto code base
PROMPT:
PROMPT: grep -A2 meta/conf/bitbake.conf -e 'TARGET_VENDOR '
131:TARGET_VENDOR = "-oe"
132-TARGET_SYS = "${TARGET_ARCH}${TARGET_VENDOR}${@['-' + d.getVar('TARGET_OS'), ''][d.getVar('TARGET_OS') == ('' or 'custom')]}"
133-TARGET_PREFIX = "${TARGET_SYS}-"
PROMPT:
PROMPT:
PROMPT: grep -A2 meta/conf/bitbake.conf -e 'SDK_VENDOR ='
140:SDK_VENDOR = "-oesdk"
141-SDK_SYS = "${SDK_ARCH}${SDK_VENDOR}${@['-' + d.getVar('SDK_OS'), ''][d.getVar('SDK_OS') == ('' or 'custom')]}"
142-SDK_PREFIX = "${SDK_SYS}-"
PROMPT:
PROMPT:
[-- Attachment #2: Type: text/html, Size: 1248 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [poky] Bitbake fails to create SDK meanwhile can create image
2020-01-02 11:00 Bitbake fails to create SDK meanwhile can create image Ashish
2020-01-06 10:11 ` Ashish
@ 2020-01-07 10:21 ` Richard Purdie
2020-01-07 10:57 ` Ashish
1 sibling, 1 reply; 6+ messages in thread
From: Richard Purdie @ 2020-01-07 10:21 UTC (permalink / raw)
To: Ashish, poky
On Thu, 2020-01-02 at 03:00 -0800, Ashish wrote:
> Hi All ,
>
> bitbake -c populate_sdk <IMAGE> fails with below error :
> | checking target system type... Invalid configuration `x86_64-build-
> config-policy-basicsdk-linux': more than four components
> | configure: error: /bin/sh ../config.sub x86_64-build-config-policy-
> basicsdk-linux failed
>
> But for same setup i am able to generate an working image using
> bitbake -k <IMAGE>
> Here IMAGE = images/armour-whiplash-image.bb & DISTRO
> = conf/distro/build-config-policy-basic.conf
> ( both derived from qemux86-64 )
>
> 1) Can member please provide any pointer / debug step as why the
> binutils-crosssdk fails to compile
> when SDK is created but compiles fine when image is created.
> 2) I even tried with cleanall option with binutils , but same
> behaviour .
I think the issue is you're using a DISTRO name with dashes in (build-
config-policy-basic) which is confusing autotools.
Try using something without dashes.
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bitbake fails to create SDK meanwhile can create image
2020-01-07 10:21 ` [poky] " Richard Purdie
@ 2020-01-07 10:57 ` Ashish
0 siblings, 0 replies; 6+ messages in thread
From: Ashish @ 2020-01-07 10:57 UTC (permalink / raw)
To: poky
[-- Attachment #1: Type: text/plain, Size: 89 bytes --]
It worked when changed to single word name "buildpolicy.conf"
Thanks Khem & Richard.
[-- Attachment #2: Type: text/html, Size: 107 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-01-07 10:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-02 11:00 Bitbake fails to create SDK meanwhile can create image Ashish
2020-01-06 10:11 ` Ashish
2020-01-06 16:54 ` [poky] " Khem Raj
2020-01-07 6:30 ` Ashish
2020-01-07 10:21 ` [poky] " Richard Purdie
2020-01-07 10:57 ` Ashish
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.