On Mon, Aug 13, 2018 at 01:19:42PM +0100, Patrick Welche wrote:
> Chugging along trying to get hpx to compile, I thought I would try the
> 1.1.0 patches I had so far on master. I just got an extra compile error:
> 
> /usr/src/local/hpx/src/hpx_init.cpp: In function ‘int 
> hpx::detail::run_or_start(hpx::util::function_nonser<int(boost::program_options::variables_map&)>&,
>  const boost::program_options::options_description&, int, char**, 
> std::vector<std::basic_string<char> >&&, hpx::startup_function_type, 
> hpx::shutdown_function_type, hpx::runtime_mode, bool)’:
> /usr/src/local/hpx/src/hpx_init.cpp:603:24: error: ‘hpx_start’ has not 
> been declared
>                      if(hpx_start::include_libhpx_wrap)
>                         
> 
> which seems to be from
> 
> commit bd77d6ed1720ba2d1c45c7129c5bf1d299a80498
> Author: Nikunj Gupta <[email protected]>
> Date:   Wed Jul 18 09:35:54 2018 +0530
> 
>     Changes according to review
> 
> 
> Would a quick glance by you suggest the #ifs served as useful protection?
> (Now to find out what HPX_HAVE_DYNAMIC_HPX_MAIN does...)

Those #ifs still currently protect

namespace hpx_start
{
    // Importing weak symbol from libhpx_wrap.a which may be shadowed by one 
present in
    // hpx_main.hpp.
    HPX_SYMBOL_EXPORT __attribute__((weak)) extern bool include_libhpx_wrap;
}


(but I don't understand the shadowing issue...)


Cheers,

Patrick
_______________________________________________
hpx-users mailing list
[email protected]
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users

Reply via email to