* Where do I override DISTRO_FEATURES? @ 2012-05-15 16:12 Thilo Fromm 2012-05-15 16:23 ` Paul Eggleton 2012-05-16 5:31 ` Koen Kooi 0 siblings, 2 replies; 13+ messages in thread From: Thilo Fromm @ 2012-05-15 16:12 UTC (permalink / raw) To: openembedded-devel Hello, I'm trying to remove an element from DISTRO_FEATURES (specifically "ld-is-gold"), but I am unable to find the right spot to do it. The distribution we're using (Angstrom, as it happens) sets this in conf/distro/angstrom-v2012.x.conf. My machine configuration is the wrong spot to modify DISTRO_FEATURES, since it will be processed first. local.conf is not working, too. So could anybody please tell me where I need to put my DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold', '')}" so it applies for the build? Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 16:12 Where do I override DISTRO_FEATURES? Thilo Fromm @ 2012-05-15 16:23 ` Paul Eggleton 2012-05-15 16:44 ` Thilo Fromm 2012-05-15 20:19 ` Denys Dmytriyenko 2012-05-16 5:31 ` Koen Kooi 1 sibling, 2 replies; 13+ messages in thread From: Paul Eggleton @ 2012-05-15 16:23 UTC (permalink / raw) To: Thilo Fromm; +Cc: openembedded-devel On Tuesday 15 May 2012 18:12:35 Thilo Fromm wrote: > I'm trying to remove an element from DISTRO_FEATURES (specifically > "ld-is-gold"), but I am unable to find the right spot to do it. The > distribution we're using (Angstrom, as it happens) sets this in > conf/distro/angstrom-v2012.x.conf. My machine configuration is the > wrong spot to modify DISTRO_FEATURES, since it will be processed > first. local.conf is not working, too. > > So could anybody please tell me where I need to put my > > DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold', '')}" > > so it applies for the build? Unfortunately such hacks only work for variables that are not set within the distro configuration, which is applied after local.conf. Ultimately you shouldn't really do this. If you want to change distro policy then you really ought to have your own distro configuration, or try to work with the existing distro to fix whatever problem exists. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 16:23 ` Paul Eggleton @ 2012-05-15 16:44 ` Thilo Fromm 2012-05-15 20:16 ` Denys Dmytriyenko 2012-05-15 20:19 ` Denys Dmytriyenko 1 sibling, 1 reply; 13+ messages in thread From: Thilo Fromm @ 2012-05-15 16:44 UTC (permalink / raw) To: Paul Eggleton; +Cc: openembedded-devel Hello, >> I'm trying to remove an element from DISTRO_FEATURES (specifically >> "ld-is-gold"), but I am unable to find the right spot to do it. The >> distribution we're using (Angstrom, as it happens) sets this in >> conf/distro/angstrom-v2012.x.conf. My machine configuration is the >> wrong spot to modify DISTRO_FEATURES, since it will be processed >> first. local.conf is not working, too. >> >> So could anybody please tell me where I need to put my >> >> DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold', '')}" >> >> so it applies for the build? > > Unfortunately such hacks only work for variables that are not set within the > distro configuration, which is applied after local.conf. I see. Fortunately I can require conf/distro/angstrom-v2012.x.conf in my own distro config file. > Ultimately you shouldn't really do this. If you want to change distro policy > then you really ought to have your own distro configuration, or try to work > with the existing distro to fix whatever problem exists. It's a backwards compatibility thing: we're bound to gcc-4.5 (we have kernel build issues with newer gcc versions; we're nailed to linux-2.6.37 thanks to lack of support by Texas Instruments) which fails to detect the correct version of binutils GOLD (LD would work) and therefore misses critical features which break the build later on. I won't, however, try to convince the Angstrom guys to further support ancient toolchains and make gold optional again just because of TI's laziness. I'll try to set up a minimal config for a distribution based on Angstrom, then, so I can fix up DISTRO_FEATURES. Thanks for your help, Paul. Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 16:44 ` Thilo Fromm @ 2012-05-15 20:16 ` Denys Dmytriyenko 2012-05-16 8:30 ` Thilo Fromm 0 siblings, 1 reply; 13+ messages in thread From: Denys Dmytriyenko @ 2012-05-15 20:16 UTC (permalink / raw) To: openembedded-devel On Tue, May 15, 2012 at 06:44:10PM +0200, Thilo Fromm wrote: > Hello, > > >> I'm trying to remove an element from DISTRO_FEATURES (specifically > >> "ld-is-gold"), but I am unable to find the right spot to do it. The > >> distribution we're using (Angstrom, as it happens) sets this in > >> conf/distro/angstrom-v2012.x.conf. My machine configuration is the > >> wrong spot to modify DISTRO_FEATURES, since it will be processed > >> first. local.conf is not working, too. > >> > >> So could anybody please tell me where I need to put my > >> > >> DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold', '')}" > >> > >> so it applies for the build? > > > > Unfortunately such hacks only work for variables that are not set within the > > distro configuration, which is applied after local.conf. > > I see. Fortunately I can require conf/distro/angstrom-v2012.x.conf in > my own distro config file. > > > Ultimately you shouldn't really do this. If you want to change distro policy > > then you really ought to have your own distro configuration, or try to work > > with the existing distro to fix whatever problem exists. > > It's a backwards compatibility thing: we're bound to gcc-4.5 (we have > kernel build issues with newer gcc versions; we're nailed to > linux-2.6.37 thanks to lack of support by Texas Instruments) which > fails to detect the correct version of binutils GOLD (LD would work) > and therefore misses critical features which break the build later on. > I won't, however, try to convince the Angstrom guys to further support > ancient toolchains and make gold optional again just because of TI's > laziness. I think you are severely misinformed! Above issues (binutils-2.20/gcc-4.5 requirement and gold ld problem with Thumb) were already fixed. I've been testing the builds with gcc-4.6 and binutils-2.22 for few weeks and even gcc-4.7 with gold linker since last week. I don't know what layer you are using, but you may need to update, if you are using meta-ti. Otherwise, if your platform is not directly supported by meta-ti, please send the bug report with the error message to meta-ti mailing list and I'll try to address it. As of linux-2.6.37 for your specific platform - this one I can't help with, you would need to talk to your TI rep from the division that makes the platform and convince them to provide support for newer kernels. -- Denys ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 20:16 ` Denys Dmytriyenko @ 2012-05-16 8:30 ` Thilo Fromm 0 siblings, 0 replies; 13+ messages in thread From: Thilo Fromm @ 2012-05-16 8:30 UTC (permalink / raw) To: openembedded-devel Hello Denys, >> >> I'm trying to remove an element from DISTRO_FEATURES (specifically >> >> "ld-is-gold"), but I am unable to find the right spot to do it. The >> >> distribution we're using (Angstrom, as it happens) sets this in >> >> conf/distro/angstrom-v2012.x.conf. My machine configuration is the >> >> wrong spot to modify DISTRO_FEATURES, since it will be processed >> >> first. local.conf is not working, too. >> >> It's a backwards compatibility thing: we're bound to gcc-4.5 (we have >> kernel build issues with newer gcc versions; we're nailed to >> linux-2.6.37 thanks to lack of support by Texas Instruments) which >> fails to detect the correct version of binutils GOLD (LD would work) >> and therefore misses critical features which break the build later on. >> I won't, however, try to convince the Angstrom guys to further support >> ancient toolchains and make gold optional again just because of TI's >> laziness. > > I think you are severely misinformed! Above issues (binutils-2.20/gcc-4.5 > requirement and gold ld problem with Thumb) were already fixed. I've been > testing the builds with gcc-4.6 and binutils-2.22 for few weeks and even > gcc-4.7 with gold linker since last week. You're right, gcc-4.7 works well in the current setup. gcc-4.5, however, does not detect the right binutils version with the GOLD linker. GOLD version output is: GNU gold (GNU Binutils 2.22) 1.11 The configure logic of gcc-4.5 would extract "1.11", not "2.22", for the version number. Since Binutils 1.11 is ancient, some features of gcc-initial are not set up correctly (gcc thinks the linker does not support the "hidden" attribute). This breaks the build of eglibc-initial later on. I overslept the whole thing and I guess I'll just provide a patch to gcc-4.5's configure so the GOLD linker version is detected correctly instead of setting up my own distribution config. > I don't know what layer you are > using, but you may need to update, if you are using meta-ti. meta-ti does not provide any toolchain anywhere. I have a toolchain issue. The issue is with gcc-4.5 from meta-oe/toolchain-layer in combination with binutils-2.22 from openembedded-core/meta/recipes-devtools/. Just in case you're curious, our layer structure is documented here: <https://github.com/DFE/HidaV/wiki/Hidav-oe-layers>. > Otherwise, if your platform is not directly supported by meta-ti, please send > the bug report with the error message to meta-ti mailing list and I'll try to > address it. Which meta-ti mailing list are you talking about? There seem to be many: this one, the arago lists, yocto-ti, ... And then again, it's a toolchain issue (see above); meta-ti doesn't have toolchains. > As of linux-2.6.37 for your specific platform - this one I can't help with, > you would need to talk to your TI rep from the division that makes the > platform and convince them to provide support for newer kernels. I know, it's OK. We talked to TI a lot for quite a while, but our realistic assessment from our TI experiences is that they'll never do it. There are still a lot of issues with their old 2.6.37 kernel, TI continually keeps breaking things. They don't have proper issue trackers or mailing lists for communication with their developers. From the reps and FAEs we'd get the occasional empty promise, but that's it. Personally I think we went wrong with buying TI in the first place. Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 16:23 ` Paul Eggleton 2012-05-15 16:44 ` Thilo Fromm @ 2012-05-15 20:19 ` Denys Dmytriyenko 2012-05-16 8:34 ` Thilo Fromm 1 sibling, 1 reply; 13+ messages in thread From: Denys Dmytriyenko @ 2012-05-15 20:19 UTC (permalink / raw) To: openembedded-devel; +Cc: Thilo Fromm On Tue, May 15, 2012 at 05:23:43PM +0100, Paul Eggleton wrote: > On Tuesday 15 May 2012 18:12:35 Thilo Fromm wrote: > > I'm trying to remove an element from DISTRO_FEATURES (specifically > > "ld-is-gold"), but I am unable to find the right spot to do it. The > > distribution we're using (Angstrom, as it happens) sets this in > > conf/distro/angstrom-v2012.x.conf. My machine configuration is the > > wrong spot to modify DISTRO_FEATURES, since it will be processed > > first. local.conf is not working, too. > > > > So could anybody please tell me where I need to put my > > > > DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold', '')}" > > > > so it applies for the build? > > Unfortunately such hacks only work for variables that are not set within the > distro configuration, which is applied after local.conf. Well, while still being an ugly hack, this should still be possible using local overrides... I.e. VAR_local in OE or VAR_forcevariable in OE-core/Yocto. You may need to use immediate assignment to avoid circular dependency, though. -- Denys ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 20:19 ` Denys Dmytriyenko @ 2012-05-16 8:34 ` Thilo Fromm 0 siblings, 0 replies; 13+ messages in thread From: Thilo Fromm @ 2012-05-16 8:34 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: openembedded-devel Hello, Denys, >> > I'm trying to remove an element from DISTRO_FEATURES (specifically >> > "ld-is-gold"), but I am unable to find the right spot to do it. The >> > distribution we're using (Angstrom, as it happens) sets this in >> > conf/distro/angstrom-v2012.x.conf. My machine configuration is the >> > wrong spot to modify DISTRO_FEATURES, since it will be processed >> > first. local.conf is not working, too. >> > >> > So could anybody please tell me where I need to put my >> > >> > DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold', '')}" >> > >> > so it applies for the build? >> >> Unfortunately such hacks only work for variables that are not set within the >> distro configuration, which is applied after local.conf. > > Well, while still being an ugly hack, this should still be possible using > local overrides... I.e. VAR_local in OE or VAR_forcevariable in OE-core/Yocto. > You may need to use immediate assignment to avoid circular dependency, though. Actually it would be easiest for me if the last 5 lines of https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/angstrom-v2012.x.conf would not be DISTRO_FEATURES += "${LDISGOLD}" LDISGOLD_arm = "ld-is-gold" LDISGOLD_x86 = "ld-is-gold" LDISGOLD_x86_64 = "ld-is-gold" LDISGOLD = "" but instead be DISTRO_FEATURES += "${LDISGOLD}" LDISGOLD_arm ?= "ld-is-gold" LDISGOLD_x86 ?= "ld-is-gold" LDISGOLD_x86_64 ?= "ld-is-gold" LDISGOLD ?= "" But anyways, I decided to fix the gcc-4.5-cross-initial build. Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-15 16:12 Where do I override DISTRO_FEATURES? Thilo Fromm 2012-05-15 16:23 ` Paul Eggleton @ 2012-05-16 5:31 ` Koen Kooi 2012-05-16 8:37 ` Thilo Fromm 1 sibling, 1 reply; 13+ messages in thread From: Koen Kooi @ 2012-05-16 5:31 UTC (permalink / raw) To: openembedded-devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Op 15-05-12 18:12, Thilo Fromm schreef: > Hello, > > I'm trying to remove an element from DISTRO_FEATURES (specifically > "ld-is-gold"), but I am unable to find the right spot to do it. The > distribution we're using (Angstrom, as it happens) sets this in > conf/distro/angstrom-v2012.x.conf. Why aren't you using the angstrom release? That isn't using gold. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJPszuyAAoJEHZqAkdh1vT6HlsP/RyLQIOKUBL3pH9XpaU1Ra6Q AmANF1QHGUMXXSYuULKN3lNu2fPXYKCbiR7sCjPLMWcIQqJ6a6UAQsWGKgAXK0P/ JXhF9RLtxXi3Ws+wo303md8zgdEHC4LHuqYl5mC90fmBr80FPbcnrNlii24HTzpt mrT7DyntO6oiXJkZBV2dTkYzeDjn2NbCwFNXn0h4OJMtwfp2dYzqwmKXeay7lmoB 2VL8dz6t9p4yFPM229XbD/A3xBynNIvd6CA2CaPu2fPc7bd7Lo19SdkDLjgRBm0d e1QwRIfNgoGATO1QFJTgSqoCTvu0YsqfjNVopCsa4zTdgobxVT8ob3MWvktYxWjG NtzoiZt58Y1/jqpJx27rSXw6fGuAozGZRVA1hCGH9h12E7s0UoD9pEAn/QOFG8BN M+JC8d8jCCmJwP/Pn2eIHRB2Kkhbvs/pN7fbQllYgMG3cZUD7HM5P1x0vukBafkT b3Pkev0LTQFOxXRTyTreCBqZLeXJbGq0tmDei2eTk2HRX8oEq0JXbp9K2bUlNlGP xCtJxPk2O3nIqUx0sLsHlrbiEXuIbmW8VBZgMp7wpBLW2IqSTQXf9lH17ZvJeamb QNj9cMjVgmCI1JMpaiRP6zCveapG8b0K42Arx6tT72ao4NGaM3Ps7Y0miSLk2BvY EE1Nqkf9aOlZFr8dT0gZ =YOd0 -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-16 5:31 ` Koen Kooi @ 2012-05-16 8:37 ` Thilo Fromm 2012-05-16 20:55 ` R U Local 0 siblings, 1 reply; 13+ messages in thread From: Thilo Fromm @ 2012-05-16 8:37 UTC (permalink / raw) To: openembedded-devel Hello Koen, >> I'm trying to remove an element from DISTRO_FEATURES (specifically >> "ld-is-gold"), but I am unable to find the right spot to do it. The >> distribution we're using (Angstrom, as it happens) sets this in >> conf/distro/angstrom-v2012.x.conf. > > Why aren't you using the angstrom release? That isn't using gold. We're using angstrom-v2012.x.conf from the git HEAD since we want to stay with latest and greatest for now. angstrom-v2012.x.conf is using gold. It's OK, really, I think I can handle the gcc-4.5 configure build problem. Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-16 8:37 ` Thilo Fromm @ 2012-05-16 20:55 ` R U Local 2012-05-16 21:19 ` Khem Raj 2012-05-18 7:42 ` Thilo Fromm 0 siblings, 2 replies; 13+ messages in thread From: R U Local @ 2012-05-16 20:55 UTC (permalink / raw) To: openembedded-devel Dear Thilo, Anyone else, How did you get oe-core/Angstrom-v2012x to build a working system using a 2.6.37 kernel? I'm in a similar position using TI AM3517. The latest angstrom is built around systemd which requires a 2.6.38 or better kernel. I've had to reluctantly revert back to oe-classic and angstrom 2011.03. Any hints on getting oe-core/Angstrom-v2012x working with a 2.6.37 kernel would be great. Cheers Mike. -----Original Message----- From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Thilo Fromm Sent: Wednesday, 16 May 2012 20:38 To: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Where do I override DISTRO_FEATURES? Hello Koen, >> I'm trying to remove an element from DISTRO_FEATURES (specifically >> "ld-is-gold"), but I am unable to find the right spot to do it. The >> distribution we're using (Angstrom, as it happens) sets this in >> conf/distro/angstrom-v2012.x.conf. > > Why aren't you using the angstrom release? That isn't using gold. We're using angstrom-v2012.x.conf from the git HEAD since we want to stay with latest and greatest for now. angstrom-v2012.x.conf is using gold. It's OK, really, I think I can handle the gcc-4.5 configure build problem. Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-16 20:55 ` R U Local @ 2012-05-16 21:19 ` Khem Raj 2012-05-17 0:35 ` Otavio Salvador 2012-05-18 7:42 ` Thilo Fromm 1 sibling, 1 reply; 13+ messages in thread From: Khem Raj @ 2012-05-16 21:19 UTC (permalink / raw) To: openembedded-devel On Wed, May 16, 2012 at 1:55 PM, R U Local <roystonvasey@slingshot.co.nz> wrote: > Dear Thilo, Anyone else, > How did you get oe-core/Angstrom-v2012x to build a working system using a 2.6.37 kernel? > I'm in a similar position using TI AM3517. The latest angstrom is built around systemd which requires a 2.6.38 or better kernel. > I've had to reluctantly revert back to oe-classic and angstrom 2011.03. > Any hints on getting oe-core/Angstrom-v2012x working with a 2.6.37 kernel would be great. I have had systemd work with 2.6.34 Koen has some options he mentions you need to enable in kconfig http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-16 21:19 ` Khem Raj @ 2012-05-17 0:35 ` Otavio Salvador 0 siblings, 0 replies; 13+ messages in thread From: Otavio Salvador @ 2012-05-17 0:35 UTC (permalink / raw) To: openembedded-devel On Wed, May 16, 2012 at 6:19 PM, Khem Raj <raj.khem@gmail.com> wrote: > I have had systemd work with 2.6.34 Koen has some options he mentions > you need to enable in kconfig Which udev? -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Where do I override DISTRO_FEATURES? 2012-05-16 20:55 ` R U Local 2012-05-16 21:19 ` Khem Raj @ 2012-05-18 7:42 ` Thilo Fromm 1 sibling, 0 replies; 13+ messages in thread From: Thilo Fromm @ 2012-05-18 7:42 UTC (permalink / raw) To: openembedded-devel Hello Mike, > Dear Thilo, Anyone else, > How did you get oe-core/Angstrom-v2012x to build a working system using a 2.6.37 kernel? > I'm in a similar position using TI AM3517. The latest angstrom is built around systemd which requires a 2.6.38 or better kernel. > I've had to reluctantly revert back to oe-classic and angstrom 2011.03. > Any hints on getting oe-core/Angstrom-v2012x working with a 2.6.37 kernel would be great. Angstrom uses linux-libc-headers-3.2 for user space ABI. It's a rather dangerous hack, but it enables you to use 2.6.37 with a state of the art user space. If you're curious just take a look at <https://github.com/DFE/HidaV>, that's our layer stack. The wiki has some documentation, too: <https://github.com/DFE/HidaV/wiki/Hidav-oe-layers>. Basically we use everything from meta-ti, meta-oe + meta-angstrom, and oe-core (let's not talk about meta-java ;) ). We just stick it together in meta-hidav, and so far angstrom-v2012.x works for us. Regards, Thilo -- Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de Fax: +49 (30) 515 932 77 http://www.dresearch.de Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058 Geschäftsführer: Dr. M. Weber, W. Mögle ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2012-05-18 7:52 UTC | newest] Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2012-05-15 16:12 Where do I override DISTRO_FEATURES? Thilo Fromm 2012-05-15 16:23 ` Paul Eggleton 2012-05-15 16:44 ` Thilo Fromm 2012-05-15 20:16 ` Denys Dmytriyenko 2012-05-16 8:30 ` Thilo Fromm 2012-05-15 20:19 ` Denys Dmytriyenko 2012-05-16 8:34 ` Thilo Fromm 2012-05-16 5:31 ` Koen Kooi 2012-05-16 8:37 ` Thilo Fromm 2012-05-16 20:55 ` R U Local 2012-05-16 21:19 ` Khem Raj 2012-05-17 0:35 ` Otavio Salvador 2012-05-18 7:42 ` Thilo Fromm
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.