You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to compile FRR for my Linksys WRT1200AC at home. And autoconf is not able to set correct build parameter for cross-compilation.. It fails will the following error:
I know this is an issue solved in the past in #958 but I'm not able to find my way in. I tried the suggestion but none of them works.. And it still tries to run my own gcc compiler, even if I overwrite --build="$(GNU_HOST_NAME)" in the `CONFIGURE_ARGS´
checking build system type... x86_64-redhat-linux-gnu
Thanks for the support !
The text was updated successfully, but these errors were encountered:
Hey - just wanted to say I've seen this issue and want to nail down our process for cross compiling (and document it!), I just haven't gotten around to it yet. Did you manage to get it built?
It is giving an error message detailing what to do:
configure: error: cross-compilation is only possible with builddir separate from srcdir. create a separate directory and run as .../path-to-frr/configure.
So to address this, when you are in the frr dir, run:
mkdir ../frr-build
cd ../frr-build
../frr/configure
You might run into other cross-compile issues, but this should address the error message you are seeing
Hi everyone !
I'm trying to compile FRR for my Linksys WRT1200AC at home. And autoconf is not able to set correct build parameter for cross-compilation.. It fails will the following error:
The following FRR package I'm trying to compile is available on my github repository here: https://github.com/lion24/frr-openwrt
I know this is an issue solved in the past in #958 but I'm not able to find my way in. I tried the suggestion but none of them works.. And it still tries to run my own gcc compiler, even if I overwrite
--build="$(GNU_HOST_NAME)"
in the `CONFIGURE_ARGS´Thanks for the support !
The text was updated successfully, but these errors were encountered: