Hi
I am using the Yocto Build Appliance to build a image using a profile of
qemux86-64, and recipe of core-image-full-cmdline.
I then sftp the image to my OSX environment and run it as shown below. That
works fine, and I can log in as root.
I want to use ssh to connect to the image, but ssh do
Jan 2016, at 15:31, Nathan Sowatskey wrote:
>
> Hi
>
> I am using the Yocto Build Appliance to build a image using a profile of
> qemux86-64, and recipe of core-image-full-cmdline.
>
> I then sftp the image to my OSX environment and run it as shown below. That
> works fin
Hi
I am using the Yocto Build Appliance to build an image using a profile of
qemux86-64, and recipe of core-image-full-cmdline.
I can, using a redirect, ssh to the VM when running on OSX. I also want to use
sftp to copy files to the image.
The sftp server is configured in the ssh_config file t
Hi
I am using the Yocto Build Appliance to build an image using a profile of
qemux86-64, and recipe of core-image-full-cmdline.
The application I need to run on that image has a dependency on Qt5 libs.
It seems that only Qt4 libs are available in the packages on the build
appliance.
Can anyon
Many thanks. I just need to figure out how to get the layers onto the Build
Appliance now …
Regards
Nathan
> On 28 Jan 2016, at 19:30, Khem Raj wrote:
>
>
> On Jan 28, 2016 1:24 PM, "Nathan Sowatskey" wrote:
> >
> > Hi
> >
> > I am using the Y
Hi
I think I am seeing something similar. I only have video in my kernel/drivers
directory, which is to say that there is no net directory either.
I have been using the Build Appliance to create a qemux86-64
core-image-full-cmdline machine. When I ran that without any -netdev arguments
at all,
As a follow up, I have just done this:
bitbake core-image-kernel-dev
And now I get the eth0 interface configured and active when I start the Yocto
image.
I do not have to configure and start it manually.
Regards
Nathan
> On 1 Feb 2016, at 13:31, Nathan Sowatskey wrote:
>
>
variable in any file in build/conf,
nor in the environment variables.
Regards
Nathan
> On 2 Feb 2016, at 06:05, Khem Raj wrote:
>
> On Mon, Feb 1, 2016 at 8:48 PM, Nathan Sowatskey wrote:
>> As a follow up, I have just done this:
>>
>> bitbake core-image-kernel-dev
&g
Hi
I can see these instructions for setting up oe-core:
http://www.openembedded.org/wiki/OE-Core_Standalone_Setup
Which overlap with instructions here for Poky:
http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html
Specifically, the part about initialising the build envir
Hi
I have these missing dependencies when running a test executable on my Yocto
image. It is a qemux86_64 core-image-kernel-dev image, built as “bitbake
core-image-kernel-dev”.
0x0001 (NEEDED) Shared library: [libsnmp.so.30]
0x0001 (NEEDED) Shar
Hi
My application has a dependency on libQt5Network.so.5.
I have my build configured here:
https://github.com/DevOps4Networks/iox-yocto-build/tree/master/conf
I expect that some combination of the BBLAYERS and the IMAGE_INSTALL_append
should allow me to get that library in my Yocto image.
I a
It turns out that the build is correct, in that the libraries are there, but
the test program I am using is not finding them :-/
So, for future reference, at least part what is required to work is correct in
my build.
Regards
Nathan
> On 4 Feb 2016, at 17:39, Nathan Sowatskey wrote:
>
Hi
I am working with a test program which has a dependency on libgcc_s.
On Ubuntu that is available, for example from a 14.04 Ubuntu desktop build:
find /usr/lib -name "*gcc*”
...
/usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc_s.so
...
On the Yocto image I am building (see below for conf files), I d
b 2016, at 12:59, Burton, Ross wrote:
>
>
> On 5 February 2016 at 11:40, Nathan Sowatskey wrote:
> Is there a way to get the libgcc_s library on a Yocto image? Is that even the
> right thing to do?
>
> It's fairly likely that your binary is actually linking to libgcc
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Feb 2016, at 16:50, Burton, Ross wrote:
>
>
> On 5 February 2016 at 15:24, Nathan Sowatskey wrote:
> I suspect that my test program, which was supplied to me as a .deb package,
> was compiled on Ubuntu, and so links to libgcc_s.so.1. I can’t see any
> obvious way to get libg
CXXABI_1.3
> On 5 Feb 2016, at 19:00, Fred Ollinger wrote:
>
> What are results of:
>
> $ file testprog
>
> Frederick
> ____
> From: Nathan Sowatskey
> Sent: Friday, February 5, 2016 9:47 AM
> To: Burton, Ross
> Cc: y
t;
> Frederick
>
>
> From: Burton, Ross
> Sent: Friday, February 5, 2016 9:56 AM
> To: Nathan Sowatskey
> Cc: yocto@yoctoproject.org; Fred Ollinger
> Subject: Re: [yocto] libgcc_s not present in Yocto image
>
>
> On 5 Februa
red Ollinger wrote:
>
> The results should tell us:
>
> $ files /usr/bin/testprog
>
> What are they? (Sitting on the edge of my seat.)
> ____
> From: Nathan Sowatskey
> Sent: Friday, February 5, 2016 10:09 AM
> To: Fred O
red Ollinger wrote:
>
> What's the result of:
>
> $ cat /proc/cpuinfo
>
> (So far, it seems like my hunch was wrong.)
>
> Frederick
> ________
> From: Nathan Sowatskey
> Sent: Friday, February 5, 2016 10:12 AM
>
Hi Kem
The testprog was given to me as a .deb package by a third party to test. I did
not compile it and I don’t know what they did either.
Regards
Nathan
> On 5 Feb 2016, at 19:21, Khem Raj wrote:
>
> On Fri, Feb 5, 2016 at 10:12 AM, Nathan Sowatskey wrote:
>> file /u
Thanks Khem. Please see below:
readelf -a /usr/bin/testprog
ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (cu
Hi Khem
Thanks for trying to help :-)
I read what you have suggested below as trying to execute “ld.so” and passing
my program as an argument.
I can’t find a file called “ld.so” on either my Yocto image, or even the Ubuntu
box that I am using to build it (which I use as a comparative reference
Hi Khem
Thanks for trying to help :-)
I read what you have suggested below as trying to execute “ld.so” and passing
my program as an argument.
I can’t find a file called “ld.so” on either my Yocto image, or even the Ubuntu
box that I am using to build it (which I use as a comparative reference
ic linker shared lib not literally ld.so file
> it should be in /lib/ld*.so
>
>
> On Fri, Feb 5, 2016 at 11:36 PM, Nathan Sowatskey wrote:
>> Hi Khem
>>
>> Thanks for trying to help :-)
>>
>> I read what you have suggested below as trying to execute “ld
Ubuntu 13.04, but I can't connect
> the qemu/kvm 1.4.0 to the virt-manager/ other vm manager.
> can you give me solutions?
>
> On Fri, Feb 5, 2016 at 10:02 PM, Nathan Sowatskey wrote:
> Gilar
>
> Please tell us what you have tried so far, and what has happened. Sho
broken - Check if you are using third party repositories.
> If so disable them, since they are a common source of problems.
> Furthermore run the following command in a Terminal: apt-get install -f
> The following packages have unmet dependencies:
> virtinst: Depends: python (>= 2.7.1-
27 matches
Mail list logo
