Re: build.sh: fails at step "link clang/clang"

2019-08-30 Thread Joerg Sonnenberger
On Fri, Aug 30, 2019 at 12:09:17PM +0200, Manuel Bouyer wrote: > clang is known to need *lots* of ram It's not clang, it is ld. It's ~540MB peak RSS here for a non-debug build. Debug builds are much worse though. Joerg

Re: build.sh: fails at step "link clang/clang"

2019-08-30 Thread N
Manuel Bouyer transcribed 1.0K bytes: > On Fri, Aug 30, 2019 at 10:04:47AM +, N wrote: > > It appears that the web report form of gnats is having problems at > > the moment, and report-pr(1) needs more pasting: > > > > > > on am64 8.1 release with gcc, while trying to upgrade to current with

Re: build.sh: fails at step "link clang/clang"

2019-08-30 Thread Manuel Bouyer
On Fri, Aug 30, 2019 at 10:04:47AM +, N wrote: > It appears that the web report form of gnats is having problems at > the moment, and report-pr(1) needs more pasting: > > > on am64 8.1 release with gcc, while trying to upgrade to current with clang: > I'm attempting to go from 8.1 release

build.sh: fails at step "link clang/clang"

2019-08-30 Thread N
It appears that the web report form of gnats is having problems at the moment, and report-pr(1) needs more pasting: on am64 8.1 release with gcc, while trying to upgrade to current with clang: I'm attempting to go from 8.1 release gcc to current with clang: NetBSD localhost 8.1_RC1 NetBSD