[esnacc-dev] [PATCH] cross-build: disable asn rose

[Aaron Conole]

Aaron Conole <aconole at bytheb.org> writes:

> When cross-compiling the system, it is not possible for the esnacc binary to
> correctly execute on the build system (well, not always).  There is a
> method to combat this, which is the approach gcc takes, to generate a stage
> one version of the compiler and then execute that to generate the final
> tools (stage 2).  That represents quite a bit of work.
>
> On the other hand, people are using esnacc *now* and as Marty Galligan
> reports at http://mail.esnacc.org/pipermail/dev/2017-July/000414.html there
> can be problems cross building, especially related to this.
>
> This commit detects that a cross-compilation is occuring and disables the
> generation of the asn.1 ROSE support.  A future commit can enable this
> when it becomes necessary.
>
> Reported-by: Marty Galligan <m_galligan at comcast.net>
> Signed-off-by: Aaron Conole <aconole at bytheb.org>
> ---

So, you'll notice that this is implemented without using --enable /
--disable for the ASN-ROSE feature.  If someone thinks that's a better
approach, I'm okay to include it, but I don't like being able to
configure away these kinds of built-in features (IE: there isn't any
real reason a user would ever build without --enable-asnrose - it's a
separate library in C++).

-Aaron