Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Mon, Aug 26, 2019 at 02:57:56PM +0200, Kamil Rytarowski wrote: > On 25.08.2019 23:42, Thomas Klausner wrote: > > On Sun, Aug 25, 2019 at 05:32:32PM +0200, Kamil Rytarowski wrote: > >> On 25.08.2019 09:31, Thomas Klausner wrote: > >>> On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 25.08.2019 23:42, Thomas Klausner wrote: > On Sun, Aug 25, 2019 at 05:32:32PM +0200, Kamil Rytarowski wrote: >> On 25.08.2019 09:31, Thomas Klausner wrote: >>> On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: On 24.08.2019 14:51, Kamil Rytarowski wrote: > On 24.08.2019

re: amd64 build failed: constructor priorities from 0 to 100 are reserved

Kamil, > ? > external/bsd/compiler_rt/lib/clang/lib/netbsd/asan-dynamic-m32/asan_activation.d i recommend building from a r/o source tree for a few days :-) this becomes a built-time failure in that case. i recommend it to everyone, really. it has been a very long time but i used to guess

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: > I will try to reproduce and fix it. I saw you committed a fix, I'll test it now. A different issue: while I was updating for testing the fix, I saw lots of files where they shouldn't be. I run build.sh with '-O /somewhere', so

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Sun, Aug 25, 2019 at 05:32:32PM +0200, Kamil Rytarowski wrote: > On 25.08.2019 09:31, Thomas Klausner wrote: > > On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: > >> On 24.08.2019 14:51, Kamil Rytarowski wrote: > >>> On 24.08.2019 10:08, Thomas Klausner wrote: > On Sat,

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Sun, Aug 25, 2019 at 07:07:04PM +0200, Kamil Rytarowski wrote: > On 25.08.2019 17:32, Kamil Rytarowski wrote: > > On 25.08.2019 09:31, Thomas Klausner wrote: > >> On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: > >>> On 24.08.2019 14:51, Kamil Rytarowski wrote: > On

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 25.08.2019 17:32, Kamil Rytarowski wrote: > On 25.08.2019 09:31, Thomas Klausner wrote: >> On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: >>> On 24.08.2019 14:51, Kamil Rytarowski wrote: On 24.08.2019 10:08, Thomas Klausner wrote: > On Sat, Aug 24, 2019 at 08:49:59AM

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 25.08.2019 09:31, Thomas Klausner wrote: > On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: >> On 24.08.2019 14:51, Kamil Rytarowski wrote: >>> On 24.08.2019 10:08, Thomas Klausner wrote: On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: > On Fri, Aug

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: > On 24.08.2019 14:51, Kamil Rytarowski wrote: > > On 24.08.2019 10:08, Thomas Klausner wrote: > >> On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: > >>> On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 24.08.2019 14:51, Kamil Rytarowski wrote: > On 24.08.2019 10:08, Thomas Klausner wrote: >> On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: >>> On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: I will try to reproduce and fix it. >>> >>> I saw you committed

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 24.08.2019 10:08, Thomas Klausner wrote: > On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: >> On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: >>> I will try to reproduce and fix it. >> >> I saw you committed a fix, I'll test it now. > > I now see > > ---

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: > On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: > > I will try to reproduce and fix it. > > I saw you committed a fix, I'll test it now. I now see --- install-tsan_cxx-m64 --- x86_64--netbsd-install:

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 23.08.2019 16:10, Thomas Klausner wrote: > On Fri, Aug 23, 2019 at 04:03:01PM +0200, Kamil Rytarowski wrote: >> On 23.08.2019 11:41, Thomas Klausner wrote: >>> With a cvs checkout from about an our ago, an amd64 build failed for >>> me: >>> >>> --- dependall-safestack-m32 --- >>>

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On Fri, Aug 23, 2019 at 04:03:01PM +0200, Kamil Rytarowski wrote: > On 23.08.2019 11:41, Thomas Klausner wrote: > > With a cvs checkout from about an our ago, an amd64 build failed for > > me: > > > > --- dependall-safestack-m32 --- > >

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

On 23.08.2019 11:41, Thomas Klausner wrote: > With a cvs checkout from about an our ago, an amd64 build failed for > me: > > --- dependall-safestack-m32 --- > /usr/src/sys/external/bsd/compiler_rt/dist/lib/safestack/safestack.cc:271:23: > error: constructor priorities from 0 to 100 are reserved

amd64 build failed: constructor priorities from 0 to 100 are reserved

With a cvs checkout from about an our ago, an amd64 build failed for me: --- dependall-safestack-m32 --- /usr/src/sys/external/bsd/compiler_rt/dist/lib/safestack/safestack.cc:271:23: error: constructor priorities from 0 to 100 are reserved for the implementation [-Werror] void