Bug 5484

Summary: boost package fail (compiled as host ARCH)
Product: [Build System, Metadata & Runtime] OE-Core Reporter: niqingliang2003 <niqingliang2003>
Component: devtools / tool chainAssignee: niqingliang2003 <niqingliang2003>
Status: RESOLVED WORKSFORME QA Contact:
Severity: janitors    
Priority: Medium CC: jack, meta.mr.watcher, meta.watcher, niqingliang2003, richard.purdie, sgw
Version: 1.5   
Target Milestone: 1.6   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
boot-build conf file none

Description niqingliang2003 2013-11-06 01:02:08 UTC
I'm working on Archlinux x64. when packaging boost, I got error:

arm-jilong-linux-gnueabi-objcopy:/xxx/tmp/work/armv6-vfp-jilong-linux-
gnueabi/boost/1.54.0-r0/package/usr/lib/libboost_iostreams.so.1.54.0: File 
format not recognized

        I don't know why boost compiled with host ARCH.
        but I have one machine can done it correctly.
        So I compared the two machine, the 'bjam --help' command result is 
different after source yocto environment.

        on the failure machine, it will use '/usr/share/boost-build/user-
config.jam'. the success machine don't have this file.

        so the different result in this error is: the failure machine installed 
package 'boost-build'.

        after remove 'boost-build' from Archlinux and bitbake -c clean boost,
I have done package correctly.
Comment 1 Laurentiu Palcu 2013-11-08 11:41:27 UTC
I need a little more info about your issue:
 * attach your /usr/share/boost-build/user-config.jam
 * the location where you run bjam --help
Comment 2 niqingliang2003 2013-11-13 10:36:14 UTC
Created attachment 1618 [details]
boot-build conf file
Comment 3 niqingliang2003 2013-11-13 10:41:35 UTC
I run bjam in <machine-build-dir> after source yocto env file "<machine-build-dir>/tmp/environment-setup-armv6-vfp-jilong-linux-gnueabi"
Comment 4 Laurentiu Palcu 2013-11-19 11:08:46 UTC
(In reply to comment #3)
> I run bjam in <machine-build-dir> after source yocto env file
> "<machine-build-dir>/tmp/environment-setup-armv6-vfp-jilong-linux-gnueabi"

I still don't understand what you're trying to do here... Are you trying to create an image that contains boost and it fails? I just built boost with bitbake for qemuarm and I copied the config file you provided to /usr/share/boost-build. The build finished just fine.

Another thing I don't understand is, why are you sourcing the environment script? This environment script is for those who want to use the SDK and don't want to download the toolchain tarball separately.

Can you please try to explain a little bit what are you trying to achieve here?
Comment 5 niqingliang2003 2013-11-20 14:04:01 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > I run bjam in <machine-build-dir> after source yocto env file
> > "<machine-build-dir>/tmp/environment-setup-armv6-vfp-jilong-linux-gnueabi"
> 
> I still don't understand what you're trying to do here... Are you trying to
> create an image that contains boost and it fails? I just built boost with
> bitbake for qemuarm and I copied the config file you provided to
> /usr/share/boost-build. The build finished just fine.

Yes, I encountered this problem when creating an image.

> Another thing I don't understand is, why are you sourcing the environment
> script? This environment script is for those who want to use the SDK and
> don't want to download the toolchain tarball separately.

I haven't source env when creating image.
I sourced env just when debugging this problem.

> Can you please try to explain a little bit what are you trying to achieve
> here?
Comment 6 Laurentiu Palcu 2013-12-02 11:21:56 UTC
Unfortunately I wasn't able to reproduce this on my machine running Ubuntu 12.04. On the other hand Archlinux is not a distro we support due to its rolling release nature.

Assigning back to reporter. If you can reproduce this on Ubuntu/Debian/Fedora, then assign it back to me and provide all the steps needed to reproduce it.
Comment 7 Jack Mitchell 2014-01-19 11:38:32 UTC
I can't reproduce this on ArchLinux x86_64, boost builds just fine here.
Comment 8 Richard Purdie 2014-02-14 16:57:21 UTC
Since nobody can reproduce this and we don't support ArchLinux anyway, I'm closing this...