[yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Hi,

Yocto 2.1:

I had working setup, and wanted to rebuild.
I am quite sure that I did not change anything, and suddenly it does not work 
any more:

Fetcher failure for URL: 'https://www.example.com/'. URL 
https://www.example.com/ doesn't work. Please ensure your network is configured 
correctly.

If I
  wget https://www.example.com/
it works

What could it be?


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


[yocto] Adding mysql in bitbaking meta-toolchain-qt5

2016-09-14 Thread ambika
 

Hello, 

I'm doing bitbake of meta-toolchain-qt5. When trying to use mysql, not
able to find it in include/ directory. 

mysql sources is located in the below path in my yocto setup, 

sources/meta-openembedded/meta-oe/recipes-support/mysql 

Tried to include mysql by adding the below to conf/local.conf under
build directory but could not able to locate mysql under include/. 
(Also not sure whether I'm doing it right.) 

IMAGE_INSTALL_append = "mysql" 

Can anyone please let me know the procedure to include mysql to the
meta-toolchain-qt5. 

Thanks in Advance. 

Regards, 
Ambika. 

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


[yocto] Adding mysql in bitbaking meta-toolchain-qt5

2016-09-14 Thread Ambika
Hello,

I’m doing bitbake of meta-toolchain-qt5. When trying to use mysql, not able to 
find it in include/ directory. 

mysql sources is located in the below path in my yocto setup,

sources/meta-openembedded/meta-oe/recipes-support/mysql 

Tried to include mysql by adding the below to conf/local.conf under build 
directory but could not able to locate mysql under include/.
(Also not sure whether I’m doing it right.)

IMAGE_INSTALL_append = ”mysql” 

Can anyone please let me know the procedure to include mysql to the 
meta-toolchain-qt5.

Thanks in Advance.

Regards,
Ambika.


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


[yocto] [meta-raspberrypi] Schizophrenic build

2016-09-14 Thread Gary Thomas

I just built for my shiny new RaspberryPi-3 and noticed this:
  $ ls -l tmp/work
  total 32
  drwxrwxr-x  13 gthomas gthomas  4096 Sep 13 05:40 all-amltd-linux
  drwxrwxr-x   3 gthomas gthomas  4096 Sep 13 05:36 all-amltd-linux-gnueabi
  drwxrwxr-x 271 gthomas gthomas 12288 Sep 13 09:20 
cortexa7hf-neon-vfpv4-amltd-linux-gnueabi
  drwxrwxr-x   3 gthomas gthomas  4096 Sep 13 05:31 
cortexa7t2hf-neon-vfpv4-amltd-linux-gnueabi
  drwxrwxr-x  20 gthomas gthomas  4096 Sep 13 18:42 
raspberrypi3-amltd-linux-gnueabi
  drwxrwxr-x 145 gthomas gthomas  4096 Sep 13 07:05 x86_64-linux

Interestingly, the cortexa7t2hf-neon-vfpv4-amltd-linux-gnueabi tree [currently]
only contains webkitgtk (which currently isn't building, under investigation).

Any idea why this split?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Burton, Ross
On 14 September 2016 at 08:52, Anicic Damir (PSI) 
wrote:

> Fetcher failure for URL: 'https://www.example.com/'. URL
> https://www.example.com/ doesn't work. Please ensure your network is
> configured correctly.
>

This is the "is networking correctly configured" test, and if it fails in
Yocto but works from a terminal then this suggests that you need to
configure your proxies in local.conf.

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
No, I have direct internet connection, no proxy needed (and was not needed 
before).

Temporarily I use
  CONNECTIVITY_CHECK_URIS=""
in local.conf

That way it works again,
but I would like to have better solution.


After investigating little bit more, I see an error:
   Fetcher failure for URL: 'https://www.example.com/'. URL 
https://www.example.com/ doesn't work. Please ensure your network is configured 
correctly.

which comes from
bitbake/lib/bb/fetch2/wget.py line 282
275:try:
276:uri = ud.url.split(";")[0]
277:r = urllib2.Request(uri)
278:r.get_method = lambda: "HEAD"
279:opener.open(r)
280:except urllib2.URLError as e:
281:# debug for now to avoid spamming the logs in e.g. remote 
sstate searches
282:logger.debug(2, "checkstatus() urlopen failed: %s" % e)
283:return False
284:return True


All I know is that python did not change,
but there were some additional packages installed,
and may be some other packages/libraries changed on my system
in scope of regular auto-updates.
Unfortunately I do not see which of the newly installed packages have anything 
to do with python.

Any help?


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


Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Sorry, the error message is:

   DEBUG: checkstatus() urlopen failed: 

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Daniel.
Can you connect to "www.example.com" from command line?! Something
like `telnet www.example.com 80' !?!?

2016-09-14 9:27 GMT-03:00 Anicic Damir (PSI) :
> Sorry, the error message is:
>
>DEBUG: checkstatus() urlopen failed:  Connection reset by peer>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
This works:
wget http://www.exampe.com/
--2016-09-14 14:42:23--  http://www.exampe.com/
Resolving www.exampe.com... 69.172.201.153
Connecting to www.exampe.com|69.172.201.153|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “index.html.1”

[ <=>   
 ] 1,558   --.-K/s   in 0s  

2016-09-14 14:42:23 (20.8 MB/s) - “index.html.1” saved [1558]



But this does not:
wget https://www.exampe.com/
--2016-09-14 14:42:39--  https://www.exampe.com/
Resolving www.exampe.com... 69.172.201.153
Connecting to www.exampe.com|69.172.201.153|:443... connected.
Unable to establish SSL connection.

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Burton, Ross
On 14 September 2016 at 13:42, Anicic Damir (PSI) 
wrote:

> wget https://www.exampe.com/
> --2016-09-14 14:42:39--  https://www.exampe.com/
> Resolving www.exampe.com... 69.172.201.153
> Connecting to www.exampe.com|69.172.201.153|:443... connected.
> Unable to establish SSL connection.
>

"example" not exampe.

$ wget https://www.example.com
--2016-09-14 13:46:51--  https://www.example.com/
Resolving www.example.com... 93.184.216.34,
2606:2800:220:1:248:1893:25c8:1946
Connecting to www.example.com|93.184.216.34|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1270 (1.2K) [text/html]
Saving to: ‘index.html’

index.html  100%[===>]   1.24K  --.-KB/sin 0s

2016-09-14 13:46:52 (18.9 MB/s) - ‘index.html’ saved [1270/1270]

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Ups, typo.

It also works


wget https://www.example.com/
--2016-09-14 14:58:03--  https://www.example.com/
Resolving www.example.com... 93.184.216.34, 2606:2800:220:1:248:1893:25c8:1946
Connecting to www.example.com|93.184.216.34|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1270 (1.2K) [text/html]
Saving to: “index.html.1”

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Daniel.
try:
python -c 'import urllib; print urllib.urlopen("http://www.example.com";).read()'


I'm running out of ideias :). I already had received "Connection reset
by peer" because dupplicate IPs on network.

Regards,

2016-09-14 9:58 GMT-03:00 Anicic Damir (PSI) :
> Ups, typo.
>
> It also works
>
>
> wget https://www.example.com/
> --2016-09-14 14:58:03--  https://www.example.com/
> Resolving www.example.com... 93.184.216.34,
> 2606:2800:220:1:248:1893:25c8:1946
> Connecting to www.example.com|93.184.216.34|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1270 (1.2K) [text/html]
> Saving to: “index.html.1”
>



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Adding mysql in bitbaking meta-toolchain-qt5

2016-09-14 Thread Zhenhua Luo
The package name is mariadb instead of mysql, If you need the mysql headers, 
you should add libmysqlclient-dev.

More details of mariadb packaging can be found in 
meta-openembedded/meta-oe/recipes-support/mysql/mariadb.inc.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ambika
Sent: Wednesday, September 14, 2016 3:29 PM
To: yocto@yoctoproject.org
Subject: [yocto] Adding mysql in bitbaking meta-toolchain-qt5

Hello,

I’m doing bitbake of meta-toolchain-qt5. When trying to use mysql, not able to 
find it in include/ directory.

mysql sources is located in the below path in my yocto setup,

sources/meta-openembedded/meta-oe/recipes-support/mysql

Tried to include mysql by adding the below to conf/local.conf under build 
directory but could not able to locate mysql under include/.
(Also not sure whether I’m doing it right.)

IMAGE_INSTALL_append = ”mysql”

Can anyone please let me know the procedure to include mysql to the 
meta-toolchain-qt5.

Thanks in Advance.

Regards,
Ambika.



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


[yocto] [meta-oic][PATCH 1/3] iotivity-simple-client: Use regular LDFLAGS variable

2016-09-14 Thread Philippe Coval
This has been tested with iotivity-1.1.1
 but also applies to earlier versions.

Without this, QA check is failing and this message is reported:

  do_package_qa: QA Issue: No GNU_HASH in the elf binary:
  (...)
  iotivity-simple-client/simpleclient' [ldflags]

Change-Id: Ib77c70331b1aaba193bc32bcd190f939d9456dc4
Bug: https://jira.iotivity.org/browse/IOT-
Cc: iotivity-...@lists.iotivity.org
Cc: yocto@yoctoproject.org
Origin: https://github.com/tizenteam/meta-oic
Signed-off-by: Philippe Coval 
---
 .../0001-build-Use-LDFLAGS-variable-from-env.patch | 35 ++
 .../iotivity-simple-client_1.1.0.bb|  3 +-
 2 files changed, 37 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-apps/iotivity-simple-client/files/0001-build-Use-LDFLAGS-variable-from-env.patch

diff --git 
a/recipes-apps/iotivity-simple-client/files/0001-build-Use-LDFLAGS-variable-from-env.patch
 
b/recipes-apps/iotivity-simple-client/files/0001-build-Use-LDFLAGS-variable-from-env.patch
new file mode 100644
index 000..e121ddd
--- /dev/null
+++ 
b/recipes-apps/iotivity-simple-client/files/0001-build-Use-LDFLAGS-variable-from-env.patch
@@ -0,0 +1,35 @@
+From c513e8e44345d7fff2a38ef5ddb108d513a40ae7 Mon Sep 17 00:00:00 2001
+From: Philippe Coval 
+Date: Tue, 13 Sep 2016 17:14:03 +0200
+Subject: [PATCH] build: Use LDFLAGS variable from env
+
+Without this, QA check is failing and this message is reported:
+
+  do_package_qa: QA Issue: No GNU_HASH in the elf binary:
+  (...)
+  'iotivity-simple-client/simpleclient' [ldflags]
+
+Change-Id: Id22e5358f75b46861cf0dfb7b2af267dbe7d7014
+Bug: https://jira.iotivity.org/browse/IOT-
+Origin: https://github.com/TizenTeam/meta-oic
+Signed-off-by: Philippe Coval 
+---
+ Makefile | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Makefile b/Makefile
+index 9323169..2389f43 100644
+--- a/Makefile
 b/Makefile
+@@ -12,7 +12,7 @@ endif
+   $(CXX) -std=c++0x -c -o $@ $< $(YOCTOCXXFLAGS)
+ 
+ simpleclient: simpleclient.o
+-  $(CXX) -o simpleclient simpleclient.o $(YOCTOLDFLAGS)
++  $(CXX) -o $@ $^ $(LDFLAGS) $(YOCTOLDFLAGS)
+ 
+ clean:
+   rm -rf simpleclient *.o
+-- 
+1.9.1
+
diff --git 
a/recipes-apps/iotivity-simple-client/iotivity-simple-client_1.1.0.bb 
b/recipes-apps/iotivity-simple-client/iotivity-simple-client_1.1.0.bb
index a01f58e..caf02f8 100644
--- a/recipes-apps/iotivity-simple-client/iotivity-simple-client_1.1.0.bb
+++ b/recipes-apps/iotivity-simple-client/iotivity-simple-client_1.1.0.bb
@@ -7,7 +7,8 @@ LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = 
"file://simpleclient.cpp;beginline=1;endline=19;md5=fc5a615cf1dc3880967127bc853b3e0c"
 
 SRC_URI = "file://iotivity-simple-client.tar.bz2 \
-  "
+file://0001-build-Use-LDFLAGS-variable-from-env.patch \
+"
 
 S = "${WORKDIR}/iotivity-simple-client"
 
-- 
1.9.1

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


[yocto] [meta-oic][PATCH 2/3] iotivity-sensorboard: Use regular LDFLAGS variable and pthread

2016-09-14 Thread Philippe Coval
Without this change and error on linkage is displayed :

  ld: observer.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5'
  libpthread.so.0: error adding symbols: DSO missing from command line
  collect2: error: ld returned 1 exit status

Also YOCTOLDFLAGS are replaced with regular LDFLAGS,
 to use quality check.

Without this, QA check is failing and this message is reported:

  do_package_qa: QA Issue: No GNU_HASH in the elf binary:

Change-Id: I80e4ab17128b8539a45843611e4aec3650e2ddef
Bug: https://jira.iotivity.org/browse/IOT-
Cc: iotivity-...@lists.iotivity.org
Cc: yocto@yoctoproject.org
Origin: https://github.com/tizenteam/meta-oic
Signed-off-by: Philippe Coval 
---
 ...DFLAGS-variable-from-env-and-add-pthread-.patch | 50 ++
 .../iotivity-sensorboard_1.0.0.bb  |  1 +
 2 files changed, 51 insertions(+)
 create mode 100644 
recipes-apps/iotivity-sensorboard/files/0001-Build-Use-LDFLAGS-variable-from-env-and-add-pthread-.patch

diff --git 
a/recipes-apps/iotivity-sensorboard/files/0001-Build-Use-LDFLAGS-variable-from-env-and-add-pthread-.patch
 
b/recipes-apps/iotivity-sensorboard/files/0001-Build-Use-LDFLAGS-variable-from-env-and-add-pthread-.patch
new file mode 100644
index 000..cb3b16d
--- /dev/null
+++ 
b/recipes-apps/iotivity-sensorboard/files/0001-Build-Use-LDFLAGS-variable-from-env-and-add-pthread-.patch
@@ -0,0 +1,50 @@
+From c6fc833f4ce28c2a811fa1077f5e0975eadc4a23 Mon Sep 17 00:00:00 2001
+From: Philippe Coval 
+Date: Tue, 13 Sep 2016 18:14:07 +0200
+Subject: [PATCH] Build: Use LDFLAGS variable from env and add -pthread flag
+
+Without this change and error on linkage is displayed :
+
+  ld: observer.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5'
+  libpthread.so.0: error adding symbols: DSO missing from command line
+  collect2: error: ld returned 1 exit status
+
+Also YOCTOLDFLAGS are replaced with regular LDFLAGS,
+to use quality check.
+
+Without this, QA check is failing and this message is reported:
+
+  do_package_qa: QA Issue: No GNU_HASH in the elf binary:
+
+Change-Id: I2f73b1c09908be38a9053943a894832519312751
+Bug: https://jira.iotivity.org/browse/IOT-
+Origin: https://github.com/TizenTeam/meta-oic
+Signed-off-by: Philippe Coval 
+---
+ Makefile | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/Makefile b/Makefile
+index e78b777..5d09cc1 100644
+--- a/Makefile
 b/Makefile
+@@ -1,6 +1,7 @@
+ YOCTOCXXFLAGS=-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/ 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/stack 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/ocrandom 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/logger 
-I$(PKG_CONFIG_SYSROOT_DIR)/usr/include/iotivity/resource/oc_logger
+ 
+ YOCTOLDFLAGS=-loc -loctbstack -loc_logger -lmraa
++YOCTOLDFLAGS+=-pthread
+ 
+ all: sensorboard
+ 
+@@ -12,7 +13,7 @@ endif
+   $(CXX) -std=c++0x -c -o $@ $< $(YOCTOCXXFLAGS)
+ 
+ sensorboard: server.o observer.o
+-  $(CXX) -o sensorboard server.o observer.o $(YOCTOLDFLAGS)
++  $(CXX) -o $@ $^ $(LDFLAGS) $(YOCTOLDFLAGS)
+ 
+ clean:
+   rm -rf sensorboard *.o
+-- 
+1.9.1
+
diff --git a/recipes-apps/iotivity-sensorboard/iotivity-sensorboard_1.0.0.bb 
b/recipes-apps/iotivity-sensorboard/iotivity-sensorboard_1.0.0.bb
index 71518bd..828c81e 100644
--- a/recipes-apps/iotivity-sensorboard/iotivity-sensorboard_1.0.0.bb
+++ b/recipes-apps/iotivity-sensorboard/iotivity-sensorboard_1.0.0.bb
@@ -7,6 +7,7 @@ LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = 
"file://server.cpp;beginline=1;endline=19;md5=a692dd0c72bcfa341a4ba826b37caf15"
 
 SRC_URI = "file://iotivity-sensorboard.tar.gz \
+file://0001-Build-Use-LDFLAGS-variable-from-env-and-add-pthread-.patch 
\
   "
 
 S = "${WORKDIR}/iotivity-sensorboard"
-- 
1.9.1

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


[yocto] [meta-oic][PATCH 3/3] Update for IoTivity 1.1.1

2016-09-14 Thread Philippe Coval
* Inspired from Kishen Maloor's iotivity_1.1.0.bb.
* Note this version of recipe
  is using upstream's git repo as source
  because it's better for upstream/downstream cooperation
  More details at:
  https://wiki.iotivity.org/yocto
* Update to upstream "1.1-rel" maintenance branch
  - QA checks are fixed
to support Yocto jethro base and later,
without it packaging task will fail and report this message :
ERROR: QA Issue: No GNU_HASH in the elf binary
* Tinycobor is updated to v0.2.1.
* Gtest is now statically linked.
* Security is still not enabled,
  but can be easly enabled with "SECURED=1" scons's flag.

Change-Id: Ib6f69c24434615d178ccef15cad96142e2b837aa
Bug: https://jira.iotivity.org/browse/IOT-
Cc: iotivity-...@lists.iotivity.org
Cc: yocto@yoctoproject.org
Credit-to: Kishen Maloor 
Origin: https://github.com/tizenteam/meta-oic
Signed-off-by: Philippe Coval 
---
As promised, I commited the needed fixes upstream.
I tested this patchset on poky master branch.
along generic, intel and artik BSPs.

More details to come at:
https://wiki.iotivity.org/yocto

ChangeLog:

* v1: use INSANE_SKIP to workaround QA check
  https://lists.yoctoproject.org/pipermail/yocto/2016-August/031441.html
  https://lists.yoctoproject.org/pipermail/yocto/2016-August/031471.html
* v2: rebase on upstream 1.1-rel maintenance branch (with fixes)
  needs also QA fixes on examples (but can be commited in any order)
  security can be enabled
  couple of improvements


 recipes-core/iotivity/iotivity_1.1.1.bb | 503 
 1 file changed, 503 insertions(+)
 create mode 100644 recipes-core/iotivity/iotivity_1.1.1.bb

diff --git a/recipes-core/iotivity/iotivity_1.1.1.bb 
b/recipes-core/iotivity/iotivity_1.1.1.bb
new file mode 100644
index 000..792411b
--- /dev/null
+++ b/recipes-core/iotivity/iotivity_1.1.1.bb
@@ -0,0 +1,503 @@
+PR = "r1"
+SUMMARY = "IoTivity framework and SDK sponsored by the Open Connectivity 
Foundation."
+DESCRIPTION = "IoTivity is an open source software framework enabling seamless 
device-to-device connectivity to address the emerging needs of the Internet of 
Things."
+HOMEPAGE = "https://www.iotivity.org/";
+DEPENDS = "boost virtual/gettext chrpath-replacement-native expat openssl 
util-linux curl glib-2.0"
+EXTRANATIVEPATH += "chrpath-native"
+SECTION = "libs"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = 
"file://resource/include/OCApi.h;beginline=1;endline=19;md5=fc5a615cf1dc3880967127bc853b3e0c"
+
+url_iotivity = "git://github.com/iotivity/iotivity.git"
+branch_iotivity = "1.1-rel"
+SRCREV = "972ef41a25624501d7cd13a18a9f49be90b9c2d1"
+SRC_URI = 
"${url_iotivity};destsuffix=${S};branch=${branch_iotivity};protocol=http;"
+
+url_tinycbor = "git://github.com/01org/tinycbor.git"
+SRCREV_tinycbor = "358a7e42ab1ed421a68e699d8d8359340bcfacbd"
+SRC_URI += 
"${url_tinycbor};name=tinycbor;destsuffix=${S}/extlibs/tinycbor/tinycbor;protocol=http"
+
+url_gtest = 
"http://pkgs.fedoraproject.org/repo/pkgs/gtest/gtest-1.7.0.zip/2d6ec8ccdf5c46b05ba54a9fd1d130d7/gtest-1.7.0.zip";
+SRC_URI[gtest.md5sum] = "2d6ec8ccdf5c46b05ba54a9fd1d130d7"
+SRC_URI[gtest.sha256sum] = 
"247ca18dd83f53deb1328be17e4b1be31514cedfc1e3424f672bf11fd7e0d60d"
+SRC_URI += "${url_gtest};name=gtest;subdir=${BP}/extlibs/gtest"
+
+url_hippomocks = "git://github.com/dascandy/hippomocks.git"
+SRCREV_hippomocks = "dca4725496abb0e41f8b582dec21d124f830a8e5"
+SRC_URI += 
"${url_hippomocks};name=hippomocks;destsuffix=${S}/extlibs/hippomocks-master;protocol=http"
+
+url_sqlite = "http://www.sqlite.org/2015/sqlite-amalgamation-3081101.zip";
+SRC_URI[sqlite3.md5sum] = "94907e831502e2080b76e281cfa24dde"
+SRC_URI[sqlite3.sha256sum] = 
"a3b0c07d1398d60ae9d21c2cc7f9be6b1bc5b0168cd94c321ede9a0fce2b3cd7"
+SRC_URI += 
"${url_sqlite};name=sqlite3;subdir=${BP}/extlibs/sqlite3;unpack=false"
+
+inherit scons
+
+
+python () {
+IOTIVITY_TARGET_ARCH = d.getVar("TARGET_ARCH", True)
+d.setVar("IOTIVITY_TARGET_ARCH", IOTIVITY_TARGET_ARCH)
+EXTRA_OESCONS = d.getVar("EXTRA_OESCONS", True)
+EXTRA_OESCONS += " TARGET_OS=yocto TARGET_ARCH=" + IOTIVITY_TARGET_ARCH + 
" RELEASE=1"
+EXTRA_OESCONS += " ROUTING=GW"
+EXTRA_OESCONS += " VERBOSE=1"
+# Enable security here or elsewhere but should be in this "=1" form:
+# EXTRA_OESCONS += " SECURED=1"
+EXTRA_OESCONS += " WITH_RD=1"
+d.setVar("EXTRA_OESCONS", EXTRA_OESCONS)
+}
+
+
+IOTIVITY_BIN_DIR = "/opt/${PN}"
+IOTIVITY_BIN_DIR_D = "${D}${IOTIVITY_BIN_DIR}"
+
+do_compile_prepend() {
+export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}"
+export PKG_CONFIG="PKG_CONFIG_SYSROOT_DIR=\"${PKG_CONFIG_SYSROOT_DIR}\" 
pkg-config"
+export LD_FLAGS="${LD_FLAGS}"
+}
+
+make_dir() {
+install -d $1
+}
+
+copy_file() {
+install -c -m 444 $1 $2
+}
+
+copy_exec() {
+install -c -m 555 $1 $2
+}
+
+copy_file_recursive() {
+cd $1 && find . -type d -exec install -d $2/"{}" \;
+cd $1 && find . -type f -exec install -c -m 444 "{}" $2/"{}" \;
+}
+
+copy_exec_recursive

Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Thanx all for a help,

I have tested with:

   python -c 'import urllib2; print urllib2.urlopen.

The problem was only with https protocol, http worked.
The certificate was not accepted (SSL, as used by bitbake wget.py),
but with TLS it worked.

it turns out that something HAS changed in my system/libraries (but not Python 
itself),
influencing python urllib2 to fail, although wget, chrome, firefox, ... worked

Fortunately we have another python version installed, and with that one it 
works again.

Thanx again for your help


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


Re: [yocto] Fetcher failure

2016-09-14 Thread Burton, Ross
On 14 September 2016 at 15:48, Anicic Damir (PSI) 
wrote:

> it turns out that something HAS changed in my system/libraries (but not
> Python itself),
> influencing python urllib2 to fail, although wget, chrome, firefox, ...
> worked
>
> Fortunately we have another python version installed, and with that one it
> works again.
>

I wouldn't be surprised if you just got the Python 2.7 security fix which
means it verifies certificates by default, and your distro doesn't have
working certificates for Python.

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


Re: [yocto] Fetcher failure

2016-09-14 Thread Daniel.
You're welcome :)

2016-09-14 11:50 GMT-03:00 Burton, Ross :
>
> On 14 September 2016 at 15:48, Anicic Damir (PSI) 
> wrote:
>>
>> it turns out that something HAS changed in my system/libraries (but not
>> Python itself),
>> influencing python urllib2 to fail, although wget, chrome, firefox, ...
>> worked
>>
>> Fortunately we have another python version installed, and with that one it
>> works again.
>
>
> I wouldn't be surprised if you just got the Python 2.7 security fix which
> means it verifies certificates by default, and your distro doesn't have
> working certificates for Python.
>
> Ross



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Adding ntfs3g to image and mouting ntfs partitions!?

2016-09-14 Thread Daniel.
Hi,

I'm trying to compile ntfs-3g but I get "nothing provides ntfs-3g"
error, the weird part is that I have that recipe:

Some commands and its outputs:

[geckos@csi24 build_x11]$ find ../sources/ -name
"ntfs*.bb*"../sources/meta-openembedded/meta-filesystems/recipes-filesystems/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb


[geckos@csi24 build_x11]$ cat
../sources/meta-openembedded/meta-filesystems/recipes-filesystems/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb
DESCRIPTION = "The NTFS-3G driver is an open source, freely available
NTFS driver for Linux with read and write support."
HOMEPAGE = "http://www.ntfs-3g.org/";
DEPENDS = "fuse libgcrypt"
PROVIDES = "ntfsprogs ntfs-3g"
LICENSE = "GPLv2 & LGPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
file://COPYING.LIB;md5=f30a9716ef3762e3467a2f62bf790f0a"

SRC_URI = "http://tuxera.com/opensource/ntfs-3g_ntfsprogs-${PV}.tgz";
S = "${WORKDIR}/ntfs-3g_ntfsprogs-${PV}"

SRC_URI[md5sum] = "2d6fb47ddf62b51733227126fe9227fe"
SRC_URI[sha256sum] =
"4b383f0074a3ab7683339d1f18222b107aaeb4983db119292c43c2b275cefb27"

inherit autotools

PACKAGECONFIG ??= ""
PACKAGECONFIG[uuid] = "--with-uuid,--without-uuid,util-linux"

# required or it calls ldconfig at install step
EXTRA_OEMAKE = "LDCONFIG=echo"

PACKAGES =+ "ntfs-3g ntfsprogs libntfs-3g"

FILES_ntfs-3g = "${base_sbindir}/*.ntfs-3g ${bindir}/ntfs-3g*
${base_sbindir}/mount.ntfs"
RDEPENDS_ntfs-3g += "fuse"
RRECOMMENDS_ntfs-3g = "util-linux-mount"

FILES_ntfsprogs = "${base_sbindir}/* ${bindir}/* ${sbindir}/*"
FILES_libntfs-3g = "${libdir}/*${SOLIBS}"

do_install_append() {
# Standard mount will execute the program /sbin/mount.TYPE
# when called. Add the symbolic to let mount could find ntfs.
ln -sf mount.ntfs-3g ${D}/${base_sbindir}/mount.ntfs
}

# Satisfy the -dev runtime dependency
ALLOW_EMPTY_${PN} = "1"
[geckos@csi24 build_x11]$



[geckos@csi24 build_x11]$ bitbake ntfs-3g
WARNING: Host distribution "Arch-Linux" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Loading cache: 100%
|#|
ETA:  00:00:00
Loaded 2228 entries from dependency cache.
ERROR: Nothing PROVIDES 'ntfs-3g'

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
[geckos@csi24 build_x11]$
[geckos@csi24 build_x11]$
[geckos@csi24 build_x11]$ bitbake ntfsprogs
WARNING: Host distribution "Arch-Linux" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Loading cache: 100%
|#|
ETA:  00:00:00
Loaded 2228 entries from dependency cache.
ERROR: Nothing PROVIDES 'ntfsprogs'. Close matches:
  e2fsprogs

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
[geckos@csi24 build_x11]$
[geckos@csi24 build_x11]$
[geckos@csi24 build_x11]$ bitbake ntfs-3g-ntfsprogs
WARNING: Host distribution "Arch-Linux" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Loading cache: 100%
|#|
ETA:  00:00:00
Loaded 2228 entries from dependency cache.
ERROR: Nothing PROVIDES 'ntfs-3g-ntfsprogs'

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
[geckos@csi24 build_x11]$


Thanks in advance
Best regards,

-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-oic][PATCH 3/3] Update for IoTivity 1.1.1

2016-09-14 Thread Phil Coval

On 14/09/16 23:55, Maloor, Kishen wrote:

Hi Philippe,

Thanks for your contributions. I reviewed your patches and also
ran a quick test build, and it all seemed to work OK. I’ve pushed
the patches up to meta-oic. Here are links to the commits:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-oic/


Hi Kishen,

I'll try to share more once 1.2.0 released,
need to figure out some changes since 1.1.1

Security wasn't enabled on 1.1.x,
do you think we should set in on 1.2 ?


I see that you’re maintaining a meta-oic mirror on github
for Tizen (?).


This is just a sandbox for "work in progress" purpose
for Tizen Yocto and others...


I’d encourage you to base your work off the upstream
repo on yoctoproject.org.

that's the plan, only upstream matters :-)
but this very convenient to use "sandbox" repos.

Thanks again for your promptness.

--
mailto:philippe.co...@osg.samsung.com gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/

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