[multi_index] problem with gcc 3.4.2 for Compaq Tru64 UNIX
Seems like some multi_index tests are failing due to lack of resources or something like that, for COMSOFT reports. http://tinyurl.com/66t2h mips-tfile, /tmp//cctFjnCI.s:10965 string too big (35326 bytes) line:? #.stabs?"and_<boost::mpl::not_<boost::is_same<boost::mpl: [very long expression] Anyone has an idea what this could be about? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
Joaquín Mª López Muñoz wrote:
Seems like some multi_index tests are failing due to lack of resources or something like that, for COMSOFT reports.
Yes, this might indeed be the fact. I'm having serious troubles compiling the regression tests with gcc because it uses such enormous amounts of file space. The machine in question has ~300MB tmp space which is ok for most tests but not for all. I'll try to play around with some env variables to see if it helps any.
mips-tfile, /tmp//cctFjnCI.s:10965 string too big (35326 bytes) line:? #.stabs?"and_<boost::mpl::not_<boost::is_same<boost::mpl: [very long expression]
A quick google search indicates that this is a problem with gcc on alpha when compiling with debug symbols. A possible workaround might be to use -gstabs instead of -g, I'll try it ASAP. Markus
Markus Schöpflin wrote:
Joaquín Mª López Muñoz wrote:
mips-tfile, /tmp//cctFjnCI.s:10965 string too big (35326 bytes) line:? #.stabs?"and_<boost::mpl::not_<boost::is_same<boost::mpl: [very long expression]
A quick google search indicates that this is a problem with gcc on alpha when compiling with debug symbols. A possible workaround might be to use -gstabs instead of -g, I'll try it ASAP.
I did some experiments and the only way to compile these files it to disable debug symbols completely. I have done that on the toolset for gcc used for the regression runs, I hope it helps to clean up some of the errors. Markus
participants (2)
-
Joaquín Mª López Muñoz -
Markus Schöpflin