Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Aug 2015 00:56:28 +0200
From:      Oliver Pinter <oliver.pinter@hardenedbsd.org>
To:        current@freebsd.org
Cc:        imp@freebsd.org
Subject:   11-CURRENT build fail with base gcc
Message-ID:  <CAPQ4ffuNzYQJHxuGKcJ%2BG5b47n-c7DjS6DJX9FrQFu9GGPrpbQ@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
Hi All!

I got this error, when I try to build recent 11-CURRENT with gcc on amd64 box:

--- delay.o ---
cc   -O2 -pipe   -fPIC -mno-red-zone
-I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../include
-I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../include/amd64
-I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../../../../lib/libstand
-I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../../common
-fformat-extensions -ffreestanding -Wformat -msoft-float -fshort-wchar
-mno-red-zone -mno-mmx -mno-sse -mno-aes -mno-avx -std=gnu99     -c
/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/delay.c -o
delay.o
cc1: error: unrecognized command line option "-mno-avx"

You can access a full build log here:
http://jenkins.hardenedbsd.org/~op/11-current-with-gcc-fail.log .

Seems like the build environment passed a wrong COMPILER_TYPE to
bsd.sys.mk: clang instead of gcc, and that's why the -mno-avx occurs
in the compiler options.

I use the following options in src.conf to build the system with gcc:
WITHOUT_CLANG_BOOTSTRAP=
WITHOUT_CLANG_IS_CC=
WITHOUT_CLANG=
WITH_GCC_BOOTSTRAP=
WITH_GCC=

and the host system is a 11-CURRENT system, which builded with clang.

Thanks,
Oliver



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPQ4ffuNzYQJHxuGKcJ%2BG5b47n-c7DjS6DJX9FrQFu9GGPrpbQ>