On Fri 2016-07-08 @ 01:55:18 PM, Khem Raj wrote:
> Trevor
>
> On Thu, Jul 7, 2016 at 1:25 PM, Khem Raj <raj.k...@gmail.com> wrote:
> > Ok thanks. Let me know if you get to see the same issue on say qemuarm or
> > qemuarm64
>
> I built core-image-sato/qemux86-64 vmdk with chromium added
>
> CORE_IMAGE_EXTRA_INSTALL_append = " chromium "
>
> launched this image in VM and chromium starts normally.
Someday I hope that we'll have a mechanism in place that will be able to
better record the full information about a build to help make it easier for
multiple people to fully recreate the exact same builds, independently (iow,
in situations like this).
I've done my best to recreate your build, and I'm still seeing the failure.
I was able, however, to convince someone else to try building and running
chromium (from master), they tried it, and are seeing the run-time failure
too.
>
> I am using github.com/kraj/openembedded-core kraj/master branch and
> github.com/kraj/meta-raspberrypi kraj/master
> everything else is upstream master and gcc is 5.x
>
> here is my build info
>
> Build Configuration:
> BB_VERSION = "1.31.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "x86_64-oe-linux"
> MACHINE = "qemux86-64"
> DISTRO = "nodistro"
> DISTRO_VERSION = "nodistro.0"
> TUNE_FEATURES = "m64 core2"
> TARGET_FPU = ""
> meta-raspberrypi = "kraj/master:b9ba221e520f39bc3e273f709b5ceea02897d525"
> meta-qcom = "master:0eaea003cac6c3175b0a3682efd6e1f20ecc9dab"
> meta-96boards = "master:6b2744bf3e82154a9329ab89cf03eec9d1f80837"
> oe-meta-go = "master:dc19a245ae5224d1c9859119a9c53b6331812400"
> meta-browser = "master:77736988073a5d90fcff9d0005c8477332ede387"
> meta-metrological = "kraj/master:356f0c33298eb63af415f333fe06121d056261e1"
> meta-multimedia
> meta-gnome
> meta-oe = "master:f11f8664de82e4f8c23b075542f4c98c16ce1f5e"
> meta = "kraj/master:96ed9e94082589a62a6c602e5f774c11de3328c6"
At first I looked at your list and thought to myself: why all the extras? For
qemux86-64, all that's needed are:
- something to provide the meta (poky or openembedded-core)
- meta-browser
- meta-openembedded
As such my first build was:
BB_VERSION = "1.31.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "SUSELINUX-42.1"
TARGET_SYS = "x86_64-oe-linux"
MACHINE = "qemux86-64"
DISTRO = "nodistro"
DISTRO_VERSION = "nodistro.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta =
"kraj/master:f30e9793b8f247f691e5ffd023e1b83301508409"
meta-browser = "master:77736988073a5d90fcff9d0005c8477332ede387"
meta-oe
meta-gnome
meta-multimedia = "master:303d9ea960e2d88281079a4e71abe2cf8c815184"
Running chromium showed the failure, as usual.
So then I thought I'd try to recreate your build exactly -- except that's not
possible:
oe-meta-go from https://github.com/errordeveloper/oe-meta-go doesn't
contain a dc19a245ae5224d1c9859119a9c53b6331812400
meta-openembedded doesn't contain a
f11f8664de82e4f8c23b075542f4c98c16ce1f5e
openembedded-core from https://github.com/kraj/openembedded-core
doesn't contain a 96ed9e94082589a62a6c602e5f774c11de3328c6
But even at that, I ended up removing meta-metrological because:
ERROR: ParseError at
/z/chromium-qemux86-64/meta-metrological/recipes-qt/qtbrowser/qtbrowser_2.0.11.bb:14:
Could not inherit file classes/qmake5.bbclass
So I performed my build with:
BB_VERSION = "1.31.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "SUSELINUX-42.1"
TARGET_SYS = "x86_64-oe-linux"
MACHINE = "qemux86-64"
DISTRO = "nodistro"
DISTRO_VERSION = "nodistro.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta-raspberrypi__kraj = "HEAD:b9ba221e520f39bc3e273f709b5ceea02897d525"
meta-qcom = "HEAD:0eaea003cac6c3175b0a3682efd6e1f20ecc9dab"
meta-96boards = "HEAD:6b2744bf3e82154a9329ab89cf03eec9d1f80837"
oe-meta-go = "master:0712320950adf810fb324d49fba5d49ae19981b0"
meta-browser = "HEAD:77736988073a5d90fcff9d0005c8477332ede387"
meta-oe
meta-gnome
meta-multimedia = "master:303d9ea960e2d88281079a4e71abe2cf8c815184"
meta =
"kraj/master:f30e9793b8f247f691e5ffd023e1b83301508409"
This build succeeded (with gcc-5%), but running chromium caused the failure to
occur, as usual.
In the last couple weeks I've built chromium for x86-64 52 times and haven't
once seen it run successfully unless glibc was at 2.23. Plus I've had someone
else independently build and run chromium once, and it failed. I'm baffled how
it could be failing for me but succeeding for you :-(
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
