Build hangs on bundled Boost iostreams (mapped_file.cpp) during deal.II compile

[prcc...@gmail.com]

Dear all,

I’m running into an issue when building deal.II (9.7.0-pre): the build always stalls on a specific Boost file, as shown below:

$ make bundled_boost_iostreams_release
Consolidate compiler generated dependencies of target bundled_boost_iostreams_release
Building CXX object bundled/boost-1.84.0/libs/iostreams/src/CMakeFiles/bundled_boost_iostreams_release.dir/mapped_file.cpp.o

I’ve attached the full deal.II configuration log for reference. My Kokkos (4.6.00) was configured with:

cmake -B builddir \
  -DCMAKE_CXX_COMPILER=c++ \
  -DCMAKE_BUILD_TYPE=Release \
  -DKokkos_ENABLE_CUDA=ON \
  -DKokkos_ARCH_AMPERE80=ON \
  -DCMAKE_INSTALL_PREFIX=/scratch/cucui/kokkos-install-4.6 \
  -DKokkos_ENABLE_CUDA_CONSTEXPR=ON \
  -DKokkos_ENABLE_CUDA_RELOCATABLE_DEVICE_CODE=ON \
  -DKokkos_ENABLE_CUDA_LAMBDA=ON

Any suggestions on how to get past this hang would be greatly appreciated. Thank you!

Best,

Cu

[Wolfgang Bangerth]

On 4/28/25 07:14, prcc...@gmail.com wrote:
>
> I’m running into an issue when building deal.II (9.7.0-pre): the build
> always stalls on a specific Boost file, as shown below:
>

> *$ make bundled_boost_iostreams_release

> Consolidate compiler generated dependencies of target
> bundled_boost_iostreams_release
> Building CXX object bundled/boost-1.84.0/libs/iostreams/src/CMakeFiles/
> bundled_boost_iostreams_release.dir/mapped_file.cpp.o

> *

This is strange -- there is nothing special about the file, nor is it
particularly large. When that happens, can you call 'top' in a separate
window to see whether the compiler is running at 100%, and what the
memory consumption is?

What happens if you call
make -j2 -k
? Does it hang on other files as well?

Best
W.

[prcc...@gmail.com]

Hi Wolfgang,

> When that happens, can you call 'top' in a separate

> window to see whether the compiler is running at 100%, and what the
> memory consumption is?

I ran 'top' in a separate window, and the compiler process is consistently at 100% CPU (see attached screenshot). 

Even after waiting for over an hour, it’s still sitting at 100%.

BTW, I am compiling on a server where I am sure there is enough memory space.

> What happens if you call 

> make -j2 -k

Nothing happens :-( — the build still hangs on this one file every time I test it.

Best,

Cu

[Wolfgang Bangerth]

On 4/29/25 11:43, prcc...@gmail.com wrote:
>
> > What happens if you call
> > make -j2 -k
>
> Nothing happens :-( — the build still hangs on this one file every time
> I test it.

I don't know what to suggest. I don't think any of us have ever seen
this. Are you saying that the compiler works fine for all other files?
With the -k flag mentioned above, it should keep going to compile other
files even while it is stuck on the one in question.

Best
W.

[prcc...@gmail.com]

I had our server administrator upgrade the CUDA version on our server to 12.8. 

We encountered no compilation issues, and the build was successful :-)

Best,

Cu

[Wolfgang Bangerth]

On 5/2/25 07:52, prcc...@gmail.com wrote:
> I had our server administrator upgrade the CUDA version on our server to 12.8.
> We encountered no compilation issues, and the build was successful :-)

Good news!
Best
W.