In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/random.cpp:15:
In file included from ../../libcxx/include/random:1642:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/random.cpp:15:
In file included from ../../libcxx/include/random:1642:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/random.cpp:15:
In file included from ../../libcxx/include/random:1642:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/regex.cpp:10:
In file included from ../../libcxx/include/regex:757:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/regex.cpp:10:
In file included from ../../libcxx/include/regex:757:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/regex.cpp:10:
In file included from ../../libcxx/include/regex:757:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/regex.cpp:10:
In file included from ../../libcxx/include/regex:757:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/shared_mutex.cpp:14:
In file included from ../../libcxx/include/shared_mutex:130:
In file included from ../../libcxx/include/__mutex_base:16:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/shared_mutex.cpp:14:
In file included from ../../libcxx/include/shared_mutex:130:
In file included from ../../libcxx/include/__mutex_base:16:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/shared_mutex.cpp:14:
In file included from ../../libcxx/include/shared_mutex:130:
In file included from ../../libcxx/include/__mutex_base:16:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/shared_mutex.cpp:14:
In file included from ../../libcxx/include/shared_mutex:130:
In file included from ../../libcxx/include/__mutex_base:16:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/stdexcept.cpp:12:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/stdexcept.cpp:12:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/stdexcept.cpp:12:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/stdexcept.cpp:12:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/string.cpp:10:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/string.cpp:10:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/string.cpp:10:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/string.cpp:10:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/strstream.cpp:10:
In file included from ../../libcxx/include/strstream:131:
In file included from ../../libcxx/include/ostream:138:
In file included from ../../libcxx/include/ios:216:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/strstream.cpp:10:
In file included from ../../libcxx/include/strstream:131:
In file included from ../../libcxx/include/ostream:138:
In file included from ../../libcxx/include/ios:216:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/strstream.cpp:10:
In file included from ../../libcxx/include/strstream:131:
In file included from ../../libcxx/include/ostream:138:
In file included from ../../libcxx/include/ios:216:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/strstream.cpp:10:
In file included from ../../libcxx/include/strstream:131:
In file included from ../../libcxx/include/ostream:138:
In file included from ../../libcxx/include/ios:216:
In file included from ../../libcxx/include/__locale:15:
In file included from ../../libcxx/include/string:439:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/system_error.cpp:13:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/system_error.cpp:13:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/system_error.cpp:13:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/system_error.cpp:13:
In file included from ../../libcxx/include/system_error:225:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/thread.cpp:13:
In file included from ../../libcxx/include/thread:90:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/thread.cpp:13:
In file included from ../../libcxx/include/thread:90:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/thread.cpp:13:
In file included from ../../libcxx/include/thread:90:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/thread.cpp:13:
In file included from ../../libcxx/include/thread:90:
In file included from ../../libcxx/include/__functional_base:18:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.
In file included from ../../libcxx/src/valarray.cpp:10:
In file included from ../../libcxx/include/valarray:346:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:131:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new(std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/valarray.cpp:10:
In file included from ../../libcxx/include/valarray:346:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:137:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete(void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/valarray.cpp:10:
In file included from ../../libcxx/include/valarray:346:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:144:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void* operator new[](std::size_t __sz)
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
In file included from ../../libcxx/src/valarray.cpp:10:
In file included from ../../libcxx/include/valarray:346:
In file included from ../../libcxx/include/algorithm:628:
In file included from ../../libcxx/include/memory:603:
../../libcxx/include/new:150:1: error: visibility does not match previous
      declaration
_LIBCPP_NEW_DELETE_VIS void  operator delete[](void* __p) _NOEXCEPT;
^
../../libcxx/include/new:128:33: note: expanded from macro
      '_LIBCPP_NEW_DELETE_VIS'
# define _LIBCPP_NEW_DELETE_VIS _LIBCPP_FUNC_VIS
                                ^
../../libcxx/include/__config:200:42: note: expanded from macro
      '_LIBCPP_FUNC_VIS'
#define _LIBCPP_FUNC_VIS __attribute__ ((__visibility__("hidden")))
                                         ^
note: previous attribute is here
4 errors generated.

It seems on pair with was written in the script (that their clang would fail).

So it seems that c++ is an alias for the system's default C++ compiler. You can try modifying the CXX variable in the script to use Homebrew's clang++ (though the visibility errors are probably not specific to Google's clang). Then you can modify it to use g++.

As you expected, those errors are no specific to Google's clang. I tried building it using Homebrew's clangs (both 3.8 and 4.0 versions) as well as g++, got more or less the same output on all of them (a bunch of visibility errors).

Does g++ point to GCC's C++ compiler, or is it also an alias for clang++?

Seems to be pointing to Xcode's clang++ too.

Well no wonder. Could you try installing GCC from homebrew and try compiling with its g++?

I installed gcc 4.9, and got a bunch of errors like this:
/var/folders/jy/d01dhkjj3wq4k42p92kvd19m0000gn/T//ccGYsKMX.s:603:7: error: register %rbp is only available in 64-bit mode
Thats strange, because I pointed to the x86_64 version:
CXX=/usr/local/Cellar/gcc49/4.9.3/bin/x86_64-apple-darwin15.4.0-g++-4.9

Could you revert CXX back to c++ and comment out all of the sed lines?

It did the job!
The script fails later by trying to upload the generated library to Google server, but it doesn't really matter since the libc++.a library is generated.
It didn't copy it to the out/Release folder, though. What supposed to do that?
(heres the missing script
 build.sh: line 50: upload_to_google_storage.py: command not found

Yeah I forgot to tell you to comment that out too. And libc++.a is supposed to go to third_party/libc++-static since that's the default path that common.gypi uses to look for it. So it looks like we just need to comment out these lines and invoke it as part of the build process.
So it looks like we need to assemble all of the GYP flags we used, download those two Mac directories, and invoke this script to make Mac building work properly. Did I miss anything else?
Oh and what archive format should I use to contain the resulting binaries? If Mac supports zip files in their archive utility already, that will make things easier (since I will be adapting the Windows buildlib code for doing this).

Yes, OS X supports zip ootb.
Here are the GYP flags used:
werror=
default_apps_list=[]
default_apps_list_linux_dest=[]
remoting=0
disable_nacl=1
disable_pnacl=1
disable_newlib=1
enable_remoting_host=0
enable_automation=0
enable_google_now=0
safe_browsing=0
enable_webrtc=0
remoting=0
enable_hotwording=0
enable_hangout_services_extension=0
enable_wifi_bootstrapping=0
use_official_google_api_keys=0
enable_rlz=0
enable_pre_sync_backup=0
enable_prod_wallet_service=0
enable_one_click_signin=0
enable_hidpi=1
fastbuild=1
disable_fatal_linker_warnings=1
tracing_like_official_build=1
fieldtrial_testing_like_official_build=1
linux_strip_binary=1
proprietary_codecs=1
ffmpeg_branding=Chrome
remove_webcore_debug_symbols=1
clang_dir=/usr/local/Cellar/llvm38/HEAD-051e787/lib/llvm-3.8/bin
make_clang_dir=/usr/local/Cellar/llvm38/HEAD-051e787/lib/llvm-3.8/
clang_use_chrome_plugins=0
clang=1
host_cc=/usr/local/Cellar/llvm38/HEAD-051e787/lib/llvm-3.8/bin/clang
CC=/usr/local/Cellar/llvm38/HEAD-051e787/lib/llvm-3.8/bin/clang
host_cxx=/usr/local/Cellar/llvm38/HEAD-051e787/lib/llvm-3.8/bin/clang++
LDPLUSPLUS=/usr/local/Cellar/llvm38/HEAD-051e787/lib/llvm-3.8/bin/clang++

I'm uploading the Mac-only folders I copied from the old build.
So, here are the things we should remember to make general instructions to build it:

The user needs to install GNU Patch through Homebrew;
The user needs to install llvm38 through Homebrew with those flags:
brew install llvm --all-targets --with-clang --with-lld --with-libcxx --with-clang-extra-tools --with-libcxxabi --with-lldb --with-compiler-rt --with-libunwind --with-openmp (the gyp flags should not include the head folder since theres no --HEAD)
I'm not sure if this still needs Xcode or not, since we used Homebrew's llvm to build it. Probably safer to install it anyway;
The compiler will stop if it get warnings;
You posted a patch here that I applied, it should be included with the OS X specific patches.

Tested and compiled using OS X 10.11.6 (last update of El Capitan).
Not sure if I'm forgetting anything. heh

(the gyp flags should not include the head folder since theres no --HEAD)

Is HEAD-051e787 in your GYP flags what you're talking about? If so, what path should I use?

Yes, I used it on my pathes.
The default path for an install without the --HEAD flag is /usr/local/Cellar/llvm/3.8.1/bin/clang.
Note: it only found the clang after I pointed the path without quotation marks.

What is the .app file you use to run? I'm looking into building a .dmg since that seems easier.

I just run the Chromium.app inside out/Release folder. I copied it to /Applications to make it appear on Launchpad.

Alright. I'll work on scripting this build process with buildlib. I'll post back with a new comment once I've got it ready for testing.

I just pushed 88c242532bf1f3c4302886d6de731ba7cb8f1166 which should build a .dmg from scratch. If you could test it out, that would be great.
You should start from scratch by deleting build_sandbox. You can leave chromium-51.0.2704.106.tar.xz and the .hashes file so you won't have to re-download them.
I also wrote new build instructions in BUILDING.md. Could you check them out and see if I missed or messed up something?
Oh yeah, and I forgot to increment the release_revision to 3 in version.ini. Could you do that before building?

Ok, lets go!
Here is the first error:
python3 build_macos.py
Traceback (most recent call last):
  File "build_macos.py", line 30, in <module>
    import buildlib.macos
  File "/Users/Morello/ungoogled-chromium/buildlib/macos.py", line 25, in <module>
    class MacOSPlatform(generic.GenericPlatform):
  File "/Users/Morello/ungoogled-chromium/buildlib/macos.py", line 26, in MacOSPlatform
    PLATFORM_RESOURCES = pathlib.Path("resources", "macos")
NameError: name 'pathlib' is not defined

I'll take a look at the build instructions and see if I find something strange. When we're finished, I'll also see if I can test this on someone else's computer.

D'oh ac66c613c6473e21def771ef796d8127f701005b

Got an error after downloading the missing files.

2016-08-21 19:27:16,888 - INFO: Downloading pdfsqueeze-5936b871e6a087b7e50d4cbcb122378d8a07499f.tar.gz ...
2016-08-21 19:27:19,050 - INFO: Downloading google-toolbox-for-mac-401878398253074c515c03cb3a3f8bb0cc8da6e9.tar.gz ...
2016-08-21 19:27:33,744 - INFO: Extracting pdfsqueeze archive...
2016-08-21 19:27:33,744 - WARNING: Symlinks not supported. Will ignore all symlinks
2016-08-21 19:27:33,766 - INFO: Extracting google-toolbox-for-mac archive...
Traceback (most recent call last):
  File "build_macos.py", line 68, in <module>
    exit(main())
  File "build_macos.py", line 57, in main
    platform.setup_chromium_source()
  File "/Users/Morello/ungoogled-chromium/buildlib/macos.py", line 66, in setup_chromium_source
    self._extract_tar_file(google_toolboxarchive, google_toolbox_dir, list(), "google-toolbox-for-mac-{}".format(self.GOOGLE_TOOLBOX_FOR_MAC))
AttributeError: 'MacOSPlatform' object has no attribute 'GOOGLE_TOOLBOX_FOR_MAC'

47b6c3b25795fe06471b2432e5d5ab2a558208df

It built libc++.a just fine, it started compiling Chromium now.
Should I expect the compiler to complain about unused functions this time?

If you're talking about google_util.cc, then that patch has already been updated.

Ok, I just got the first error about unused functions. I'll list the file(s) here.
components/domain_reliability/google_configs.cc

New commits should fix these problems. I also updated disable-domain-reliability.patch, so you might want to extract the original google_configs.cc and reapply the relevant section of the patch, or reverse patch that file and apply the new section.

I'm having trouble restarting the build process.
After editing autofill_download_manager.cc, I've commented the following lines in build_macos.py before running it again and resuming the building:
    #platform.setup_chromium_source()
    #platform.setup_build_sandbox()
    #platform.apply_patches() # Change the command for GNU patch here
    #platform.setup_build_utilities(python2_command="python") # Change the commands for ninja and Python 2 here

But I got the following error:
build_macos.py
2016-08-21 23:31:51,167 - INFO: Running gyp command...
2016-08-21 23:31:51,168 - DEBUG: Successfully appended platform list
2016-08-21 23:31:51,168 - DEBUG: GYP command: build/gyp_chromium --depth=. --check -Dhost_cc=/usr/local/Cellar/llvm/3.8.1/bin/clang -Dremove_webcore_debug_symbols=1 -Ddisable_pnacl=1 -Dwerror= -Denable_automation=0 -Ddisable_newlib=1 -Dtracing_like_official_build=1 -Ddefault_apps_list_linux_dest=[] -Denable_prod_wallet_service=0 -Duse_official_google_api_keys=0 -Dlinux_strip_binary=1 -DCC=/usr/local/Cellar/llvm/3.8.1/bin/clang -Denable_remoting_host=0 -Denable_google_now=0 -Ddefault_apps_list=[] -Dproprietary_codecs=1 -DLDPLUSPLUS=/usr/local/Cellar/llvm/3.8.1/bin/clang++ -Dfieldtrial_testing_like_official_build=1 -Denable_hotwording=0 -Dfastbuild=1 -Denable_webrtc=0 -Denable_wifi_bootstrapping=0 -Dhost_cxx=/usr/local/Cellar/llvm/3.8.1/bin/clang++ -Dsafe_browsing=0 -Denable_one_click_signin=0 -Dremoting=0 -Denable_hangout_services_extension=0 -Dffmpeg_branding=Chrome -Dclang=1 -Dclang_dir=/usr/local/Cellar/llvm/3.8.1/bin -Dclang_use_chrome_plugins=0 -Denable_pre_sync_backup=0 -Ddisable_fatal_linker_warnings=1 -Denable_rlz=0 -Dmake_clang_dir=/usr/local/Cellar/llvm/3.8.1 -Ddisable_nacl=1 -Denable_hidpi=1
Updating projects from gyp files...
2016-08-21 23:32:33,529 - INFO: libc++.a already exists. Skipping its building
2016-08-21 23:32:33,529 - INFO: Running build command...
Traceback (most recent call last):
  File "build_macos.py", line 68, in <module>
    exit(main())
  File "build_macos.py", line 62, in main
    platform.build()
  File "/Users/Morello/ungoogled-chromium/buildlib/macos.py", line 88, in build
    super(MacOSPlatform, self).build(*args, **kwargs)
  File "/Users/Morello/ungoogled-chromium/buildlib/generic.py", line 450, in build
    self._run_ninja(self.ninja_command, self.build_output, build_targets)
  File "/Users/Morello/ungoogled-chromium/buildlib/generic.py", line 320, in _run_ninja
    result = self._run_subprocess([ninja_command, "-C", str(build_output), *targets], cwd=str(self.sandbox_root))
  File "/Users/Morello/ungoogled-chromium/buildlib/generic.py", line 271, in _run_subprocess
    return subprocess.run(*args, **kwargs)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 696, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 950, in __init__
    restore_signals, start_new_session)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 1467, in _execute_child
    executable = os.fsencode(executable)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/os.py", line 820, in fsencode
    raise TypeError("expect bytes or str, not %s" % type(filename).__name__)
TypeError: expect bytes or str, not NoneType

You should uncomment setup_build_utilities. That function sets an attribute for the command to invoke ninja. Or you can set the ninja_command attribute. I should revise this interface...

Got the first error in the post build process.
[180/251] PACKAGE FRAMEWORK 'Chromium Framework.framework', POSTBUILDS
FAILED: Chromium Framework.framework
./gyp-mac-tool package-framework 'Chromium Framework.framework' A && (export BUILT_FRAMEWORKS_DIR=/Users/Morello/ungoogled-chromium/build_sandbox/out/Release; export BUILT_PRODUCTS_DIR=/Users/Morello/ungoogled-chromium/build_sandbox/out/Release; export CONFIGURATION=Release; export CONTENTS_FOLDER_PATH="Chromium Framework.framework/Versions/A"; export<EMAIL_ADDRESS>export EXECUTABLE_NAME="Chromium Framework"; export EXECUTABLE_PATH="Chromium Framework.framework/Versions/A/Chromium Framework"; export FULL_PRODUCT_NAME="Chromium Framework.framework"; export INFOPLIST_PATH="Chromium Framework.framework/Versions/A/Resources/Info.plist"; export<EMAIL_ADDRESS>Framework.framework/Chromium Framework"; export MACH_O_TYPE=mh_dylib; export PRODUCT_NAME="Chromium Framework"; export PRODUCT_TYPE=com.apple.product-type.framework; export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk; export SRCROOT=/Users/Morello/ungoogled-chromium/build_sandbox/out/Release/../../chrome; export SOURCE_ROOT="${SRCROOT}"; export TARGET_BUILD_DIR=/Users/Morello/ungoogled-chromium/build_sandbox/out/Release; export TEMP_DIR="${TMPDIR}"; export UNLOCALIZED_RESOURCES_FOLDER_PATH="Chromium Framework.framework/Versions/A/Resources"; export WRAPPER_NAME="Chromium Framework.framework"; export XCODE_VERSION_ACTUAL=0731; (cd ../../chrome && ../build/mac/tweak_info_plist.py "--breakpad=1" "--breakpad_uploads=0" "--keystone=0" "--scm=1" "--branding=Chromium" && tools/build/mac/verify_order _ChromeMain "${BUILT_PRODUCTS_DIR}/${EXECUTABLE_PATH}"); G=$?; ((exit $G) || rm -rf 'Chromium Framework.framework') && exit $G) && touch 'Chromium Framework.framework'
tools/build/mac/verify_order: unordered symbols in /Users/Morello/ungoogled-chromium/build_sandbox/out/Release/Chromium Framework.framework/Versions/A/Chromium Framework:
__ZNSt3__18__rs_getEv
__ZNSt3__16__sortIRNS_6__lessIccEEPcEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIccEEPcEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIwwEEPwEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIwwEEPwEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIaaEEPaEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIaaEEPaEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIhhEEPhEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIhhEEPhEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIssEEPsEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIssEEPsEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIttEEPtEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIttEEPtEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIiiEEPiEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIiiEEPiEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIjjEEPjEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIjjEEPjEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIllEEPlEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIllEEPlEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessImmEEPmEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessImmEEPmEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIxxEEPxEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIxxEEPxEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIyyEEPyEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIyyEEPyEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIffEEPfEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIffEEPfEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIddEEPdEEvT0_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIddEEPdEEbT0_S5_T_
__ZNSt3__16__sortIRNS_6__lessIeeEEPeEEvT0_S5_T_
__ZNSt3__17__sort5IRNS_6__lessIeeEEPeEEjT0_S5_S5_S5_S5_T_
__ZNSt3__127__insertion_sort_incompleteIRNS_6__lessIeeEEPeEEbT0_S5_T_
__ZNSt3__125notify_all_at_thread_exitERNS_18condition_variableENS_11unique_lockINS_5mutexEEE
__ZSt18uncaught_exceptionv
__ZSt19uncaught_exceptionsv
__ZNSt16nested_exceptionC2Ev
__ZSt17current_exceptionv
__ZNSt16nested_exceptionC1Ev
__ZNSt16nested_exceptionD2Ev
__ZNSt16nested_exceptionD1Ev
__ZNSt16nested_exceptionD0Ev
__ZNKSt16nested_exception14rethrow_nestedEv
__ZSt17rethrow_exceptionSt13exception_ptr
__ZNSt3__115future_categoryEv
__ZNSt3__112future_errorC2ENS_10error_codeE
__ZNSt3__112future_errorC1ENS_10error_codeE
__ZNSt3__112future_errorD2Ev
__ZNSt3__112future_errorD1Ev
__ZNSt3__112future_errorD0Ev
__ZNSt3__112__next_primeEm
__ZNSt3__117iostream_categoryEv
__ZNSt3__18ios_base7failureC2ERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEERKNS_10error_codeE
__ZNSt3__18ios_base7failureC1ERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEERKNS_10error_codeE
__ZNSt3__18ios_base7failureC2EPKcRKNS_10error_codeE
__ZNSt3__18ios_base7failureC1EPKcRKNS_10error_codeE
__ZNSt3__18ios_base7failureD2Ev
__ZNSt3__18ios_base7failureD1Ev
__ZNSt3__18ios_base7failureD0Ev
__ZNSt3__112__do_nothingEPv
__ZNSt3__121__throw_runtime_errorEPKc
__ZNSt3__116__check_groupingERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEEPjS8_Rj
__ZNSt3__112bad_weak_ptrD2Ev
__ZNSt3__112bad_weak_ptrD1Ev
__ZNSt3__112bad_weak_ptrD0Ev
__ZNKSt3__112bad_weak_ptr4whatEv
__ZNSt3__112__get_sp_mutEPKv
__ZNSt3__117declare_reachableEPv
__ZNSt3__119declare_no_pointersEPcm
__ZNSt3__121undeclare_no_pointersEPcm
__ZNSt3__118get_pointer_safetyEv
__ZNSt3__121__undeclare_reachableEPv
__ZNSt3__15alignEmmRPvRm
__ZNSt3__111__call_onceERVmPvPFvS2_E
__ZSt17__throw_bad_allocv
__Znwm
__ZnwmRKSt9nothrow_t
__Znam
__ZnamRKSt9nothrow_t
__ZdlPv
__ZdlPvRKSt9nothrow_t
__ZdlPvm
__ZdaPv
__ZdaPvRKSt9nothrow_t
__ZdaPvm
__ZNSt11logic_errorC2ERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE
__ZNSt11logic_errorC1ERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE
__ZNSt11logic_errorC2EPKc
__ZNSt11logic_errorC1EPKc
__ZNSt11logic_errorC2ERKS_
__ZNSt11logic_errorC1ERKS_
__ZNSt11logic_erroraSERKS_
__ZNSt13runtime_errorC2ERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE
__ZNSt13runtime_errorC1ERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE
__ZNSt13runtime_errorC2EPKc
__ZNSt13runtime_errorC1EPKc
__ZNSt13runtime_errorC2ERKS_
__ZNSt13runtime_errorC1ERKS_
__ZNSt13runtime_erroraSERKS_
__ZNSt3__14stoiERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEEPmi
__ZNSt3__14stoiERKNS_12basic_stringIwNS_11char_traitsIwEENS_9allocatorIwEEEEPmi
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "build_macos.py", line 68, in <module>
    exit(main())
  File "build_macos.py", line 62, in main
    platform.build()
  File "/Users/Morello/ungoogled-chromium/buildlib/macos.py", line 88, in build
    super(MacOSPlatform, self).build(*args, **kwargs)
  File "/Users/Morello/ungoogled-chromium/buildlib/generic.py", line 450, in build
    self._run_ninja(self.ninja_command, self.build_output, build_targets)
  File "/Users/Morello/ungoogled-chromium/buildlib/generic.py", line 322, in _run_ninja
    raise Exception("ninja returned non-zero exit code: {}".format(result.returncode))
Exception: ninja returned non-zero exit code: 1

Could you try replacing libc++.a with the one that Google provides? I'm not sure if ninja will pick-up the change, so if that doesn't fix th error, we may need to start deleting some object files.

Alternatively, you could try uncommenting the sed lines in the build.sh script and change the CXX variable to point to Xcode's g++ compiler (not clang++). Then move the existing libc++.a out of the way so buildlib will rebuild it.

Ok, indeed the error was from a broken libc++.a. I used the one from the older build and it worked perfectly, creating the .dmg file. For convenience, its a good idea to include a shortcut to /Applications aside Chromium.app. Most software in OS X distributed by third-parties are installed by copying them to that folder.
About compiling libc++.a, I'm not sure I'm using Xcode's g++. It seems that the g++ binary is just a shortcut to Xcode's clang. How can I check it? For some reason the system sees it as an UNIX binary instead of a shortcut, so I can't see where it points. Running g++ --version says installed in in /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin, but theres no bin for it there.

For convenience, its a good idea to include a shortcut to /Applications aside Chromium.app. Most software in OS X distributed by third-parties are installed by copying them to that folder.

I'm still not very familiar with Mac's application system, so any help in explaining that would be appreciated. What is a "shortcut"? Is it a file that is given special treatment like on Windows? Is "/Applications" a path on your root drive? Where is Chromium.app located? How is the dmg involved in this?

It seems that the g++ binary is just a shortcut to Xcode's clang. How can I check it? For some reason the system sees it as an UNIX binary instead of a shortcut, so I can't see where it points.

Is this "shortcut" term the same as the one you used earlier? Also how are you checking where things point to? Does the checker you use also tell you where symlinks point to?

Nevermind, managed to get it to work. There problem was the arch -i386 flag and the way THIS_DIR was declared. Here is my modified script:

#!/bin/bash
# Copyright 2015 The Chromium Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

set -eux

REV=245965
DIR=$(mktemp -d -t libcpp)

THIS_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

# TODO(thakis): Figure out why our clang complains about visibility and
# redeclarations.
#CXX="$THIS_DIR/../llvm-build/Release+Asserts/bin/clang++"
CXX=/usr/local/Cellar/gcc49/4.9.3/bin/x86_64-apple-darwin15.4.0-c++-4.9

FLAGS="-nostdinc++ -O3 -std=c++11 -fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -mmacosx-version-min=10.6 -arch x86_64 -isysroot $(xcrun -show-sdk-path)"

pushd "${DIR}"

svn co --force https://llvm.org/svn/llvm-project/libcxx/trunk@$REV libcxx
svn co --force https://llvm.org/svn/llvm-project/libcxxabi/trunk@$REV libcxxabi

mkdir libcxxbuild
cd libcxxbuild

mkdir libcxx
pushd libcxx
sed -i '' 's/"default"/"hidden"/g' ../../libcxx/include/__config
"$CXX" -c -I../../libcxx/include/ ../../libcxx/src/*.cpp $FLAGS
popd

mkdir libcxxabi
pushd libcxxabi
sed -i '' 's/"default"/"hidden"/g' ../../libcxxabi/src/*
sed -i '' 's/push(default)/push(hidden)/g' ../../libcxxabi/src/*

# Let the default handler not depend on __cxa_demangle, this saves 0.5MB binary
# size in each binary linking against libc++.a
patch -d ../../libcxxabi -p0 < "${THIS_DIR}/libcxxabi.patch"

"$CXX" -c -I../../libcxx/include/ -I../../libcxxabi/include ../../libcxxabi/src/*.cpp $FLAGS
popd

libtool -static -o libc++.a libcxx*/*.o

cp libc++.a "${THIS_DIR}/libc++.a"
#upload_to_google_storage.py -b chromium-libcpp "${THIS_DIR}/libc++.a"

popd
rm -rf "${DIR}"

So, right now, we just need to patch the files I pointed in this comment, test with the new libc++.a from that script and see if it works ootb. Then I'll test the whole process from the start to see if we can get through without errors and user input.

I'm still alive, I just had other things come up so I didn't get to work on this for a little while.
I did some inspection of Firefox's .dmg with dmg2img, and I think i have a better idea of how it works now.

There's a symlink in the .dmg (which has a space as a filename) that points to /Applications
In .background, there's a PNG file that provides the blue background and arrow symbol you see.
There's also a .VolumeIcon.icns which apparently is a image file format used on Mac that gives the dmg file an icon (I think).
The .DS_Store file defines the positions and sizes of the icons when viewed, and maybe the background image to use. This is what makes the icons look large and in the right positions relative to the background.
And of course, there's also Firefox.app which is the directory that gets dragged into the /Applications symlink.

Here's an example of creating a .dmg that pkg-dmg gives us:
pkg-dmg --source /Applications/DeerPark.app --target ~/DeerPark.dmg
  --sourcefile --volname DeerPark --icon ~/DeerPark.icns
  --mkdir /.background
  --copy DeerParkBackground.png:/.background/background.png
  --copy DeerParkDSStore:/.DS_Store
  --symlink /Applications:"/Drag to here"

Since I don't have a Mac, I can't generate all of these files. For now, I can just add a symlink to /Applications so users can drag the Chromium app onto it. If you want to make the installer look nicer, you can provide me a .DS_Store, the contents of .background/, and .VolumeIcon.icns so I can add them in to the dmg.
In the meantime, I will fixup the patches so the warnings won't break building.

Ok, I'll be waiting.
By the way, is buildlib configured to generate a 32-bit binary? I feel that this could be related to the compiler stopping after warnings, somehow.
Depending on which OS X releases you want to support, its generally okay to drop 32-bit. All releases after Lion were 64-bit only.
I'll work on these files asap so we can get a nice .dmg ready for distribution.

I don't touch any compiler flags related to CPU architecture on Mac, so it's probably building a 64-bit binary. But I don't think the warnings are affected by this, since I build a 32-bit binary on Windows and 64-bit on Linux.
I can probably ignore the warnings if I tweak some compiler flags in GYP. Apparently they're hardcoded on Mac but not Linux or Windows. I was trying to avoid doing this but it would seem to take more effort given the number of warnings.

3bc83dfe4ae75b98e9410ef58f796b51406f01f9
I don't remember if we've tried building with Xcode's clang with -arch i386 removed, so let's try that first. If it works, then it would fix that fingerprint issue.
Also the new buildlib doesn't require you to set the object attributes if you skip certain functions (if you leave the defaults). Also, the functions don't accept arguments anymore; they are now all object properties. See build.py for more info.

Traceback (most recent call last):
  File "build.py", line 44, in <module>
    exit(main())
  File "build.py", line 32, in main
    builder.check_build_environment()
TypeError: check_build_environment() missing 1 required positional argument: 'self'

Fixed.<PHONE_NUMBER>e85a59a3db7f262366596212170096

Error:

Morello$ python3 build.py
2016-08-29 16:32:38,338 - INFO: Initialized default logger
2016-08-29 16:32:38,338 - INFO: sandbox_root path build_sandbox does not exist. Creating...
2016-08-29 16:32:38,339 - INFO: _ungoogled_dir path build_sandbox/.ungoogled does not exist. Creating...
Traceback (most recent call last):
  File "build.py", line 44, in <module>
    exit(main())
  File "build.py", line 33, in main
    builder.setup_chromium_source()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 633, in setup_chromium_source
    super(MacOSBuilder, self).setup_chromium_source()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 350, in setup_chromium_source
    self.source_archive = self.download_dir / pathlib.Path("chromium-{version}.tar.xz".format(version=self.chromium_version))
AttributeError: 'MacOSBuilder' object has no attribute 'chromium_version'

Fixed that and ninja invocation bug

Error:
Morello$ python3 build.py
2016-08-29 17:00:42,061 - INFO: Initialized default logger
2016-08-29 17:00:42,061 - INFO: sandbox_root path build_sandbox does not exist. Creating...
2016-08-29 17:00:42,061 - INFO: _ungoogled_dir path build_sandbox/.ungoogled does not exist. Creating...
Traceback (most recent call last):
  File "build.py", line 44, in <module>
    exit(main())
  File "build.py", line 33, in main
    builder.setup_chromium_source()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 630, in setup_chromium_source
    super(MacOSBuilder, self).setup_chromium_source()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 351, in setup_chromium_source
    self._download_if_needed(self.source_archive, "https://commondatastorage.googleapis.com/chromium-browser-official/chromium-{version}.tar.xz".format(version=self.chromium_version))
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 152, in _download_if_needed
    elif force_download or not file_path.is_file():
NameError: name 'force_download' is not defined

44066c711aa3953cf2e2b3535f5292bf6a85113c
That should put the end to these silly errors.

Got the usual visibility errors when trying to build libc++.a.

Alright I reverted the build script to gcc.
I did some quick research and it looks like the fingerprint trusting you got is due to the binary's certificate. I don't know if homebrew signs its binaries and if it publishes its certificates used for signing, but you can also create your own certificate and sign the binaries yourself. Do you have to trust the fingerprint every time?

Yep, I do.

Got an error compiling libc++.a.
+ popd
/var/folders/jy/d01dhkjj3wq4k42p92kvd19m0000gn/T/libcpp.W2us72Tp/libcxxbuild ~/ungoogled-chromium
+ mkdir libcxxabi
+ pushd libcxxabi
/var/folders/jy/d01dhkjj3wq4k42p92kvd19m0000gn/T/libcpp.W2us72Tp/libcxxbuild/libcxxabi /var/folders/jy/d01dhkjj3wq4k42p92kvd19m0000gn/T/libcpp.W2us72Tp/libcxxbuild ~/ungoogled-chromium
+ sed -i '' 's/"default"/"hidden"/g' ../../libcxxabi/src/CMakeLists.txt ../../libcxxabi/src/abort_message.cpp ../../libcxxabi/src/abort_message.h ../../libcxxabi/src/config.h ../../libcxxabi/src/cxa_aux_runtime.cpp ../../libcxxabi/src/cxa_default_handlers.cpp ../../libcxxabi/src/cxa_demangle.cpp ../../libcxxabi/src/cxa_exception.cpp ../../libcxxabi/src/cxa_exception.hpp ../../libcxxabi/src/cxa_exception_storage.cpp ../../libcxxabi/src/cxa_guard.cpp ../../libcxxabi/src/cxa_handlers.cpp ../../libcxxabi/src/cxa_handlers.hpp ../../libcxxabi/src/cxa_new_delete.cpp ../../libcxxabi/src/cxa_personality.cpp ../../libcxxabi/src/cxa_thread_atexit.cpp ../../libcxxabi/src/cxa_unexpected.cpp ../../libcxxabi/src/cxa_vector.cpp ../../libcxxabi/src/cxa_virtual.cpp ../../libcxxabi/src/exception.cpp ../../libcxxabi/src/fallback_malloc.ipp ../../libcxxabi/src/private_typeinfo.cpp ../../libcxxabi/src/private_typeinfo.h ../../libcxxabi/src/stdexcept.cpp ../../libcxxabi/src/typeinfo.cpp
+ sed -i '' 's/push(default)/push(hidden)/g' ../../libcxxabi/src/CMakeLists.txt ../../libcxxabi/src/abort_message.cpp ../../libcxxabi/src/abort_message.h ../../libcxxabi/src/config.h ../../libcxxabi/src/cxa_aux_runtime.cpp ../../libcxxabi/src/cxa_default_handlers.cpp ../../libcxxabi/src/cxa_demangle.cpp ../../libcxxabi/src/cxa_exception.cpp ../../libcxxabi/src/cxa_exception.hpp ../../libcxxabi/src/cxa_exception_storage.cpp ../../libcxxabi/src/cxa_guard.cpp ../../libcxxabi/src/cxa_handlers.cpp ../../libcxxabi/src/cxa_handlers.hpp ../../libcxxabi/src/cxa_new_delete.cpp ../../libcxxabi/src/cxa_personality.cpp ../../libcxxabi/src/cxa_thread_atexit.cpp ../../libcxxabi/src/cxa_unexpected.cpp ../../libcxxabi/src/cxa_vector.cpp ../../libcxxabi/src/cxa_virtual.cpp ../../libcxxabi/src/exception.cpp ../../libcxxabi/src/fallback_malloc.ipp ../../libcxxabi/src/private_typeinfo.cpp ../../libcxxabi/src/private_typeinfo.h ../../libcxxabi/src/stdexcept.cpp ../../libcxxabi/src/typeinfo.cpp
+ patch -d ../../libcxxabi -p0
build_sandbox/third_party/libc++-static/build.sh: line 42: build_sandbox/third_party/libc++-static/libcxxabi.patch: No such file or directory
Traceback (most recent call last):
  File "build.py", line 44, in <module>
    exit(main())
  File "build.py", line 38, in main
    builder.build()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 807, in build
    raise Exception("libc++.a build script returned non-zero exit code")
Exception: libc++.a build script returned non-zero exit code
ungoogled-chromium Morello$ /Users/Morello/ungoogled-chromium/build_sandbox/third_party/libc++-static/libcxxabi.patch

It didn't find libcxxabi.patch for some reason. In the last line, I dragged libcxxabi.patch to the terminal to make sure the folder was the same.
This seems to be the same problem I had before. I got it to work by changing the way $THIS_DIR was defined to this:
THIS_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

cf7bb0c76b52a7754a958d32e79185c92ed894d5 Here's an attempt at trying to fix this.
I don't like that you have to manually trust the fingerprint each time, so I would like to somehow automate this or fix it. Signing the executable is one method, but it takes several steps and it would have to be done each time the executable changes. Could you describe in more detail how you trust the fingerprint? Is it all done in the terminal, or does some GUI dialog box show up?

Its all done in the terminal. It asks if I want to trust the fringerprint, and I just need to press 'p' 2 times for the 2 downloads it does.
The annoying part is that the timeout is really small, so you can't start the script then pay attention to something else. If you miss the timeout, then you have to edit build.py (to comment the steps you've already done, ie patching) before trying it again.
+ svn co --force https://llvm.org/svn/llvm-project/libcxx/trunk@245965 libcxx
Error validating server certificate for 'https://llvm.org:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: llvm.org
 - Valid: from Tue, 24 Jun 2014 00:00:00 GMT until Fri, 23 Jun 2017 23:59:59 GMT
 - Issuer: InCommon, Internet2, US
 - Fingerprint: 87:b8:45:4d:9d:66:7e:93:fb:30:58:79:bc:a7:f8:53:f0:44:05:69
(R)eject, accept (t)emporarily or accept (p)ermanently? p

I got the first warning about an unused constant in autofill_download_manager.cc and it stopped the compiling as usual.

Oh the fingerprint error was due to svn and NOT gcc?
That changes everything.
This is really easy to fix. Can you send me the output of svn help co? That way I can determine what arguments I will need to add.

You're the boss.

Morello$ svn help co
checkout (co): Check out a working copy from a repository.
usage: checkout<EMAIL_ADDRESS>[PATH]

  If specified, REV determines in which revision the URL is first
  looked up.

  If PATH is omitted, the basename of the URL will be used as
  the destination. If multiple URLs are given each will be checked
  out into a sub-directory of PATH, with the name of the sub-directory
  being the basename of the URL.

  If --force is used, unversioned obstructing paths in the working
  copy destination do not automatically cause the check out to fail.
  If the obstructing path is the same type (file or directory) as the
  corresponding path in the repository it becomes versioned but its
  contents are left 'as-is' in the working copy.  This means that an
  obstructing directory's unversioned children may also obstruct and
  become versioned.  For files, any content differences between the
  obstruction and the repository are treated like a local modification
  to the working copy.  All properties from the repository are applied
  to the obstructing path.

  See also 'svn help update' for a list of possible characters
  reporting the action taken.

Valid options:
  -r [--revision] ARG      : ARG (some commands also take ARG1:ARG2 range)
                             A revision argument can be one of:
                                NUMBER       revision number
                                '{' DATE '}' revision at start of the date
                                'HEAD'       latest in repository
                                'BASE'       base rev of item's working copy
                                'COMMITTED'  last commit at or before BASE
                                'PREV'       revision just before COMMITTED
  -q [--quiet]             : print nothing, or only summary information
  -N [--non-recursive]     : obsolete; try --depth=files or --depth=immediates
  --depth ARG              : limit operation by depth ARG ('empty', 'files',
                             'immediates', or 'infinity')
  --force                  : force operation to run
  --ignore-externals       : ignore externals definitions

Global options:
  --username ARG           : specify a username ARG
  --password ARG           : specify a password ARG
  --no-auth-cache          : do not cache authentication tokens
  --non-interactive        : do no interactive prompting
  --trust-server-cert      : accept SSL server certificates from unknown
                             certificate authorities without prompting (but only
                             with '--non-interactive')
  --config-dir ARG         : read user configuration files from directory ARG
  --config-option ARG      : set user configuration option in the format:
                                 FILE:SECTION:OPTION=[VALUE]
                             For example:
                                 servers:global:http-library=serf

d2a01cfee882c72c92247a258347f75a189c5c56
I'm not exactly sure what compiler flags I can set to fix those linker warnings, so we'll see what happens.

It didn't find build.sh for some reason.
Updating projects from gyp files...
2016-08-30 23:39:48,526 - INFO: Building libc++.a ...
/bin/sh: build.sh: command not found
Traceback (most recent call last):
  File "build.py", line 44, in <module>
    exit(main())
  File "build.py", line 38, in main
    builder.build()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 808, in build
    raise Exception("libc++.a build script returned non-zero exit code")
Exception: libc++.a build script returned non-zero exit code

Hopefully I fixed it now...

Now it got to build libc++.a, but I had to manually trust the certificates like before.
Interesting though, I get some warnings building it but it proceeds normally. Why would it stop when building Chromium?

Got an error, I think this is the first time we get this one.
FAILED: obj/url/url_lib.gurl.o
/usr/local/Cellar/llvm/3.8.1/bin/clang++ -MMD -MF obj/url/url_lib.gurl.o.d -DV8_DEPRECATION_WARNINGS -DCLD_VERSION=2 -D__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORE=0 -DDISABLE_NACL -DCHROMIUM_BUILD -DCR_CLANG_REVISION=264915-1 -DUSE_LIBJPEG_TURBO=1 -DENABLE_MEDIA_ROUTER=1 -DUSE_PROPRIETARY_CODECS -DENABLE_PEPPER_CDMS -DENABLE_NOTIFICATIONS -DENABLE_TOPCHROME_MD=1 -DTRACING_IS_OFFICIAL_BUILD=1 -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PDF=1 -DENABLE_PLUGIN_INSTALLATION=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -DUSE_BROWSER_SPELLCHECKER=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_SUPERVISED_USERS=1 -DENABLE_SERVICE_DISCOVERY=1 -DV8_USE_EXTERNAL_STARTUP_DATA -DURL_IMPLEMENTATION -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_NOEXCEPT= -DU_STATIC_IMPLEMENTATION -DUSE_LIBPCI=1 -DUSE_OPENSSL=1 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -D_FORTIFY_SOURCE=2 -Igen -I../.. -I../../third_party/icu/source/i18n -I../../third_party/icu/source/common -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -O2 -fvisibility=hidden -mmacosx-version-min=10.7 -arch x86_64 -Wall -Wextra -Wno-unused -Wno-unused-parameter -Wno-missing-field-initializers -Wno-selector-type-mismatch -Wpartial-availability -Wheader-hygiene -Wno-char-subscripts -Wno-unneeded-internal-declaration -Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing -Wno-deprecated-register -Wno-inconsistent-missing-override -Wno-shift-negative-value -std=c++11 -stdlib=libc++ -fno-rtti -fno-exceptions -fvisibility-inlines-hidden -fno-threadsafe-statics -fcolor-diagnostics -fno-strict-aliasing  -c ../../url/gurl.cc -o obj/url/url_lib.gurl.o
../../url/gurl.cc:571:14: error: redefinition of 'gurl_strip_trk'
std::string &gurl_strip_trk(std::string &s)
             ^
../../url/gurl.cc:544:14: note: previous definition is here
std::string &gurl_strip_trk(std::string &s)
             ^
../../url/gurl.cc:576:6: error: redefinition of 'gurl_is_trq'
bool gurl_is_trq(const std::string &s)
     ^
../../url/gurl.cc:549:6: note: previous definition is here
bool gurl_is_trq(const std::string &s)
     ^
../../url/gurl.cc:583:12: error: redefinition of 'strip_trk'
GURL GURL::strip_trk(void) const
           ^
../../url/gurl.cc:556:12: note: previous definition is here
GURL GURL::strip_trk(void) const
           ^
../../url/gurl.cc:591:12: error: redefinition of 'is_trq'
bool GURL::is_trq(void) const
           ^
../../url/gurl.cc:564:12: note: previous definition is here
bool GURL::is_trq(void) const
           ^
4 errors generated.
[5871/19472] ACTION Generating resourc... policy/resources/policy_templates.grd
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "build.py", line 44, in <module>
    exit(main())
  File "build.py", line 38, in main
    builder.build()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 810, in build
    super(MacOSBuilder, self).build()
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 510, in build
    self._run_ninja(self.build_output, self.build_targets)
  File "/Users/Morello/ungoogled-chromium/buildlib.py", line 361, in _run_ninja
    raise Exception("ninja returned non-zero exit code: {}".format(result.returncode))
Exception: ninja returned non-zero exit code: 1

Now it got to build libc++.a, but I had to manually trust the certificates like before.

That's strange. I updated the Mac OS-specific patches already so SVN would get --non-interactive --ignore-server-cert flags (in build.sh). Are you sure you applied the updated patches?
If so, that probably means your SVN help is lying to us. Could you try running svn info https://llvm.org/svn/llvm-project twice and see if you have to accept the fingerprint the second time (assuming you permanently accept it the first time)? If you do have to, then try the solutions on this page.

Why would it stop when building Chromium?

I'm slightly confused by your question. Are you asking why the warnings stop the Chromium build but not the build script for libc++? If so, that's because the build script manually invokes the compiler and has its own set of compiler flags. When building Chromium, GYP and Ninja determine the compiler and the flags to use.
By default, the compiler doesn't stop on warnings. But Google made warnings into errors, so it halts building. I tried setting a GYP flag to disable converting warnings into errors, but it doesn't seem to work on Mac OS. So I added a Mac OS-specific patch for a GYP file to disable converting warnings into errors.

Got an error, I think this is the first time we get this one.

Yes they seem to be new ones. Though they're quite puzzling. I'm not sure what we changed that is causing these errors...

Something is wrong with your url/gurl.cc file. I can see the definitions in the lines specified for the first occurance of every function, but there are no duplicates and your file has more lines than mine. Perhaps your build sandbox has become corrupted?

That's strange. I updated the Mac OS-specific patches already so SVN would get --non-interactive --trust-server-cert (EDIT: I mean trust-server-cert) flags in build.sh. Are you sure you applied the updated patches?
Yes, I'm sure. I had modified buildlib.py to skip already applied patches and remember reading the line where it applied the new ones.

I'll just delete the folders and start from scratch.
The link you sent me solves the problem with trusting the fingerprints. It would ask me to trust it again after trusting it once.

Nice! It built libc++.a and started building Chromium without any input by me. Lets see how well it goes this time. I'm still getting those warnings, though:
ld: warning: object file (../../third_party/libc++-static/libc++.a(future.o)) was built for newer OSX version (10.11) than being linked (10.7)

I wonder if we have extra symbols here because we didn't set the proper compiler flags for building libc++.a. Maybe if we tell the compiler to generate object files for the right Mac OS version, the extra symbols will go away? Maybe because I changed the minimum Mac OS version when building libc++.a? I don't know enough about the compiler flags to know how it affects the symbol table, but at least the unordered symbol list is a lot smaller now since we hide certain symbols like Google intended.
Maybe it will be fine if we skip the symbol order verification, since this is probably a way that Google checks to make sure there's no extra code lingering around or all the symbols they need are present. Here's the Wikipedia page on the symbol table if you are a bit confused as to what is going on.
8eb490803de53f0e7166224c2740111dde8b539c disables running the verify_order script. You'll need to re-run GYP for this to take effect.

Welp, I messed gurl.cc again.
Here is what I did to apply the new patch: ran git pull, added the -N flag to the patch command, and changed the line 794 of buildlib.py to not stop if it returns 1. The output was skipping patches it had already applied:
2016-09-01 09:11:53,313 - DEBUG: Applying patch ungoogled-chromium/disable-domain-reliability.patch ...
patching file components/domain_reliability/baked_in_configs.gypi
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file components/domain_reliability/baked_in_configs.gypi.rej
patching file components/domain_reliability/google_configs.cc
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file components/domain_reliability/google_configs.cc.rej
patching file components/domain_reliability/uploader.cc
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file components/domain_reliability/uploader.cc.rej
2016-09-01 09:11:53,318 - DEBUG: Applying patch ungoogled-chromium/intercept-all-modified-domains.patch ...
patching file chrome/app/chrome_main.cc
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file chrome/app/chrome_main.cc.rej
patching file content/browser/browser_url_handler_impl.cc
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file content/browser/browser_url_handler_impl.cc.rej
patching file url/gurl.cc
Hunk #1 succeeded at 582 (offset 27 lines).

As you can see, it fails to detect that gurl.cc was patched before and then reapplies the patch. I can just copy it from the older build, and the average user won't be running buildlib multiple times, but any idea on how to solve this? If skipping the already applied patches works, it'll make testing next releases easier.

As you can see, it fails to detect that gurl.cc was patched before and then reapplies the patch.

Huh that's interesting. The algorithms to make patching easier and lazier ends up making recursively applicable patches possible.
There's a pretty simple solution to this. I can just create a file in the ungoogled dir (.ungoogled in the build sandbox) that will track what patches have been applied. This is kind of how quilt does it.
But I just had another thought. Since we're already requiring Homebrew, we could just ask the user to install quilt via brew (apparently they have it). Quilt will keep track of applied patches (it makes copies of them when they are applied) and there are commands to check what patches have been applied, apply new ones, remove patches up to a certain point, etc.
I already use quilt on Debian, so this will be a quick change to make.

I can just copy it from the older build, and the average user won't be running buildlib multiple times

I'm actually wondering who the "average user" that uses buildlib is.  Regardless, making the build process user-friendly to development on this project isn't a high priority right now.
Regarding your second edit on things to improve, I will create separate issues instead of continuing this one. This issue is for getting ungoogled-chromium to build on Mac OS via buildlib, and we've got that to work.
Anyways, I'm glad we got this to work. Good thing the extra symbols didn't break the build.

Here is the .dmg: https://my.mixtape.moe/pdxynp.dmg
Yes, I'm happy we got this to work too. I hope I can contribute to future releases and debugging on OS X as well.

I've added #34 and #35

Aaand here we go!
Just tried to build the next release, got the following error:
Morello$ python3 build.py
2016-09-16 23:20:25,859 - INFO: Initialized default console logging handler
2016-09-16 23:20:25,859 - INFO: Using builder MacOSBuilder
2016-09-16 23:20:25,859 - INFO: Checking Python 2 command...
2016-09-16 23:20:25,859 - INFO: No Python 2 command specified; testing with 'python'
2016-09-16 23:20:25,879 - DEBUG: Using Python version '2.7.12'
2016-09-16 23:20:25,879 - INFO: Checking ninja command...
2016-09-16 23:20:25,882 - DEBUG: Using ninja version '1.7.1'
2016-09-16 23:20:25,883 - INFO: Checking quilt command...
2016-09-16 23:20:25,886 - DEBUG: Using quilt command '0.64'
2016-09-16 23:20:25,886 - INFO: Checking svn command...
2016-09-16 23:20:26,284 - DEBUG: Using svn command version '1.9.4'
2016-09-16 23:20:26,285 - INFO: Checking libtool command...
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: unknown option character `-' in: --version
Usage: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT] [-no_warning_for_no_symbols]
Usage: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table <filename>] [-seg_addr_table_filename <file_system_path>] [-all_load] [-noall_load]
2016-09-16 23:20:26,623 - ERROR: libtool command returned non-zero exit code 1

Might be related to the new version of Xcode that was released a few days ago.


Update widget tests

The widget test for testing headline text change was not actually checking the text change. A second assertion has been added to confirm if the text actually changed from Foo to Bar.
Another test to verify color change has been added as well.

Thank you! LGTM.


Change demo URL of Money sample application.

I have moved the demo of the Money sample application to a sub-domain app..
So here is a corresponding update.

Thank's!


Improved Sklearn Compatibility

This PR adds the following:

An option for the weighted mean of the gaussians: return_mean.
An option to return the weighted standard deviation: return_std.
Conforms with existing sklearn return_std functionality.

I have spent a fair bit of time thinking about how the scikit-mdn api might be improved. My main consideration is that it conforms with sklearn across several areas:

Single quantile predictions (think QuantileRegressor)
'return_std(thinkBayesianRidge`)
mean vs median outputs (think SGDRegressor with mse vs huber)

skmdn has an intersection of several rare features that make it unique to sklearn API, while also having features that significantly extend it. I have tried to preserve as much of the existing skmdn API as possible but there is one small but notable change - predict gives a single (n x 3) array when passed a list of quantiles instead of the median output and quantiles array.
pred_quantiles = mdn.predict(X, quantiles=[0.1, 0.5, 0.9])
print(pred_quantiles.shape)
print(X.shape, pred_quantiles.shape)
Out[1]:
(10, 1), (10, 3)

Other considerations
I think this really improves interoperability with sklearn's other features but there are a few other things we could consider adding to make it even more useable across wider sklearn ecosystem:

skpro integration could be considered.
there is also an on going discussion https://github.com/scikit-learn/scikit-learn/issues/23334 about how to extend the sklearn API for multi-quantile outputs. skmdn provides a great example of a model that would benefit from this api extension.

Funny you mention that API discussion, one of my colleagues mentioned it and that also served as the inspiration to work on this project. Partially as a "demo" of how the API might be used externally. More of a demo than a final design on that front though.
While skpro looks interesting, I think I mainly want to target sklearn for the time being. Keeps things simple.

Funny you mention that API discussion, one of my colleagues mentioned it and that also served as the inspiration to work on this project. Partially as a "demo" of how the API might be used externally. More of a demo than a final design on that front though.
While skpro looks interesting, I think I mainly want to target sklearn for the time being. Keeps things simple.

That's fascinating to know! I have engaged on that discussion with my old work-linked account but the conversation seems to have gone a little stale. I think the changes I have suggested here are about as far as you can go within the current sklearn API. It would be amazing if this could get the convo going again and I'd be very happy to be involved and help where I can!
Fortunately, skpro seems quite happy to take existing 3rd party probabilistic regressors, put a light wrapper around them and have them as skpro estimators: NGBoost and CyclicBoosting are two good examples. This could always be a option.

Funny you mention that API discussion, one of my colleagues mentioned it and that also served as the inspiration to work on this project. Partially as a "demo" of how the API might be used externally. More of a demo than a final design on that front though.
While skpro looks interesting, I think I mainly want to target sklearn for the time being. Keeps things simple.

That's fascinating to know! I have engaged on that discussion with my old work-linked account but the conversation seems to have gone a little stale. I think the changes I have suggested here are about as far as you can go within the current sklearn API. It would be amazing if this project could get the convo going again and I'd be very happy to be involved and help where I can!
Fortunately, skpro seems quite happy to take existing 3rd party probabilistic regressors, put a light wrapper around them and have them as skpro estimators: NGBoost and CyclicBoosting are two good examples. This could always be a option.

Hey, I saw Olivier briefly mentioned MDNs in his talk at pydata Paris. Interesting talk. I wondered if there had been any further discussion on this?

Not really, and we are also in the time of year when a lot of people are on holiday. 😅

Yes, I thought that might be the case. I have a bit of time off and have some capacity to refine this over the holidays so thought it would be worth pinging you.


The image is loaded transposed with pyheif==0.8.0

Describe the bug
The PIL.Image is loaded transposed with pyheif==0.8.0.
Expected behavior
The image is loaded in original shape.
Code
import HeifImagePlugin
import pyheif
from PIL import Image

image = pyheif.open("example.heif")
print(image.size)
# (3024, 4032)

image_pil = Image.open("example.heif")
print(image_pil.size)
# (4032, 3024)

example.heif.zip
Environment

Library version: 0.6.2
Language/framework version: Python 3.11.9
OS version: Linux

The image is loaded transposed

This is desired behavior since image bitmap in the file actually rotated and correct orientation is stored in exif. You should use PIL.ImageOps.exif_transpose() function to restore orientation.
This is made since built-in libheif transposition is several times slower than highly optimized for CPU cache implementation in Pillow.


Remove jeykll github pages deployment

Description
This PR removes the defunct Jekyll github pages deployment. I think we used that in the very early days to publish some sort of markdown documentation for the samples. This is no longer required and also no longer working, which has CI fail for all PRs.
Note: Pure build fix, no code changes
General Checklist:
Please ensure the following points are checked:

[ ] My code follows the coding style
[ ] I have reviewed file licenses
[ ] I have commented any added functions (in line with Doxygen)
[ ] I have commented any code that could be hard to understand
[ ] My changes do not add any new compiler warnings
[ ] My changes do not add any new validation layer errors or warnings
[ ] I have used existing framework/helper functions where possible
[ ] My changes do not add any regressions
[ ] I have tested every sample to ensure everything runs correctly
[ ] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[ ] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

If this PR contains framework changes:

[ ] I did a full batch run using the batch command line argument to make sure all samples still work properly

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[ ] I have tested the sample on at least one compliant Vulkan implementation
[ ] If the sample is vendor-specific, I have tagged it appropriately
[ ] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[ ] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the readme of the folder that the sample belongs to e.g. api samples readme
[ ] For new samples, I have added a tutorial README.md file to guide users through what they need to know to implement code using this feature. For example, see conditional_rendering
[ ] For new samples, I have added a link to the Antora navigation so that the sample will be listed at the Vulkan documentation site

Merging this to make sure builds on master no longer fail.


text! not found

When running cargo loco generate scaffold answer answer_text:text! question_id:int sequential_priority_answer:decimal, I get:
...
Writing src/models/_entities/prelude.rs
Warning: can't set `wrap_comments = true`, unstable features are only available in nightly channel.
Warning: can't set `comment_width = 80`, unstable features are only available in nightly channel.
Warning: can't set `format_strings = true`, unstable features are only available in nightly channel.
Warning: can't set `imports_granularity = Crate`, unstable features are only available in nightly channel.
Warning: can't set `group_imports = StdExternalCrate`, unstable features are only available in nightly channel.
Warning: can't set `wrap_comments = true`, unstable features are only available in nightly channel.
Warning: can't set `comment_width = 80`, unstable features are only available in nightly channel.
Warning: can't set `format_strings = true`, unstable features are only available in nightly channel.
Warning: can't set `imports_granularity = Crate`, unstable features are only available in nightly channel.
Warning: can't set `group_imports = StdExternalCrate`, unstable features are only available in nightly channel.
Warning: can't set `wrap_comments = true`, unstable features are only available in nightly channel.
Warning: can't set `comment_width = 80`, unstable features are only available in nightly channel.
Warning: can't set `format_strings = true`, unstable features are only available in nightly channel.
Warning: can't set `imports_granularity = Crate`, unstable features are only available in nightly channel.
Warning: can't set `group_imports = StdExternalCrate`, unstable features are only available in nightly channel.
Warning: can't set `wrap_comments = true`, unstable features are only available in nightly channel.
Warning: can't set `comment_width = 80`, unstable features are only available in nightly channel.
Warning: can't set `format_strings = true`, unstable features are only available in nightly channel.
Warning: can't set `imports_granularity = Crate`, unstable features are only available in nightly channel.
Warning: can't set `group_imports = StdExternalCrate`, unstable features are only available in nightly channel.
Warning: can't set `wrap_comments = true`, unstable features are only available in nightly channel.
Warning: can't set `comment_width = 80`, unstable features are only available in nightly channel.
Warning: can't set `format_strings = true`, unstable features are only available in nightly channel.
Warning: can't set `imports_granularity = Crate`, unstable features are only available in nightly channel.
Warning: can't set `group_imports = StdExternalCrate`, unstable features are only available in nightly channel.
... Done.
2024-03-29T13:15:37.698589Z  WARN app: loco_rs::boot:  environment=development
Error: type: text! not found. try any of: ["string!", "ts", "string^", "jsonb", "uuid", "int", "int!", "int^", "json!", "string", "bool!", "ts!", "text", "bool", "json", "jsonb!", "uuid!"]

Whereas text! is included in docs...?! under 'migrations' header.
Ah, found this issue. So is 'scaffold' still a thing?
And I don't quite understand why I get these warnings, looks like users are assumed to use nightly?

thanks! should be resolved via #526


Fixes to get rpi mission working with recent NMF

This PR includes four small fixes to the code to get it to compile and upload to an RPi, including updated documentation to reflect changes.
Another issue seemed to be better to fix at the framework level, that is described in the tiny pull request at: https://github.com/esa/nanosat-mo-framework/pull/184
Let me know if you want me to split this up, or alter in any way,
thanks!

Yes, it actually only works with the phi-sat-2 branch, as the code already expects some dependencies from it.
(it however only works if https://github.com/esa/nanosat-mo-framework/pull/184 is merged to the phi-sat-2 branch)

I think you compile it against the dev branch because the phi-sat-2 has the new AI service that you removed.
Also, I removed the orekit dependency that was just bloating the deployment, I see that you are adding it back.
Try deleting your .m2 repository and compiling from scratch with the phi-sat-2 branch.  :)

I just checked everything again, and compiled against phi-sat-2
Without orekit I get the following error regarding GPSSoftSimAdapter:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on project nmf-platform-impl-raspberrypi: Compilation failure: Compilation failure:
[ERROR] /home/sacha/os3/nmf-mission-raspberry-pi/platform-service-impl/src/main/java/esa/mo/platform/impl/provider/raspberrypi/GPSSoftSimAdapter.java:[30,45] package org.orekit.propagation.analytical.tle does not exist
[ERROR] /home/sacha/os3/nmf-mission-raspberry-pi/platform-service-impl/src/main/java/esa/mo/platform/impl/provider/raspberrypi/GPSSoftSimAdapter.java:[63,12] cannot find symbol
[ERROR]   symbol:   class TLE
[ERROR]   location: class esa.mo.platform.impl.provider.raspberrypi.GPSSoftSimAdapter
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Adding orekit solves this error

Hi @CesarCoelho sorry for the commit mess, but I have now removed orekit from the code, so the dependency could be removed again, and further fixed the docker and rp environment so it works  with the phi-sat-2 branch. Except for the PR still open in that branch, let me know if you rather have me add that here, although I think my proposed change in https://github.com/esa/nanosat-mo-framework/pull/184 makes sense to implement never-the-less.


Problem with tableview cell selection

Hey!
Great project! Thanks!
However, I have a problem. I want to be able to press the tableview cell with the collection view and still push to a new view (Call tableView didSelectRowAtIndexPath). I think that the collection view is blocking the touch mechanism to the tableview cell.
I want to press anywhere at the cell and push a new view.
Any ideas?

Hmm. Tricky. I'd play around with setting  userInteractionEnabled on various views, like the collection views, or maybe just the cells. Play around until it works. Take a peek and let me know!
--
Ash Furrow
iOS Developer, Author
http://ashfurrow.com

On Aug 25, 2015, at 4:08 PM, VisionAppsStudio<EMAIL_ADDRESS>wrote:
Hey!
Great project! Thanks!
However, I have a problem. I want to be able to press the tableview cell with the collection view and still push to a new view (Call tableView didSelectRowAtIndexPath). I think that the collection view is blocking the touch mechanism to the tableview cell.
I want to press anywhere at the cell and push a new view.
Any ideas?
—
Reply to this email directly or view it on GitHub.


[20.09] mupdf: fix CVE-2021-3407

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117199 at e934c5dc run on aarch64-linux 1

10 packages built successfully:

cups-filters
llpp
mupdf
python27Packages.pymupdf
python37Packages.pymupdf
python38Packages.pymupdf
splix
system-config-printer
termpdfpy
zathura

1 suggestion:

warning: EvalError
Cannot evaluate attribute ‘mupdf’ in ‘/nix/store/97acv9f1qqli2dvy5djqgw7aj4b1ary0-nixpkgs’.

WFM linux x86_64, marked as broken on darwin in stable it seems.


Solving forward in Solvers

I fixed several issues:

SupervisedSolver was not working after batch addition
Network now handles the forward pass for all networks, solving #204
Fixing tutorial 5 which was not working due to the problem reported in #204

TODO

[ ] Add tests for SupervisedSolver

The tests not running are due to issue #200


Extend pipeline functionality to classical forecasters

See pmdarima Python package for a working example
related to #7 and #44

Useful transformers on target (y) include

detrending
deseasonalizing

Transformations have to be applied before passing to prediction model and inverse transformations after prediction model (i.e. on predicted values)

Following #44 and scikit-learns [TransformedTargetRegressor], I would implement a TransformedTargetForecaster to handle y-transformations.

Closed by #111


⚠ API - Lens has degraded performance

In 2bbc04c, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 502
Response time: 357 ms

Resolved: API - Lens performance has improved in 271c96b after 10 minutes.


added all-blocks UI

UI integration with all blocks

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: aashaykapoor:white_check_mark: raghukapur9:x: ankit723You have signed the CLA already but the status is still pending? Let us recheck it.


Log exceptions

On most actions, when there's an exception the EntityService catches it and return false, so it's basically impossible to know what's wrong.
I suggest to log as DEBUG all such exceptions.

Closing for inactivity.


Possible conflict of settings?

First, thanks for this wonderful piece of work!
Quick question, do these two settings create a conflict? They both appear on paper to deal specifically in security patching and I have noticed some failures from super to reboot the Mac when having both enabled.
Configuration profile setting:
AllowRSRUpdates

Apple auto updates config profile setting
"automatically install system data files and security updates"

These two settings do not conflict with each other...
AllowRSRUpdates = super will not ignore RSR updates (the default behavior is to ignore them), but instead ask softwareupdate to install them. This function literally only controls super's workflow.
Apple "Automatically install..." = tell softwareupdated to automatically install any security updates if it finds them during the occasional automatic check. This function literally only controls softwareupdated's automatically scheduled workflow.
In other words each only controls TIMING of when an RSR might install automatically... neither setting can "prevent" an RSR from being installed.
Also if your referencing this week's RSR... Apple horked it up badly on their own... https://www.macrumors.com/2023/07/10/apple-pulls-ios-16-5-1-macos-13-4-1-rsrs/


Questions about open_manipulator on turtlebot3

Dear Robotis Representative,
My team recently purchased a turtlebot3 from Robotis and the package came with a intel joule 570x board and OpenCR 1.0 board. In addition to that, we have reproduced and assembled an open-manipulator using five Dynamixel X-series servos. Now, we are trying to control the open-manipulator using the OpenCR 1.0 board and we are having some difficulties. First, we are not sure if we need to upload new Arduino code into the OpenCR 1.0 board in order to control the open-manipulator. Second, we have set the dynamixel servos to position control mode, 1000000 baudrate and ID numbers of 3,4,5,6,7 (one ID number for each of the five dynamixel servos), and we are not sure if we are setting these parameters correctly. Lastly, would there be a more detailed guideline on how to control the open-manipulator? We have followed this website : http://turtlebot3.readthedocs.io/en/latest/manipulation.html and it did not work very well. Thank you for your help and time in advance!
SIncerely,
Hong

Hello Hong,
Thank you for your inquiry.
The Arduino code is currently uploaded from Github.
However, the code depending on other packages such as Dynamixel SDK and Dynamixel Workbench, setting the environment might be complicated.
Official OpenManipulator code will be available when the product is released to the market.
Thank you.