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!


On Tue, Dec 10, 2013 at 2:07 PM, Derek Gaston <friedmud@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...


On Tue, Dec 10, 2013 at 2:04 PM, Kirk, Benjamin (JSC-EG311) <benjamin.kirk@nasa.gov> wrote:
On Dec 10, 2013, at 3:01 PM, Derek Gaston <friedmud@gmail.com>

> 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.