Re: [yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Hi Maxin,

> > Do I have to add shadow-native in all these recipes or is it a bug / 
> > regression in
> pyro?
> 
> It is one of those "known" limitations which fell through the cracks.
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8078
> 
> Thanks for bringing this up. We need to address this for pyro/master.

okay, thanks, so I am adding shadow-native as a workaround for the moment.

Regards
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Hi Laurent,

> In pyro the creation of users and group (using the useradd class) is done 
> during
> the package pre-installation.
> 
> So my best guess is that you could move the owner/group change in the package
> post-installation as follows:

thanks for your advice. Currently it seems - as stated by Maxim B. John - do be 
a bug / regression in pyro, so adding shadow-native to the dependencies helps. 
Besides that I think that it is okay to access the user in the install task, 
since it should already be available then.

Regards
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Configure eth0 to come up with Link-Local IPv6 address only

[Thomas Thorne]

I was unable to get the Raspberry Pi 3 I am targeting to start with eth0 up and 
only an IPv6 link local address present on eth0, using only a 
/etc/network/interfaces file.  In the end I added shell script under /etc/rc5.d 
which called out to `ifconfig eth0 up`.  This brought eth0 up with only a IPv6 
link local address.

If someone has a solution using just /etc/network/interface based settings I 
would be interested to hear it.

Regards, Thomas Thorne

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Errors while building imx6qsabresd using fsl-community-bsp repo

[Charmi Suchak]

Hi,

I am new to yocto training and I am trying to build a linux for imx series
target from NXP. I got the bsp layer along with poky using the following:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b
daisy
repo sync

Now when I try to build core-image-minimal I get the following errors:

Parsing recipes: 100%
||
Time: 00:01:23
Parsing of 1398 .bb files complete (0 cached, 1398 parsed). 1826 targets,
101 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.22.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "imx6qsabresd"
DISTRO= "poky"
DISTRO_VERSION= "1.6.3"
TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "(nobranch):39ec0738d4bdc566eca2724dc35c557955042242"
meta-oe   = "(nobranch):d3d14d3fcca7fcde362cf0b31411dc4eea6d20aa"
meta-fsl-arm  = "(nobranch):0c4de80867c3ab4e9682dd7802d3fd907d1e1a23"
meta-fsl-arm-extra = "(nobranch):c95f3f8b5b347f1b3e77d2d11063207ddb7dc5ec"
meta-fsl-demos= "(nobranch):f141c7d1158b8addbd6f1ed047a1b47c2ed85f8f"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Checksum failure encountered with download of
http://downloads.yoctoproject.org/releases/gnu-config/gnu-config-20120814.tar.bz2
- will attempt other sources if available
WARNING: Renaming
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/gnu-config-20120814.tar.bz2
to
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/gnu-config-20120814.tar.bz2_bad-checksum_550a1f90200546416f8d12b878edfb50
WARNING: Checksum failure encountered with download of
http://download.savannah.gnu.org/releases/quilt/quilt-0.61.tar.gz - will
attempt other sources if available
WARNING: Renaming
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/quilt-0.61.tar.gz
to
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/quilt-0.61.tar.gz_bad-checksum_edff525cc95ce8932e66c2e2bfeabdbf
WARNING: Checksum failure encountered with download of
ftp://ftp.gnu.org/gnu/automake/automake-1.14.tar.gz - will attempt other
sources if available
WARNING: Renaming
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/automake-1.14.tar.gz
to
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/automake-1.14.tar.gz_bad-checksum_1ada9887dbde94d6fbda52bd91543738
WARNING: Checksum failure encountered with download of
ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.gz - will attempt other
sources if available
WARNING: Renaming
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/libtool-2.4.2.tar.gz
to
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/libtool-2.4.2.tar.gz_bad-checksum_9546fcbc4c15aada3464891bfe3f484b
WARNING: Failed to fetch URL
http://download.gna.org/cryptodev-linux/cryptodev-linux-1.6.tar.gz,
attempting MIRRORS if available
WARNING: Failed to fetch URL
http://gnome-build-stage-1.googlecode.com/files/uuid-1.6.2.tar.gz,
attempting MIRRORS if available
WARNING: Checksum failure encountered with download of
http://download.oracle.com/berkeley-db/db-5.3.21.tar.gz - will attempt
other sources if available
WARNING: Renaming
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/db-5.3.21.tar.gz
to
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/downloads/db-5.3.21.tar.gz_bad-checksum_49429d4ac8880348db65209c82fd2549
WARNING: Failed to fetch URL http://zlib.net/pigz/pigz-2.3.1.tar.gz,
attempting MIRRORS if available
WARNING: Failed to fetch URL
http://downloads.sourceforge.net/libusb/libusb-1.0.9.tar.bz2, attempting
MIRRORS if available
WARNING: Failed to fetch URL git://
git.freescale.com/imx/linux-2.6-imx.git;branch=imx_3.10.17_1.0.1_ga,
attempting MIRRORS if available


*ERROR: Fetcher failure: Fetch command failed with exit code 128,
output:fatal: Not a git repository (or any of the parent directories): .git*


*ERROR: Function failed: Fetcher failure for URL:
'git://git.freescale.com/imx/linux-2.6-imx.git;branch=imx_3.10.17_1.0.1_ga
'.
Unable to fetch URL from any source.ERROR: Logfile of failure stored in:
/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_fetch.17316ERROR:
Task 70
(/home/charmi/charmi/charmi/Training/yocto/imx6/fsl-community-bsp/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
, do_fetch) failed with exit code '1'*
NOTE: Tasks Summary: Attempted 624 tasks of which 13 didn't need 

Re: [yocto] [prelink-cross][PATCH] src/rtld: Add MicroBlaze support based on glibc-2.24

[Nathan Rossi]

On 20 June 2017 at 00:20, Mark Hatle  wrote:
> I've merged this to the cross_prelink_staging (and master_staging, even though
> it's a no-op there).  The change seems fairly obvious to me.
>
> Can you verify it is working properly as merged into cross_prelink_staging, 
> then
> I'll move it to the full cross_prelink and master.

Tested the cross_prelink_staging branch and verified that it behaves
as expected.

Sorry I forgot to add the ChangeLog entry. However when you added it
you used 2016 for the year.

On a side note, once merged into the cross_prelink branch do you see
any issues with updating the SRCREV in oe-core?

Thanks,
Nathan

>
> --Mark
>
> On 6/19/17 8:45 AM, Nathan Rossi wrote:
>> Add definitions/config to support MicroBlaze, using glibc-2.24 as
>> reference.
>>
>> Signed-off-by: Nathan Rossi 
>> ---
>>  src/rtld/dl-tls.c |  5 +
>>  src/rtld/rtld.c   | 12 
>>  2 files changed, 17 insertions(+)
>>
>> diff --git a/src/rtld/dl-tls.c b/src/rtld/dl-tls.c
>> index 8b972ff126..2da6bc5c66 100644
>> --- a/src/rtld/dl-tls.c
>> +++ b/src/rtld/dl-tls.c
>> @@ -133,6 +133,11 @@ rtld_determine_tlsoffsets (int e_machine, struct 
>> r_scope_elem *search_list)
>>tls_tcb_size = 0;
>>break;
>>
>> +case EM_MICROBLAZE:
>> +  tls_dtv_at_tp = 1;
>> +  tls_tcb_size = 8;
>> +  break;
>> +
>>  default:
>>/* Hope there's no TLS!  */
>>for (i = 0; i < search_list->r_nlist; i++)
>> diff --git a/src/rtld/rtld.c b/src/rtld/rtld.c
>> index 8d7d760a57..3196981247 100644
>> --- a/src/rtld/rtld.c
>> +++ b/src/rtld/rtld.c
>> @@ -215,6 +215,15 @@ parse_opt (int key, char *arg, struct argp_state *state)
>> | (((type) == R_NIOS2_COPY) * ELF_RTYPE_CLASS_COPY)  \
>> | (((type) == R_NIOS2_GLOB_DAT) * 
>> ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA(EM_ALTERA_NIOS2)))
>>
>> +/* From glibc-2.24: sysdeps/microblaze/dl-machine.h */
>> +# define microblaze_elf_machine_type_class(type) \
>> +  (((type) == R_MICROBLAZE_JUMP_SLOT || \
>> +(type) == R_MICROBLAZE_TLSDTPREL32 || \
>> +(type) == R_MICROBLAZE_TLSDTPMOD32 || \
>> +(type) == R_MICROBLAZE_TLSTPREL32) \
>> +* ELF_RTYPE_CLASS_PLT \
>> +   | ((type) == R_MICROBLAZE_COPY) * ELF_RTYPE_CLASS_COPY)
>> +
>>  int
>>  elf_machine_type_class (int type, int machine)
>>  {
>> @@ -243,6 +252,8 @@ elf_machine_type_class (int type, int machine)
>>   return sparc64_elf_machine_type_class(type);
>>  case EM_ALTERA_NIOS2:
>>   return nios2_elf_machine_type_class(type);
>> +case EM_MICROBLAZE:
>> + return microblaze_elf_machine_type_class(type);
>>
>>  default:
>>printf ("Unknown architecture!\n");
>> @@ -284,6 +295,7 @@ machine_no_rela (int machine)
>>  case EM_SPARC32PLUS:
>>  case EM_SPARCV9:
>>  case EM_ALTERA_NIOS2:
>> +case EM_MICROBLAZE:
>>return 0;
>>  default:
>>return 1;
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross][PATCH] src/rtld: Add MicroBlaze support based on glibc-2.24

[Mark Hatle]

On 6/20/17 7:08 AM, Nathan Rossi wrote:
> On 20 June 2017 at 00:20, Mark Hatle  wrote:
>> I've merged this to the cross_prelink_staging (and master_staging, even 
>> though
>> it's a no-op there).  The change seems fairly obvious to me.
>>
>> Can you verify it is working properly as merged into cross_prelink_staging, 
>> then
>> I'll move it to the full cross_prelink and master.
> 
> Tested the cross_prelink_staging branch and verified that it behaves
> as expected.
> 
> Sorry I forgot to add the ChangeLog entry. However when you added it
> you used 2016 for the year.

whoops.  I'll correct that.

> On a side note, once merged into the cross_prelink branch do you see
> any issues with updating the SRCREV in oe-core?

I've got a few other patches that I'd forgotten about.  Once I merge those (and
do some basic validation on them).. I'll send up a request for oe-core.  If you
don't see it in the next few days, feel free to send up an update yourself.

--Mark

> Thanks,
> Nathan
> 
>>
>> --Mark
>>
>> On 6/19/17 8:45 AM, Nathan Rossi wrote:
>>> Add definitions/config to support MicroBlaze, using glibc-2.24 as
>>> reference.
>>>
>>> Signed-off-by: Nathan Rossi 
>>> ---
>>>  src/rtld/dl-tls.c |  5 +
>>>  src/rtld/rtld.c   | 12 
>>>  2 files changed, 17 insertions(+)
>>>
>>> diff --git a/src/rtld/dl-tls.c b/src/rtld/dl-tls.c
>>> index 8b972ff126..2da6bc5c66 100644
>>> --- a/src/rtld/dl-tls.c
>>> +++ b/src/rtld/dl-tls.c
>>> @@ -133,6 +133,11 @@ rtld_determine_tlsoffsets (int e_machine, struct 
>>> r_scope_elem *search_list)
>>>tls_tcb_size = 0;
>>>break;
>>>
>>> +case EM_MICROBLAZE:
>>> +  tls_dtv_at_tp = 1;
>>> +  tls_tcb_size = 8;
>>> +  break;
>>> +
>>>  default:
>>>/* Hope there's no TLS!  */
>>>for (i = 0; i < search_list->r_nlist; i++)
>>> diff --git a/src/rtld/rtld.c b/src/rtld/rtld.c
>>> index 8d7d760a57..3196981247 100644
>>> --- a/src/rtld/rtld.c
>>> +++ b/src/rtld/rtld.c
>>> @@ -215,6 +215,15 @@ parse_opt (int key, char *arg, struct argp_state 
>>> *state)
>>> | (((type) == R_NIOS2_COPY) * ELF_RTYPE_CLASS_COPY)  \
>>> | (((type) == R_NIOS2_GLOB_DAT) * 
>>> ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA(EM_ALTERA_NIOS2)))
>>>
>>> +/* From glibc-2.24: sysdeps/microblaze/dl-machine.h */
>>> +# define microblaze_elf_machine_type_class(type) \
>>> +  (((type) == R_MICROBLAZE_JUMP_SLOT || \
>>> +(type) == R_MICROBLAZE_TLSDTPREL32 || \
>>> +(type) == R_MICROBLAZE_TLSDTPMOD32 || \
>>> +(type) == R_MICROBLAZE_TLSTPREL32) \
>>> +* ELF_RTYPE_CLASS_PLT \
>>> +   | ((type) == R_MICROBLAZE_COPY) * ELF_RTYPE_CLASS_COPY)
>>> +
>>>  int
>>>  elf_machine_type_class (int type, int machine)
>>>  {
>>> @@ -243,6 +252,8 @@ elf_machine_type_class (int type, int machine)
>>>   return sparc64_elf_machine_type_class(type);
>>>  case EM_ALTERA_NIOS2:
>>>   return nios2_elf_machine_type_class(type);
>>> +case EM_MICROBLAZE:
>>> + return microblaze_elf_machine_type_class(type);
>>>
>>>  default:
>>>printf ("Unknown architecture!\n");
>>> @@ -284,6 +295,7 @@ machine_no_rela (int machine)
>>>  case EM_SPARC32PLUS:
>>>  case EM_SPARCV9:
>>>  case EM_ALTERA_NIOS2:
>>> +case EM_MICROBLAZE:
>>>return 0;
>>>  default:
>>>return 1;
>>>
>>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] AppArmor

[Anders Montonen]

Hi,

Has anyone tried using AppArmor with Yocto? The recipe in the 
meta-security layer is broken, and when fixed so it actually builds, it 
turns out the installed init script relies on functions not found in 
Yocto's version of LSB.


Regards,
Anders
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Some Arch Linux build fixes

[Anton Novikov]

Hi, and all have a nice day.


My company contributes to OpenBMC project, whose code has an 
'import-layers/yocto-poky'


git subtree. I'm trying to build it on Arch Linux, which is a rolling 
release distribution, and


has pretty recent package versions, which triggers some bugs, which I'm 
fixing.



Patrick, an OpenBMC maintainer, sent me here, as the code in this folder 
seems to be


synchronized with Yocto code. So somebody, please look at 
https://github.com/openbmc/openbmc/pull/1817


and comment on it here. I want to either re-contribute the changes to 
Yocto, or just maintain arch-fixes


branch of github.com/an146/openbmc and have someone else to adapt the 
fixes to Yocto.



Thanks,

Anton

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Minimal eSDK with PKGDATA causes licensing issues

[Aaron_Wright]

I added these lines to my eSDK image I'm trying to build:
 
SDK_EXT_TYPE = "minimal"
SDK_INCLUDE_TOOLCHAIN = "1"
SDK_INCLUDE_PKGDATA = "1"

But bitbake comes back with lots of license issues (mpv, gstreamer, 
libvdpau, etc). These are all the commercial licensed recipes.

I don't want PKGDATA for recipes that I haven't already listed in 
LICENSE_FLAGS_WHITELIST to end up the eSDK, so I don't care about 
these errors, but they stop the build in its tracks.

How can I exclude commercial licensed (or any incompatible license) 
recipes from my eSDK?-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-docs][PATCH v2] ref-manual: Replace uclibc to musl

[Changhyeok Bae]

Hi Scott, Kristi

Could review my changes?

Thanks
Changhyeok

2017-06-12 14:52 GMT+09:00 Changhyeok Bae :

> This patch should be merged in morty (2.2), pryo (2.3), and master branch.
>
> Thanks
> Changhyeok
>
> 2017-06-12 13:07 GMT+09:00 Changhyeok Bae :
>
>> uClibc Replaced by musl from Yocto 2.2
>>
>> Signed-off-by: Changhyeok Bae 
>> ---
>>  documentation/ref-manual/ref-variables.xml | 14 +++---
>>  1 file changed, 7 insertions(+), 7 deletions(-)
>>
>> diff --git a/documentation/ref-manual/ref-variables.xml
>> b/documentation/ref-manual/ref-variables.xml
>> index bd9e517..0967e40 100644
>> --- a/documentation/ref-manual/ref-variables.xml
>> +++ b/documentation/ref-manual/ref-variables.xml
>> @@ -5131,9 +5131,9 @@
>>  is normally the same as the
>>  > ame>TARGET_OS.
>>  The variable can be set to "linux" for
>> glibc-based systems and
>> -to "linux-uclibc" for uclibc.
>> +to "linux-musl" for musl.
>>  For ARM/EABI targets, there are also "linux-gnueabi"
>> and
>> -"linux-uclibc-gnueabi" values possible.
>> +"linux-musleabi" values possible.
>>  
>>  
>>  
>> @@ -14152,9 +14152,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
>> = "${INC_PR}.3"
>>  
>>  Specifies the target's operating system.
>>  The variable can be set to "linux" for
>> glibc-based systems and
>> -to "linux-uclibc" for uclibc.
>> +to "linux-musl" for musl.
>>  For ARM/EABI targets, there are also "linux-gnueabi"
>> and
>> -"linux-uclibc-gnueabi" values possible.
>> +"linux-musleabi" values possible.
>>  
>>  
>>  
>> @@ -14283,7 +14283,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
>> = "${INC_PR}.3"
>>
>>  TCLIBC
>>  
>> -TCLIBC[doc] = "Specifies GNU standard C library (libc)
>> variant to use during the build process. You can select 'glibc' or
>> 'uclibc'."
>> +TCLIBC[doc] = "Specifies GNU standard C library (libc)
>> variant to use during the build process. You can select 'glibc' or 'musl'."
>>  
>>  
>>  
>> @@ -14295,7 +14295,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
>> = "${INC_PR}.3"
>>  
>>
>>  
>> -You can select "glibc" or "uclibc".
>> +You can select "glibc" or "musl".
>>  
>>  
>>  
>> @@ -14334,7 +14334,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
>> = "${INC_PR}.3"
>>  > >TCLIBC,
>>  which controls the variant of the GNU standard C
>> library
>>  (libc) used during the build
>> process:
>> -glibc or
>> uclibc.
>> +glibc or
>> musl.
>>  
>>
>>  
>> --
>> 2.7.4
>>
>>
>
>
> --
> Thanks
> Changhyeok
>



-- 
Thanks
Changhyeok
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] patch files

[RUSSELL PETERSON]

Hello,


I am fetching a src RPM file inside a simple library.  The RPM basically 
contains a tar file with the source and 2 patch files.  How to I apply those 
patch files?  If I put them in the SRC_URI the fetch fails.  Is there a way I 
can add them to some list that do_patche uses or do something in 
do_patch_prepend??


Regards,


Russell

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] patch files

[RUSSELL PETERSON]

Sorry.  I'm doing 5 things at once here.


I am fetching a source RPM inside a simple RECIPE.


> On June 20, 2017 at 1:33 PM RUSSELL PETERSON  wrote:
> 
> 
> Hello,
> 
> 
> I am fetching a src RPM file inside a simple library.  The RPM basically 
> contains a tar file with the source and 2 patch files.  How to I apply those 
> patch files?  If I put them in the SRC_URI the fetch fails.  Is there a way I 
> can add them to some list that do_patche uses or do something in 
> do_patch_prepend??
> 
> 
> Regards,
> 
> 
> Russell
> 
> 


 

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto eSDK, Editing/Adding Recipes, and VCS

[Aaron_Wright]

I've been trying to document some workflows for my developers using the 
Yocto eSDK for our image, but I am coming up empty when it comes to 
editing or adding recipes. I can use devtool to edit a recipe like so:

devtool edit-recipe -a my-recipe

But any changes I make are hidden away in the 
esdk/layers/poky/meta-mylayer directory, which isn't managed by a VCS (git 
in this instance). So there's this modified file in a directory--great. 
What is the developer supposed to do with it? Copy it over to a VCS 
managed directory of meta-mylayer, commit, and push?

I feel like I'm missing something with the devtool workflow. Can anyone 
point me in the right direction?
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross][PATCH] src/rtld: Add MicroBlaze support based on glibc-2.24

[Mark Hatle]

Ok, I've verify this is working properly (not on MicroBlaze, but on other
architectures).

One observation, recent gcc appears to have changed something in CXX (at least
on x86-64), and I'm now getting:

../src/prelink: /home/root/prelink-cross/testsuite/cxx1: COPY relocations don't
point into .bss or .sbss section

when running the testsuite

Anyway, what is there is now usable.  I've got a small number of x32 patches
that need to be merged.. (that will come next.)

--Mark

On 6/20/17 8:08 AM, Mark Hatle wrote:
> On 6/20/17 7:08 AM, Nathan Rossi wrote:
>> On 20 June 2017 at 00:20, Mark Hatle  wrote:
>>> I've merged this to the cross_prelink_staging (and master_staging, even 
>>> though
>>> it's a no-op there).  The change seems fairly obvious to me.
>>>
>>> Can you verify it is working properly as merged into cross_prelink_staging, 
>>> then
>>> I'll move it to the full cross_prelink and master.
>>
>> Tested the cross_prelink_staging branch and verified that it behaves
>> as expected.
>>
>> Sorry I forgot to add the ChangeLog entry. However when you added it
>> you used 2016 for the year.
> 
> whoops.  I'll correct that.
> 
>> On a side note, once merged into the cross_prelink branch do you see
>> any issues with updating the SRCREV in oe-core?
> 
> I've got a few other patches that I'd forgotten about.  Once I merge those 
> (and
> do some basic validation on them).. I'll send up a request for oe-core.  If 
> you
> don't see it in the next few days, feel free to send up an update yourself.
> 
> --Mark
> 
>> Thanks,
>> Nathan
>>
>>>
>>> --Mark
>>>
>>> On 6/19/17 8:45 AM, Nathan Rossi wrote:
 Add definitions/config to support MicroBlaze, using glibc-2.24 as
 reference.

 Signed-off-by: Nathan Rossi 
 ---
  src/rtld/dl-tls.c |  5 +
  src/rtld/rtld.c   | 12 
  2 files changed, 17 insertions(+)

 diff --git a/src/rtld/dl-tls.c b/src/rtld/dl-tls.c
 index 8b972ff126..2da6bc5c66 100644
 --- a/src/rtld/dl-tls.c
 +++ b/src/rtld/dl-tls.c
 @@ -133,6 +133,11 @@ rtld_determine_tlsoffsets (int e_machine, struct 
 r_scope_elem *search_list)
tls_tcb_size = 0;
break;

 +case EM_MICROBLAZE:
 +  tls_dtv_at_tp = 1;
 +  tls_tcb_size = 8;
 +  break;
 +
  default:
/* Hope there's no TLS!  */
for (i = 0; i < search_list->r_nlist; i++)
 diff --git a/src/rtld/rtld.c b/src/rtld/rtld.c
 index 8d7d760a57..3196981247 100644
 --- a/src/rtld/rtld.c
 +++ b/src/rtld/rtld.c
 @@ -215,6 +215,15 @@ parse_opt (int key, char *arg, struct argp_state 
 *state)
 | (((type) == R_NIOS2_COPY) * ELF_RTYPE_CLASS_COPY)  \
 | (((type) == R_NIOS2_GLOB_DAT) * 
 ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA(EM_ALTERA_NIOS2)))

 +/* From glibc-2.24: sysdeps/microblaze/dl-machine.h */
 +# define microblaze_elf_machine_type_class(type) \
 +  (((type) == R_MICROBLAZE_JUMP_SLOT || \
 +(type) == R_MICROBLAZE_TLSDTPREL32 || \
 +(type) == R_MICROBLAZE_TLSDTPMOD32 || \
 +(type) == R_MICROBLAZE_TLSTPREL32) \
 +* ELF_RTYPE_CLASS_PLT \
 +   | ((type) == R_MICROBLAZE_COPY) * ELF_RTYPE_CLASS_COPY)
 +
  int
  elf_machine_type_class (int type, int machine)
  {
 @@ -243,6 +252,8 @@ elf_machine_type_class (int type, int machine)
   return sparc64_elf_machine_type_class(type);
  case EM_ALTERA_NIOS2:
   return nios2_elf_machine_type_class(type);
 +case EM_MICROBLAZE:
 + return microblaze_elf_machine_type_class(type);

  default:
printf ("Unknown architecture!\n");
 @@ -284,6 +295,7 @@ machine_no_rela (int machine)
  case EM_SPARC32PLUS:
  case EM_SPARCV9:
  case EM_ALTERA_NIOS2:
 +case EM_MICROBLAZE:
return 0;
  default:
return 1;

>>>
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-docs][PATCH v2] ref-manual: Replace uclibc to musl

[Changhyeok Bae]

Thanks. I confirmed it.

Changhyeok

2017-06-21 9:24 GMT+09:00 Kristi Rifenbark :

> Changhyeok,
>
> Fix is backported to morty (2.2.2) - http://git.yoctoproject.org/
> cgit/cgit.cgi/yocto-docs/commit/?h=morty&id=e131c26ee1ab268679f7762dbe2676
> 0bd859e0e5
>
> Fix is backported to pyro (2.3.1) - http://git.yoctoproject.org/
> cgit/cgit.cgi/yocto-docs/commit/?h=pyro&id=859549a1dbc0b63bc04310a121600e
> a622509256
>
> Fix is the current master branch (2.4) - http://git.yoctoproject.org/
> cgit/cgit.cgi/yocto-docs/commit/?id=ed7e62f5937576d7878eb955fda12c
> 18e787db18
>
> If you want to see these changes in the manual see the published
> ref-manual for 2.2.2, 2.3.1, and 2.4.
>
> Thanks,
> Kristi
>
> On Tue, Jun 20, 2017 at 9:44 AM, Changhyeok Bae 
> wrote:
>
>> Hi Scott, Kristi
>>
>> Could review my changes?
>>
>> Thanks
>> Changhyeok
>>
>> 2017-06-12 14:52 GMT+09:00 Changhyeok Bae :
>>
>>> This patch should be merged in morty (2.2), pryo (2.3), and master
>>> branch.
>>>
>>> Thanks
>>> Changhyeok
>>>
>>> 2017-06-12 13:07 GMT+09:00 Changhyeok Bae :
>>>
 uClibc Replaced by musl from Yocto 2.2

 Signed-off-by: Changhyeok Bae 
 ---
  documentation/ref-manual/ref-variables.xml | 14 +++---
  1 file changed, 7 insertions(+), 7 deletions(-)

 diff --git a/documentation/ref-manual/ref-variables.xml
 b/documentation/ref-manual/ref-variables.xml
 index bd9e517..0967e40 100644
 --- a/documentation/ref-manual/ref-variables.xml
 +++ b/documentation/ref-manual/ref-variables.xml
 @@ -5131,9 +5131,9 @@
  is normally the same as the
  >>> ame>TARGET_OS.
  The variable can be set to "linux" for
 glibc-based systems and
 -to "linux-uclibc" for uclibc.
 +to "linux-musl" for musl.
  For ARM/EABI targets, there are also
 "linux-gnueabi" and
 -"linux-uclibc-gnueabi" values possible.
 +"linux-musleabi" values possible.
  
  
  
 @@ -14152,9 +14152,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
 = "${INC_PR}.3"
  
  Specifies the target's operating system.
  The variable can be set to "linux" for
 glibc-based systems and
 -to "linux-uclibc" for uclibc.
 +to "linux-musl" for musl.
  For ARM/EABI targets, there are also
 "linux-gnueabi" and
 -"linux-uclibc-gnueabi" values possible.
 +"linux-musleabi" values possible.
  
  
  
 @@ -14283,7 +14283,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
 = "${INC_PR}.3"

  TCLIBC
  
 -TCLIBC[doc] = "Specifies GNU standard C library (libc)
 variant to use during the build process. You can select 'glibc' or
 'uclibc'."
 +TCLIBC[doc] = "Specifies GNU standard C library (libc)
 variant to use during the build process. You can select 'glibc' or 'musl'."
  
  
  
 @@ -14295,7 +14295,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
 = "${INC_PR}.3"
  

  
 -You can select "glibc" or "uclibc".
 +You can select "glibc" or "musl".
  
  
  
 @@ -14334,7 +14334,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR
 = "${INC_PR}.3"
  >>> >TCLIBC,
  which controls the variant of the GNU standard C
 library
  (libc) used during the build
 process:
 -glibc or
 uclibc.
 +glibc or
 musl.
  

  
 --
 2.7.4


>>>
>>>
>>> --
>>> Thanks
>>> Changhyeok
>>>
>>
>>
>>
>> --
>> Thanks
>> Changhyeok
>>
>
>


-- 
Thanks
Changhyeok
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?

[Riko Ho]

How can I obtain that "udev" ? and where can I find the log ? "dmesg" | 
"grep" ?


Two days ago, I saw activity on UART when the dongle was inserted, but 
it's gone now, I can't see the activity..

Any clues ?
Thanks
On 20/06/17 12:51, Khem Raj wrote:

On Mon, Jun 19, 2017 at 8:46 PM, Riko Ho  wrote:

I got all the files needed, but now I get no response from the dongle when I
plug it,

you might want to check logs and see if there are udev events generated
on insertion.


Here's the files on the board :
root@beaglebone:/lib/firmware/rtlwifi# ls
rtl8188efw.bin   rtl8192eu_ap_wowlan.bin  rtl8723bs_bt.bin
rtl8188eufw.bin  rtl8192eu_nic.binrtl8723bs_nic.bin
rtl8192cfw.bin   rtl8192eu_wowlan.bin rtl8723bs_wowlan.bin
rtl8192cfwU.bin  rtl8192sefw.bin  rtl8723bu_ap_wowlan.bin
rtl8192cfwU_B.binrtl8712u.bin rtl8723bu_nic.bin
rtl8192cufw.bin  rtl8723aufw_A.binrtl8723bu_wowlan.bin
rtl8192cufw_A.binrtl8723aufw_B.binrtl8723fw.bin
rtl8192cufw_B.binrtl8723aufw_B_NoBT.bin   rtl8723fw_B.bin
rtl8192cufw_TMSC.bin rtl8723befw.bin  rtl8821aefw.bin
rtl8192defw.bin  rtl8723befw_36.bin   rtl8821aefw_29.bin
rtl8192eefw.bin  rtl8723bs_ap_wowlan.bin  rtl8821aefw_wowlan.bin


On 20/06/17 03:57, Khem Raj wrote:

On Sun, Jun 18, 2017 at 8:00 PM, Riko Ho  wrote:

Hello Everyone,

How can I obtain : rtl8192eu_nic.bin?

I got this message :

RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
usb 1-1: RTL8192EU MAC: 00:0b:81:a2:a5:60
usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
usb 1-1: Direct firmware load for rtlwifi/rtl8192eu_nic.bin failed with
error -2
usb 1-1: request_firmware(rtlwifi/rtl8192eu_nic.bin) failed

you probably need to add the nonfree firmware bits something like this

https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend

and

https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/rtl8192cu/rtl8192cu_4.0.2_9000.bb

might help

Thanks,

On 18/06/17 15:49, Martin Jansa wrote:

You didn't say which versions you're using.

If you're using latest oe-core with gcc7 then you will need v3 version of
this change:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113247.html
I'll send it later today.

And how can I clean after building it ? It took about 70Gb of my drive

Like any other recipe:
bitbake -c clean foo

On Sun, Jun 18, 2017 at 1:41 AM, Riko Ho  wrote:

Hello Everyone,

I tried to compile chromium but never succeeded, took me already 12 hours
and stopped on 99%,
I used bitbake for doing it,

Is chromium not compatible with arm CPU ? it was working with X86_64
before.
And how can I clean after building it ? It took about 70Gb of my drive

Thanks
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

[Riko Ho]

Ok, thanks a lot for the parameter idea, where will I put that ? 
local.conf, bblayers.conf ?



On 20/06/17 13:08, Khem Raj wrote:

On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho  wrote:

My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can
help ?


add something like

EXTRA_OEGYP_prepend = " -Dcomponent=shared_library
-Dremove_webcore_debug_symbols=1 -Dfastbuild=1 "

and see if that helps.


I compiled firefox and it worked well, but still wondering why chromium
didn't work.


On 20/06/17 04:01, Khem Raj wrote:

On Mon, Jun 19, 2017 at 7:21 AM, Jacobo Aragunde Pérez
 wrote:

On 18/06/17 20:10, Gunnar Andersson wrote:

Riko Ho  wrote:

Hello Everyone,

I tried to compile chromium but never succeeded, took me already 12
hours and stopped on 99%, I used bitbake for doing it,

Not sure what would cause it to just stop and it could have been some
temporary glitch?   Maybe you want to provide some logs of your build if
Martin's reference does not help.

Just a heads-up, if it stopped at 99% it probably was in the linking
phase (you can check the logs under
tmp/work/$arch/chromium-wayland/$version/temp/log.do_compile to be
certain). This phase has a very high RAM demand, you could even need to
temporarily increase your swap space to go past that point.

linker takes a whole lot of memory here, if you have < 8G of RAM
its likely to fail with out of memory errors. Can you check your dmesg
and see if there were such errors in there

Best,
--
Jacobo Aragunde
Software Engineer at Igalia
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

[Khem Raj]

add it to chromium recipe itself if you dont have a bbappend for it.

On Tue, Jun 20, 2017 at 9:53 PM, Riko Ho  wrote:
> Ok, thanks a lot for the parameter idea, where will I put that ? local.conf,
> bblayers.conf ?
>
>
> On 20/06/17 13:08, Khem Raj wrote:
>
> On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho  wrote:
>
> My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can
> help ?
>
> add something like
>
> EXTRA_OEGYP_prepend = " -Dcomponent=shared_library
> -Dremove_webcore_debug_symbols=1 -Dfastbuild=1 "
>
> and see if that helps.
>
> I compiled firefox and it worked well, but still wondering why chromium
> didn't work.
>
>
> On 20/06/17 04:01, Khem Raj wrote:
>
> On Mon, Jun 19, 2017 at 7:21 AM, Jacobo Aragunde Pérez
>  wrote:
>
> On 18/06/17 20:10, Gunnar Andersson wrote:
>
> Riko Ho  wrote:
>
> Hello Everyone,
>
> I tried to compile chromium but never succeeded, took me already 12
> hours and stopped on 99%, I used bitbake for doing it,
>
> Not sure what would cause it to just stop and it could have been some
> temporary glitch?   Maybe you want to provide some logs of your build if
> Martin's reference does not help.
>
> Just a heads-up, if it stopped at 99% it probably was in the linking
> phase (you can check the logs under
> tmp/work/$arch/chromium-wayland/$version/temp/log.do_compile to be
> certain). This phase has a very high RAM demand, you could even need to
> temporarily increase your swap space to go past that point.
>
> linker takes a whole lot of memory here, if you have < 8G of RAM
> its likely to fail with out of memory errors. Can you check your dmesg
> and see if there were such errors in there
>
> Best,
> --
> Jacobo Aragunde
> Software Engineer at Igalia
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> --
>
> /***/
> Sent by Ubuntu LTS 16.04,
> 谢谢,
> Regards,
> Riko Ho
> /***/
>
>
> --
>
> /***/
> Sent by Ubuntu LTS 16.04,
> 谢谢,
> Regards,
> Riko Ho
> /***/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?

[Khem Raj]

On Tue, Jun 20, 2017 at 9:52 PM, Riko Ho  wrote:
> How can I obtain that "udev" ? and where can I find the log ? "dmesg" |
> "grep" ?
>
> Two days ago, I saw activity on UART when the dongle was inserted, but it's
> gone now, I can't see the activity..
> Any clues ?

dmesg should have some information may be

> Thanks
>
> On 20/06/17 12:51, Khem Raj wrote:
>
> On Mon, Jun 19, 2017 at 8:46 PM, Riko Ho  wrote:
>
> I got all the files needed, but now I get no response from the dongle when I
> plug it,
>
> you might want to check logs and see if there are udev events generated
> on insertion.
>
> Here's the files on the board :
> root@beaglebone:/lib/firmware/rtlwifi# ls
> rtl8188efw.bin   rtl8192eu_ap_wowlan.bin  rtl8723bs_bt.bin
> rtl8188eufw.bin  rtl8192eu_nic.binrtl8723bs_nic.bin
> rtl8192cfw.bin   rtl8192eu_wowlan.bin rtl8723bs_wowlan.bin
> rtl8192cfwU.bin  rtl8192sefw.bin  rtl8723bu_ap_wowlan.bin
> rtl8192cfwU_B.binrtl8712u.bin rtl8723bu_nic.bin
> rtl8192cufw.bin  rtl8723aufw_A.binrtl8723bu_wowlan.bin
> rtl8192cufw_A.binrtl8723aufw_B.binrtl8723fw.bin
> rtl8192cufw_B.binrtl8723aufw_B_NoBT.bin   rtl8723fw_B.bin
> rtl8192cufw_TMSC.bin rtl8723befw.bin  rtl8821aefw.bin
> rtl8192defw.bin  rtl8723befw_36.bin   rtl8821aefw_29.bin
> rtl8192eefw.bin  rtl8723bs_ap_wowlan.bin  rtl8821aefw_wowlan.bin
>
>
> On 20/06/17 03:57, Khem Raj wrote:
>
> On Sun, Jun 18, 2017 at 8:00 PM, Riko Ho  wrote:
>
> Hello Everyone,
>
> How can I obtain : rtl8192eu_nic.bin?
>
> I got this message :
>
> RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
> usb 1-1: RTL8192EU MAC: 00:0b:81:a2:a5:60
> usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
> usb 1-1: Direct firmware load for rtlwifi/rtl8192eu_nic.bin failed with
> error -2
> usb 1-1: request_firmware(rtlwifi/rtl8192eu_nic.bin) failed
>
> you probably need to add the nonfree firmware bits something like this
>
> https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
>
> and
>
> https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/rtl8192cu/rtl8192cu_4.0.2_9000.bb
>
> might help
>
> Thanks,
>
> On 18/06/17 15:49, Martin Jansa wrote:
>
> You didn't say which versions you're using.
>
> If you're using latest oe-core with gcc7 then you will need v3 version of
> this change:
> http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113247.html
> I'll send it later today.
>
> And how can I clean after building it ? It took about 70Gb of my drive
>
> Like any other recipe:
> bitbake -c clean foo
>
> On Sun, Jun 18, 2017 at 1:41 AM, Riko Ho  wrote:
>
> Hello Everyone,
>
> I tried to compile chromium but never succeeded, took me already 12 hours
> and stopped on 99%,
> I used bitbake for doing it,
>
> Is chromium not compatible with arm CPU ? it was working with X86_64
> before.
> And how can I clean after building it ? It took about 70Gb of my drive
>
> Thanks
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> --
>
> /***/
> Sent by Ubuntu LTS 16.04,
> 谢谢,
> Regards,
> Riko Ho
> /***/
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> --
>
> /***/
> Sent by Ubuntu LTS 16.04,
> 谢谢,
> Regards,
> Riko Ho
> /***/
>
>
> --
>
> /***/
> Sent by Ubuntu LTS 16.04,
> 谢谢,
> Regards,
> Riko Ho
> /***/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?

[Riko Ho]

I got those messages :

===

musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (89, retry #1, port1 0100
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (89, retry #2, port1 0104
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (89, retry #3, port1 0104
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, retry #3, port1 0008010c



waiting for vrise ?


On 21/06/17 10:28, Khem Raj wrote:

On Tue, Jun 20, 2017 at 9:52 PM, Riko Ho  wrote:

How can I obtain that "udev" ? and where can I find the log ? "dmesg" |
"grep" ?

Two days ago, I saw activity on UART when the dongle was inserted, but it's
gone now, I can't see the activity..
Any clues ?

dmesg should have some information may be


Thanks

On 20/06/17 12:51, Khem Raj wrote:

On Mon, Jun 19, 2017 at 8:46 PM, Riko Ho  wrote:

I got all the files needed, but now I get no response from the dongle when I
plug it,

you might want to check logs and see if there are udev events generated
on insertion.

Here's the files on the board :
root@beaglebone:/lib/firmware/rtlwifi# ls
rtl8188efw.bin   rtl8192eu_ap_wowlan.bin  rtl8723bs_bt.bin
rtl8188eufw.bin  rtl8192eu_nic.binrtl8723bs_nic.bin
rtl8192cfw.bin   rtl8192eu_wowlan.bin rtl8723bs_wowlan.bin
rtl8192cfwU.bin  rtl8192sefw.bin  rtl8723bu_ap_wowlan.bin
rtl8192cfwU_B.binrtl8712u.bin rtl8723bu_nic.bin
rtl8192cufw.bin  rtl8723aufw_A.binrtl8723bu_wowlan.bin
rtl8192cufw_A.binrtl8723aufw_B.binrtl8723fw.bin
rtl8192cufw_B.binrtl8723aufw_B_NoBT.bin   rtl8723fw_B.bin
rtl8192cufw_TMSC.bin rtl8723befw.bin  rtl8821aefw.bin
rtl8192defw.bin  rtl8723befw_36.bin   rtl8821aefw_29.bin
rtl8192eefw.bin  rtl8723bs_ap_wowlan.bin  rtl8821aefw_wowlan.bin


On 20/06/17 03:57, Khem Raj wrote:

On Sun, Jun 18, 2017 at 8:00 PM, Riko Ho  wrote:

Hello Everyone,

How can I obtain : rtl8192eu_nic.bin?

I got this message :

RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
usb 1-1: RTL8192EU MAC: 00:0b:81:a2:a5:60
usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
usb 1-1: Direct firmware load for rtlwifi/rtl8192eu_nic.bin failed with
error -2
usb 1-1: request_firmware(rtlwifi/rtl8192eu_nic.bin) failed

you probably need to add the nonfree firmware bits something like this

https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend

and

https://github.com/resin-os/meta-resin/blob/master/meta-resin-common/recipes-kernel/rtl8192cu/rtl8192cu_4.0.2_9000.bb

might help

Thanks,

On 18/06/17 15:49, Martin Jansa wrote:

You didn't say which versions you're using.

If you're using latest oe-core with gcc7 then you will need v3 version of
this change:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113247.html
I'll send it later today.

And how can I clean after building it ? It took about 70Gb of my drive

Like any other recipe:
bitbake -c clean foo

On Sun, Jun 18, 2017 at 1:41 AM, Riko Ho  wrote:

Hello Everyone,

I tried to compile chromium but never succeeded, took me already 12 hours
and stopped on 99%,
I used bitbake for doing it,

Is chromium not compatible with arm CPU ? it was working with X86_64
before.
And how can I clean after building it ? It took about 70Gb of my drive

Thanks
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Some Arch Linux build fixes

[Khem Raj]

On Tue, Jun 20, 2017 at 10:09 AM, Anton Novikov  wrote:
> Hi, and all have a nice day.
>
>
> My company contributes to OpenBMC project, whose code has an
> 'import-layers/yocto-poky'
>
> git subtree. I'm trying to build it on Arch Linux, which is a rolling
> release distribution, and
>
> has pretty recent package versions, which triggers some bugs, which I'm
> fixing.
>
>
> Patrick, an OpenBMC maintainer, sent me here, as the code in this folder
> seems to be
>
> synchronized with Yocto code. So somebody, please look at
> https://github.com/openbmc/openbmc/pull/1817

this are good fixes. Please send them to openembedded-core@ mailing list
for review and inclusion in branches they are required. Please be aware
that rolling releases are hard to use for a time based release like Yocto
since over period of time things will change unless you keep using master
of yocto. I would suggest to consider this fact.

>
> and comment on it here. I want to either re-contribute the changes to Yocto,
> or just maintain arch-fixes
>
> branch of github.com/an146/openbmc and have someone else to adapt the fixes
> to Yocto.
>
>
> Thanks,
>
> Anton
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

[Riko Ho]

drwxrwxr-x 5 bianchi77 bianchi77 4.0K Jun 14 14:31 .
drwxrwxr-x 3 bianchi77 bianchi77 4.0K Jun 12 15:50 ..
drwxrwxr-x 2 bianchi77 bianchi77 4.0K Jun 12 15:50 cef3
-rw-rw-r-- 1 bianchi77 bianchi77 2.7K Jun 12 15:50 cef3_280796.bb
drwxrwxr-x 4 bianchi77 bianchi77 4.0K Jun 12 15:50 chromium
*-rw-rw-r-- 1 bianchi77 bianchi77 1.2K Jun 12 15:50 chromium_54.0.2810.2.bb*
-rw-rw-r-- 1 bianchi77 bianchi77  11K Jun 12 15:50 chromium-browser.inc
-rw-rw-r-- 1 bianchi77 bianchi77 4.6K Jun 12 15:50 chromium.inc
-rw-rw-r-- 1 bianchi77 bianchi77 2.2K Jun 12 15:50 
chromium-wayland_53.0.2785.143.bb

drwxrwxr-x 8 bianchi77 bianchi77 4.0K Jun 12 15:50 files

is this one ? *chromium_54.0.2810.2.bb ?

Thanks
*
On 21/06/17 10:28, Khem Raj wrote:

add it to chromium recipe itself if you dont have a bbappend for it.

On Tue, Jun 20, 2017 at 9:53 PM, Riko Ho  wrote:

Ok, thanks a lot for the parameter idea, where will I put that ? local.conf,
bblayers.conf ?


On 20/06/17 13:08, Khem Raj wrote:

On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho  wrote:

My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can
help ?

add something like

EXTRA_OEGYP_prepend = " -Dcomponent=shared_library
-Dremove_webcore_debug_symbols=1 -Dfastbuild=1 "

and see if that helps.

I compiled firefox and it worked well, but still wondering why chromium
didn't work.


On 20/06/17 04:01, Khem Raj wrote:

On Mon, Jun 19, 2017 at 7:21 AM, Jacobo Aragunde Pérez
 wrote:

On 18/06/17 20:10, Gunnar Andersson wrote:

Riko Ho  wrote:

Hello Everyone,

I tried to compile chromium but never succeeded, took me already 12
hours and stopped on 99%, I used bitbake for doing it,

Not sure what would cause it to just stop and it could have been some
temporary glitch?   Maybe you want to provide some logs of your build if
Martin's reference does not help.

Just a heads-up, if it stopped at 99% it probably was in the linking
phase (you can check the logs under
tmp/work/$arch/chromium-wayland/$version/temp/log.do_compile to be
certain). This phase has a very high RAM demand, you could even need to
temporarily increase your swap space to go past that point.

linker takes a whole lot of memory here, if you have < 8G of RAM
its likely to fail with out of memory errors. Can you check your dmesg
and see if there were such errors in there

Best,
--
Jacobo Aragunde
Software Engineer at Igalia
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

[Riko Ho]

did I put it wrongly ?

===

Loading cache: 100% 
|#| 
Time: 0:00:01

Loaded 2794 entries from dependency cache.
ERROR: ParseError at 
/home/bianchi77/poky/meta-browser/recipes-browser/chromium/chromium_54.0.2810.2.bb:7: 
unparsed line: 'EXTRA_OEGYP_prepend = " -Dcomponent=shared_library



On 21/06/17 10:28, Khem Raj wrote:

add it to chromium recipe itself if you dont have a bbappend for it.

On Tue, Jun 20, 2017 at 9:53 PM, Riko Ho  wrote:

Ok, thanks a lot for the parameter idea, where will I put that ? local.conf,
bblayers.conf ?


On 20/06/17 13:08, Khem Raj wrote:

On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho  wrote:

My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can
help ?

add something like

EXTRA_OEGYP_prepend = " -Dcomponent=shared_library
-Dremove_webcore_debug_symbols=1 -Dfastbuild=1 "

and see if that helps.

I compiled firefox and it worked well, but still wondering why chromium
didn't work.


On 20/06/17 04:01, Khem Raj wrote:

On Mon, Jun 19, 2017 at 7:21 AM, Jacobo Aragunde Pérez
 wrote:

On 18/06/17 20:10, Gunnar Andersson wrote:

Riko Ho  wrote:

Hello Everyone,

I tried to compile chromium but never succeeded, took me already 12
hours and stopped on 99%, I used bitbake for doing it,

Not sure what would cause it to just stop and it could have been some
temporary glitch?   Maybe you want to provide some logs of your build if
Martin's reference does not help.

Just a heads-up, if it stopped at 99% it probably was in the linking
phase (you can check the logs under
tmp/work/$arch/chromium-wayland/$version/temp/log.do_compile to be
certain). This phase has a very high RAM demand, you could even need to
temporarily increase your swap space to go past that point.

linker takes a whole lot of memory here, if you have < 8G of RAM
its likely to fail with out of memory errors. Can you check your dmesg
and see if there were such errors in there

Best,
--
Jacobo Aragunde
Software Engineer at Igalia
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/


--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [EXTERNAL] Re: Openjdk-8 fetcher failure

[Pawar, Alok]

HI John, 

Using the 'wget',  I am able to download the file.

Best Regards
Alok Pawar
Sr. Engineer Product Development

-Original Message-
From: Maxin B. John [mailto:maxin.j...@intel.com] 
Sent: Monday, June 19, 2017 6:37 PM
To: Pawar, Alok 
Cc: yocto@yoctoproject.org
Subject: [EXTERNAL] Re: [yocto] Openjdk-8 fetcher failure

Hi Alok,

On Mon, Jun 19, 2017 at 06:11:20AM +, Pawar, Alok wrote:
> 
>Hi All,
>
> I am using yocto 2.1.2 krogoth, and I added meta-java in it, but when I tried 
> to bitbake. I faced fetcher failure, following are the Error :
>
>ERROR: openjdk-8-102b14-r0 do_fetch: Fetcher failure: Fetch command failed 
>with exit code 4, output:
>
>  Read error (Connection timed out) in headers.
>
>  Read error (Connection timed out) in headers.
>
>ERROR: openjdk-8-102b14-r0 do_fetch: Function failed: Fetcher failure for URL: 
>'http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/archive/ac29c9c1193a.tar.bz2;name=hotspot;unpack=false'.
> Unable to fetch URL from any source.
>
>Please give your inputs.

This could be related to the network configuration in your build machine.

Have you tried to fetch that file manually using wget from your machine ?
ie:
# wget 
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/archive/ac29c9c1193a.tar.bz2


Best Regards,
Maxin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto