Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho

so which one is the right one ? :)


On 04/07/17 14:43, Takuro Ashie wrote:

ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Oops, it's wrong.

  ac_add_options --with-system-nss
  ac_add_options --with-system-nspr


On 2017年07月04日 15:34, Takuro Ashie wrote:

You need latest poky (current master branch is needed).
But upgrading poky may also introduce unexpected changes for you.

Another solution is using built-in nss & nspr instead of system's one.
To use it remove or comment out following lines in your 
meta-browser/recipes-mozilla/firefox/firefox/mozconfig


  ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Regards,




--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Takuro Ashie

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,

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


Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho

These lines :

# System libraries
#ac_add_options --with-system-nss #comment out for nss bug
#ac_add_options --with-system-nspr

Let me try...


On 04/07/17 15:03, Takuro Ashie wrote:

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,



--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho

It's compiling now..


On 04/07/17 15:03, Takuro Ashie wrote:

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,



--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho

Still in error :

| 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/firefox-52.1.2esr/firefox-build-dir/dist/system_wrappers/pk11pub.h:3:26: 
fatal error: pk11pub.h: No such file or directory

|  #include_next 
|   ^
| compilation terminated.


On 04/07/17 15:03, Takuro Ashie wrote:

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,



--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Takuro Ashie


On 2017年07月04日 17:06, Riko Ho wrote:


Still in error :

| 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/firefox-52.1.2esr/firefox-build-dir/dist/system_wrappers/pk11pub.h:3:26: 
fatal error: pk11pub.h: No such file or directory

|  #include_next 
|   ^
| compilation terminated.



I confirmed it.
Hmm, there are some issues which prevent using built-in nss & nspr.
I can't resolve it soon.

It seems that upgrading poky is a easier way to build firefox if it's 
acceptable for you.


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


Re: [yocto] File system optimization in yocto

2017-07-04 Thread Esponde, Joel
Hi Prasoon,

What do you mean by file system loading?
Are you talking about file system mounting time?

Joël Esponde
Honeywell | Safety and Productivity Solutions

De : yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] De 
la part de Prasoon Kumar
Envoyé : lundi 3 juillet 2017 16:34
À : yocto@yoctoproject.org
Objet : [yocto] File system optimization in yocto

Hi,

I am trying to optimise the file system. I have removed the packages which are 
not required using PACKAGE_EXCLUDE. It still take around 8 seconds to load the 
file system.

How can I optimization so that my file system loading take less time. Is there 
any way to load files in a multi-threaded way so that loading is faster.

Any suggestions on optimising the file system in terms of size or time will be 
helpful.


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


Re: [yocto] How to make changes and build u-boot source code in yocto

2017-07-04 Thread Prasoon Kumar
It worked with devtool .

Thanks for the help.

On 04-Jul-2017 1:43 AM, "Khem Raj"  wrote:

>
>
> On 7/2/17 11:26 PM, Prasoon Kumar wrote:
>
> Hi,
>
> I am trying to make some changes in u-boot code and using bitbake u-boot
> to build. But it doesn't build.
> I also tried bitbake u-boot -c compile and bitbake u-boot deploy. This
> also didn't work.
>
> Can I Get some help on how to change and build u-boot.
>
>
> you should share more information about errors for someone to effectively
> help you.
>
>
> Thanks,
> Prasoon
>
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] AppArmor

2017-07-04 Thread Tom Rini
On Thu, Jun 29, 2017 at 09:35:06PM -0400, Tom Rini wrote:
> On Thu, Jun 29, 2017 at 01:56:22PM +0300, Anders Montonen wrote:
> > Hi Tom,
> > 
> > On Thu, 22 Jun 2017, Tom Rini wrote:
> > >
> > >I did fix the latter of these (along with the perl problem), but I'm
> > >using sysvinit and needed apache2 in my project anyhow.
> > 
> > Your commit fixes most of the problems, but /usr/bin/aa-easyprof
> > still gets installed with a shebang referring to the host python3
> > interpreter. The script is processed and installed by
> > utils/python-tools-setup.py, which captures whatever $PYTHON is set
> > to at the time.
> 
> Oh thanks!  I'll v2 things shortly with that fixed up.

So, FYI all, here's where I'm at.  Fixing up aa-easyprof for the shebang
part is easy as there's a few other cases around of "manually correct a
shebang".  But this exposes another problem of needing to basically
RDEPEND on python3-modules as not only does apparmor depend on a few
different core modules but the core modules themselves do not have
correct interdependencies.  As it stand today for perl this is handled
by some very fragile looking shell expressions that get re-run per perl
upgrade.  I don't think I can come up with the equivalent for python.
So my local version also has this just saying we need all of
python3-modules to be installed, and then it works.

I've also fixed up some minor logging issues in the sysvinit script
(which I know isn't a concern for Anders as he's using systemd, but just
being complete).  I will post another version in a few days just so
others can have functioning apparmor if they want it, at least until
Armin speaks up.

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


[yocto] Update SRCREV doesn't work?

2017-07-04 Thread Ngọc Thi Huỳnh
Hi everyone,

I'm using poky pyro to build a beaglebone image with swupdate.

First time I built swupdate (by bitbake swupdate), it used the latest git
version and I encountered an make error which related to swupdate only.

Then I changed swupdate version to 2017.04 (by using
PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
latest git version and I had the make error again.

But when I used devshell and changed the git revision to 2017.04 then
do_configure and do_compile, everything went fine.

My question is, is there a simple way to solve this problem?

*Note:*
The swupdate recipes for beaglebone that I'm using are from
https://github.com/sbabic/meta-swupdate

Content of swupdate_2017.04.bb:

> require swupdate.inc
>
> SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
>

Content of swupdate_git.bb

> require swupdate.inc
>
> DEFAULT_PREFERENCE = "-1"
>

A snippet of swupdate.inc

> SRCREV = "${AUTOREV}"
>

Thanks,
Huỳnh Ngọc Thi
-so61pi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Update SRCREV doesn't work?

2017-07-04 Thread Stefano Babic
Hi,

On 04/07/2017 18:13, Ngọc Thi Huỳnh wrote:
> Hi everyone,
> 
> I'm using poky pyro to build a beaglebone image with swupdate.
> 
> First time I built swupdate (by bitbake swupdate), it used the latest
> git version and I encountered an make error which related to swupdate only.
> 
> Then I changed swupdate version to 2017.04 (by using
> PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
> latest git version and I had the make error again.
> 

I cannot confirm this. I have built a custom board and setting
PREFERRED_VERSION_swupdate works without issues.

> But when I used devshell and changed the git revision to 2017.04 then
> do_configure and do_compile, everything went fine.
> 
> My question is, is there a simple way to solve this problem?
> 
> /Note:/
> The swupdate recipes for beaglebone that I'm using are from
> https://github.com/sbabic/meta-swupdate
> 
> Content of swupdate_2017.04.bb :
> 
> require swupdate.inc
> 
> SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
> 
> 
> Content of swupdate_git.bb 
> 
> require swupdate.inc
> 
> DEFAULT_PREFERENCE = "-1"
> 
> 
> A snippet of swupdate.inc
> 
> SRCREV = "${AUTOREV}"
> 
> 

Best regards,
Stefano Babic


-- 
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [qa-tools][PATCH 1/4] poduct/init: Add support for PackageManagement component

2017-07-04 Thread jose . perez . carranza
From: Jose Perez Carranza 

Create package_management_issues.py product and add support to use this
product on init file.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update/product/__init__.py  | 2 ++
 testopia_update/product/package_management_issues.py | 4 
 2 files changed, 6 insertions(+)
 create mode 100644 testopia_update/product/package_management_issues.py

diff --git a/testopia_update/product/__init__.py 
b/testopia_update/product/__init__.py
index 8d31a1e..30b2201 100644
--- a/testopia_update/product/__init__.py
+++ b/testopia_update/product/__init__.py
@@ -262,6 +262,7 @@ def get_products(testopia, opts, config, logger, **kwargs):
 from . import esdk
 from . import kernel
 from . import general_runtime
+from . import package_management_issues
 
 products = []
 
@@ -277,6 +278,7 @@ def get_products(testopia, opts, config, logger, **kwargs):
 products.append(esdk.eSDKProduct(testopia, opts, logger, config, **kwargs))
 products.append(kernel.KernelProduct(testopia, opts, logger, config, 
**kwargs))
 products.append(general_runtime.GeneralRuntimeProduct(testopia, opts, 
logger, config, **kwargs))
+
products.append(package_management_issues.PackageManagementIssues(testopia, 
opts, logger, config, **kwargs))
 products.append(DummyProduct(testopia, opts, logger, config, **kwargs))
 
 
diff --git a/testopia_update/product/package_management_issues.py 
b/testopia_update/product/package_management_issues.py
new file mode 100644
index 000..1f3ecc7
--- /dev/null
+++ b/testopia_update/product/package_management_issues.py
@@ -0,0 +1,4 @@
+from testopia_update.product import Product
+
+class PackageManagementIssues(Product):
+name = 'Package Management Issues'
-- 
2.11.0

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


[yocto] [qa-tools][PATCH 2/4] scripts/full-test-cycle-wrapper: Add support for new 2.4 components

2017-07-04 Thread jose . perez . carranza
From: Jose Perez Carranza 

Add support for new packages supported for 2.4 release and update
components list according to release version.

Signed-off-by: Jose Perez Carranza 
---
 scripts/full-test-cycle-wrapper.sh | 26 --
 1 file changed, 24 insertions(+), 2 deletions(-)

diff --git a/scripts/full-test-cycle-wrapper.sh 
b/scripts/full-test-cycle-wrapper.sh
index 7dcd62e..6b62d7f 100755
--- a/scripts/full-test-cycle-wrapper.sh
+++ b/scripts/full-test-cycle-wrapper.sh
@@ -89,7 +89,7 @@ create_yocto(){
create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
 
#QEMUs Autos
-   ENVIRONMENTS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" "qemumips64" 
"qemuppc" "qemux86-64")
+   ENVIRONMENTS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" "qemumips64" 
"qemuppc" "qemux86-64", "qemux86-64-WIC", "qemux86-WIC")
EXECUTION_TYPE="AUTO"
create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
 
@@ -218,6 +218,14 @@ create_test_cycle(){
   OPTIONAL="UI"
   create_test_run "${1}" $OPTIONAL
   ;;
+"Package Management Issues")
+  ENVIRONMENTS=("Any Supported Distro")
+  EXECUTION_TYPE="MANUAL"
+  #This case test plan name is diferent from product name
+  TEST_PLAN="--test-plan Package-Management-Updates"
+  create_test_run "${1}"
+   
  ;;
+
   esac
 }
 
@@ -296,7 +304,21 @@ source venv/bin/activate
 
 ## Define components by t ype of test cycle
 if [[ $TYPE == "YOCTO" ]]; then
-COMPONENTS=("ADT" "BitBake" "BSP/QEMU" "CROPS" "Eclipse Plugin" "eSDK" 
"General Runtime" "Kernel" "Meta-yocto" "OE-Core" "Runtime" "Toaster")
+case $VERSION in
+   "2.1")   COMPONENTS=("ADT" "BitBake" "BSP/QEMU" "Eclipse Plugin" 
"General Runtime" "Meta-yocto" "OE-Core" "Runtime" "Toaster")
+;;
+   "2.2")   COMPONENTS=("ADT" "BitBake" "BSP/QEMU" "Eclipse Plugin" 
"eSDK" "General Runtime" "Meta-yocto" "OE-Core" "Runtime" "Toaster")
+;;
+   "2.3")   COMPONENTS=("ADT" "BitBake" "BSP/QEMU" "CROPS" "Eclipse 
Plugin" "eSDK" "General Runtime" "Kernel" "Meta-yocto" "OE-Core" "Runtime" 
"Toaster")
+;;
+   "2.4")   COMPONENTS=("ADT" "BitBake" "BSP/QEMU" "CROPS" "Eclipse 
Plugin" "eSDK" "General Runtime" "Kernel" "Meta-yocto" "OE-Core" "Runtime" 
"Toaster" "Package Management Issues")
+;;
+  \?)
+echo "ERROR: INAVLID RELEASE VERSION"
+exit 1
+;;
+esac
+
 else
 COMPONENTS=("BSP/QEMU")
 fi
-- 
2.11.0

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


[yocto] [qa-tools][PATCH 3/4] testopia_update: Add validation for empty sub parameters on setup

2017-07-04 Thread jose . perez . carranza
From: Jose Perez Carranza 

Add an error message for the cases when “setup” is selected and no sub
parameters are given.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/testopia_update.py b/testopia_update.py
index 0015d69..8080256 100755
--- a/testopia_update.py
+++ b/testopia_update.py
@@ -72,7 +72,6 @@ def connect_to_testopia():
 config = None
 opts = Options()
 
-#testopia_config = ['url', 'username', 'password', 'store_location']
 testopia_config = ['url', 'username', 'password']
 
 if not args.config and os.path.exists(DEFAULT_CONFIG_FILE):
@@ -270,6 +269,9 @@ if __name__ == '__main__':
 print(wikivars)
 create_wiki(wikivars, wikivars_list)
 
+else:
+logger.error("Sub arguments --clone-templates or --create-wiki 
should be given")
+
 sys.exit(0)
 
 
-- 
2.11.0

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


[yocto] [qa-tools][PATCH 4/4] utils/wikimaker: Add default values

2017-07-04 Thread jose . perez . carranza
From: Jose Perez Carranza 

Add default values for section of “performance” and “pTest” to avoid use
old data on new reports.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update/utils/wikimaker.py | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/testopia_update/utils/wikimaker.py 
b/testopia_update/utils/wikimaker.py
index 96fdfc0..b3cce60 100644
--- a/testopia_update/utils/wikimaker.py
+++ b/testopia_update/utils/wikimaker.py
@@ -99,18 +99,18 @@ def wiki_perf_tests(file_name):
 '.html GDC Charts]\n\nBelow chars are showing the latest' + \
 'performance results taken from the current milestone.\n\n' + \
 '== Performance Charts==\n\nFor Bitbake core-image-sato with' 
+ \
-'rm_work\n\n[[File:Ww19-2k17 - rmwork.png | 1280px | ' + \
+'rm_work\n\n[[File:Ww##-2k17 - rmwork.png | 1280px | ' + \
 'link=https://wiki.yoctoproject.org/charts/perf_milestone_' + \
 'GDC/bitbake-core-image-sato-rmwork.html ]]\n\nBuilding the ' 
+ \
-'Virtual kernel\n\n[[File:Ww19-2k17 - kernel.png | 1280px | ' 
+ \
+'Virtual kernel\n\n[[File:WwXX-2k17 - kernel.png | 1280px | ' 
+ \
 'link=https://wiki.yoctoproject.org/charts/perf_milestone_' + \
 'GDC/bitbake-virtual-kernel.html]]\n\nBuilding the rootfs\n' + 
\
-'\n[[File:Ww19-2k17_-_rootfs.png | 1280px | link=https://' + \
+'\n[[File:WwXX-2k17_-_rootfs.png | 1280px | link=https://' + \
 'wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-' + \
 'core-image-sato-rootfs.html]]\n\nBuilding core-image-sato' + \
-'\n\n[[File:Ww19-2k17_-_sato.png | 1280px | link=https://' + \
+'\n\n[[File:WwXX-2k17_-_sato.png | 1280px | link=https://' + \
 'wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-' + \
-'core-image-sato.html]]\n\neSDK Deploy time\n\n[[File:Ww19' + \
+'core-image-sato.html]]\n\neSDK Deploy time\n\n[[File:WwXX' + \
 '-2k17_-_esdk.png | 1280px | link=https://wiki.yoctoproject' + 
\
 '.org/charts/perf_milestone_GDC/bitbake-eSDK.html]]\n'
 
@@ -123,7 +123,7 @@ def wic_ptest_results(file_name):
 'milestone,status,resolution,cf_regression_type,created\n' + \
 '|noresultsmessage="None"\n|sort=status\n' + \
 '|group=product\n|id=\n}}\n\n== results ==\n\n' + \
-'{{:Ptest 381897c64069ea43d595380a3ae913bcc79cf7e1}}\n'
+'{{:Ptest }}\n'
 
 with open(file_name, 'a') as f:
 f.write(perf_data)
-- 
2.11.0

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


Re: [yocto] [qa-tools][PATCH 1/4] poduct/init: Add support for PackageManagement component

2017-07-04 Thread Robert P. J. Day

  "poduct/init" ?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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


[yocto] Kernel image and dts

2017-07-04 Thread Riko Ho

Hello Yocto Team Member,

I have a question related with *.dtbo,

Can I use *.dtbo for beaglebone directly with linux yocto kernel, 
without using ti mainline kernel ?


I want to use SPI port.

One example I can read : arch/arm/boot/dts/sun7i-a20-pcduino3.dts, where 
can I find those source files on yocto ? ==> build/tmp/ .??


Thanks


--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


Re: [yocto] Update SRCREV doesn't work?

2017-07-04 Thread Ngọc Thi Huỳnh
Hi,

I guess I'll remove build/tmp directory and rebuild everything from scratch.
I'll post the result later then.

BTW, thank you so much for writing swupdate.

Best Regards,
Thi Huynh

Huỳnh Ngọc Thi
-so61pi

On Wed, Jul 5, 2017 at 12:08 AM, Stefano Babic  wrote:

> Hi,
>
> On 04/07/2017 18:13, Ngọc Thi Huỳnh wrote:
> > Hi everyone,
> >
> > I'm using poky pyro to build a beaglebone image with swupdate.
> >
> > First time I built swupdate (by bitbake swupdate), it used the latest
> > git version and I encountered an make error which related to swupdate
> only.
> >
> > Then I changed swupdate version to 2017.04 (by using
> > PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
> > latest git version and I had the make error again.
> >
>
> I cannot confirm this. I have built a custom board and setting
> PREFERRED_VERSION_swupdate works without issues.
>
> > But when I used devshell and changed the git revision to 2017.04 then
> > do_configure and do_compile, everything went fine.
> >
> > My question is, is there a simple way to solve this problem?
> >
> > /Note:/
> > The swupdate recipes for beaglebone that I'm using are from
> > https://github.com/sbabic/meta-swupdate
> >
> > Content of swupdate_2017.04.bb :
> >
> > require swupdate.inc
> >
> > SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
> >
> >
> > Content of swupdate_git.bb 
> >
> > require swupdate.inc
> >
> > DEFAULT_PREFERENCE = "-1"
> >
> >
> > A snippet of swupdate.inc
> >
> > SRCREV = "${AUTOREV}"
> >
> >
>
> Best regards,
> Stefano Babic
>
>
> --
> =
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
> =
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho

When I upgrade poky, will it delete all the configuration I had done?


On 04/07/17 17:51, Takuro Ashie wrote:


On 2017年07月04日 17:06, Riko Ho wrote:


Still in error :

| 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/firefox-52.1.2esr/firefox-build-dir/dist/system_wrappers/pk11pub.h:3:26: 
fatal error: pk11pub.h: No such file or directory

|  #include_next 
|   ^
| compilation terminated.



I confirmed it.
Hmm, there are some issues which prevent using built-in nss & nspr.
I can't resolve it soon.

It seems that upgrading poky is a easier way to build firefox if it's 
acceptable for you.




--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


[yocto] /boot/dtbs/4.4.54-ti-r93/am335x-boneblack.dtb

2017-07-04 Thread Riko Ho

Dear Yocto Team Member,

Is it possible that I use this dtb with beagle yocto kernel ? if it is, 
how to do that ?


loading */boot/dtbs/4.4.54-ti-r93/am335x-boneblack.dtb *

--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


[yocto] SPI0 dev loop back = 000 ? why ?

2017-07-04 Thread Riko Ho

Hello Yocto Team Member,

I tried to compile spidev_test  on loopback ,but got , why is it ?? 
I checked all the cable and /dev/spidev1.0, they're all there ??


spi mode: 0
bits per word: 8
max speed: 240 Hz (2400 KHz)

00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00 00 00 00 00
00 00

--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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


Re: [yocto] [meta-selinux][PATCH] initscripts: use the 'i' option for restorecon command

2017-07-04 Thread Zhixiong Chi

Ping...

On 2017年06月22日 10:17, Zhixiong Chi wrote:

Use the 'i' option for restorecon command to ignore the files that
don't exist when building project.

Signed-off-by: Zhixiong Chi 
---
  recipes-core/initscripts/initscripts_1.0.bbappend | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-core/initscripts/initscripts_1.0.bbappend 
b/recipes-core/initscripts/initscripts_1.0.bbappend
index f17cf07..0fc7a5e 100644
--- a/recipes-core/initscripts/initscripts_1.0.bbappend
+++ b/recipes-core/initscripts/initscripts_1.0.bbappend
@@ -5,9 +5,9 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
  do_install_append () {
cat <<-EOF >> ${D}${sysconfdir}/init.d/populate-volatile.sh
  touch /var/log/lastlog
-test ! -x /sbin/restorecon || /sbin/restorecon -RF /var/volatile/ /var/lib 
/run \
+test ! -x /sbin/restorecon || /sbin/restorecon -iRF /var/volatile/ /var/lib 
/run \
  /etc/resolv.conf /etc/adjtime
  EOF
-   sed -i '/mount -n -o remount,$rootmode/i\test ! -x /sbin/restorecon || 
/sbin/restorecon -RF /run' \
+   sed -i '/mount -n -o remount,$rootmode/i\test ! -x /sbin/restorecon || 
/sbin/restorecon -iRF /run' \
${D}${sysconfdir}/init.d/checkroot.sh
  }


--
-
Thanks,
Zhixiong Chi
Tel: +86-10-8477-7036

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


Re: [yocto] Update SRCREV doesn't work?

2017-07-04 Thread Stefano Babic
Hi Huynh,

On 05/07/2017 04:09, Ngọc Thi Huỳnh wrote:
> Hi,
> 
> I guess I'll remove build/tmp directory and rebuild everything from scratch.
> I'll post the result later then.
>

The recipe for beaglebone was dropped from meta-swupdate. I moved the
examples for bbb and raspi into a separate layer (meta-swupdate-boards,
-master).

> BTW, thank you so much for writing swupdate.

You're welcome.

> 
Best regards,
Stefano Babic

> Best Regards,
> Thi Huynh
> 
> Huỳnh Ngọc Thi
> -so61pi
> 
> On Wed, Jul 5, 2017 at 12:08 AM, Stefano Babic  > wrote:
> 
> Hi,
> 
> On 04/07/2017 18:13, Ngọc Thi Huỳnh wrote:
> > Hi everyone,
> >
> > I'm using poky pyro to build a beaglebone image with swupdate.
> >
> > First time I built swupdate (by bitbake swupdate), it used the latest
> > git version and I encountered an make error which related to swupdate 
> only.
> >
> > Then I changed swupdate version to 2017.04 (by using
> > PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
> > latest git version and I had the make error again.
> >
> 
> I cannot confirm this. I have built a custom board and setting
> PREFERRED_VERSION_swupdate works without issues.
> 
> > But when I used devshell and changed the git revision to 2017.04 then
> > do_configure and do_compile, everything went fine.
> >
> > My question is, is there a simple way to solve this problem?
> >
> > /Note:/
> > The swupdate recipes for beaglebone that I'm using are from
> > https://github.com/sbabic/meta-swupdate
> 
> >
> > Content of swupdate_2017.04.bb 
> :
> >
> > require swupdate.inc
> >
> > SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
> >
> >
> > Content of swupdate_git.bb 
> 
> >
> > require swupdate.inc
> >
> > DEFAULT_PREFERENCE = "-1"
> >
> >
> > A snippet of swupdate.inc
> >
> > SRCREV = "${AUTOREV}"
> >
> >
> 
> Best regards,
> Stefano Babic
> 
> 
> --
> =
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email:
> sba...@denx.de 
> =
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto