Dear all,

I’m not sure if it is a bug or I’m just doing it wrong, so I decided to write here. However I can move this letter to the bug tracker.

 

Configure script acts different when restart in the same build directory. I would consider it as a wrong use model unless it wouldn’t actually do the job J

 

Scenario 1.

Trying to build picongpu from the scratch (makeit script and log_makeit). Compilation fails due to the boost error with __float128. Please notice that although I have explicitly loaded gcc 4.9 version, cmake still thinks that gcc 4.8.5 is used (loading this module from bashrc doesn’t change it).

 

Scenario 2.

I “forget” to provide C++11 flag  (makeit_restart and log_makeit_restart). First compilation fails asking for a C+11 flag. Then I immediately correct my mistake and restart configuration and compilation in the same directory.  This works like a charm. From the log it is evident that somehow after restart a different compiler version was picked. (also note that the build type was changed to a  DEBUG version for some reason.)

 

Scenario 3.

If I clean the build directory before the restart (makeit_restart_remove and log_makeit_restart_remove) it will be the same as Sc.1,  same compiler version and the very same boost error.

 

I checked the CMakeCache.txt between Sc1. and Sc2. before the restart and didn’t find any relevant difference. Could you please advise me how can I fix the Sc.1?

 

Best regards,

Danila.

 

P.S. Please note that I don’t have an access to the boost config file (https://svn.boost.org/trac/boost/ticket/11852)