On Fri, 24 Jun 2011, Derek Gaston wrote:
> I'm thinking of changing lines in Make.common.in around 222 from: > > libmesh_CXXFLAGS += @CXXFLAGS_OPT@ > > to > > libmesh_CXXFLAGS := @CXXFLAGS_OPT@ $libmesh_CXXFLAGS > > The reason is that the way it is setup now doesn't allow users to actually > override the flags libMesh picks! For instance on my particular system > libMesh is picking -O2... but I have no way to override that because even if > I put "-O3" into my environmental libmesh_CXXFLAGS the -O2 will appear > _after_ it... overriding it! > > With the scheme outlined above any user flags coming from the environment > would be after the libMesh flags allowing the user to override anything > libMesh does by default. > > Any opinions on this? I've noticed the same problem, but been a little too lazy to test the solution and a little too responsible to commit the solution without testing it. This looks like a good idea to me. --- Roy ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
