reply alll.... Curious if anyone does care to comment on state of the art in
linker optimizations of any related issues that effect build system.
Thanks.
----------------------------------------
> From: marchy...@hotmail.com
> To: royst...@ices.utexas.edu
> Subject: RE: [Libmesh-users] Example files won't run a second time
> Date: Fri, 12 Aug 2016 18:30:48 -0400
>
>
>
>
>
>
> ----------------------------------------
>> Date: Fri, 12 Aug 2016 16:59:32 -0500
>> From: royst...@ices.utexas.edu
>> To: marchy...@hotmail.com
>> CC: harroontheg...@gmail.com; libmesh-users@lists.sourceforge.net
>> Subject: Re: [Libmesh-users] Example files won't run a second time
>>
>>
>> On Fri, 12 Aug 2016, Mike Marchywka wrote:
>>
>>> Again, the compile seems normal but maybe someone could explain the
>>> odd linking lol. What is the point of this?
>>
>> Originally, the point of running libtool was that it allowed the same
>> build system to support all the weird options for static and dynamic
>> linking that were available and sometimes necessary on a dozen weird
>> variations of Unix.
>>
>> Now that everybody runs Linux or nearly-compatible influencees
>> thereof, the point of running libtool is that automake uses libtool
>> and we like automake more than we dislike libtool.
>
> Well, for these example programs the run.sh could have simply
> invoked a.out lol. I thought there may be some optimizations
> that could only be made during special linking or some real performance
> or architecture features. I did not really look at all the stuff,j just
> noted it was libtool...
>
>
>>
>> Note that all the weird libtool script stuff is an intermediate state
>> of a build; libtool gets out of the way and puts normal binaries in
>> their final places (as specified by your --prefix= argument to
>> configure) when you do "make install".
>> ---
>> Roy
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
