This is the mail archive of the
mailing list for the libstdc++ project.
Re: [patch] Default to --enable-libstdcxx-time=auto
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>, Jakub Jelinek <jakub at redhat dot com>, Rainer Orth <ro at cebitec dot uni-bielefeld dot de>
- Date: Wed, 22 May 2013 12:48:04 +0200
- Subject: Re: [patch] Default to --enable-libstdcxx-time=auto
- References: <CAH6eHdTgTspzbfHhD3uDwDVD3uXAapb_NMZ0jAZ-4-UjfD4H4g at mail dot gmail dot com> <519C942D dot 6050100 at oracle dot com> <CAH6eHdTjdi75WSwKYfdGBtOeQwbsSvMbzzxo24qofMexFSmETA at mail dot gmail dot com> <519C9AF5 dot 8090300 at oracle dot com> <519C9CBC dot 4050606 at oracle dot com> <519C9E3B dot 60609 at oracle dot com> <CAH6eHdRXAK1r0g7u+50RobAxTo=6DJsvRZzo75m7x+5ir3opKQ at mail dot gmail dot com>
On 05/22/2013 12:40 PM, Jonathan Wakely wrote:
That for sure. But I don't think the situation is exactly the same, to
be honest. Note, I don't know what exactly "undesignated" means, I
understand you already used that approach, thus don't hesitate to try it
On 22 May 2013 11:30, Paolo Carlini wrote:
.. put an abort or something in the dummy implementations, to make sure
people don't try to run an executable built with headers which have the
clock available linked at run time to a .so which doesn't, really.
Suboptimal solution because ideally we would like to fail at build time, but
this is the best I have got so far. Be very clear in the docs, anyway.
Based on feedback for <regex> users much prefer to have something
undefined than to have it defined but non-functional or causing an
Take your time (no pun intended ;) you may want to disable temporarily
the auto with a FIXME comment.