[oe] [meta-java][PATCH] classpath: fix invalid options

2015-12-31 Thread jackie.huang 
From: Jackie Huang 

After updated to version 0.99, the following options
became invalid:

* --with-ecj: use JAVAC env variable instead
* --with-fastjar: change to --with-jar
* --with-vm: uae JAVA env variable instead
* --disable-qt4-peer: invalid even in 0.93, just drop it.

Signed-off-by: Jackie Huang 
---
 recipes-core/classpath/classpath.inc | 7 ++-
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/recipes-core/classpath/classpath.inc 
b/recipes-core/classpath/classpath.inc
index 1bdfd78..2be849b 100644
--- a/recipes-core/classpath/classpath.inc
+++ b/recipes-core/classpath/classpath.inc
@@ -28,24 +28,21 @@ SRC_URI = "${GNU_MIRROR}/classpath/classpath-${PV}.tar.gz"
 S = "${WORKDIR}/${PBN}-${PV}"
 
 export JAVA = "java"
+export JAVAC = "javac"
 
 EXTRA_OECONF = "\
   --with-glibj \
-  --with-ecj=javac \
-  --with-fastjar=fastjar \
+  --with-jar=${STAGING_BINDIR_NATIVE}/fastjar \
   --includedir=${includedir}/classpath \
-  --with-vm=java \
   --disable-Werror \
   --with-antlr-jar=${STAGING_DATADIR_JAVA_NATIVE}/antlr.jar \
   --with-gmp=${STAGING_LIBDIR}/.. \
   --disable-alsa \
   --disable-dssi \
-  --disable-qt4-peer \
   --disable-plugin \
   --enable-gconf-peer \
   --enable-gtk-peer \
   --enable-local-sockets \
-  --with-vm=java \
   "
 
 
-- 
1.9.1

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [PATCH][meta-networking][V2] net-snmp: fix the replacement in net-snmp-config

2015-12-31 Thread rongqing.li 
From: Roy Li 

when net-snmp-config is used to configure by other package, and fail since
/libnl3 is not found, in fact, it should be -I/usr/include/libnl3, and is
modified as /libnl3 incorrectly.

instead of modify the net-snmp-config for target, the one under
${bindir_crossscripts} should be replaced with ${TAGING_INCDIR}

Signed-off-by: Roy Li 
---
 meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.3.bb | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.3.bb 
b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.3.bb
index b32d842..68eea3f 100644
--- a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.3.bb
+++ b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.3.bb
@@ -63,8 +63,7 @@ do_install_append() {
 install -m 755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/snmpd
 install -m 644 ${WORKDIR}/snmpd.conf ${D}${sysconfdir}/snmp/
 install -m 644 ${WORKDIR}/snmptrapd.conf ${D}${sysconfdir}/snmp/
-sed -e "s@-I/usr/include@@g" \
--e "s@^prefix=.*@prefix=${STAGING_DIR_HOST}@g" \
+sed-e "s@^prefix=.*@prefix=${STAGING_DIR_HOST}@g" \
 -e "s@^exec_prefix=.*@exec_prefix=${STAGING_DIR_HOST}@g" \
 -e "s@^includedir=.*@includedir=${STAGING_INCDIR}@g" \
 -e "s@^libdir=.*@libdir=${STAGING_LIBDIR}@g" \
@@ -98,6 +97,8 @@ net_snmp_sysroot_preprocess () {
 if [ -e ${D}${bindir}/net-snmp-config ]; then
 install -d ${SYSROOT_DESTDIR}${bindir_crossscripts}/
 install -m 755 ${D}${bindir}/net-snmp-config 
${SYSROOT_DESTDIR}${bindir_crossscripts}/
+sed -e "s@-I/usr/include@-I${STAGING_INCDIR}@g" \
+  -i  ${SYSROOT_DESTDIR}${bindir_crossscripts}/net-snmp-config
 fi
 }
 
-- 
1.9.1

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-oe][PATCH] mariadb: -native also needs gold workaround

2015-12-31 Thread Koen Kooi 

> Op 30 dec. 2015, om 19:34 heeft Khem Raj  het volgende 
> geschreven:
> 
> On Wed, Dec 30, 2015 at 5:57 AM, Koen Kooi  wrote:
>> When the host distro uses gold mariadb-native fails to build.
>> 
> 
> what is the failure ?

The same one as in 
http://lists.openembedded.org/pipermail/openembedded-devel/2014-August/097495.html

> 
>> Signed-off-by: Koen Kooi 
>> ---
>> meta-oe/recipes-support/mysql/mariadb.inc | 3 +++
>> 1 file changed, 3 insertions(+)
>> 
>> diff --git a/meta-oe/recipes-support/mysql/mariadb.inc 
>> b/meta-oe/recipes-support/mysql/mariadb.inc
>> index a6826c3..6a55476 100644
>> --- a/meta-oe/recipes-support/mysql/mariadb.inc
>> +++ b/meta-oe/recipes-support/mysql/mariadb.inc
>> @@ -60,6 +60,9 @@ PACKAGECONFIG[setupdb] = ", ,,${PN}-setupdb"
>> # https://mariadb.atlassian.net/browse/MDEV-5982
>> TARGET_CFLAGS += "-fuse-ld=bfd"
>> 
>> +BUILD_CFLAGS += "-fuse-ld=bfd"
>> +BUILD_CXXFLAGS += "-fuse-ld=bfd"
>> +
>> EXTRA_OECMAKE = "-DWITH_EMBEDDED_SERVER=ON \
>>  -DWITH_JEMALLOC=no \
>>  -DWITHOUT_TOKUDB=TRUE \
>> --
>> 2.0.1
>> 
>> --
>> ___
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-oe][PATCH] mariadb: -native also needs gold workaround

2015-12-31 Thread Khem Raj 

> On Dec 31, 2015, at 12:14 AM, Koen Kooi  wrote:
> 
> 
>> Op 30 dec. 2015, om 19:34 heeft Khem Raj  het volgende 
>> geschreven:
>> 
>> On Wed, Dec 30, 2015 at 5:57 AM, Koen Kooi  
>> wrote:
>>> When the host distro uses gold mariadb-native fails to build.
>>> 
>> 
>> what is the failure ?
> 
> The same one as in 
> http://lists.openembedded.org/pipermail/openembedded-devel/2014-August/097495.html

OK. So it seems that a linker script is being used by without specifying linker 
option -T to denote that
which will actually make ld.bfd to treat it as add-on to default linker script. 
however gold will fail
to generate same behavior in current form. If you added -T then gold will do it 
same as ld.bfd but same won’t
work for ld.bfd since -T will override the implicit/internal linker script that 
ld.bfd uses. I don’t see an easy common
solution :(

> 
>> 
>>> Signed-off-by: Koen Kooi 
>>> ---
>>> meta-oe/recipes-support/mysql/mariadb.inc | 3 +++
>>> 1 file changed, 3 insertions(+)
>>> 
>>> diff --git a/meta-oe/recipes-support/mysql/mariadb.inc 
>>> b/meta-oe/recipes-support/mysql/mariadb.inc
>>> index a6826c3..6a55476 100644
>>> --- a/meta-oe/recipes-support/mysql/mariadb.inc
>>> +++ b/meta-oe/recipes-support/mysql/mariadb.inc
>>> @@ -60,6 +60,9 @@ PACKAGECONFIG[setupdb] = ", ,,${PN}-setupdb"
>>> # https://mariadb.atlassian.net/browse/MDEV-5982
>>> TARGET_CFLAGS += "-fuse-ld=bfd"
>>> 
>>> +BUILD_CFLAGS += "-fuse-ld=bfd"
>>> +BUILD_CXXFLAGS += "-fuse-ld=bfd"
>>> +
>>> EXTRA_OECMAKE = "-DWITH_EMBEDDED_SERVER=ON \
>>> -DWITH_JEMALLOC=no \
>>> -DWITHOUT_TOKUDB=TRUE \
>>> --
>>> 2.0.1
>>> 
>>> --
>>> ___
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [PATCH v2 00/54] Jentrho-next pull request

2015-12-31 Thread Martin Jansa 
On Wed, Dec 23, 2015 at 08:39:59AM -0800, Armin Kuster wrote:
> Please consider these changes for Jethro-next
> 
> I dropped the netmap changes but add more.
> 
>   mcelog: remove bashism and create ptest subpackage

mcelog is completely broken in jethro, because mcelog-inject is missing
there, I'll add:

commit 906cb0dcf0d40893849b5bd76189b119e9a6c7dc
Author: Kai Kang 
Date:   Fri Dec 4 15:09:15 2015 +0800

mce-inject: add recipe

Add recipe of mce-inject which is required to run mcelog ptest
cases.

to this patchset.


signature.asc
Description: Digital signature
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] chromium 40.0.2214.91 doesn't like gcc5.3

2015-12-31 Thread Trevor Woerner 
The version of chromium we're using is a bit old (it's almost a year old
now) and I thought that maybe a newer version might have the required
fixes in it already. Along those lines I tried updating the recipe to
build chromium-49.0.2607.0 which was released December 30, 2015. As it
turned out 49.0.2607.0 didn't have any fixes for gcc-5.3, I ran into the
exact same build problems I had seen building 40.0.2214.91 with gcc-5.3.
But, for fun, I thought it would be worth seeing if I could get
49.0.2607.0 to build and, patch after patch, I not only got it building
but I have also run-time tested it on my turbot. These patches, by the
way, adjust the code and don't simply turn off compiler warnings/errors.

I haven't tried getting 40 to build, but seeing that I have 49 building
(and running) I was wondering if I should work on getting 40 to build (I
assume most of the patches I developed for 49 will probably be the same
for 40) or should I just concentrate on updating the recipe to 49 and
getting that to work?

There's a lot of wayland-specific stuff in the recipe and I've never
built or run a wayland image, so if I'm going to work on making sure my
recipe for 49 works it'll take a bit of time for me to wrap my head
around the wayland stuff. Also, from what I can tell, the Linaro people
use their own branch/version for their ARM builds[1] so I'm wondering
how much testing people would need to accept such an update?




[1] https://github.com/ndechesne/qcom-oe-manifest/blob/master/default.xml
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] chromium 40.0.2214.91 doesn't like gcc5.3

2015-12-31 Thread Khem Raj 
Update is long due so please work on upgrade. X86 and arm are most
interesting platform. Please post it with RFT and lets give interested devs
a chance to try it out
On Dec 31, 2015 7:11 PM, "Trevor Woerner"  wrote:

> The version of chromium we're using is a bit old (it's almost a year old
> now) and I thought that maybe a newer version might have the required
> fixes in it already. Along those lines I tried updating the recipe to
> build chromium-49.0.2607.0 which was released December 30, 2015. As it
> turned out 49.0.2607.0 didn't have any fixes for gcc-5.3, I ran into the
> exact same build problems I had seen building 40.0.2214.91 with gcc-5.3.
> But, for fun, I thought it would be worth seeing if I could get
> 49.0.2607.0 to build and, patch after patch, I not only got it building
> but I have also run-time tested it on my turbot. These patches, by the
> way, adjust the code and don't simply turn off compiler warnings/errors.
>
> I haven't tried getting 40 to build, but seeing that I have 49 building
> (and running) I was wondering if I should work on getting 40 to build (I
> assume most of the patches I developed for 49 will probably be the same
> for 40) or should I just concentrate on updating the recipe to 49 and
> getting that to work?
>
> There's a lot of wayland-specific stuff in the recipe and I've never
> built or run a wayland image, so if I'm going to work on making sure my
> recipe for 49 works it'll take a bit of time for me to wrap my head
> around the wayland stuff. Also, from what I can tell, the Linaro people
> use their own branch/version for their ARM builds[1] so I'm wondering
> how much testing people would need to accept such an update?
>
>
>
>
> [1] https://github.com/ndechesne/qcom-oe-manifest/blob/master/default.xml
>
> --
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel