Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#35 closed defect (wontfix)

Compiling OSI on Maverick@TAcc

Reported by: erry Owned by: andreasw
Priority: major Component: configuration tests
Version: 0.5 Keywords:
Cc:

Description (last modified by andreasw)

Problem with linking on SUN machine (see attached output)

Attachments (1)

output.txt (70.4 KB) - added by andreasw 13 years ago.
configuration and make output (originally in descriptioni)

Download all attachments as: .zip

Change History (7)

Changed 13 years ago by andreasw

configuration and make output (originally in descriptioni)

comment:1 Changed 13 years ago by andreasw

  • Description modified (diff)

I (AW) put output which was in Description now as attachement.

Maybe the following warnings in the output file give a hint:

CC -DHAVE_CONFIG_H -I. -I`echo .` -I../inc  -I`echo /home/teragrid/tg457654/Coin-Osi/CoinUtils/src` -I`echo /home/teragrid/tg457654/Coin-Osi/Clp/../CoinUtils/inc`   -O4 -DNDEBUG -xarch=v8plus   -c -o ClpMain.o ClpMain.cpp
"ClpPlusMinusOneMatrix.hpp", line 272: Warning: ClpPlusMinusOneMatrix::transposeTimes hides the virtual function ClpMatrixBase::transposeTimes(double, const double*, double*, const double*, const double*, double*) const.
"ClpNetworkMatrix.hpp", line 194: Warning: ClpNetworkMatrix::transposeTimes hides the virtual function ClpMatrixBase::transposeTimes(double, const double*, double*, const double*, const double*, double*) const.
2 Warning(s) detected.

comment:2 Changed 13 years ago by lou

Warnings are likely not significant --- clp and osi produce these by the dozen. It's an overload resolution problem. If memory serves, the solution breaks GCC 2.95. The Interlocked* symbols should be defined in libCstd. I'll see if I can make time to try a build.

comment:3 Changed 13 years ago by lou

Did a few test builds. Locally, I need -mt to force a multithreaded build, but once that's in place I see the various Interlocked* symbols. No link problems, however. Current working theory is incorrect LD_LIBRARY_PATH in build environment. Requested additional info from user.

comment:4 Changed 13 years ago by lou

Based on config.log from the user, misconfigured LD_LIBRARY_PATH and/or compiler installation seems the most likely problem. Sent detailed diagnosis 06.12.02 with suggestion to force -mt flag, and further suggestion to take it up with systems staff if that fails and let us know the diagnosis. Have not heard back. Further investigation likely requires login access to TACC systems.

comment:5 Changed 13 years ago by lou

Pinged the user 06.12.08, he has referred the problem to TACC systems staff to see if they can diagnose the linkage problem.

comment:6 Changed 13 years ago by andreasw

  • Resolution set to wontfix
  • Status changed from new to closed

The ticket hasn't been touched in 6 weeks, I'm cloing it.

Note: See TracTickets for help on using tickets.