On Wednesday 14 October 2015 15:03:09 Thanassis Silis wrote:
> The problem has been fixed with changing the CONFIG_FEATURE_DATE_NANO in
> busybox's defconfig. I don't know which of the 2 defconfigs is responsible
> though.
Unless you're using DISTRO = "poky-tiny" then it's not the one in the
I think #2 is a reasonable solution.?
From: yocto-boun...@yoctoproject.org on behalf
of Dave Mulder
Sent: Tuesday, October 13, 2015 1:30 PM
To: yocto@yoctoproject.org
Subject: [yocto] Updating NIC drivers in
The problem has been fixed with changing the CONFIG_FEATURE_DATE_NANO in
busybox's defconfig.
I don't know which of the 2 defconfigs is responsible though.
From: djnass...@hotmail.com
To: leonardo.sandoval.gonza...@linux.intel.com; yocto@yoctoproject.org;
yocto-boun...@yoctoproject.org;
Hi,
On 14/10/15 14:50, akuster808 wrote:
> Chris,
>
>
> On 10/14/2015 06:28 AM, Chris Simmonds wrote:
>> Hi,
>>
>> Is there a statement about the period of support for a Yocto release?
>> Looking through the updates, it seems that 12 months is typical, a was
>> the case for 1.4, 1.5 and 1.6 for
On Wed, Oct 14, 2015 at 02:51:17PM +0200, Ricardo Ribalda Delgado wrote:
> If the path is absolute, it invalidates the SSTATE, which also
> invalidates all the recipes depending on this package.
> Signed-off-by: Ricardo Ribalda Delgado
> ---
>
On 10/14/15 8:28 AM, Chris Simmonds wrote:
> Hi,
>
> Is there a statement about the period of support for a Yocto release?
> Looking through the updates, it seems that 12 months is typical, a was
> the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
> declaration anywhere that this is
> On Oct 14, 2015, at 9:25 AM, Vuille, Martin (Martin)
> wrote:
>
> Hi,
>
> I am having a bit of trouble understanding something about
> packaging.
>
> I have a custom recipe to build a package that contains both
> a daemon executable and a shared object interface library
On Oct 14, 2015, at 10:16 AM, Khem Raj wrote:
>
>> On Oct 14, 2015, at 9:32 AM, Allen Curtis
>> wrote:
>>
>> Hello,
>>
>> When I execute any of the mtd utilities from a Yocto AM335x build, they
>> terminate with a floating point
Hello,
When I execute any of the mtd utilities from a Yocto AM335x build, they
terminate with a floating point exception.
Is this a known bug?
Is there a patch?
TIA
--
___
yocto mailing list
yocto@yoctoproject.org
On 15-10-14 11:12 AM, Chris Simmonds wrote:
Hi,
On 14/10/15 14:50, akuster808 wrote:
Chris,
On 10/14/2015 06:28 AM, Chris Simmonds wrote:
Hi,
Is there a statement about the period of support for a Yocto release?
Looking through the updates, it seems that 12 months is typical, a was
the
On 14/10/15 17:27, Mark Hatle wrote:
> On 10/14/15 8:28 AM, Chris Simmonds wrote:
>> Hi,
>>
>> Is there a statement about the period of support for a Yocto release?
>> Looking through the updates, it seems that 12 months is typical, a was
>> the case for 1.4, 1.5 and 1.6 for example, but I cannot
Hi,
I am having a bit of trouble understanding something about
packaging.
I have a custom recipe to build a package that contains both
a daemon executable and a shared object interface library
for the daemon.
But the .so is only packaged in ${PN}-dev, not ${PN}, so
it doesn't end up on the
On 14 October 2015 at 03:57, Finn Carlsvi wrote:
> Thanks Ross,
>
> That makes much more sense. I incorporated your edits, however, I used:
>
> EXTRA_OECONF_append = " --with-external-capnp"
> instead of EXTRA_OECMAKE, since it was used for the configuration
> originally.
Hello,
The current dizzy version under test is 1.7.3. Will there be one more
update after 2.0 releases, a 1.7.4? I have not done a last call and I
have patches being stage for one more update. I have updated the 3.14
kernel but it introduced lttng issues. If 1.7.3 is the last update,
there is no
Hi there,
I noticed a curious problem when trying to build a cmake based recipe. During
configuration phase pthead.h is found.
>
?space?--cmake
/opt/ZX3/yocto/poky/build/tmp/work/cortexa9-vfp-neon-poky-linux-gnueabi/vs100k/0.1-r0/src
-DCMAKE_INSTALL_PREFIX:PATH=/usr
Hi,
Is there a statement about the period of support for a Yocto release?
Looking through the updates, it seems that 12 months is typical, a was
the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
declaration anywhere that this is the expected norm.
Leading on from that, is 12 months
Chris,
On 10/14/2015 06:28 AM, Chris Simmonds wrote:
> Hi,
>
> Is there a statement about the period of support for a Yocto release?
> Looking through the updates, it seems that 12 months is typical, a was
> the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
> declaration anywhere
> On Oct 14, 2015, at 9:32 AM, Allen Curtis
> wrote:
>
> Hello,
>
> When I execute any of the mtd utilities from a Yocto AM335x build, they
> terminate with a floating point exception.
>
> Is this a known bug?
Can you provide more details
>
> Is there a
If the path is absolute, it invalidates the SSTATE, which also
invalidates all the recipes depending on this package.
Signed-off-by: Ricardo Ribalda Delgado
---
recipes-devtools/oracle-java/oracle-jse-ejre.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
If the path is absolute, it invalidates the SSTATE, which also
invalidates all the recipes depending on this package.
Signed-off-by: Ricardo Ribalda Delgado
---
recipes-devtools/oracle-java/oracle-jse.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
If the path is absolute, it invalidates the SSTATE, which also
invalidates all the recipes depending on this package.
Signed-off-by: Ricardo Ribalda Delgado
---
recipes-devtools/oracle-java/oracle-jse-ejre.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The status email sent to the Yocto Project mailing
list by the Recipe Reporting Tool still shows the
old URL (http://packages.yoctoproject.org).
This patch changes it to the new URL:
http://recipes.yoctoproject.org
Signed-off-by: Belen Barros Pena
---
This makes the resulting /etc/os-release file have valid shell
assignment syntax. This makes it loadable by a shell script, using the
'source' command:
source /etc/os-release
---
meta/recipes-core/os-release/os-release.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Ross Burton wrote:
> On 2 July 2015 at 09:00, Craig McQueen wrote:
> > It would be good if the /etc/os-release file (created by the core
> > os-release package) could be loadable by a shell script. That is, a shell
> > script can do:
> >
> > source
24 matches
Mail list logo