* [Buildroot] Insufficient RPC options for crosstool-ng toolchain @ 2013-02-04 22:36 Shawn J. Goff 2013-02-04 23:32 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: Shawn J. Goff @ 2013-02-04 22:36 UTC (permalink / raw) To: buildroot I'm getting an error about a missing rpc_msg.h while building conntrack-tools. That package selects libtirpc if !BR2_TOOLCHAIN_HAS_NATIVE_RPC. I'm having BR build the toolchain using ct-ng; I looked at the toolchain-crosstool-ng/Config.in and it selects BR2_TOOLCHAIN_HAS_NATIVE_RPC because the ct-ng config that ships with BR uses glibc 2.9. My ct-ng config uses glibc 2.14, which doesn't have native RPC support. I started to make a patch that allows for explicitly selecting BR2_TOOLCHAIN_HAS_NATIVE_RPC like the external-toolchain allows, but I ran across check_glibc function and the ext-toolchain-checked stamp and it looks like quite a lot, so I wanted to find out if you actually want all that for this fix. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Insufficient RPC options for crosstool-ng toolchain 2013-02-04 22:36 [Buildroot] Insufficient RPC options for crosstool-ng toolchain Shawn J. Goff @ 2013-02-04 23:32 ` Thomas Petazzoni 2013-02-04 23:39 ` Shawn J. Goff 0 siblings, 1 reply; 5+ messages in thread From: Thomas Petazzoni @ 2013-02-04 23:32 UTC (permalink / raw) To: buildroot Dear Shawn J. Goff, On Mon, 04 Feb 2013 17:36:36 -0500, Shawn J. Goff wrote: > I'm getting an error about a missing rpc_msg.h while building > conntrack-tools. That package selects libtirpc if > !BR2_TOOLCHAIN_HAS_NATIVE_RPC. I'm having BR build the toolchain using > ct-ng; I looked at the toolchain-crosstool-ng/Config.in and it selects > BR2_TOOLCHAIN_HAS_NATIVE_RPC because the ct-ng config that ships with BR > uses glibc 2.9. My ct-ng config uses glibc 2.14, which doesn't have > native RPC support. Correct. > I started to make a patch that allows for explicitly selecting > BR2_TOOLCHAIN_HAS_NATIVE_RPC like the external-toolchain allows, Seems like the good solution yes. > but I > ran across check_glibc function and the ext-toolchain-checked stamp and > it looks like quite a lot, so I wanted to find out if you actually want > all that for this fix. What problems did you encounter exactly? It should be fairly similar to what we do for external toolchains I believe, no? Thanks, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Insufficient RPC options for crosstool-ng toolchain 2013-02-04 23:32 ` Thomas Petazzoni @ 2013-02-04 23:39 ` Shawn J. Goff 2013-02-04 23:49 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: Shawn J. Goff @ 2013-02-04 23:39 UTC (permalink / raw) To: buildroot On 02/04/2013 06:32 PM, Thomas Petazzoni wrote: > Dear Shawn J. Goff, > > On Mon, 04 Feb 2013 17:36:36 -0500, Shawn J. Goff wrote: >> I'm getting an error about a missing rpc_msg.h while building >> conntrack-tools. That package selects libtirpc if >> !BR2_TOOLCHAIN_HAS_NATIVE_RPC. I'm having BR build the toolchain using >> ct-ng; I looked at the toolchain-crosstool-ng/Config.in and it selects >> BR2_TOOLCHAIN_HAS_NATIVE_RPC because the ct-ng config that ships with BR >> uses glibc 2.9. My ct-ng config uses glibc 2.14, which doesn't have >> native RPC support. > Correct. > >> I started to make a patch that allows for explicitly selecting >> BR2_TOOLCHAIN_HAS_NATIVE_RPC like the external-toolchain allows, > Seems like the good solution yes. > >> but I >> ran across check_glibc function and the ext-toolchain-checked stamp and >> it looks like quite a lot, so I wanted to find out if you actually want >> all that for this fix. > What problems did you encounter exactly? It should be fairly similar to > what we do for external toolchains I believe, no? No problems, it just that when I started down the path, I thought it would be just an option, but there turned out to be this whole toolchain-checked thing behind it, so I wanted to make sure that is what's wanted before I do it. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Insufficient RPC options for crosstool-ng toolchain 2013-02-04 23:39 ` Shawn J. Goff @ 2013-02-04 23:49 ` Thomas Petazzoni 2013-02-06 22:06 ` Yann E. MORIN 0 siblings, 1 reply; 5+ messages in thread From: Thomas Petazzoni @ 2013-02-04 23:49 UTC (permalink / raw) To: buildroot Dear Shawn J. Goff, On Mon, 04 Feb 2013 18:39:43 -0500, Shawn J. Goff wrote: > No problems, it just that when I started down the path, I thought it > would be just an option, but there turned out to be this whole > toolchain-checked thing behind it, so I wanted to make sure that is > what's wanted before I do it. Yann will confirm or infirm, but since the glibc version selection is not done in Buildroot, but directly inside Crosstool-NG, there is no way for Buildroot to automatically now if the glibc of the toolchain will have RPC support or not. Therefore, the only practical solution is to have an option similar to the one we have in external toolchain, where we leave it to the user to say whether the toolchain generated by Crosstool-NG will have RPC support or not. However, I haven't thought in detail about the detailed impact on the implementation. Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Insufficient RPC options for crosstool-ng toolchain 2013-02-04 23:49 ` Thomas Petazzoni @ 2013-02-06 22:06 ` Yann E. MORIN 0 siblings, 0 replies; 5+ messages in thread From: Yann E. MORIN @ 2013-02-06 22:06 UTC (permalink / raw) To: buildroot Shawn, Thomas, All, On Tuesday 05 February 2013 Thomas Petazzoni wrote: > On Mon, 04 Feb 2013 18:39:43 -0500, Shawn J. Goff wrote: > > No problems, it just that when I started down the path, I thought it > > would be just an option, but there turned out to be this whole > > toolchain-checked thing behind it, so I wanted to make sure that is > > what's wanted before I do it. > > Yann will confirm or infirm, but since the glibc version selection is > not done in Buildroot, but directly inside Crosstool-NG, there is no > way for Buildroot to automatically now if the glibc of the toolchain > will have RPC support or not. Indeed. > Therefore, the only practical solution is > to have an option similar to the one we have in external toolchain, > where we leave it to the user to say whether the toolchain generated by > Crosstool-NG will have RPC support or not. I can't see any other solution either. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-02-06 22:06 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-02-04 22:36 [Buildroot] Insufficient RPC options for crosstool-ng toolchain Shawn J. Goff 2013-02-04 23:32 ` Thomas Petazzoni 2013-02-04 23:39 ` Shawn J. Goff 2013-02-04 23:49 ` Thomas Petazzoni 2013-02-06 22:06 ` Yann E. MORIN
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox