From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Problem installing git version on debian sid
Date: Mon, 04 Dec 2017 15:36:27 -0500 [thread overview]
Message-ID: <20171104153627.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1712041504080.3475@debian.pulsar.com>
I am rather confused by all this.
> The error said the option -c was not recognized by the preprocessor.
Of course not.
cpp is the c preprocessor, the program that expands all the #ifdefs #includes etc.
It's basically a macro expander, very specific to C.
It doesn't know anything about the C language or compilation or objects or linkage or anything else.
It's a front end program, and you shouldn't be calling it with -c or any of the compiler options.
If you want the c++ compiler you need c++ or g++ or some such.
It's damn confusing, since c++ files end in the extension .cpp, but no, that doesn't mean you should call cpp on them.
And I don't think any of tidy is c++, so that's even more confusing.
Karl Dahlke
prev parent reply other threads:[~2017-12-04 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:48 Chuck Hallenbeck
2017-12-04 18:19 ` Geoff McLane
2017-12-04 19:48 ` Chuck Hallenbeck
2017-12-04 20:23 ` Geoff McLane
2017-12-04 23:42 ` Kevin Carhart
2017-12-05 0:47 ` Chuck Hallenbeck
2017-12-05 14:58 ` Chris Brannon
2017-12-05 16:36 ` Chuck Hallenbeck
2017-12-05 16:54 ` Karl Dahlke
2017-12-05 17:26 ` Chuck Hallenbeck
2017-12-05 18:57 ` Geoff McLane
2017-12-05 20:03 ` Chuck Hallenbeck
2017-12-10 6:39 ` [Edbrowse-dev] what is dispatchEvent and is it needed? Kevin Carhart
2017-12-10 6:48 ` Karl Dahlke
2017-12-10 8:28 ` Kevin Carhart
2017-12-05 1:01 ` [Edbrowse-dev] Problem installing git version on debian sid Chuck Hallenbeck
2017-12-04 20:12 ` Chuck Hallenbeck
2017-12-04 20:36 ` Karl Dahlke [this message]
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=20171104153627.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@lists.the-brannons.com \
/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 NNTP newsgroup(s).