unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Pretest compilation problem
Date: Wed, 16 Feb 2011 14:11:37 -0500	[thread overview]
Message-ID: <4y7hczeqvq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <878vxgjbyn.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 16 Feb 2011 09:22:40 -0500")

Chong Yidong wrote:

> Adding $(CFLAGS) sounds correct,

ALL_CFLAGS used to be there in Emacs 23.1. It was removed in r1.461,
2009-12-16, by Andreas ("Don't compile prefix-args.c twice.")
I'm sure he will be happy to provide a detailed explanation.

http://cvs.savannah.gnu.org/viewvc/emacs/src/Makefile.in?root=emacs&r1=1.460&r2=1.461&pathrev=MAIN

>  except for a comment about this rule in Makefile.in, which I don't
> understand:
>
> /* We do not use ALL_LDFLAGS because LD_SWITCH_SYSTEM and LD_SWITCH_MACHINE
>    often contain options that have to do with using Emacs''s crt0,
>    which are only good with temacs.  */

IIRC, the Makefiles tried to make a distinction between flags that were
only needed to link temacs (see the various TEMACS variables, eg
LD_SWITCH_SYSTEM_TEMACS), and flags that were needed to compile separate
things like prefix-args. It's quite possible that the comment is
inaccurate or outdated though.



  parent reply	other threads:[~2011-02-16 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CMM.0.94.0.1297820041.beebe@psi.math.utah.edu>
2011-02-16 14:22 ` Pretest compilation problem Chong Yidong
2011-02-16 15:32   ` Andreas Schwab
2011-02-17  3:16     ` CC, CFLAGS, and -m32 [was Re: Pretest compilation problem] Glenn Morris
2011-02-17 17:28       ` Paul Eggert
2011-02-19 17:39         ` Chong Yidong
2011-02-19 18:14           ` Paul Eggert
2011-02-17 22:57       ` Miles Bader
2011-02-16 19:11   ` Glenn Morris [this message]
2011-02-16 22:22     ` Pretest compilation problem Andreas Schwab
2011-02-17  1:40       ` Chong Yidong

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=4y7hczeqvq.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@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 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).