Hi,
2015-06-11 12:49 GMT+02:00 Mayank Agarwal :
> Hi,
>
> I have configured the yocto project and i am getting vmdk.ext3 image
> I want to configure that iso image should also be generated.
> I have changed IMAGE_FSTYPE in qemux86.conf to iso.
>
> But on building i am getting do_configure failure
Hi Khem,
Thankyou for your quick response. I will try installing the package to
image itself and let you know.
Regards,
Sai
On Wed, Jun 10, 2015 at 9:16 PM, Khem Raj wrote:
> On Wed, Jun 10, 2015 at 1:01 AM, Sai Prasad B
> wrote:
> > Hi ,
> >
> >I hope this is correct place for my doub
On 11/06/15 16:05, Paul Eggleton wrote:
On Thursday 11 June 2015 15:56:57 Aníbal Limón wrote:
Hi Paul,
Comments below,
Kind regards,
alimon
On 11/06/15 15:51, Paul Eggleton wrote:
On Wednesday 10 June 2015 16:28:50 Aníbal Limón wrote:
Now send emails almost in all cases this give th
On Thursday 11 June 2015 15:56:57 Aníbal Limón wrote:
> Hi Paul,
>
> Comments below,
>
> Kind regards,
> alimon
>
> On 11/06/15 15:51, Paul Eggleton wrote:
> > On Wednesday 10 June 2015 16:28:50 Aníbal Limón wrote:
> >> Now send emails almost in all cases this give the maintainer
> >> patch
Hi Paul,
Comments below,
Kind regards,
alimon
On 11/06/15 15:51, Paul Eggleton wrote:
On Wednesday 10 June 2015 16:28:50 Aníbal Limón wrote:
Now send emails almost in all cases this give the maintainer
patches and diff to continue work also if the build isn't
succesful.
[YOCTO #7489]
Si
On Wednesday 10 June 2015 16:28:50 Aníbal Limón wrote:
> Now send emails almost in all cases this give the maintainer
> patches and diff to continue work also if the build isn't
> succesful.
>
> [YOCTO #7489]
>
> Signed-off-by: Aníbal Limón
> ---
> upgradehelper.py | 19 ++-
> 1
Hi,
I have configured the yocto project and i am getting vmdk.ext3 image
I want to configure that iso image should also be generated.
I have changed IMAGE_FSTYPE in qemux86.conf to iso.
But on building i am getting do_configure failure in grub_0.xx recipe.
and the error is: cannot link at address
Hi,
On 06/10/2015 10:25 PM, Luke (Lucas) Starrett wrote:
> Hi,
>
>
>
> I’m trying to understand the feasibility of shared-state across multiple
> users in a development environment. Does anyone have first-hand
> experience with this? Am I asking for trouble?
Have a look here [1] 3.2.1.2. Co
On Wed, Jun 10, 2015 at 2:03 AM, Edward Wingate wrote:
> Thanks, Nathan, for your help. It worked, with a little oddity I don't
> understand.
>
> In my uEnv.txt, I set both fdt_high and initrd_high to 0x1000 and
> fdt/initrd are now loaded to 1st 256 MB:
>Loading Kernel Image ... OK
>L
On 11 June 2015 at 11:31, Robert P. J. Day wrote:
> i vaguely recall from way back that the tar packaging was not really
> supported, or was mostly unused, or something to that effect. what's
> the status on that these days?
>
As it's barely functional (no metadata, obviously) it doesn't get u
Hi All,
One more thing the convert task has different flow for both the recipes and the
names of the package is different as below is snapshot of the actual code.
Also PACKAGE_CLASSES has both rpm and tar. We have explicitly turned off one of
the task in the recipe based on the requirement.
Tha
On Thu, 11 Jun 2015, Burton, Ross wrote:
>
> On 11 June 2015 at 10:54, Bipnesh, Abhinav (Abhinav)
> wrote:
>
> So I want to merge these both recipes to produce the same artificats as
> above but using a single
> recipe. So any thoughts how to do it.
>
>
> Just add "tar" to PACKAGE_C
On 11 June 2015 at 10:54, Bipnesh, Abhinav (Abhinav) <
abhinavbipn...@avaya.com> wrote:
> So I want to merge these both recipes to produce the same artificats as
> above but using a single recipe. So any thoughts how to do it.
>
>
Just add "tar" to PACKAGE_CLASSES and you'll get a tarball of every
Hello all,
Why 'yocto-bsp create ... i386' (Yocto dizzy 1.7.2) is defining a kernel
config with the MATOM=y even if I select the default kernel with the '586'
tune (neither the 'Atom' nor the 'core2')? is this expected? Im using and
old Celeron M (petium M based)
I'm also using the meta-intel la
Hi,
Currently I have two different recipes for similar type of package with a minor
differences. Below is the list
1. One being packaged as tar.gz and don't have pre or post install
activity
2. Other one being packaged as RPM and have a post install section in it.
Below is the extr
Hi Vincent,
> On 10 Jun 2015, at 03:50, Cheah, Vincent Beng Keat
> wrote:
>
> Hi Chris,
>
> I don’t have any idea with regard to the issue that you are getting below.
> All the work that we are doing here so far is on CHV (yocto-kernel-3.19.5
> standard/base branch).
>
> From your statement
16 matches
Mail list logo