chromium-58.0.3029.110_1 fails to build with cllang40

Jan Beich jbeich at FreeBSD.org
Sun May 21 06:58:03 UTC 2017


Matthias Apitz <guru at unixarea.de> writes:

>> > The full log is here
>> >
>> > http://www.unixarea.de/chromium-58.0.3029.110_1.log.gz
[...]
>> > In file included from ../../services/ui/ws/user_activity_monitor.cc:5:
>> > In file included from ../../services/ui/ws/user_activity_monitor.h:8:
>> > In file included from ../../base/time/tick_clock.h:9:
>> > In file included from ../../base/time/time.h:62:
>> > In file included from ../../base/logging.h:12:
>> > In file included from /usr/include/c++/v1/sstream:174:
>> > In file included from /usr/include/c++/v1/ostream:138:
>> > In file included from /usr/include/c++/v1/ios:216:
>> > In file included from /usr/include/c++/v1/__locale:15:
>> > In file included from /usr/include/c++/v1/string:442:
>> > In file included from /usr/include/c++/v1/algorithm:633:
>> > /usr/include/c++/v1/utility:316:11: error: call to deleted constructor of 'mojo::InterfacePtr<ui::mojom::UserActivityObserver>'
>> >           second(__p.second)
>> >           ^      ~~~~~~~~~~
>> > /usr/include/c++/v1/memory:1747:31: note: in instantiation of member function 'std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >::pair' requested here
>> >             ::new((void*)__p) _Up(_VSTD::forward<_Args>(__args)...);
>> >                               ^
>> > /usr/include/c++/v1/memory:1658:18: note: in instantiation of function template specialization 'std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > >::construct<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >, const std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > &>' requested here
>> >             {__a.construct(__p, _VSTD::forward<_Args>(__args)...);}
>> >                  ^
>> > /usr/include/c++/v1/memory:1504:14: note: in instantiation of function template specialization 'std::__1::allocator_traits<std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > > >::__construct<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >, const std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > &>' requested here
>> >             {__construct(__has_construct<allocator_type, _Tp*, _Args...>(),
>> >              ^
>> > /usr/include/c++/v1/memory:1620:17: note: in instantiation of function template specialization 'std::__1::allocator_traits<std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > > >::construct<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >, const std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > &>' requested here
>> >                 construct(__a, _VSTD::__to_raw_pointer(__end2-1), _VSTD::move_if_noexcept(*--__end1));
>> >                 ^
>> > /usr/include/c++/v1/vector:892:21: note: in instantiation of function template specialization 'std::__1::allocator_traits<std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > > >::__construct_backward<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > *>' requested here
>> >     __alloc_traits::__construct_backward(this->__alloc(), this->__begin_, this->__end_, __v.__begin_);
>> >                     ^
>> > /usr/include/c++/v1/vector:1577:5: note: in instantiation of member function 'std::__1::vector<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >, std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > > >::__swap_out_circular_buffer' requested here
>> >     __swap_out_circular_buffer(__v);
>> >     ^
>> > /usr/include/c++/v1/vector:1614:9: note: in instantiation of function template specialization 'std::__1::vector<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >, std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > > >::__push_back_slow_path<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > >' requested here
>> >         __push_back_slow_path(_VSTD::move(__x));
>> >         ^
>> > ../../services/ui/ws/user_activity_monitor.cc:63:23: note: in instantiation of member function 'std::__1::vector<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> >, std::__1::allocator<std::__1::pair<ui::ws::UserActivityMonitor::ActivityObserverInfo, mojo::InterfacePtr<ui::mojom::UserActivityObserver> > > >::push_back' requested here
>> >   activity_observers_.push_back(std::make_pair(info, std::move(observer)));
>> >                       ^
>> > ../../mojo/public/cpp/bindings/interface_ptr.h:224:28: note: 'InterfacePtr' has been explicitly marked deleted here
>> >   DISALLOW_COPY_AND_ASSIGN(InterfacePtr);
>> >                            ^

Looks like https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217948

>> Mathias, what platform and version? I had no problem building with clang40
>> on 11-STABLE on amd64.
>
> Sorry. I'm on 12-CURRENT r314251 amd64. More details in the above log
> file.

That's before libc++ 4.0 merge. Arbitrarily old -CURRENT/-STABLE
snapshots are not supported (for any port). Either upgrade to latest
base revision or dowgrade the ports tree to a similar date.


More information about the freebsd-ports mailing list