* Re: Issue in combining configure options in different tunes
[not found] <177AAA8C9A6604498BA86410157A63C95D7B680878@GUREXMB01.ASIAN.AD.ARICENT.COM>
@ 2014-01-17 4:34 ` Rohit2 Jindal
[not found] ` <177AAA8C9A6604498BA86410157A63C972FA330401@GUREXMB01.ASIAN.AD.ARICENT.COM>
1 sibling, 0 replies; 6+ messages in thread
From: Rohit2 Jindal @ 2014-01-17 4:34 UTC (permalink / raw)
To: 'yocto@yoctoproject.org'; +Cc: 'Paul Eggleton'
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
Please help me out!!!!!
From: Rohit2 Jindal
Sent: Thursday, January 16, 2014 11:10 AM
To: yocto@yoctoproject.org; Paul Eggleton; Marko Lindqvist
Subject: Issue in combining configure options in different tunes
Hi,
Actually I am able to build both elf(for xloader uboot) and linux toolchain(linux and userspace components) using tune mips32 and tune mips64-n32 with the required libgcc libraries and other required headers.
Glibc libraries were also build using tune-mips64-n32 with different combinations of abi arch and endianness.
Now my issue is to combine both the toolchain in single meta-xtoolchain layer so that both can be build in one yocto workspace using single meta-xtoolchain layer by just changing a variable in local.conf and all is done.
Example say Toolchain_var ="elf"
DEFAULTTUNE="mips32"
Build using the same gcc recipes the elf toolchain
Toolchain_var="linux"
DEFAULTTUNE="mips64-n32"
Build using the same gcc recipes the linux toolchain
EXTRA_OECONF_append_mips32= "${@bb.utils.contains(<mailto:$%7b@bb.utils.contains(>"Toolchain_var ", "elf", "put elf related extra_oeconf", "put linux related extra_oeconf", d)}"
Is this type of thing possible to put EXTRA_OECONF configure options on the basis of toolchian variable ?????? and this EXTRA_OECONF_append_mips32 or EXTRA_OECONF_append_mips64-n32 works???
Or tell me the way that I can add specific Configure options for gcc on the basis of tune passed?????????????
Please help me out on the issue.
Thanks in advance!!!!
Regards,
Rohit Jindal
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
[-- Attachment #2: Type: text/html, Size: 6248 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Issue in combining configure options in different tunes
[not found] ` <177AAA8C9A6604498BA86410157A63C972FA330401@GUREXMB01.ASIAN.AD.ARICENT.COM>
@ 2014-01-21 9:42 ` Rohit2 Jindal
2014-01-22 11:03 ` Rohit2 Jindal
1 sibling, 0 replies; 6+ messages in thread
From: Rohit2 Jindal @ 2014-01-21 9:42 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Hi,
Actually I am able to build both elf(for xloader uboot) and linux toolchain(linux and userspace components) using tune mips32 and tune mips64-n32 with the required libgcc libraries and other required headers.
Glibc libraries were also build using tune-mips64-n32 with different combinations of abi arch and endianness.
Now my issue is to combine both the toolchain in single meta-xtoolchain layer so that both can be build in one yocto workspace using single meta-xtoolchain layer by just changing a variable in local.conf and all is done.
Example say Toolchain_var ="elf"
DEFAULTTUNE="mips32"
Build using the same gcc recipes the elf toolchain
Toolchain_var="linux"
DEFAULTTUNE="mips64-n32"
Build using the same gcc recipes the linux toolchain
EXTRA_OECONF_append_mips32= "${@bb.utils.contains(<mailto:$%7b@bb.utils.contains(>"Toolchain_var ", "elf", "put elf related extra_oeconf", "put linux related extra_oeconf", d)}"
Is this type of thing possible to put EXTRA_OECONF configure options on the basis of toolchian variable ?????? and this EXTRA_OECONF_append_mips32 or EXTRA_OECONF_append_mips64-n32 works???
Or tell me the way that I can add specific Configure options for gcc on the basis of tune passed?????????????
Please help me out on the issue.
Thanks in advance!!!!
Regards,
Rohit Jindal
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
[-- Attachment #2: Type: text/html, Size: 5608 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Issue in combining configure options in different tunes
[not found] ` <177AAA8C9A6604498BA86410157A63C972FA330401@GUREXMB01.ASIAN.AD.ARICENT.COM>
2014-01-21 9:42 ` Rohit2 Jindal
@ 2014-01-22 11:03 ` Rohit2 Jindal
1 sibling, 0 replies; 6+ messages in thread
From: Rohit2 Jindal @ 2014-01-22 11:03 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Hi,
Actually I am able to build both elf(for xloader uboot) and linux toolchain(linux and userspace components) using tune mips32 and tune mips64-n32 with the required libgcc libraries and other required headers.
Glibc libraries were also build using tune-mips64-n32 with different combinations of abi arch and endianness.
Now my issue is to combine both the toolchain in single meta-xtoolchain layer so that both can be build in one yocto workspace using single meta-xtoolchain layer by just changing a variable in local.conf and all is done.
Example say Toolchain_var ="elf"
DEFAULTTUNE="mips32"
Build using the same gcc recipes the elf toolchain
Toolchain_var="linux"
DEFAULTTUNE="mips64-n32"
Build using the same gcc recipes the linux toolchain
EXTRA_OECONF_append_mips32= "${@bb.utils.contains(<mailto:$%7b@bb.utils.contains(>"Toolchain_var ", "elf", "put elf related extra_oeconf", "put linux related extra_oeconf", d)}"
Is this type of thing possible to put EXTRA_OECONF configure options on the basis of toolchian variable ?????? and this EXTRA_OECONF_append_mips32 or EXTRA_OECONF_append_mips64-n32 works???
Or tell me the way that I can add specific Configure options for gcc on the basis of tune passed?????????????
Please help me out on the issue.
Thanks in advance!!!!
Regards,
Rohit Jindal
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
[-- Attachment #2: Type: text/html, Size: 5711 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Issue in combining configure options in different tunes
@ 2014-01-16 5:40 Rohit2 Jindal
0 siblings, 0 replies; 6+ messages in thread
From: Rohit2 Jindal @ 2014-01-16 5:40 UTC (permalink / raw)
To: yocto, Paul Eggleton, Marko Lindqvist
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Hi,
Actually I am able to build both elf(for xloader uboot) and linux toolchain(linux and userspace components) using tune mips32 and tune mips64-n32 with the required libgcc libraries and other required headers.
Glibc libraries were also build using tune-mips64-n32 with different combinations of abi arch and endianness.
Now my issue is to combine both the toolchain in single meta-xtoolchain layer so that both can be build in one yocto workspace using single meta-xtoolchain layer by just changing a variable in local.conf and all is done.
Example say Toolchain_var ="elf"
DEFAULTTUNE="mips32"
Build using the same gcc recipes the elf toolchain
Toolchain_var="linux"
DEFAULTTUNE="mips64-n32"
Build using the same gcc recipes the linux toolchain
EXTRA_OECONF_append_mips32= "${@bb.utils.contains(<mailto:$%7b@bb.utils.contains(>"Toolchain_var ", "elf", "put elf related extra_oeconf", "put linux related extra_oeconf", d)}"
Is this type of thing possible to put EXTRA_OECONF configure options on the basis of toolchian variable ?????? and this EXTRA_OECONF_append_mips32 or EXTRA_OECONF_append_mips64-n32 works???
Or tell me the way that I can add specific Configure options for gcc on the basis of tune passed?????????????
Please help me out on the issue.
Thanks in advance!!!!
Regards,
Rohit Jindal
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
[-- Attachment #2: Type: text/html, Size: 5367 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Issue in combining configure options in different tunes
@ 2014-01-15 8:08 Rohit2 Jindal
0 siblings, 0 replies; 6+ messages in thread
From: Rohit2 Jindal @ 2014-01-15 8:08 UTC (permalink / raw)
To: yocto, Paul Eggleton, Marko Lindqvist
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
Humble reminder!!!!
Please help me out....
From: Rohit2 Jindal
Sent: Tuesday, January 14, 2014 12:27 PM
To: yocto@yoctoproject.org; 'Paul Eggleton'; 'Marko Lindqvist'
Subject: Issue in combining configure options in different tunes
Hi,
Actually I am able to build both elf(for xloader uboot) and linux toolchain(linux and userspace components) using tune mips32 and tune mips64-n32 with the required libgcc libraries and other required headers.
Glibc libraries were also build using tune-mips64-n32 with different combinations of abi arch and endianness.
Now my issue is to combine both the toolchain in single meta-xtoolchain layer so that both can be build in one yocto workspace using single meta-xtoolchain layer by just changing a variable in local.conf and all is done.
Example say Toolchain_var ="elf"
DEFAULTTUNE="mips32"
Build using the same gcc recipes the elf toolchain
Toolchain_var="linux"
DEFAULTTUNE="mips64-n32"
Build using the same gcc recipes the linux toolchain
EXTRA_OECONF_append_mips32= "${@bb.utils.contains(<mailto:$%7b@bb.utils.contains(>"Toolchain_var ", "elf", "put elf related extra_oeconf", "put linux related extra_oeconf", d)}"
Is this type of thing possible to put EXTRA_OECONF configure options on the basis of toolchian variable ?????? and this EXTRA_OECONF_append_mips32 or EXTRA_OECONF_append_mips64-n32 works???
Or tell me the way that I can add specific Configure options for gcc on the basis of tune passed?????????????
Please help me out on the issue.
Thanks in advance!!!!
Regards,
Rohit Jindal
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
[-- Attachment #2: Type: text/html, Size: 5857 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Issue in combining configure options in different tunes
@ 2014-01-14 6:56 Rohit2 Jindal
0 siblings, 0 replies; 6+ messages in thread
From: Rohit2 Jindal @ 2014-01-14 6:56 UTC (permalink / raw)
To: yocto, Paul Eggleton, Marko Lindqvist
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
Hi,
Actually I am able to build both elf(for xloader uboot) and linux toolchain(linux and userspace components) using tune mips32 and tune mips64-n32 with the required libgcc libraries and other required headers.
Glibc libraries were also build using tune-mips64-n32 with different combinations of abi arch and endianness.
Now my issue is to combine both the toolchain in single meta-xtoolchain layer so that both can be build in one yocto workspace using single meta-xtoolchain layer by just changing a variable in local.conf and all is done.
Example say Toolchain_var ="elf"
DEFAULTTUNE="mips32"
Build using the same gcc recipes the elf toolchain
Toolchain_var="linux"
DEFAULTTUNE="mips64-n32"
Build using the same gcc recipes the linux toolchain
EXTRA_OECONF_append_mips32= "${@bb.utils.contains("Toolchain_var ", "elf", "put elf related extra_oeconf", "put linux related extra_oeconf", d)}"
Is this type of thing possible to put EXTRA_OECONF configure options on the basis of toolchian variable ?????? and this EXTRA_OECONF_append_mips32 or EXTRA_OECONF_append_mips64-n32 works???
Or tell me the way that I can add specific Configure options for gcc on the basis of tune passed?????????????
Please help me out on the issue.
Thanks in advance!!!!
Regards,
Rohit Jindal
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
[-- Attachment #2: Type: text/html, Size: 4667 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-01-22 11:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <177AAA8C9A6604498BA86410157A63C95D7B680878@GUREXMB01.ASIAN.AD.ARICENT.COM>
2014-01-17 4:34 ` Issue in combining configure options in different tunes Rohit2 Jindal
[not found] ` <177AAA8C9A6604498BA86410157A63C972FA330401@GUREXMB01.ASIAN.AD.ARICENT.COM>
2014-01-21 9:42 ` Rohit2 Jindal
2014-01-22 11:03 ` Rohit2 Jindal
2014-01-16 5:40 Rohit2 Jindal
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 8:08 Rohit2 Jindal
2014-01-14 6:56 Rohit2 Jindal
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.