public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Petr Machata <pmachata@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH 1/2] Enable C++
Date: Fri, 03 Apr 2015 23:40:58 +0200	[thread overview]
Message-ID: <87wq1sevpx.fsf@redhat.com> (raw)
In-Reply-To: 1428060790.10607.203.camel@bordewijk.wildebeest.org

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

Mark Wielaard <mjw@redhat.com> writes:

> On Fri, 2015-04-03 at 10:28 +0200, Petr Machata wrote:
>> - Detect C++ compiler in configure, add supporting infrastructure to
>>   eu.am.
>
> Looks good. Two questions below, but not blockers. Just curious.
>
>> index faf8add..f1d290b 100644
>> --- a/config/eu.am
>> +++ b/config/eu.am
>> [...]
>>  %.os: %.c %.o
>>  if AMDEP
>> +	test -d $(DEPDIR)/$(*D) || mkdir $(DEPDIR)/$(*D)
>>  	if $(COMPILE.os) -c -o $@ -fpic -DPIC -DSHARED -MT $@ -MD -MP \
>>  	  -MF "$(DEPDIR)/$*.Tpo" `test -f '$<' || echo '$(srcdir)/'`$<; \
>>  	then cat "$(DEPDIR)/$*.Tpo" >> "$(DEPDIR)/$*.Po"; \
>
> Why is that mkdir now necessary?

It's not, but I thought it's a good idea for symmetry.  The reason the
c++ bits need this mkdir is that we keep that code in a sub-directory,
and this creates the corresponding sub-directory for the dependency
tracking helper files.

>> +AC_CACHE_CHECK([for working C++ compiler], ac_cv_cxx_works,
>> +[AC_LANG_PUSH([C++])
>> + AC_COMPILE_IFELSE([AC_LANG_SOURCE([dnl
>> +struct foo {
>> +  int i;
>> +  explicit foo () : i (0) {}
>> +  virtual ~foo () {}
>> +};])], ac_cv_cxx_works=yes, ac_cv_cxx_works=no)
>> + AC_LANG_POP()])
>> +AM_CONDITIONAL(HAVE_CXX, test "$ac_cv_cxx_works" = yes)
>
> We require gnu++98 above.
> Is the explicit enough to make sure the compiler supports C++98?

Well, this is a C++98 code.  It's of course not enough to test the whole
C++98--the language is vast.  The reason for that test is that I want to
make sure we really do have a C++ compiler.  AC_PROG_CXX happily exports
CXX even if none is available, so we can't use that in conditionals.

Thanks,
Petr

             reply	other threads:[~2015-04-03 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 21:40 Petr Machata [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-14 14:47 Mark Wielaard
2015-04-14 14:37 Petr Machata
2015-04-07 17:10 Petr Machata
2015-04-07 15:27 Mark Wielaard
2015-04-03 11:33 Mark Wielaard
2015-04-03  8:28 Petr Machata

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq1sevpx.fsf@redhat.com \
    --to=pmachata@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).