A blast from the past, from a TACC consulting ticket last year:

Response Date: Wed, 23 Apr 2008 01:20:43
Responder: Jesse Snead
Response Cc'd:

Roy:

An administrator tells me that you are correct, that the mpicxx script
is not functioning correctly.

Until it gets fixed, which may be a while, there is a workaround. For
instance, putting your explicit library after the "-L" directive seems
to work:

$ mpicxx -o test.o test.cc -c
-L/opt/apps/intel10_1/mvapich1_0_9_9/petsc/2.3.3/lib/
/share/home/00885/roystgnr/libmesh/svn/contrib/lib/x86_64-unknown-linux-gnu_opt/libHilbert.so
-lpetsc

Can you try that and let me know if it does bypass the issue?

Thanks
Bryan


Response Date: Wed, 23 Apr 2008 01:53:45
Responder: Roy Stogner
Response Cc'd:

Rearranging the linker flags gives a warning:

"icc: warning #10147: no action performed for specified file(s)"

but the linked executable output seems fine for my stripped-down test
case.

I haven't tested rearranging the linker flags on the libMesh utilities
yet; our "grab flags from every dependency under the sun" build system
makes that task easier said than done... but if I end up needing one
of those utilities on ranger, we already know that "compile and link
in two separate steps" is a sufficient workaround for our apps. I just
wanted to make sure you knew about the mpicxx bug before someone else
got bit by it.


On Fri, 4 Sep 2009, Derek Gaston wrote:

> It's pretty funny... because we get this same error on our supercomputer 
> (Icestorm).... but not anywhere else.  We tried to track it down forever but 
> didn't have any luck so we just live with it now...
>
> Derek
>
> On Sep 4, 2009, at 3:54 PM, Roy Stogner wrote:
>
>> 
>> On Fri, 4 Sep 2009, Andrea Hawkins wrote:
>> 
>>> I am trying to compile libMesh on lonestar out at TACC and I am getting an
>>> error when I get the the building bin/amr.
>> 
>> I've run into this too; IIRC it was a bug in their compiler script
>> that we trigger when trying build and link in the same step.  It
>> affected us when building those bin/ utilities but it shouldn't affect
>> anything in the examples/ directory or any user codes built with
>> similar Makefiles.
>> ---
>> Roy
>> 
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus 
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Libmesh-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/libmesh-users
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to