Re: 11-CURRENT build fail with base gcc

2015-08-21 Thread Eric van Gyzen
On 08/20/2015 14:21, Warner Losh wrote:
 
 On Aug 20, 2015, at 10:32 AM, Dimitry Andric d...@freebsd.org wrote:

 Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD
 variable, then?
 
 Perhaps. Didn’t know this was a thing. That could use useful many places, 
 though
 there were two clang specific args I needed to move, not just the one that’s 
 in this
 flag. Maybe things are over-specified?
 
 Not sure I like bsd.cpu.mk growing more name-space pollution, especially 
 stuff that
 isn’t documented somewhere (bsd.cpu.mk is included from sys.mk, which is 
 automaticallyed
 globally included).

I couldn't find any _good_ place for it, so I stuck it in the least bad place.  
I also didn't know where to document it.  I'll gladly move it and document it 
if someone can suggest good locations.

 All these hacks being stashed hither and yon are starting to get
 very hard to keep straight for someone who looks at this code every day, let 
 alone
 somebody who invested CFLAGS_NO_SIMD independently for their code and finds
 that breaks in an upgrade...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Eric van Gyzen
On 08/20/2015 11:32, Dimitry Andric wrote:
 On 20 Aug 2015, at 18:24, Warner Losh i...@bsdimp.com wrote:

 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…
 
 Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD
 variable, then?

Yes, probably so.

Eric
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Dimitry Andric
On 20 Aug 2015, at 00:56, Oliver Pinter oliver.pin...@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?

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Oliver Pinter
On 8/20/15, Dimitry Andric d...@freebsd.org wrote:
 On 20 Aug 2015, at 00:56, Oliver Pinter oliver.pin...@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@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


 -Dimitry


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Warner Losh

 On Aug 20, 2015, at 10:32 AM, Dimitry Andric d...@freebsd.org wrote:
 
 On 20 Aug 2015, at 18:24, Warner Losh i...@bsdimp.com wrote:
 
 On Aug 20, 2015, at 9:38 AM, Oliver Pinter oliver.pin...@hardenedbsd.org 
 wrote:
 ...
 
 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…
 
 Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD
 variable, then?

Perhaps. Didn’t know this was a thing. That could use useful many places, though
there were two clang specific args I needed to move, not just the one that’s in 
this
flag. Maybe things are over-specified?

Not sure I like bsd.cpu.mk growing more name-space pollution, especially stuff 
that
isn’t documented somewhere (bsd.cpu.mk is included from sys.mk, which is 
automaticallyed
globally included). All these hacks being stashed hither and yon are starting 
to get
very hard to keep straight for someone who looks at this code every day, let 
alone
somebody who invested CFLAGS_NO_SIMD independently for their code and finds
that breaks in an upgrade...

Warner



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Warner Losh

 On Aug 20, 2015, at 1:21 PM, Warner Losh i...@bsdimp.com wrote:
 
 
 On Aug 20, 2015, at 10:32 AM, Dimitry Andric d...@freebsd.org wrote:
 
 On 20 Aug 2015, at 18:24, Warner Losh i...@bsdimp.com wrote:
 
 On Aug 20, 2015, at 9:38 AM, Oliver Pinter oliver.pin...@hardenedbsd.org 
 wrote:
 ...
 
 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…
 
 Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD
 variable, then?
 
 Perhaps. Didn’t know this was a thing. That could use useful many places, 
 though
 there were two clang specific args I needed to move, not just the one that’s 
 in this
 flag. Maybe things are over-specified?
 
 Not sure I like bsd.cpu.mk growing more name-space pollution, especially 
 stuff that
 isn’t documented somewhere (bsd.cpu.mk is included from sys.mk, which is 
 automaticallyed
 globally included). All these hacks being stashed hither and yon are starting 
 to get
 very hard to keep straight for someone who looks at this code every day, let 
 alone
 somebody who invested CFLAGS_NO_SIMD independently for their code and finds
 that breaks in an upgrade...

Ah, it doesn’t include -mno-aes, but luckily that’s understood by both. Not 
sure why that’s
needed, but is that the same ‘class’ or no?

Warner



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Dimitry Andric
On 20 Aug 2015, at 18:24, Warner Losh i...@bsdimp.com wrote:
 
 On Aug 20, 2015, at 9:38 AM, Oliver Pinter oliver.pin...@hardenedbsd.org 
 wrote:
...
 
 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…

Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD
variable, then?

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Oliver Pinter
On 8/20/15, Warner Losh i...@bsdimp.com wrote:

 On Aug 20, 2015, at 9:38 AM, Oliver Pinter oliver.pin...@hardenedbsd.org
 wrote:

 On 8/20/15, Dimitry Andric d...@freebsd.org wrote:
 On 20 Aug 2015, at 00:56, Oliver Pinter oliver.pin...@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@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


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: 11-CURRENT build fail with base gcc

2015-08-20 Thread Warner Losh

 On Aug 20, 2015, at 9:38 AM, Oliver Pinter oliver.pin...@hardenedbsd.org 
 wrote:
 
 On 8/20/15, Dimitry Andric d...@freebsd.org wrote:
 On 20 Aug 2015, at 00:56, Oliver Pinter oliver.pin...@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@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…

Warner



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: 11-CURRENT build fail with base gcc

2015-08-19 Thread Julian Elischer

On 8/20/15 6:56 AM, Oliver Pinter wrote:

Hi All!

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


I thought that the switch do only allow clang had already been thrown...



--- 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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: 11-CURRENT build fail with base gcc

2015-08-19 Thread Warner Losh

 On Aug 19, 2015, at 8:36 PM, Julian Elischer jul...@freebsd.org wrote:
 
 On 8/20/15 6:56 AM, Oliver Pinter wrote:
 Hi All!
 
 I got this error, when I try to build recent 11-CURRENT with gcc on amd64 
 box:
 
 I thought that the switch do only allow clang had already been thrown…

Not even close. Clang is default, but gcc is still required for mips, for 
example. current
must still build with gcc on all architectures.

This looks to be a cross-threading issue, but one that should be easy to track 
down.

Warner

 
 --- 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
 ___
 freebsd-current@freebsd.org mailing list
 https://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
 
 



signature.asc
Description: Message signed with OpenPGP using GPGMail