Insufficient RPC options for crosstool-ng toolchain

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.

Dear Shawn J. Goff,

Quoted 7 lines · Shawn J. Goff

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.

Quoted 2 lines

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.

Quoted 4 lines

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.

Quoted 4 lines · Shawn J. Goff

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.