Ok: It turns out that one of the admins symlinked the old directory to the
new one... that's why it's working now and why libtool is printing out
those warnings.
It's definitely not libMesh's fault - definitely a problem with the
configuration on the machine. I just wonder why none of the other codes
they're building on that machine aren't having trouble...
Thanks again everyone for the help!
Derek
On Tue, Dec 10, 2013 at 2:07 PM, Derek Gaston <fried...@gmail.com> wrote:
> Sounds good Ben - I do still think there is value in having that option -
> but it's something we can get at a later date.
>
> I'm still trying to recreate the problem now - I don't like it when things
> just "start working"... I'm asking the admin if they changed something on
> their side...
>
> Derek
>
>
> On Tue, Dec 10, 2013 at 2:04 PM, Kirk, Benjamin (JSC-EG311) <
> benjamin.k...@nasa.gov> wrote:
>
>> On Dec 10, 2013, at 3:01 PM, Derek Gaston <fried...@gmail.com>
>> wrote:
>>
>> > I don't know why it wasn't able to detect that earlier... or what they
>> might have changed - but.... IT WORKS!
>> >
>> > Thanks everyone for your help - I REALLY appreciate it!
>>
>> Glad to hear that - getting a no-libtool build is proving to be a bit of
>> a challenge because of our 'convenience libraries.'
>>
>> I'll still work on this option but at a low level.
>>
>> -Ben
>>
>>
>>
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
