After my last master pull, I noticed that I cannot build without boost,
tested on a clean Ubuntu 18.04 Docker:

apt install apt install gcc g++ scons python-dev zlib1g-dev
protobuf-compiler m4
scons -j8 build/ARM/gem5.opt

fails with:

build/ARM/systemc/ext/systemc:37:10: fatal error: boost/bind.hpp: No
such file or directory
  #include <boost/bind.hpp>
           ^~~~~~~~~~~~~~~~

The problem can be fixed by installing:

     apt install libboost-all-dev

The commit that introduced this line is
c172a64db11daa14e11b614374688934112dffd2 systemc: Include boost/bind.hpp
in the systemc header.

 > This should be mostly ok to include here since gem5 itself shouldn't
 > include systemc, just the sub headers that systemc brings in. systemc
 > code which includes systemc *will* have a dependency on boost, but that
 > at least contains the new dependency somewhat.

I think that previously this was not required for the default build.

So I just want to double check: is this intentional that the default
build depends on Boost now?

While not ideal, it is not impossible to allow this. But in that case, I
just want to check what the Boost policy will be moving forward. I'd
recommend: "no boost outside of systemc" to prevent getting large
compilation times due to Boost.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to