You receive this bug because this package does not respect my system's CC ( x86_64-pc-linux-gnu-gcc - /usr/bin/x86_64-pc-linux-gnu-gcc ) and calls directly gcc -/usr/bin/gcc The possible solutions to fix this issue are: 1)Fix the buildsystem, if you can 2)inherit toolchain-funcs and use tc-export CC 3)inherit toolchain-funcs and use emake CC="$(tc-getCC)" gcc -march=native -O2 -g0 -pipe -Wall -pipe `pkg-config --cflags gtk+-2.0` -c crypto.c -DVERSION=\"0.97\" -DHAVE_CONFIG_H gcc -march=native -O2 -g0 -pipe -Wall -pipe `pkg-config --cflags gtk+-2.0` -c gui.c -DVERSION=\"0.97\" -DHAVE_CONFIG_H gcc -march=native -O2 -g0 -pipe -Wall -pipe `pkg-config --cflags gtk+-2.0` -c callbacks.c -DVERSION=\"0.97\" -DHAVE_CONFIG_H gcc -march=native -O2 -g0 -pipe -Wall -pipe `pkg-config --cflags gtk+-2.0` -c utility.c -DVERSION=\"0.97\" -DHAVE_CONFIG_H gcc -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu -march=native -O2 -g0 -pipe -Wall -pipe `pkg-config --cflags gtk+-2.0` crypto.o gui.o callbacks.o utility.o -o otpCalc `pkg-config --libs gtk+-2.0` -lcrypto -DVERSION=\"0.97\" -DHAVE_CONFIG_H
The usual problem with autoconf 2.13. Fixed, thanks.
(In reply to comment #1) > The usual problem with autoconf 2.13. > Fixed, thanks. Not fixed. Looks at configure phase, it does the test with gcc and compiles with $CC: checking whether the C compiler (gcc -march=native -O2 -g0 -pipe -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu) works... yes checking whether the C compiler (gcc -march=native -O2 -g0 -pipe -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu) is a cross-compiler... no
Fixed again.