I should probably add that this would for g++, but perhaps not other
compilers. This is a common enough case that it is perhaps worth
supporting as a special case nontheless? 

Or we could take the decision that cmake builds are the way to go, and we
can't support all non-standard cases for the traditional build.

Andrew

On Thu, May 21, 2015 at 10:54:19PM +0100, Andrew Ross wrote:
> 
> Alan,
> 
> I think your summary is probably correct, but the solution of just
> explicitly linking stdc++ is so simple, that it makes me think it must be
> possible to work round this. A flag if there is any C++ code would be
> sufficient to identify the need to link with stdc++?
> 
> Andrew
> 
> On Wed, May 20, 2015 at 10:25:06PM -0700, Alan Irwin wrote:
> > Hi Andrew:
> > 
> > Would you please take a quick look at the commit message for a09dc18?
> > In that commit message I outline the linking model I used to draw the
> > conclusion that the ada, d, f95, java, and ocaml traditional examples
> > builds were going to _sometimes_ fail for a certain combination of
> > circumstances (static PLplot build with at least one of the C++ device
> > drivers enabled).
> > 
> > I am asking for that review because I hate to give up all those
> > components of the comprehensive test of the traditional build for the
> > given circumstances if I don't have to.  I am pretty sure your review
> > of the linking model I use will show I am right, but nevertheless that
> > review would be much appreciated since it would help to put my mind at
> > ease about this commit (which disables the relevant parts of the
> > comprehensive test for the given combination of circumstances).
> > 
> > Alan
> > __________________________
> > Alan W. Irwin
> > 
> > Astronomical research affiliation with Department of Physics and Astronomy,
> > University of Victoria (astrowww.phys.uvic.ca).
> > 
> > Programming affiliations with the FreeEOS equation-of-state
> > implementation for stellar interiors (freeeos.sf.net); the Time
> > Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> > software package (plplot.sf.net); the libLASi project
> > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> > and the Linux Brochure Project (lbproject.sf.net).
> > __________________________
> > 
> > Linux-powered Science
> > __________________________
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Plplot-devel mailing list
> Plplot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/plplot-devel

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to