unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: don't process $(LDFLAGS) with prefix-args
Date: Thu, 27 Mar 2003 14:04:47 -0500	[thread overview]
Message-ID: <E18ycgB-00080l-00@fencepost.gnu.org> (raw)
In-Reply-To: <m34r5p3gk3.fsf@multivac.cwru.edu> (prj@po.cwru.edu)

    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.

Can you find the difference in 21.3 which brought back the bug?  I
don't see any change in Makefile.in between 21.2 and 21.3 that would
relate to this at all.  It appears that the use of YMF_PASS_LDFLAGS
for all of LDFLAGS remains unchanged since then.

You might want to look at whether LINKER_WAS_SPECIFIED is defined in
21.2 and in 21.3.  A change in that might affect it.

    User-supplied $(LDFLAGS) is used with both $(CC) and, when building
    temacs, $(LD).

I see it is used with $(CC) when compiling prefix-args.
Anywhere else?  Why do you use -Wl or -Xlinker args in it?
Precisely which executables do you want those options for?

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

As far as I can see, src/Makefile.in already does this, except in on
case: when compiling prefix-args itself.

  reply	other threads:[~2003-03-27 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 22:31 don't process $(LDFLAGS) with prefix-args Paul Jarc
2003-03-27 19:04 ` Richard Stallman [this message]
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

  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=E18ycgB-00080l-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).