Re: Inability to build FreeBSD-current amd64

2019-05-18 Thread Thomas Mueller
from Niclas Zeising:


So now I wonder why I failed four times straight building current.  One 
definition of insanity is doing the same thing repeatedly and expecting a 
different result.

Maybe the build host, 11.1-STABLE from July 30, 2017, was too old?  I wouldn't 
have thought it was too old.

I could also try an old current host from August 2, 2017, or try to build 
12-STABLE from my 11.1-STABLE host.  Would I do better to build amd64 or i386 
from amd64 host?  I presently have no FreeBSD i386 installation, only amd64.

I can't quote anything from your message because of problems with mutt on 
xterm; this is NetBSD 8.99.39 amd64 with icewm.

But here is the relevant error message, I believe:

===> usr.bin/clang/llvm-mca (all)
Warning: Object directory not changed from original 
/usr/src/usr.bin/clang/llvm-mca
c++  -target x86_64-unknown-freebsd13.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe 
-I/usr/src/contrib/llvm/tools/llvm-mca 
-I/usr/obj/usr/src/amd64.amd64/lib/clang/libllvm -I/usr/src/lib/clang/include 
-I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS 
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd13.0\" 
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd13.0\" -DDEFAULT_SYSROOT=\"\" 
-DLLVM_TARGET_ENABLE_AARCH64 -DLLVM_TARGET_ENABLE_ARM -DLLVM_TARGET_ENABLE_MIPS 
-DLLVM_TARGET_ENABLE_POWERPC -DLLVM_TARGET_ENABLE_SPARC 
-DLLVM_TARGET_ENABLE_X86 -DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser 
-DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter 
-DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler 
-DLLVM_NATIVE_TARGET=LLVMInitializeX86Target 
-DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo 
-DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -ffunction-sections 
-fdata-sections -g
 line-tables-only -MD -MF.depend.Views_DispatchStatistics.o 
-MTViews/DispatchStatistics.o -fstack-protector-strong -Wno-empty-body 
-Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare 
-Wno-unused-value -Wno-parentheses-equality -Wno-unused-function 
-Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member 
-Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses 
-Qunused-arguments  -fno-exceptions -fno-rtti -std=c++11 -stdlib=libc++ 
-Wno-c++11-extensions  -c 
/usr/src/contrib/llvm/tools/llvm-mca/Views/DispatchStatistics.cpp -o 
Views/DispatchStatistics.o
error: unable to open output file 'Views/DispatchStatistics.o': 'No such file 
or directory'
1 error generated.
*** Error code 1

I switched to the other computer with an installation of FreeBSD-current from 
August 2, 2017, and managed to succeed.

I had the same mergemaster problem cited in another thread, copied 
etc/master.passwd and etc/group from the 12-STABLE src tree.

That enabled me to successfully get through the update, but the result was a 
strong negative selling point for FreeBSD: no internet access.

Ethernet (re) would not connect, Hiro H50191 USB wi-fi adapter gave "Device not 
configured" as rsu0, and Edimax USB wi-fi adapter dropped the connection as I 
was trying the dhclient or ifconfig step.  Only other thing I could try is 
urndis with my mobile phone as access point.  I really ought to try that on 
FreeBSD and/or NetBSD.

I thought maybe the lack of etc/master.passwd and etc/group in src tree was a 
fault of subversion on NetBSD from pkgsrc as opposed to subversion on FreeBSD 
from ports, but browsing svnweb.freebsd.org/base/head revealed that 
master.passwd and group had indeed been moved, and mergemaster had not been 
appropriately updated.

Tom

___
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: Inability to build FreeBSD-current amd64

2019-05-16 Thread Niclas Zeising

On 2019-05-16 09:36, Thomas Mueller wrote:

from Niclas Zeising:


I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if
that's what you're asking about.
  

This won't take away the need for llvm ports in certain ports builds, however,
such as firefox and mesa.


So now I wonder why I failed four times straight building current.  One 
definition of insanity is doing the same thing repeatedly and expecting a 
different result.

Maybe the build host, 11.1-STABLE from July 30, 2017, was too old?  I wouldn't 
have thought it was too old.

I could also try an old current host from August 2, 2017, or try to build 
12-STABLE from my 11.1-STABLE host.  Would I do better to build amd64 or i386 
from amd64 host?  I presently have no FreeBSD i386 installation, only amd64.



That could be that the toolchain on 11.1 stable is too old to build 
current.  If you've posted the error you're getting, I've missed it, 
however.

Regards
--
Niclas
___
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: Inability to build FreeBSD-current amd64

2019-05-16 Thread Thomas Mueller
from Niclas Zeising:

> I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if
> that's what you're asking about.
 
> This won't take away the need for llvm ports in certain ports builds, however,
> such as firefox and mesa.

So now I wonder why I failed four times straight building current.  One 
definition of insanity is doing the same thing repeatedly and expecting a 
different result.

Maybe the build host, 11.1-STABLE from July 30, 2017, was too old?  I wouldn't 
have thought it was too old.

I could also try an old current host from August 2, 2017, or try to build 
12-STABLE from my 11.1-STABLE host.  Would I do better to build amd64 or i386 
from amd64 host?  I presently have no FreeBSD i386 installation, only amd64.

Tom

___
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: Inability to build FreeBSD-current amd64

2019-05-16 Thread Niclas Zeising

On 2019-05-16 03:46, Thomas Mueller wrote:

In general, WITH_CLANG_EXTRAS controls the building of extra tools such
as a disassembler, and tools for working on clang itself such as bug
reporting tools.  I don't have a really detailed answer because I've
never enabled the option.  I've always perceived it as being something
most people don't need.  WITHOUT_CLANG_EXTRAS may cut some time from
your build, but it probably won't cut it in half or anything.



- Ian


I am not concerned about the time to build CLANG_EXTRAS so much as the 
possibility of CLANG_EXTRAS stopping the build.

WITH_CLANG_EXTRAS worked back in July-August 2017, but it may have ballooned 
since then beyond FreeBSD buildability.



I run a build WITH_CLANG_EXTRAS, and that worked, on current, last 
weekend, if that's what you're asking about.


This won't take away the need for llvm ports in certain ports builds, 
however, such as firefox and mesa.


Regards
--
Niclas
___
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: Inability to build FreeBSD-current amd64

2019-05-15 Thread Thomas Mueller
> In general, WITH_CLANG_EXTRAS controls the building of extra tools such
> as a disassembler, and tools for working on clang itself such as bug
> reporting tools.  I don't have a really detailed answer because I've
> never enabled the option.  I've always perceived it as being something
> most people don't need.  WITHOUT_CLANG_EXTRAS may cut some time from
> your build, but it probably won't cut it in half or anything.

>- Ian  

I am not concerned about the time to build CLANG_EXTRAS so much as the 
possibility of CLANG_EXTRAS stopping the build.

WITH_CLANG_EXTRAS worked back in July-August 2017, but it may have ballooned 
since then beyond FreeBSD buildability.


Tom

___
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: Inability to build FreeBSD-current amd64

2019-05-15 Thread Ian Lepore
On Wed, 2019-05-15 at 23:23 +, Thomas Mueller wrote:
> What do most FreeBSD users who rebuild system from source do
> regarding WITH_CLANG_EXTRAS in /etc/src.conf ?
> 
> I have WITH_CLANG_EXTRAS=yes in /etc/src.conf and wonder if that
> could be screwing my build.
> 
> Build seems to stumble on the llvm stuff, and llvm has really bloated
> in recent times.
> 
> But then if I remove WITH_CLANG_EXTRAS, would I face great trouble
> with llvm in the ports, where llvm is so critical to the bigger
> things including Xorg?
> 
> Would removing WITH_CLANG_EXTRAS also reduce the build time which has
> been around 6:45 (hours:minutes) just to fail?
> 
> 
> Tom
> 

In general, WITH_CLANG_EXTRAS controls the building of extra tools such
as a disassembler, and tools for working on clang itself such as bug
reporting tools.  I don't have a really detailed answer because I've
never enabled the option.  I've always perceived it as being something
most people don't need.  WITHOUT_CLANG_EXTRAS may cut some time from
your build, but it probably won't cut it in half or anything.

-- Ian


___
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: Inability to build FreeBSD-current amd64

2019-05-15 Thread Thomas Mueller
What do most FreeBSD users who rebuild system from source do regarding 
WITH_CLANG_EXTRAS in /etc/src.conf ?

I have WITH_CLANG_EXTRAS=yes in /etc/src.conf and wonder if that could be 
screwing my build.

Build seems to stumble on the llvm stuff, and llvm has really bloated in recent 
times.

But then if I remove WITH_CLANG_EXTRAS, would I face great trouble with llvm in 
the ports, where llvm is so critical to the bigger things including Xorg?

Would removing WITH_CLANG_EXTRAS also reduce the build time which has been 
around 6:45 (hours:minutes) just to fail?


Tom

___
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: Inability to build FreeBSD-current amd64

2019-05-15 Thread Ian Lepore
On Wed, 2019-05-15 at 19:26 +, Thomas Mueller wrote:
> from tech-lists:
> 
> > What do you do before buildworld?
> 
> 
> > I'll rm -rf /usr/obj and /var/cache/ccache [1], create them again,
> > then in
> > /usr/src I'll do this:
> > make -j32 cleanworld && make -j32 cleandir && make -j32 clean
> 
> 
> > before make buildworld. it's probably overkill but it'll for sure
> > clean
> > away any cruft
> > [1] make sure they get deleted without error. I've encountered
> > bad_file_descriptor error in ccache dir before and it caused all
> > kinds
> > of errors when building, which looked like build errors but obv.
> > were
> > not.
> 
> I did rm -R /usr/obj/* , so everything there was clean as far as I
> could see.
> 
> I had no /var/cache/cache .
> 
> I could still try to build current from the old current from August
> 2, 2017, or STABLE-12 from the old 11.1-STABLE from July 30, 2017.
> 
> Otherwise I still have stuff to do with NetBSD and Linux toolchains
> (OpenWRT, buildroot, crosstool-ng and ptxdist from Pengutronix).
> 
> Is there anything comparable to 
> https://releng.netbsd.org/cgi-bin/builds.cgi , but for FreeBSD?
> 
> If I see 0 passed, 67 failed for NetBSD-HEAD, I figure I should wait
> for a better time.  But what about FreeBSD?
> 
> Tom

A couple different views on the freebsd build CI...

https://ci.freebsd.org/
https://ci.freebsd.org/tinderbox/

-- Ian


___
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: Inability to build FreeBSD-current amd64

2019-05-15 Thread Thomas Mueller
from tech-lists:

> What do you do before buildworld?

> I'll rm -rf /usr/obj and /var/cache/ccache [1], create them again, then in
> /usr/src I'll do this:

> make -j32 cleanworld && make -j32 cleandir && make -j32 clean

> before make buildworld. it's probably overkill but it'll for sure clean
> away any cruft

> [1] make sure they get deleted without error. I've encountered
> bad_file_descriptor error in ccache dir before and it caused all kinds
> of errors when building, which looked like build errors but obv. were
> not.

I did rm -R /usr/obj/* , so everything there was clean as far as I could see.

I had no /var/cache/cache .

I could still try to build current from the old current from August 2, 2017, or 
STABLE-12 from the old 11.1-STABLE from July 30, 2017.

Otherwise I still have stuff to do with NetBSD and Linux toolchains (OpenWRT, 
buildroot, crosstool-ng and ptxdist from Pengutronix).

Is there anything comparable to https://releng.netbsd.org/cgi-bin/builds.cgi , 
but for FreeBSD?

If I see 0 passed, 67 failed for NetBSD-HEAD, I figure I should wait for a 
better time.  But what about FreeBSD?

Tom

___
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: Inability to build FreeBSD-current amd64

2019-05-15 Thread tech-lists

On Wed, May 15, 2019 at 06:46:04AM +, Thomas Mueller wrote:

Hi Tom,
Are you using any nonstandard build options/modes?
Cheers!
-Enji


I don't think I am using any nonstandard build options/modes.


[...]


Build didn't even start when I had WITHOUT_MANCOMPRESS on.



Trouble occurs before there is any attempt to build the kernel.


hi,

What do you do before buildworld?

I'll rm -rf /usr/obj and /var/cache/ccache [1], create them again, then in
/usr/src I'll do this:

make -j32 cleanworld && make -j32 cleandir && make -j32 clean

before make buildworld. it's probably overkill but it'll for sure clean
away any cruft

[1] make sure they get deleted without error. I've encountered
bad_file_descriptor error in ccache dir before and it caused all kinds
of errors when building, which looked like build errors but obv. were
not.

--
J.


signature.asc
Description: PGP signature


Re: Inability to build FreeBSD-current amd64

2019-05-15 Thread Thomas Mueller
> Hi Tom,
> Are you using any nonstandard build options/modes?
> Cheers!
> -Enji

I don't think I am using any nonstandard build options/modes.

/etc/src.conf is

WITHOUT_SVNLITE=yes
WITHOUT_PORTSNAP=yes
#WITHOUT_MANCOMPRESS=yes
#WITHOUT_DOCCOMPRESS=yes
WITHOUT_SENDMAIL=yes
WITH_CLANG_EXTRAS=yes
WITH_LLD_IS_LD=yes

/etc/make.conf is

PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=${.CURDIR}/work11.amd64
#MANCOMPRESSED=no
#MK_MANCOMPRESS="no"
#WITHOUT_MANCOMPRESS=yes
MAKE_JOBS_UNSAFE=yes
FORCE_PKG_REGISTER=yes
# WITH_PKGNG=yes
OPTIONS_SET.mpop=GNUTLS NLS
WITH_BDB_VER=6
WITH_SSP_PORTS=yes
DEFAULT_VERSIONS+= perl5=5.28
DISABLE_VULNERABILITIES=yes

Build didn't even start when I had WITHOUT_MANCOMPRESS on.

Trouble occurs before there is any attempt to build the kernel.

Tom

___
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: Inability to build FreeBSD-current amd64

2019-05-14 Thread Enji Cooper


> On May 14, 2019, at 13:18, Thomas Mueller  wrote:
> 
> I have failed in three attempts over the past week to build FreeBSD-current 
> amd64, error message is about the same each time.
> 
> Build host uname -a shows
> 
> FreeBSD amelia 11.1-STABLE FreeBSD 11.1-STABLE #4: Sun Jul 30 17:28:39 UTC 
> 2017 root@amelia2:/usr/obj/BETA1/usr/src11/sys/SANDY11NC  amd64
> 
> Is there a known snag?  Would I do better to attempt to build 12-STABLE, or 
> use a FreeBSD-current installation from August 2, 2017 as host?
> 
> Snag seems related to llwm, which has been a troublemaker.

Hi Tom,
Are you using any nonstandard build options/modes?
Cheers!
-Enji
___
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"