Re: 11-CURRENT build fail with base gcc

From: Oliver Pinter <oliver.pinter_at_hardenedbsd.org>
Date: Thu, 20 Aug 2015 18:27:29 +0200
On 8/20/15, Warner Losh <imp_at_bsdimp.com> wrote:
>
>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter <oliver.pinter_at_hardenedbsd.org>
>> wrote:
>>
>> On 8/20/15, Dimitry Andric <dim_at_freebsd.org> wrote:
>>> On 20 Aug 2015, at 00:56, Oliver Pinter <oliver.pinter_at_hardenedbsd.org>
>>> wrote:
>>>> 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.
>>>
>>> At what build stage is this error occuring?
>>
>> At 4.4 build everything:
>>
>> op_at_opn /tmp> grep '>>>' 11-current-with-gcc-fail.log
>>>>> World build started on Thu Aug 20 00:32:24 CEST 2015
>>>>> Rebuilding the temporary build tree
>>>>> stage 1.1: legacy release compatibility shims
>>>>> stage 1.2: bootstrap tools
>>>>> stage 2.1: cleaning up the object tree
>>>>> stage 2.2: rebuilding the object tree
>>>>> stage 2.3: build tools
>>>>> stage 3: cross tools
>>>>> stage 4.1: building includes
>>>>> stage 4.2: building libraries
>>>>> stage 4.3: make dependencies
>>>>> stage 4.4: building everything
>
> I think you are wrong about the cause. -mno-avx is bogusly listed
> unconditionally
> in efi/Makefile.inc. I’m working on a patch now…

Sure, you have right. Thanks Warner!

>
> Warner
>
>
Received on Thu Aug 20 2015 - 14:27:32 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:59 UTC