Compiling the Source Code.

[Apelli]

Spoiler: Log

<...
checking whether to enable maintainer-specific portions of Makefiles... no
checking for arm-linux-gcc... mipsel-uclibc-gcc
checking whether the C compiler works... no
configure: error: in `/home/builderbot/asuswrt-merlin/release/src/router/wtfast/libev-4.20':
configure: error: C compiler cannot create executables
See `config.log' for more details
make[5]: *** [config.status] Error 77
make[5]: Leaving directory `/home/builderbot/asuswrt-merlin/release/src/router/wtfast/libev-4.20'
make[4]: *** [libev-4.20] Error 2
make[4]: Leaving directory `/home/builderbot/asuswrt-merlin/release/src/router/wtfast'
make[3]: *** [wtfast] Error 2
make[3]: Leaving directory `/home/builderbot/asuswrt-merlin/release/src/router'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/builderbot/asuswrt-merlin/release/src-rt-7.14.114.x/src'
make[1]: *** [bin] Error 2
make[1]: Leaving directory `/home/builderbot/asuswrt-merlin/release/src-rt-7.14.114.x/src'
make: *** [rt-ac88u] Error 2
...>

Hello, everyone.

I am getting this error every time, after verifying git source, downloading every package ever said to be needed for compilation, on i686 Debian 7.2, although when I was compiling 380.58 alpha 3 a while ago, all went without a hitch after fixing netatalk 3.0.5 (the fix is somewhere on the forum), I fixed it this time too, but it dies later on this wt****fast.
The question is, how can I fix it, or the other way, if there is no solution currently available, how can I rip the wtffast from my router - 2 birds with 1 stone, never needed some ****ty VPN for gaming on my router, especially when I have a year's worth subscription to a good provider and an OpenVPN package installed.

 

[RMerlin]

See `config.log' for more details

This will tell you more info as to what is failing.

To remove wtfast, set WTFAST=n in the target.mak profile, delete the .config file and rebuild.

 

[Apelli]

Thanks for the fast reply!

config.log output was rather the same, but this part made me interested.
If I am right, it tried to find an arm compiler, but somehow found mips compiler, and tried to use it, with clear consequences.

Spoiler: config.log

configure:2387: result: yes
configure:2446: checking for arm-linux-strip
configure:2473: result: mipsel-uclibc-strip -R .note -R .comment
configure:2538: checking for a thread-safe mkdir -p
configure:2577: result: /bin/mkdir -p
configure:2584: checking for gawk
configure:2600: found /usr/bin/gawk
configure:2611: result: gawk
configure:2622: checking whether make sets $(MAKE)
configure:2644: result: yes
configure:2673: checking whether make supports nested variables
configure:2690: result: yes
configure:2820: checking whether to enable maintainer-specific portions of Makefiles
configure:2829: result: no
configure:2851: checking for arm-linux-gcc
configure:2878: result: mipsel-uclibc-gcc
configure:3147: checking for C compiler version
configure:3156: mipsel-uclibc-gcc --version >&5
./configure: line 3158: mipsel-uclibc-gcc: command not found
configure:3167: $? = 127
configure:3156: mipsel-uclibc-gcc -v >&5
./configure: line 3158: mipsel-uclibc-gcc: command not found
configure:3167: $? = 127
configure:3156: mipsel-uclibc-gcc -V >&5
./configure: line 3158: mipsel-uclibc-gcc: command not found
configure:3167: $? = 127
configure:3156: mipsel-uclibc-gcc -qversion >&5
./configure: line 3158: mipsel-uclibc-gcc: command not found
configure:3167: $? = 127
configure:3187: checking whether the C compiler works
configure:3209: mipsel-uclibc-gcc -DBCMWPA2 -DBCMQOS -DBCM_DCS -DEXT_ACS -DD11AC_IOTYPES -DPHYMON -DPROXYARP -DTRAFFIC_MGMT -DTRAFFIC_MGMT_RSSI_POLICY -DLINUX26 -DCONFIG_BCMWL5 -DDEBUG_NOISY -DDEBUG_RCTEST -pipe -DBCMWPA2 -funit-at-a-ti$
./configure: line 3211: mipsel-uclibc-gcc: command not found
configure:3213: $? = 127
configure:3251: result: no
configure: failed program was:

Would love a confirmation of my theory!

 

[RMerlin]

It did try to use the wrong compiler indeed. Make sure you don't have some leftovers from a previous MIPS-based compile, and that your toolchain is properly configured.