bitbake gets confused with ~/user-config.jam

bitbake gets confused with ~/user-config.jam

[Johannes König]

Hi,

It seems that bitbake (or more precisely the boost_1.44.0.bb recipe) gets
confused with an user-config.jam file in the users home directory.

When trying to build core-image-sato (or zypper) the build aborts due to
an error in the zypper package. I use poky-edison-6.0.1.tar.gz.

Relevant part of the do_compile.log:

> build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> skipping incompatible  
> build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.so when  
> searching for -lboost_signals-mt
> build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> skipping incompatible  
> build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.a when searching  
> for -lboost_signals-mt
> build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> skipping incompatible  
> build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.so when  
> searching for -lboost_signals-mt
> build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> skipping incompatible  
> build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.a when searching  
> for -lboost_signals-mt
> build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> cannot find -lboost_signals-mt
> collect2: ld returned 1 exit status
> make[2]: *** [zypp/libzypp.so.810.1.0] Error 1
> make[2]: Leaving directory  
> `build/tmp/work/crownbay-poky-linux/libzypp-0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433-r16/git'
> make[1]: *** [zypp/CMakeFiles/zypp.dir/all] Error 2
> make[1]: Leaving directory  
> `build/tmp/work/crownbay-poky-linux/libzypp-0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433-r16/git'
> make: *** [all] Error 2
> ERROR: oe_runmake failed
> ERROR: Function 'do_compile' failed (see  
> build/tmp/work/crownbay-poky-linux/libzypp-0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433-r16/temp/log.do_compile.31334  
> for further information)

After removing the ~/user-config.jam file and recompiling zypper with

     bitbake -c cleanall libzypp boost zypper && bitbake zypper

no more errors are reported.

Content of the ~/user-config.jam file is:

> using gcc ;

(Usually I have more options in my user-config.jam, but I can strip it
down to the single line above to reproduce the error.)


Can this problem be fixed without removeing the user-config.jam?

-- 
Johannes König

Re: bitbake gets confused with ~/user-config.jam

[Richard Purdie]

On Fri, 2012-04-13 at 11:53 +0200, Johannes König wrote:
> Hi,
> 
> It seems that bitbake (or more precisely the boost_1.44.0.bb recipe) gets
> confused with an user-config.jam file in the users home directory.
> 
> When trying to build core-image-sato (or zypper) the build aborts due to
> an error in the zypper package. I use poky-edison-6.0.1.tar.gz.
> 
> Relevant part of the do_compile.log:
> 
> > build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> > skipping incompatible  
> > build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.so when  
> > searching for -lboost_signals-mt
> > build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> > skipping incompatible  
> > build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.a when searching  
> > for -lboost_signals-mt
> > build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> > skipping incompatible  
> > build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.so when  
> > searching for -lboost_signals-mt
> > build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> > skipping incompatible  
> > build/tmp/sysroots/crownbay/usr/lib/libboost_signals-mt.a when searching  
> > for -lboost_signals-mt
> > build/tmp/sysroots/x86_64-linux/usr/libexec/core2-poky-linux/gcc/i586-poky-linux/4.6.3/ld:  
> > cannot find -lboost_signals-mt
> > collect2: ld returned 1 exit status
> > make[2]: *** [zypp/libzypp.so.810.1.0] Error 1
> > make[2]: Leaving directory  
> > `build/tmp/work/crownbay-poky-linux/libzypp-0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433-r16/git'
> > make[1]: *** [zypp/CMakeFiles/zypp.dir/all] Error 2
> > make[1]: Leaving directory  
> > `build/tmp/work/crownbay-poky-linux/libzypp-0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433-r16/git'
> > make: *** [all] Error 2
> > ERROR: oe_runmake failed
> > ERROR: Function 'do_compile' failed (see  
> > build/tmp/work/crownbay-poky-linux/libzypp-0.0-git1+15b6c52260bbc52b3d8e585e271b67e10cc7c433-r16/temp/log.do_compile.31334  
> > for further information)
> 
> After removing the ~/user-config.jam file and recompiling zypper with
> 
>      bitbake -c cleanall libzypp boost zypper && bitbake zypper
> 
> no more errors are reported.
> 
> Content of the ~/user-config.jam file is:
> 
> > using gcc ;
> 
> (Usually I have more options in my user-config.jam, but I can strip it
> down to the single line above to reproduce the error.)
>
> Can this problem be fixed without removeing the user-config.jam?

This sounds like a host contamination issue, we shoudn't be looking at
files like that during the build. We probably need to stop the system
looking at those files but I'm not familiar with boost to know enough
about how to stop it doing that.

I'd recommend filing a bug in the bugzilla to ensure this doesn't get
forgotten about...

Cheers,

Richard