On Apr 17, 2013, at 10:30 PM, Michael Fainstein
wrote:
> IMHO program strip should be removed from meta/site/common-linux.
>
> I had a problem in my recipe: 'make install' was failing due to
> /usr/bin/strip failure to recognize file format (I am building for powerpc on
> x86_64 PC). I trace
On Apr 17, 2013, at 8:11 AM, Satya Swaroop Damarla
wrote:
> Hi Burton,
>
> Please have a look at the build error I had
>
> WARNING: File '/usr/bin/sdusb-cmd' from skidata-tools was already stripped,
> this will prevent future debugging!
> ERROR: QA Issue: No GNU_HASH in the elf binary:
> '/
On Tue, Apr 9, 2013 at 6:11 PM, Tom Zanussi wrote:
> On Tue, 2013-04-09 at 18:06 -0400, Trevor Woerner wrote:
>> On Tue, Apr 9, 2013 at 5:46 PM, Robert P. J. Day
>> wrote:
>> > ok, so what am i looking for?
>>
>> I couldn't get lab3 to work fully unless I switched from package_ipk
>> to packag
Hi Atanas,
Looks good to me.
Thanks,
Jessica
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Atanas Gegov
Sent: Thursday, April 25, 2013 5:32 AM
To: yocto@yoctoproject.org
Subject: [yocto] [eclipse-poky][RFCv2 0/7] Introducing
You can use the license manifest to give you this information. See:
build/tmp/deploy/licenses/--/...
There is a license.manifest and package.manifest. The license.manifest includes
package version.
--Mark
On 4/25/13 9:10 AM, Jon Szymaniak wrote:
Hi all,
I generally like to keep a little
On 4/25/13 10:36 AM, Nicolas Dechesne wrote:
Hi there,
I have a couple of questions regarding the compliance program. If
there is a better place for asking such questions, please let me know.
I have studied the Yocto compliance documentation, [1] on the website,
and I have the following questio
Jeff,
On Thu, Apr 25, 2013 at 7:52 PM, Jeff Osier-Mixon wrote:
> Hi Nicolas, thanks for asking these questions. We are in the process
> of revising the documentation and application forms for that program,
> so your questions come at a very good time.
thanks a lot for your quick answer, and I am
Hi Nicolas, thanks for asking these questions. We are in the process
of revising the documentation and application forms for that program,
so your questions come at a very good time.
I have a few answers:
On Thu, Apr 25, 2013 at 8:36 AM, Nicolas Dechesne wrote:
> Hi there,
>
> I have a couple of
Hi there,
I have a couple of questions regarding the compliance program. If
there is a better place for asking such questions, please let me know.
I have studied the Yocto compliance documentation, [1] on the website,
and I have the following questions:
- is there any 'practical' guide with "do
Ross and Martin -- thanks for your quick responses.
I failed to mention that I wanted both the ${PV} and ${PR} for packages, so
unfortunately the *-pkgs.txt files won't suffice.
Is there a particular reason why these files don't contain this
information? I haven't looked into where these are gene
Attendees:
MarkH (also represents KevinM), Saul, Corneliu, AlexG, Cristiana, AlexD,
Laurentiu, Ionut, Jessica (also represents DaveST), Ross, BogdanM, Richard,
Cristian, Song
Notes:
- We have all CCB members here or represented here.
- Review release criteria: please see:
https://wiki.yoctopro
Attendees:
MarkH (also represents KevinM), Saul, Corneliu, AlexG, Cristiana, AlexD,
Laurentiu, Ionut, Jessica (also represents DaveST), Ross, BogdanM, Richard,
Cristian, Song
Notes:
- We have all CCB members here or represented here.
- Review release criteria: please see:
https://wiki.yoctopro
On 2013-04-25 08:49, Gary Thomas wrote:
On 2013-04-25 08:25, Burton, Ross wrote:
Hi Jon,
On 25 April 2013 15:10, Jon Szymaniak wrote:
In my current situation, I have a small read-only image where I can't afford
to ship pkg data, and wanted to gather this info on the host side of things.
I ass
On 2013-04-25 08:25, Burton, Ross wrote:
Hi Jon,
On 25 April 2013 15:10, Jon Szymaniak wrote:
In my current situation, I have a small read-only image where I can't afford
to ship pkg data, and wanted to gather this info on the host side of things.
I assume this information is tracked somewhere
On Thu, Apr 25, 2013 at 10:10:31AM -0400, Jon Szymaniak wrote:
> Hi all,
>
> I generally like to keep a little manifest file with my rootfs images,
> containing a list of installed packages and their associated versions. On
> images where I keep package data around, I usually generate this via 'o
Hi Jon,
On 25 April 2013 15:10, Jon Szymaniak wrote:
> In my current situation, I have a small read-only image where I can't afford
> to ship pkg data, and wanted to gather this info on the host side of things.
> I assume this information is tracked somewhere in the poky build directory,
> but I'
Hi all,
I generally like to keep a little manifest file with my rootfs images,
containing a list of installed packages and their associated versions. On
images where I keep package data around, I usually generate this via 'opkg
list'.
In my current situation, I have a small read-only image where
I'm trying to supply a target specific file for which there are
already many alternatives. For whatever reason, the wrong file
is always being chosen.
Here are the details: I have a local layer (meta-imx6) which is used
to override/overlay a BSP layer (meta-fsl-arm) which in turn is
supplying so
On 25 April 2013 13:57, Seth Bollinger wrote:
> On Thu, Apr 25, 2013 at 7:51 AM, Paul Barker wrote:
>>
>> Trying to apply this email I get:
>>
>> Applying: sdcard_image-rpi.bbclass: Copy startup files required
>> for 16MB GPU operation.
>> fatal: corrupt patch at line 14
>> Patch fail
Hi Diego,
On 25 April 2013 13:27, Diego Santa Cruz wrote:
> Many thanks for the valuable input. Is the traditional init system still
> supported, or is Yocto using systemd exclusively?
With 1.4 (about to be released), systemd is an option but the default
init is still sysvinit.
Ross
___
On 25 April 2013 13:51, Seth Bollinger wrote:
> On Thu, Apr 25, 2013 at 7:38 AM, Paul Barker wrote:
>>
>> '[[' should be a bash builtin. What host OS are you using for the build?
>
> I'm using debian. I'll check what the default shell is. You're right, it's
> probably dash.
>
Try 'sudo dpkg-re
On 25 April 2013 02:00, seth bollinger wrote:
> start_cd.elf and fixup_cd.dat are required when running the system with
> a 16MB GPU memory configuration. This change copies all files contained
> in bcm2835-bootfiles instead of cherry picking.
>
> Signed-off-by: Seth Bollinger
Trying to apply t
Martin Jansa
writes:
> On Thu, Apr 25, 2013 at 09:34:09AM +0200, Francesco Del Degan wrote:
>> Hi all, i just found an error building core-image-basic with icecc
>> inherited:
>
> You can send patch extending blacklist defined in icecc.bbclass:
> system_package_blacklist = [ "uclibc", "glibc"
2013/4/25 Paul Barker :
> On 25 April 2013 02:00, seth bollinger wrote:
>> When the shell tests for rootfs type I was seeing "[[: not found". I
>> use echo and egrep to test for the xz rootfs type to work around this
>> error.
>>
>
> '[[' should be a bash builtin. What host OS are you using for t
On 25 April 2013 02:00, seth bollinger wrote:
> When the shell tests for rootfs type I was seeing "[[: not found". I
> use echo and egrep to test for the xz rootfs type to work around this
> error.
>
'[[' should be a bash builtin. What host OS are you using for the build?
Also what's the exact
From: Atanas Gegov
Simplified the calling of the addNatures(...)
method. Variables describing the nature of the
project are not more local for the process(...)
method, but private object members.
---
.../ide/wizard/NewYoctoProjectTemplateProcess.java | 29 ++--
1 file changed,
From: Atanas Gegov
Resolved whitespace issues which popped up while
renaming the NewYoctoProjectTemplateProcess. Also
added some missing "//$NON-NLS-1$" declarations.
---
.../ide/wizard/NewYoctoProjectTemplateProcess.java | 37 +++-
1 file changed, 21 insertions(+), 16 deletion
From: Atanas Gegov
The original name of the class had two drawbacks:
firstly, it suggested that it applies only for C
projects and secondly, it did not state that this
is a process.
---
plugins/org.yocto.sdk.ide/plugin.xml |2 +-
.../sdk/ide/wizard/NewYoctoCProjectTemplate.java
From: Atanas Gegov
CMake projects will use additional variables in
the environment. They have to be set if the Yocto
settings are changed.
---
.../src/org/yocto/sdk/ide/utils/YoctoSDKUtils.java |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
a/plugins/org.yocto.sdk.id
From: Atanas Gegov
This enables creating projects with the introduced
CMake nature. What is still upcoming are the
template projects and a corresponfig CMake
ManagedBuilder (CMake build toolchain for
Eclipse).
---
.../ide/natures/YoctoSDKCMakeProjectNature.java| 72
..
From: Atanas Gegov
This nature is intended for Yocto projects that
use CMake as a build system. It requires the
YoctoSDKProjectNature and can be used by upcoming
CMake project templates. It excludes the
YoctoSDKAutotoolsProjectNature, e.g. their
relation in plugin.xml is declared as
"one-of-natur
From: Atanas Gegov
Added an extra variable to the templates and the
creating process to prepare them for the new CMake
nature.
---
plugins/org.yocto.sdk.ide/plugin.xml |4
.../sdk/ide/wizard/NewYoctoCProjectTemplate.java |2 ++
.../EmptyCAutotoolsProject/template.xml
From: Atanas Gegov
Hi,
This patch series introduces a YoctoSDKCMakeProjectNature as a new
nature for CMake-based Yocto Projects in the IDE. It requires the
basic YoctoSDKProjectNature and is an alternative to the
YoctoSDKAutotoolsProjectNature.
This does not affect the currently existing Autoto
> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: 24 April 2013 15:36
> To: Diego Santa Cruz
> Cc: yocto@yoctoproject.org; Bruce Ashfield
> Subject: Re: [yocto] About running old kernels with Yoctoo 1.2 or 1.3
>
> On Wednesday 24 April 2013 08:53:31
Hello,
I have included this folder in my poky folder, but still i'm not getting
the UAP drivers and firmware up and running.
https://github.com/chrisw957/meta-gumstix/commit/d0dbc51e1643860f9066c5e817db023fb062362c
I'm compiling for Gumstix overo fire on an x86 Ubuntu Studio machine.
No files re
Hi Jessica,
thank you for the input, I will resend the patches.
Best regards,
Atanas
On Thu, Apr 25, 2013 at 6:27 AM, Zhang, Jessica wrote:
> Hi Atanas,
>
> ** **
>
> Please see my comments below…
>
> ** **
>
> Thanks,
>
> Jessica
>
> ** **
>
> *From:* Atanas Gegov [mailto:ata
On Thu, Apr 25, 2013 at 09:34:09AM +0200, Francesco Del Degan wrote:
> Hi all, i just found an error building core-image-basic with icecc
> inherited:
You can send patch extending blacklist defined in icecc.bbclass:
system_package_blacklist = [ "uclibc", "glibc", "gcc", "bind", "u-boot",
"dhc
Hi all, i just found an error building core-image-basic with icecc
inherited:
NameError: global name 'set_icecc_env' is not defined
ERROR: The stack trace of python calls that resulted in this
exception/failure was:
ERROR: File "do_compile", line 26, in
ERROR:
ERROR: File "do_compile", lin
38 matches
Mail list logo
