On 2018年07月24日 03:21, Bruce Ashfield wrote:
> Which version/branches is this for ?
>
This is for linux-yocto rt branches. linux-yocto-4.12 does not need this
fix, since the commit, see below, causing the issue have not been included.
On Mon, Jul 23, 2018 at 1:29 PM, Simon Chamlian wrote:
> Hi,
>
> In order to remove package from busybox, I used:
>
> $ bitbake -c menuconfig busybox
>
> Under 'System Logging Itilities -->' I unchecked syslogd
>
> Then ran
> $ bitbake busybox
>
> and I get the following error:
>
> WARNING:
grpc has build dependencies that are also in meta-oe, add the layer to
conf/bblayers.conf instead of just copying it piece by piece.
Ross
On 23 July 2018 at 21:45, Simon Chamlian wrote:
> So I cloned the git meta-networking.
>
> Copied the whole
>
So I cloned the git meta-networking.
Copied the whole
meta-openembedded/meta-networking/recipes-devtools/grpc
into my layer. Ran bitbake and I get the following errors:
$ bitbake grpc
Loading cache: 100%
|#|
Time:
Hi,
In order to remove package from busybox, I used:
$ bitbake -c menuconfig busybox
Under 'System Logging Itilities -->' I unchecked *syslogd*
Then ran
$ bitbake busybox
and I get the following error:
WARNING: busybox-1.24.1-r0 do_package: busybox: alternative target
(/etc/syslog.conf or
Note that we programmatically create the rpm spec files, and there is
currently no support for writing changelogs into them.
Generally, hand-crafted changelogs are just a maintenance burden, if you ask me.
Alex
2018-07-23 20:49 GMT+02:00 Burton, Ross :
> On 23 July 2018 at 18:30, Vikram
On Sat, Jul 21, 2018 at 12:55 AM, MOHAMMAD RASIM
wrote:
> well apparently this is caused by the unzip binary that is compiled by the
> openembedded unzip recipe.
> If I unzip the same zip file with the unzip binary that is shipped with my
> system(manjaro) then the files are not corrupted but
Thanks Mark. Is it possible to somehow use already created changelog while
building rpm?
Thanks
On Tue, Jul 17, 2018 at 11:51 AM Mark Hatle
wrote:
> On 7/17/18 1:39 PM, Vikram Chhibber wrote:
> > Hi All,
> >
> > I use the rpm created from my recipe and I need to know if there is a
> way to add
Thanks, the OE_TERMINALvariable did it for me
You cannot access d if you mean that
I don't mean d the object but the variables that are accessed by
d.getVar method.
all the variables are exported to the shell.
What variables exactly? I just tried to echo some of the machine config
and
You can use the variable OE_TERMINAL to choose your preferred terminal.
By default it's set to auto and Bitbake figures out what terminal is
available on your system. Please refer to the manual at:
https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#var-OE_TERMINAL.
> Also, is it
Doesn't matter as the file doesn't exist anymore.
Ross
On 23 July 2018 at 13:02, tugouxp <13824125...@163.com> wrote:
> hi burton:
>
>thank you, just as you say, i remove it.
>
> but, did this operation affect the function of the curl? or it does not
> matter?
>
> thanks !
>
>
>
>
>
>
> At
hi burton:
thank you, just as you say, i remove it.
but, did this operation affect the function of the curl? or it does not matter?
thanks !
At 2018-07-23 19:37:43, "Burton, Ross" wrote:
>On 23 July 2018 at 12:21, tugouxp <13824125...@163.com> wrote:
>> hi burton:
>> sorry for
On 23 July 2018 at 12:21, tugouxp <13824125...@163.com> wrote:
> hi burton:
> sorry for that. :-|
>
> i still cant get what you said, forgive me for my foolish on that, can you
> show me how to do this? thanks for your kindly help.
Find the curl recipe, open it in an editor. They'll be a
hi burton:
sorry for that. :-|
i still cant get what you said, forgive me for my foolish on that, can you
show me how to do this? thanks for your kindly help.
At 2018-07-23 18:59:32, "Burton, Ross" wrote:
>Please remember to CC the list to that everyone can see.
>
>On 23 July 2018
Please remember to CC the list to that everyone can see.
On 23 July 2018 at 11:51, tugouxp <13824125...@163.com> wrote:
> hi burton:
> thanks for your answer. so how to dealt with this, seems two selection.
>
> 1. revert the version of curl
> 2. remove “oe_multilib_header”
>
> i am a fresh man
Now the logic is:
Use options.layer_type if specified, guess if not, default to 'M'.
Note choices=['A', 'B', 'S', 'D', 'M', ''], the '' is for default='', we can't
use default='M' here, otherwise we don't know whether the 'M' is specified by
user or not, we don't guess if it is specified by user,
The following changes since commit 65d058237f96a151c913a70ba4d639c7aa0fb0b5:
Dockerfile: Reduce image size by merging RUN stages together (2018-07-23
08:40:00 +0200)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib rbt/li
It looks like you (or whoever maintains this glibc-dev branch you are
using) have upgraded curl yourself and didn't notice that curlbuild
doesn't exist in 7.57 onwards, so the oe_multilib_header call should
be removed.
(see oe-core 215d5677004537fc190b5381157ac8b94db6d7e8)
Ross
On 23 July 2018
Hi,
when running bitbake with a recipe and giving the devshell as a command
bitbake runs the devshell inside xterm, on my other machine it runs tmux.
looking at the openembedded source code here
https://github.com/openembedded/openembedded-core/blob/master/meta/lib/oe/terminal.py
I can see
Hi folks:
i meet a compiler error when compile with bitbake, look at following logs.
it seems this error cant result to failure the compile process, the image file
can be generated and running ok, but i was a bit worry on this for i dont
confirm whether it hints some fatal issues.
so, i
20 matches
Mail list logo
