OK, I'll come up with a simple test case + procedure to reproduce it.
Cheers,
Nick
On Wed, Nov 12, 2014 at 1:49 AM, nick wrote:
> I would state so as if you need it and it doesn't work then it probably is
> a bug
> with bitbake.
> Cheers Nick
>
> On 14-11-11
if that was going to
> prevent the build from you companies requirements. I would recommend only
> making the build 64 bit as it seems that there is no reason for backwards
> compatibility with older 32 bit libraries for your build.
> Regards Nick
>
> On 14-11-11 06:23 AM, Nick
Any ideas where to look in regard to my custom machine config?
> >
> >
> >
> > On Mon, Nov 10, 2014 at 10:11 PM, nick wrote:
> >>
> >> Nick,
> >> Yes this is a issue with your custom machine and I believe this is a
> issue
> >>
this is a issue
> with your your machine
> conf is located in the build directories.
> Cheers Nick
>
> On 14-11-10 02:26 AM, Nick D'Ademo wrote:
> > menuconfig works with a core-image-minimal vanilla build:
> >
> >
> >
> >
> >
> &g
you able
> to build a poky distro with a working kernel and this is just a issue with
> you building the yocto
> kernel alone or can you also not build poky too?
> Cheers Nick
>
> On 14-11-09 10:36 PM, Nick D'Ademo wrote:
> > Just tried with the latest 3.17.2 kernel
gt; the root of the kernel source tree, if this works then I am assuming
> either ncurses or your machine conf is wrong
> somewhere.
> Cheers Nick
>
> On 14-11-09 09:51 PM, Nick D'Ademo wrote:
> > Hi Nick,
> >
> > I removed build/tmp/ and performed a rebuild - I'
> build and then rebuild as it may be an issue with out of date temp files.
> Cheers Nick
>
> On 14-11-09 08:51 PM, Nick D'Ademo wrote:
> > Thanks for trying that out Nick.
> >
> > Issue is present on both 3.14 and 3.17 for me.
> > All paths in the re
Nick
> On 14-11-09 08:40 PM, Nick D'Ademo wrote:
> > Thanks Nick.
> >
> > Machine conf is as follows (it's actually nearly identical to nuc.conf -
> > however, BT support, multilib, and preferred providers have been added):
> >
> > #@TYPE: Machine
>
Thanks Bob - glad to hear I'm not the first to see this!
Not using the ADT and 'source oe-init-build-env' is run before building.
On Mon, Nov 10, 2014 at 12:31 PM, Bob Cochran wrote:
> On 11/09/2014 08:15 PM, Nick D'Ademo wrote:
>
>> Thanks for the quick reply N
Nov 10, 2014 at 12:36 PM, nick wrote:
> Hey Nick,
> This seems to then be an issue with incorrect paths or build information
> in your nuc.conf
> as the most likely culprit. If you can post your machine's conf file I
> will be glad to see
> if there are any issues I can
first. If
> this is still an
> issue please reply with a newer error message.
> Cheers Nick
>
> On 14-11-09 08:05 PM, Nick D'Ademo wrote:
> > Getting a strange error when attempting to configure the Yocto Linux
> kernel
> > via: bitbake linux-yocto -c menuconfig.
&
Getting a strange error when attempting to configure the Yocto Linux kernel
via: bitbake linux-yocto -c menuconfig.
Does anyone have any ideas? (error message below)
Much appreciated.
Build Configuration:
BB_VERSION= "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-
-- Forwarded message --
From: Nick D'Ademo
Date: Wed, May 7, 2014 at 8:26 AM
Subject: Re: [meta-security][PATCH] nmap: inherit autotools-brokensep to
allow B=S build.
To: Yocto list discussion
This is a resubmission - added required blank line between subject and SOB.
O
This is a resubmission - added required blank line between subject and SOB.
On Wed, May 7, 2014 at 8:24 AM, Nick D'Ademo wrote:
> Signed-off-by: Nick D'Ademo
> ---
> recipes-security/nmap/nmap_6.25.bb |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
&g
Signed-off-by: Nick D'Ademo
---
recipes-security/nmap/nmap_6.25.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/nmap/nmap_6.25.bb
b/recipes-security/nmap/nmap_6.25.bb
index aff5c63..5efcc70 100644
--- a/recipes-security/nmap/nmap_6.25.bb
+++ b/re
Re-submitted with new lines at end of recipe preserved.
Nick
On Tue, May 6, 2014 at 9:28 PM, Nick D'Ademo wrote:
> ---
> recipes-security/nmap/nmap_6.25.bb |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-security/nmap/nmap_6.25.bb b/r
---
recipes-security/nmap/nmap_6.25.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/nmap/nmap_6.25.bb
b/recipes-security/nmap/nmap_6.25.bb
index aff5c63..5efcc70 100644
--- a/recipes-security/nmap/nmap_6.25.bb
+++ b/recipes-security/nmap/nmap_6.25.bb
@@
---
recipes-security/nmap/nmap_6.25.bb |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/recipes-security/nmap/nmap_6.25.bb
b/recipes-security/nmap/nmap_6.25.bb
index aff5c63..0c70fd3 100644
--- a/recipes-security/nmap/nmap_6.25.bb
+++ b/recipes-security/nmap/nmap_6.25.b
Forwarded to Yocto List
-- Forwarded message --
From: Nick D'Ademo
Date: Sun, Jan 12, 2014 at 3:32 PM
Subject: autogen-native recipe compilation error (since upgrade to 5.18.2)
To: p...@yoctoproject.org
Cc: liezhi.y...@windriver.com, richard.pur...@linuxfoundation.org
Sinc
d?
Thanks,
Nick
On Wed, Jan 8, 2014 at 12:24 AM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:
>
> On Tue, Jan 7, 2014 at 2:19 PM, Nick D'Ademo wrote:
>
>> Can't seem to get the build process to create a EXT4 filesystem - I've
>> tried the followi
Can't seem to get the build process to create a EXT4 filesystem - I've
tried the following:
1. Tried adding ROOTFSTYPE ?= "*ext4*" to the machine .conf file
2. Ensured EXT4 is enabled in the Linux kernel (using menuconfig)
This is a build for the Intel NUC hardware.
Anyone have any ideas on how
On Sun, Nov 24, 2013 at 8:53 PM, Nick D'Ademo wrote:
> *A follow up to this (after further testing with the Yocto image classes -
> i.e. not my own custom image):*
>
> *After adding the following to local.conf (keeping all other variables to
> their defaults):*
>
nick/poky/meta/recipes-multimedia/x264/x264_git.bb
<http://x264_git.bb>, do_package
/home/nick/poky/meta/recipes-multimedia/libav/libav_0.8.8.bb
<http://libav_0.8.8.bb>, do_configureSummary: There were 4 ERROR messages
shown, returning a non-zero exit code.*
*This appears to be a bug wit
>From what I've read so far, by adding the following to the local.conf file
(e.g. for a x86_64 build; in my case for the Intel NUC machine), Yocto will
build an image which also contains 32-bit compiled system libraries (+ any
32-bit packages/recipes you have specified):
require conf/multilib.conf
24 matches
Mail list logo
