all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: don't process $(LDFLAGS) with prefix-args
Date: Wed, 26 Mar 2003 17:31:50 -0500	[thread overview]
Message-ID: <m34r5p3gk3.fsf@multivac.cwru.edu> (raw)

Earlier versions of Emacs had a bug where user-supplied $(LDFLAGS)
would be processed by prefix-args when building temacs.  The bug was
fixed for 21.2 (or perhaps earlier), but it's back again in 21.3.

User-supplied $(LDFLAGS) is used with both $(CC) and, when building
temacs, $(LD).  Since it's used with $(CC), it may already contain
-Wl, or -Xlinker arguments.  So if $(LD) is $(CC) (with or without
-nostdlib), $(LDFLAGS) should not be re-escaped with -Xlinker.

If $(LD) is ld, then (currently) you're stuck; you can't pass anything
in $(LDFLAGS) except what is intelligible to both $(CC) and ld
directly.  This could be fixed by using prefix-args whenever we pass
$(LDFLAGS) to $(CC), but not when we pass $(LDFLAGS) to ld; then the
instructions would have to tell users to pass flags as they should
appear to ld, instead of as they should appear to $(CC).

The Makefile could be made to work this way on all systems: use
prefix-args whenever we pass $(LDFLAGS) to $(CC) (including when we
pass it to $(LD), on systems where $(LD) is $(CC)), but not when we
pass it to $(LD) if $(LD) is ld.  This is a tradeoff between
consistency across platforms and similarity with other packages on
systems where $(LD) is $(CC).


paul

             reply	other threads:[~2003-03-26 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 22:31 Paul Jarc [this message]
2003-03-27 19:04 ` don't process $(LDFLAGS) with prefix-args Richard Stallman
2003-03-27 20:38   ` Paul Jarc
2003-03-28 15:21     ` Richard Stallman
2003-03-28 18:08     ` Paul Jarc

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=m34r5p3gk3.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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.