minimal.conf: Prefer perl 5.10.1 and opie 1.2.5
PATCH 1/2 minimal.conf: Prefer perl 5.10.1 and opie 1.2.5
* Tested various builds seems to hold fine
--- conf/distro/minimal.conf | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)
conf/distro/minimal.conf +3 -2
@@ -108,7 +108,7 @@ INHERIT += "recipe_sanity" # PREFERRED VERSIONS ############################################################################# require conf/distro/include/preferred-e-versions.inc -require conf/distro/include/preferred-opie-versions-1.2.4.inc +require conf/distro/include/preferred-opie-versions-1.2.5.inc PREFERRED_PROVIDER_opkg ?= "opkg" PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
@@ -119,7 +119,8 @@ PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-embedded-gles = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free-gles = "${PREFERRED_QT_VERSION}" - +PREFERRED_VERSION_perl = "5.10.1" +PREFERRED_VERSION_perl-native = "5.10.1" ############################################################################# # CONTENTS #############################################################################
Signature · 1 line
1.7.2.3
PATCH 2/2 sane-toolchain.inc: Prefer binutils 2.21
--- conf/distro/include/sane-toolchain.inc | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
conf/distro/include/sane-toolchain.inc +1 -1
@@ -6,7 +6,7 @@ # Base line versions, good for most things PREFERRED_GCC_VERSION ?= "4.5" -PREFERRED_BINUTILS_VERSION ?= "2.20.1" +PREFERRED_BINUTILS_VERSION ?= "2.21" PREFERRED_UCLIBC_VERSION ?= "git" PREFERRED_EGLIBC_VERSION ?= "2.12" PREFERRED_GLIBC_VERSION ?= "2.10.1"
Signature · 1 line
1.7.2.3
Re: [PATCH 2/2] sane-toolchain.inc: Prefer binutils 2.21
Quoted 1 line · Khem Raj
Signed-off-by Khem Raj <[email protected]>
I'm using it locally for a while and looks ok.
Quoted 25 lines
--- conf/distro/include/sane-toolchain.inc | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)conf/distro/include/sane-toolchain.inc +1
-1@@ -6,7 +6,7 @@ # Base line versions, good for most things PREFERRED_GCC_VERSION ?= "4.5" -PREFERRED_BINUTILS_VERSION ?= "2.20.1" +PREFERRED_BINUTILS_VERSION ?= "2.21" PREFERRED_UCLIBC_VERSION ?= "git" PREFERRED_EGLIBC_VERSION ?= "2.12" PREFERRED_GLIBC_VERSION ?= "2.10.1"Signature · 7 lines
1.7.2.3 _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
2011/1/17 Khem Raj <[email protected]>:
Quoted 27 lines
* Tested various builds seems to hold fine
Signed-off-by Khem Raj <[email protected]>---
conf/distro/minimal.conf | 5 +++--1 files changed, 3 insertions(+), 2 deletions(-)conf/distro/minimal.conf +0
-0@@ -108,7 +108,7 @@ INHERIT += "recipe_sanity" # PREFERRED VERSIONS #############################################################################require conf/distro/include/preferred-e-versions.inc
conf/distro/minimal.conf +1
-1-require conf/distro/include/preferred-opie-versions-1.2.4.inc +require conf/distro/include/preferred-opie-versions-1.2.5.incPREFERRED_PROVIDER_opkg ?= "opkg" PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
conf/distro/minimal.conf +0
-0@@ -119,7 +119,8 @@ PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}"PREFERRED_VERSION_qt4-embedded-gles = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free-gles = "${PREFERRED_QT_VERSION}"
conf/distro/minimal.conf +2
-1- +PREFERRED_VERSION_perl = "5.10.1" +PREFERRED_VERSION_perl-native = "5.10.1"
Quoted 5 lines
#############################################################################
# CONTENTS
#############################################################################
--
1.7.2.3
No opinion on the opie stuff, but I'm using perl 5.10.1 for quite a while, so that part has my ack.
(maybe split into two patches, one for opie, one for perl).
Frans
Quoted 29 lines · Frans Meulenbroeks
2011/1/17 Khem Raj <[email protected]>:
Quoted 28 lines
* Tested various builds seems to hold fine
Signed-off-by Khem Raj <[email protected]>---
conf/distro/minimal.conf | 5 +++--1 files changed, 3 insertions(+), 2 deletions(-)conf/distro/minimal.conf +0
-0@@ -108,7 +108,7 @@ INHERIT += "recipe_sanity" # PREFERRED VERSIONS #############################################################################require conf/distro/include/preferred-e-versions.inc
conf/distro/minimal.conf +1
-1-require conf/distro/include/preferred-opie-versions-1.2.4.inc +require conf/distro/include/preferred-opie-versions-1.2.5.incPREFERRED_PROVIDER_opkg ?= "opkg" PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
conf/distro/minimal.conf +0
-0@@ -119,7 +119,8 @@ PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}"PREFERRED_VERSION_qt4-embedded-gles = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free-gles = "${PREFERRED_QT_VERSION}"
conf/distro/minimal.conf +2
-1- +PREFERRED_VERSION_perl = "5.10.1" +PREFERRED_VERSION_perl-native = "5.10.1"#############################################################################
Quoted 9 lines
Quoted 4 lines
# CONTENTS
#############################################################################
--
1.7.2.3No opinion on the opie stuff, but I'm using perl 5.10.1 for quite a while, so that part has my ack.
(maybe split into two patches, one for opie, one for perl).
I will commit them as two patches if that helps
Quoted 7 lines
Frans
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
2011/1/17 Khem Raj <[email protected]>:
Quoted 41 lines
Quoted 29 lines · Frans Meulenbroeks
2011/1/17 Khem Raj <[email protected]>:
Quoted 28 lines
* Tested various builds seems to hold fine
Signed-off-by Khem Raj <[email protected]>---
conf/distro/minimal.conf | 5 +++--1 files changed, 3 insertions(+), 2 deletions(-)conf/distro/minimal.conf +0
-0@@ -108,7 +108,7 @@ INHERIT += "recipe_sanity" # PREFERRED VERSIONS #############################################################################require conf/distro/include/preferred-e-versions.inc
conf/distro/minimal.conf +1
-1-require conf/distro/include/preferred-opie-versions-1.2.4.inc +require conf/distro/include/preferred-opie-versions-1.2.5.incPREFERRED_PROVIDER_opkg ?= "opkg" PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
conf/distro/minimal.conf +0
-0@@ -119,7 +119,8 @@ PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}"PREFERRED_VERSION_qt4-embedded-gles = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free-gles = "${PREFERRED_QT_VERSION}"
conf/distro/minimal.conf +2
-1- +PREFERRED_VERSION_perl = "5.10.1" +PREFERRED_VERSION_perl-native = "5.10.1"#############################################################################
Quoted 9 lines
Quoted 4 lines
# CONTENTS
#############################################################################
--
1.7.2.3No opinion on the opie stuff, but I'm using perl 5.10.1 for quite a while, so that part has my ack.
(maybe split into two patches, one for opie, one for perl).
Quoted 1 line
I will commit them as two patches if that helps
If others are happy (and ack) the combined thing that is fine with me, but as a non-opie user or builder I cannot ack the opie part. Frans.
Quoted 21 lines · Khem Raj
* Tested various builds seems to hold fine
Signed-off-by Khem Raj<[email protected]>--- conf/distro/minimal.conf | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)conf/distro/minimal.conf +1
-1@@ -108,7 +108,7 @@ INHERIT += "recipe_sanity" # PREFERRED VERSIONS ############################################################################# require conf/distro/include/preferred-e-versions.inc -require conf/distro/include/preferred-opie-versions-1.2.4.inc +require conf/distro/include/preferred-opie-versions-1.2.5.inc PREFERRED_PROVIDER_opkg ?= "opkg" PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
conf/distro/minimal.conf PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}" · line 126
Quoted 9 lines
conf/distro/minimal.conf +2
-1@@ -119,7 +119,8 @@ PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-embedded-gles = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free = "${PREFERRED_QT_VERSION}" PREFERRED_VERSION_qt4-x11-free-gles = "${PREFERRED_QT_VERSION}" - +PREFERRED_VERSION_perl = "5.10.1" +PREFERRED_VERSION_perl-native = "5.10.1" ############################################################################# # CONTENTS #############################################################################
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess this is fine with me.
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 3 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess this is fine with me.
What kind of problems?
Signature · 3 lines
http://roman.khimov.ru mailto: [email protected] gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3
Quoted 6 lines · Roman I Khimov
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 3 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess this is fine with me.
What kind of problems?
Khem fixed it tonight. At heart, there's been a need to make much better use of the libc-uclibc override rather than testing TARGET_OS as there's at least 'linux-uclibc', 'linux-uclibceabi' and 'linux-uclibcspe' as valid TARGET_OS combinations. perl has been doing a test for the first two and Khem added a test for the 3rd. This got me to go and audit the recipes for using the _linux-uclibc append and switching them en masse to libc-uclibc. There were a very small number of places that had been catching all 3, but for the most part it was 80% catching the first two and 20% catching just linux-uclibc. I believe but didn't check that Khem caught the rest of the places that were testing for TARGET_OS in shell code and updated them for linux-uclibcspe.
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
Quoted 6 lines · Tom Rini
Quoted 5 lines · Roman I Khimov
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 3 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess this is fine with me.
Quoted 6 lines
Quoted 1 line
What kind of problems?
Khem fixed it tonight. At heart, there's been a need to make much better use of the libc-uclibc override rather than testing
TARGET_OSas there's at least 'linux-uclibc', 'linux-uclibceabi' and 'linux-uclibcspe' as validTARGET_OScombinations.
I thought about it and indeed it would be better to have a LIBC override but its defined in .inc files which may not be included by all distributions, if this makes into bitbake.conf somehow then that would be better or we can decide to have a global data var called LIBC or some sort.
perl has been
Quoted 17 lines
doing a test for the first two and Khem added a test for the 3rd. This got me to go and audit the recipes for using the _linux-uclibc append and switching them en masse to libc-uclibc. There were a very small number of places that had been catching all 3, but for the most part it was 80% catching the first two and 20% catching just linux-uclibc. I believe but didn't check that Khem caught the rest of the places that were testing for
TARGET_OSin shell code and updated them for linux-uclibcspe.Signature · 7 lines
Tom Rini Mentor Graphics Corporation _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 14 lines · Khem Raj
Quoted 6 lines · Tom Rini
Quoted 5 lines · Roman I Khimov
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 3 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess this is fine with me.
Quoted 6 lines
Quoted 1 line
What kind of problems?
Khem fixed it tonight. At heart, there's been a need to make much better use of the libc-uclibc override rather than testing
TARGET_OSas there's at least 'linux-uclibc', 'linux-uclibceabi' and 'linux-uclibcspe' as validTARGET_OScombinations.
Quoted 5 lines
I thought about it and indeed it would be better to have a LIBC override but its defined in .inc files which may not be included by all distributions, if this makes into bitbake.conf somehow then that would be better or we can decide to have a global data var called LIBC or some sort.
We already did this. A distro that doesn't pull in the right libc inc file is either broken or on its own (I forget and can't check atm if Angstrom uses the files eventually or just also has the libc-foo OVERRIDES, but is correct here). We also have LIBC as a global env way to say what LIBC to use (Angstrom has ANGSTROMLIBC and LIBC since they originated the feature).
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
Quoted 27 lines · Tom Rini
Quoted 20 lines · Khem Raj
Quoted 11 lines · Tom Rini
Quoted 9 lines · Roman I Khimov
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 5 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess
this is fine with me.Quoted 6 lines
Quoted 1 line
What kind of problems?
Khem fixed it tonight. At heart, there's been a need to make much better use of the libc-uclibc override rather than testing
TARGET_OSas there's at least 'linux-uclibc', 'linux-uclibceabi' and 'linux-uclibcspe' as validTARGET_OScombinations.Quoted 5 lines
I thought about it and indeed it would be better to have a LIBC override but its defined in .inc files which may not be included by all distributions, if this makes into bitbake.conf somehow then that would be better or we can decide to have a global data var called LIBC or some sort.
Quoted 4 lines
We already did this. A distro that doesn't pull in the right libc inc file is either broken or on its own (I forget and can't check atm if Angstrom uses the files eventually or just also has the libc-foo OVERRIDES, but is correct here).
yes angstrom does. Ok I moved slugos to use it recently so its no more broken :)
We also have LIBC as a global env way to say what LIBC to
Quoted 1 line
use (Angstrom has ANGSTROMLIBC and LIBC since they originated the feature).
nice we can use LIBC as well if need be but override is more elegant
Quoted 10 lines
--
Tom Rini
Mentor Graphics Corporation_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 28 lines · Khem Raj
Quoted 27 lines · Tom Rini
Quoted 25 lines · Khem Raj
Quoted 11 lines · Tom Rini
Quoted 9 lines · Roman I Khimov
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 5 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess
this is fine with me.Quoted 6 lines
Quoted 1 line
What kind of problems?
Khem fixed it tonight. At heart, there's been a need to make much better use of the libc-uclibc override rather than testing
TARGET_OSas there's at least 'linux-uclibc', 'linux-uclibceabi' and 'linux-uclibcspe' as validTARGET_OScombinations.I thought about it and indeed it would be better to have a LIBC override but its defined in .inc files which may not be included by all distributions, if this makes into bitbake.conf somehow then that would be better or we can decide to have a global data var called LIBC or some sort.
Quoted 6 lines
Quoted 4 lines
We already did this. A distro that doesn't pull in the right libc inc file is either broken or on its own (I forget and can't check atm if Angstrom uses the files eventually or just also has the libc-foo OVERRIDES, but is correct here).
yes angstrom does. Ok I moved slugos to use it recently so its no more broken :)
Um, when did SlugOS break then? When I introduced the libc overrides I moved everyone over to it.
Quoted 4 lines
We also have LIBC as a global env way to say what LIBC to
Quoted 1 line
use (Angstrom has ANGSTROMLIBC and LIBC since they originated the feature).
nice we can use LIBC as well if need be but override is more elegant
Yes, LIBC shouldn't be parsed like that, it's like MACHINE :)
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
Quoted 37 lines · Tom Rini
Quoted 36 lines · Khem Raj
Quoted 33 lines · Tom Rini
Quoted 20 lines · Khem Raj
Quoted 11 lines · Tom Rini
Quoted 9 lines · Roman I Khimov
В сообщении от Понедельник 17 января 2011 22:14:51 автор Tom Rini написал:
Quoted 5 lines · Khem Raj
I see different problems with perl 5.10.1 + uclibc + p2020ds, so I guess
this is fine with me.Quoted 6 lines
Quoted 1 line
What kind of problems?
Khem fixed it tonight. At heart, there's been a need to make much better use of the libc-uclibc override rather than testing
TARGET_OSas there's at least 'linux-uclibc', 'linux-uclibceabi' and 'linux-uclibcspe' as validTARGET_OScombinations.Quoted 5 lines
I thought about it and indeed it would be better to have a LIBC override but its defined in .inc files which may not be included by all distributions, if this makes into bitbake.conf somehow then that would be better or we can decide to have a global data var called LIBC or some sort.
We already did this. A distro that doesn't pull in the right libc inc file
is either broken or on its own (I forget and can't check atm if Angstrom uses the files eventually or just also has the libc-foo OVERRIDES, but is correct here).
Quoted 5 lines
Quoted 2 lines
yes angstrom does. Ok I moved slugos to use it recently so its no more broken :)
Um, when did SlugOS break then? When I introduced the libc overrides I moved everyone over to it.
indeed, I just thought now that its using sane-toolchain but it included
conf/distro/include/${LIBC}.inc
before too so it was not broken
Quoted 19 lines
Quoted 7 lines
We also have LIBC as a global env way to say what LIBC to
Quoted 3 lines
use (Angstrom has ANGSTROMLIBC and LIBC since they originated the feature).
nice we can use LIBC as well if need be but override is more elegant
Yes, LIBC shouldn't be parsed like that, it's like MACHINE :)
--
Tom Rini
Mentor Graphics Corporation_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel