unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Cc: Alex Ott <alexott@gmail.com>, "Eric M. Ludlam" <eric@siege-engine.com>
Subject: CEDET calls cpp -E -dM -x c++ /dev/null
Date: Wed, 1 Jul 2009 21:06:17 +0200	[thread overview]
Message-ID: <e01d8a50907011206p11655e4nb06ce7f28ad6ec72@mail.gmail.com> (raw)

CEDET does the call above in semantic-gcc-setup. Doing that from the
command line using MingGW on w32 fails.

It fails because /dev/null is not valid on w32. Shouldn't it be NUL
there? However looking through Emacs lisp sources I see several uses
of just /dev/null. Wouldn't it be better to use some defsubst for
this?

Now, if the command instead is

    cpp -E -dM -x c++ nul

it fails for me with

  cpp: installation problem, cannot exec `cc1plus': No such file or directory

Does it work for anyone else using MinGW? What should perhaps be used instead?




             reply	other threads:[~2009-07-01 19:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 19:06 Lennart Borgman [this message]
2009-07-01 19:20 ` CEDET calls cpp -E -dM -x c++ /dev/null Eli Zaretskii
2009-07-01 19:25   ` Lennart Borgman
2009-07-01 19:36     ` Eli Zaretskii
2009-07-01 20:01       ` Sean O'Rourke
2009-07-01 20:16         ` Lennart Borgman
2009-07-01 20:32           ` Sean O'Rourke
2009-07-01 20:25       ` Lennart Borgman
2009-07-02  3:24         ` Eli Zaretskii
2009-07-02  3:34           ` Eric M. Ludlam
2009-07-02 18:13             ` Lennart Borgman
2009-07-02 19:29               ` Eli Zaretskii
2009-07-03  0:31                 ` Lennart Borgman
2009-07-03  0:46                   ` Miles Bader
2009-07-03  1:13                     ` Lennart Borgman
2009-07-03  9:36                       ` Eli Zaretskii
2009-07-03 11:22                         ` Lennart Borgman
2009-07-01 19:58     ` Lennart Borgman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=e01d8a50907011206p11655e4nb06ce7f28ad6ec72@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=alexott@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).