all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Glenn Morris <rgm@gnu.org>
Cc: 5603@debbugs.gnu.org
Subject: bug#5603: 23.1.90; value of CPP not used in configure script
Date: Thu, 17 May 2012 00:30:24 +0200	[thread overview]
Message-ID: <F0F905C3-36A2-4F1D-90EC-8DFE37645633@Freenet.DE> (raw)
In-Reply-To: <78k40czixl.fsf@fencepost.gnu.org>


Am 16.05.2012 um 09:25 schrieb Glenn Morris:

> I can't tell what the issue is supposed to be here.

It's that I have set for configure the environment variable "CPP=llvm-cpp-4.2" because './configure --help' tells:

	Some influential environment variables:
	  CC          C compiler command
	  CFLAGS      C compiler flags
	  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
	              nonstandard directory <lib dir>
	  LIBS        libraries to pass to the linker, e.g. -l<library>
	  CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
	              you have headers in a nonstandard directory <include dir>
	  CPP         C preprocessor
	  XMKMF       Path to xmkmf, Makefile generator for X Window System

But this does not seem to be true because it's

	+ ac_cv_prog_CPP='llvm-gcc-4.2 -E -no-cpp-precomp -I/sw/include -L/sw/lib'

that's used as C pre-processor. So either the configure script has a bug or its help function.


The mention of "-no-cpp-precomp" is more or less an additional remark.

--
Greetings

  Pete

’Twas a woman who drove me to drink, and I never had the courtesy to thank her for it.
				— W.C. Fields






      reply	other threads:[~2012-05-16 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 11:34 bug#5603: 23.1.90; value of CPP not used in configure script Peter Dyballa
2012-05-16  7:25 ` Glenn Morris
2012-05-16 22:30   ` Peter Dyballa [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=F0F905C3-36A2-4F1D-90EC-8DFE37645633@Freenet.DE \
    --to=peter_dyballa@freenet.de \
    --cc=5603@debbugs.gnu.org \
    --cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.