Date
1 - 9 of 9
toolchain queries
|
Kumar Gala <galak@...>
Where is the best place to ask questions and try and get support for adding some toolchain variations in?
I'm wanting to add support in for a few different flavors of PPC that are not currently supported: * e500v2 (gcc needs --enable-e500_double, eglibc * e5500 (64-bit embedded ppc) * e5500 - multilib support for 32/64-bit - k |
|
|
|
niqingliang
may be meta/conf/machine/include.
toggle quoted message
Show quoted text
On Fri, 2011-07-15 at 10:36 +0800, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding some toolchain variations in? |
|
|
|
Bruce Ashfield <bruce.ashfield@...>
On 11-07-14 10:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding some toolchain variations in?Here can work, or the oe-core lists. There are oe and oe-dev references for at least the e500v2 (that's what I've been working on importing .. slowly), and I haven't looked for others yet. So that's a good place to look for real world examples. Once I get a few kernel-3.0 issues sorted out, I'll be back to this and could definitely collaborate on these items. Cheers, Bruce * e5500 - multilib support for 32/64-bit |
|
|
|
Kumar Gala <galak@...>
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding some toolchain variations in?The other reason I ask is the recipes today don't seem to use (or allow for use of) --with-cpu. Wondering who is the expect on these recipes to discuss such issues with. - k |
|
|
|
Richard Purdie
On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:The tune files (conf/machine/include/tune*) usually set the march andWhere is the best place to ask questions and try and get support for adding some toolchain variations in?The other reason I ask is the recipes today don't seem to use (or allow for use of) --with-cpu. mcpu options which are added to CFLAGS. Does that provide the functionality you're looking for? Cheers, Richard |
|
|
|
Kumar Gala <galak@...>
On Jul 15, 2011, at 8:37 AM, Richard Purdie wrote:
On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:No, I'm dealing with different configure issues for gcc, eglibc for these targets:On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:The tune files (conf/machine/include/tune*) usually set the march andWhere is the best place to ask questions and try and get support for adding some toolchain variations in?The other reason I ask is the recipes today don't seem to use (or allow for use of) --with-cpu. PPC e500v2 PPC e5500 (64-bit, multilib) - k |
|
|
|
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala <galak@...> wrote:
Where is the best place to ask questions and try and get support for adding some toolchain variations in?this means ABI change especially due to double formats. This should be doable in machine.conf files or tune files. * e5500 (64-bit embedded ppc)this is new I guess. Its like adding a new arch to OE. See around http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-September/024661.html is roughly what can be helpful in getting ppc64 going * e5500 - multilib support for 32/64-bitthere is some thought and work RP has been doing on multilib.
|
|
|
|
Kumar Gala <galak@...>
On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala <galak@...> wrote:how so? What can I set in there that would actually get passed into gcc's configure (not really seeing anything). Also what exactly do you mean by a machine.confWhere is the best place to ask questions and try and get support for adding some toolchain variations in?this means ABI change especially due to double formats. This should be Thanks, will take a look at that.* e5500 (64-bit embedded ppc)this is new I guess. Its like adding a new arch to OE. See around - k |
|
|
|
On Fri, Jul 15, 2011 at 2:13 PM, Kumar Gala <galak@...> wrote:
Well as I see not so easily which is since we share toolchain for architectures and if we let machines add ABI conflicting options then we will be in trouble think of using I could have suggested using something like GLIBC_EXTRA_OECONF but I would not encourage that So one way to go about this is that we use -gnuspe in target triplet which will differentiate SPE targets from classic ppc and then in gcc recipe include files you can do something like EXTRA_OECONF_append_linux-gnuspe = " --enable-e500_double " Thanks, will take a look at that.* e5500 (64-bit embedded ppc)this is new I guess. Its like adding a new arch to OE. See around |
|
|