On 28/03/12 10:21, Ni Qingliang wrote:
no echo again?
what's the problem?
am I wrong? where?
On Tue, 2012-03-27 at 18:09 +0800, 倪庆亮 wrote:
thanks your reply, indeed, this is not the first email thread about the
gconf compile problem. it in there only because of no echo.
I have installed python2, and made a symlink in the build directory, and
exported to the env var PATH.
this is the script I used to build (located in the build directory):
#!/bin/bash
loc_dir="`pwd`"
. ${loc_dir}/../optimus/oe-init-build-env ${loc_dir}
export PATH="${loc_dir}:$PATH"
bitbake $@
OS: x86-64 arch / desktop env: gnome 3.2
local.conf ( modified section ):
MACHINE ??= "qemux86-64"
DISTRO ?= "poky-lsb"
SOURCE_MIRROR_URL = "http://10.10.20.149/optimussources/";
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "0"
INHERIT += "rm_work"
CCACHE = ""
when build gconf, got error:
/usr/lib/../lib/libXrandr.so.2: undefined reference to
`memcpy@GLIBC_2.14'
when 'do_compile' at sanity-check step.
the log of do_compile is attached, here is the last cmd (only reserve
rpath):
../x86_64-poky-linux-libtool ... -Wl,-rpath -Wl,/usr/lib/../lib
the libXrandr.so.2 (depended by the libgtk/libgdk) not appear in the
command explicitly.
I have add --verbose in the command, and found the ld find it in the
host's rootfs, but it should search it in the sysroot arg.
If remove the rpath arg or with the rpath arg prefixed by sysroot arg, I
can build success. (wich will search the libXrandr in the sysroot arg
correctly)
so I think the error is focused on the `ld' which should search in the
sysroot arg at first for implicit dependended libs, but not host's
rootfs.
On Tue, 2012-03-27 at 16:49 +0800, Jack Mitchell wrote:
On 27/03/12 03:33, Ni Qingliang wrote:
who are using archlinux? I want to talk about gconf compile fail
problem.
I use Archlinux for OE/Yocto, could you post your error so we can get an
idea of the problem you are having?
One note for Archlinux is that it ships Python 3 as default, to you must
install Python2 from the repositories then symlink python2 to python in
/usb/bin.
Regards,
I'm not 100% sure what the issue is. How come you are using a custom
build script and not the one bundled with OE? I'm not an expert by any
stretch of the imagination but by not using the given initialisation
scripts leaves me completely out of ideas as you're running a custom
setup which I couldn't possibly know the extent of.
All I can really comment on is that Yocto builds fine and consistently
with Archlinux using the latest packages (I update nearly everyday) so
the only issue I can see is that your build setup script doesn't cut the
mustard. Have you tried a completely clean build with only the bare git
clone and no modifications?
Regards,
--
Jack Mitchell (j...@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
