id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
8394,"py_environment.cpp ""list"" is ambiguous",alan@…,Ralf W. Grosse-Kunstleve,"I'm seeing the following using PGI 12.2 on Cray Linux 4 (SuSE 11 derivative):


{{{
    ""CC"" -INLINE:none --gnu -Kieee -fpic -fPIC -gopt -Minform=warn -DBOOST_ALL_NO_LIB=1 -DBOOST_MPI_DYN_LINK=1 -DBOOST_MPI_PYTHON_DYN_LINK=1 -DBOOST_PYTHON_DYN_LINK=1 -D__need_IOV_MAX -I""."" -I""/apps_hpc/epd/default/include/python2.7"" -c -o ""bin.v2/libs/mpi/build/pgi/debug/boost.locale.icu-off/python/py_environment.o"" ""libs/mpi/src/python/py_environment.cpp""

""/apps_hpc/epd/default/include/python2.7/pyfpe.h"", line 8: warning: white
          space between backslash and newline in line splice ignored
      /                       Copyright (c) 1996.                           \
                                                                             ^

""libs/mpi/src/python/py_environment.cpp"", line 34: error: ""list"" is ambiguous
  bool mpi_init(list python_argv, bool abort_on_exception)
                ^

""libs/mpi/src/python/py_environment.cpp"", line 82: error: ""list"" is ambiguous
      mpi_init(extract<list>(sys.attr(""argv"")), true);
                       ^

2 errors detected in the compilation of ""libs/mpi/src/python/py_environment.cpp"".
}}}

Not concerned about the warning from my header (didn't want to edit it out though), but it looks to me like maybe one of the other list classes has found it's way into the namespace?

These particuliar builds were bootstrapped and run with


{{{
./bootstrap.sh --without-icu --with-libraries=mpi,graph_parallel,python --with-python=##EDITED## --with-python-root=##EDITED## --with-python-version=2.7 --with-toolset=pgi

./b2 -d0 -d+2 -j32 --debug-configuration --disable-icu boost.locale.icu=off -sNO_BZIP2=1 --build-type=complete --layout=tagged threading=single variant=debug toolset=pgi install
}}}
",Bugs,new,To Be Determined,python USE GITHUB,Boost 1.53.0,Problem,,,