Makefile show all flags

When porting software FreeBSD has a lot of internal makefiles that gets pulled in that setup the build environment: /usr/ports/Mk/* Is there a way to print out the env during the make process so that I can see what knobs, switches and flags were set before the build is run?

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

Am Sat, 9 Dec 2017 14:30:38 -0700 Warner Losh schrieb: > On Sat, Dec 9, 2017 at 1:47 PM, O. Hartmann wrote: > > > Am Sat, 9 Dec 2017 13:00:12 -0700 > > Warner Losh schrieb: > > > > > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

Am Sat, 9 Dec 2017 13:00:12 -0700 Warner Losh schrieb: > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen wrote: > > > > On 9. Dec 2017, at 19:41, O. Hartmann wrote: > > > > > > Running a PCengines APU2C4 with FreeBSD Current,

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

On Sat, Dec 9, 2017 at 6:35 PM, O. Hartmann wrote: > Am Sat, 9 Dec 2017 14:30:38 -0700 > Warner Losh schrieb: > > > On Sat, Dec 9, 2017 at 1:47 PM, O. Hartmann > wrote: > > > > > Am Sat, 9 Dec 2017 13:00:12 -0700 > > > Warner

Re: GPTZFSBOOT in Current r326622 has problems

Toomas Soome [tso...@me.com] wrote: > > > With BIOS boot you can try to press key (space or anything else except enter) > - if boot1 is good, you will get boot: prompt. > BTX fails a long time before boot1 is read. I don't even get a prompt for my Geli password. Tom -- Public Keys: PGP

Re: GPTZFSBOOT in Current r326622 has problems

Warner Losh [i...@bsdimp.com] wrote: > OK. I don't recall seeing a screen shot of the entire boot. Can you send > that too (privately if you like) so I know exactly what's failing? Is it > gptzfsboot loading /boot/loader? Is it early in /boot/laoder or > It is failing with a hex dump with a

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

> On 9. Dec 2017, at 21:00, Warner Losh wrote: > > > > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen wrote: > > On 9. Dec 2017, at 19:41, O. Hartmann wrote: > > > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

On Sat, Dec 9, 2017 at 1:47 PM, O. Hartmann wrote: > Am Sat, 9 Dec 2017 13:00:12 -0700 > Warner Losh schrieb: > > > On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen > wrote: > > > > > > On 9. Dec 2017, at 19:41, O. Hartmann

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

On Sat, Dec 9, 2017 at 12:58 PM, Warner Losh wrote: > > > On Sat, Dec 9, 2017 at 12:04 PM, Ed Schouten wrote: > >> 2017-12-09 19:41 GMT+01:00 O. Hartmann : >> > r326734 fails to boot, >> > r324234 works fine. >> > >> > What the heck has

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen wrote: > > On 9. Dec 2017, at 19:41, O. Hartmann wrote: > > > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to boot, > it gets stuck at > > the very first messages on the serial

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

On Sat, Dec 9, 2017 at 12:04 PM, Ed Schouten wrote: > 2017-12-09 19:41 GMT+01:00 O. Hartmann : > > r326734 fails to boot, > > r324234 works fine. > > > > What the heck has changed? > > Could you please try to bisect SVN revisions to figure out which exact >

Re: GPTZFSBOOT in Current r326622 has problems

> On 9 Dec 2017, at 19:56, Warner Losh wrote: > > On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote: > >> On 12/08/17 22:06, Warner Losh wrote: >>> >>> Clean build? >>> >> It was a clean build. I performed a rm -rf /usr/obj/* before starting >> the

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

> On 9. Dec 2017, at 19:41, O. Hartmann wrote: > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to boot, it > gets stuck at > the very first messages on the serial console prompting > > Consoles: internal video/keyboard > > and then nothing more. I

Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

2017-12-09 19:41 GMT+01:00 O. Hartmann : > r326734 fails to boot, > r324234 works fine. > > What the heck has changed? Could you please try to bisect SVN revisions to figure out which exact commit causes the problem? -- Ed Schouten Nuxi, 's-Hertogenbosch,

r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to boot, it gets stuck at the very first messages on the serial console prompting Consoles: internal video/keyboard and then nothing more. FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct 3 11:00:53 CEST 2017 amd64

Re: GPTZFSBOOT in Current r326622 has problems

On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote: > On 12/08/17 22:06, Warner Losh wrote: > > > > Clean build? > > > It was a clean build. I performed a rm -rf /usr/obj/* before starting > the buildworld after cvs updating to r326720. > > A couple of notes on my hardware: > > I

Re: reducing build times; selecting specific clang targets

Just my $0.02: On 12/09/17 02:50, Ed Schouten wrote: > Hi Michael, > > 2017-12-09 4:57 GMT+01:00 Michael Butler : >> As clang builds for multiple targets unconditionally, it takes *days* to >> build on one of my devices (700MHz Pentium-3). >> >> Is there a way to

Re: GPTZFSBOOT in Current r326622 has problems

On 12/08/17 22:06, Warner Losh wrote: > Clean build? > Here is the contents of my loader.conf: loader_logo="beastie" #Desired logo:orbbw, orb, fbsdbw, beastiebw, beastie, none aesni_load="YES" geom_eli_load="YES" kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0"

Re: GPTZFSBOOT in Current r326622 has problems

On 12/08/17 22:06, Warner Losh wrote: > > Clean build? > It was a clean build. I performed a rm -rf /usr/obj/* before starting the buildworld after cvs updating to r326720. A couple of notes on my hardware: I am not using UEFI and my CPU is an early Intel i5 Skylake that has the Silicon Debug

Re: reducing build times; selecting specific clang targets

On 12/09/17 02:50, Ed Schouten wrote: Hi Michael, 2017-12-09 4:57 GMT+01:00 Michael Butler : As clang builds for multiple targets unconditionally, it takes *days* to build on one of my devices (700MHz Pentium-3). Is there a way to restrict the build targets to