From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: weird LD definition in src/Makefile
Date: Tue, 20 Aug 2002 18:13:40 -0400 [thread overview]
Message-ID: <m3elctw53p.fsf@multivac.cwru.edu> (raw)
In-Reply-To: m3ptweivfg.fsf@multivac.cwru.edu
Ok, I got it to work with "LD=$(CC) -nostdlib" by editing
src/s/gnu-linux.h to refer to the right paths for crt*.o on my system.
However, I still have the problem I had weeks ago when I was getting
LD=ld - namely, that LDFLAGS is restricted to the intersection of
flags that can be passed to gcc or directly to ld. But it's for a
different reason this time: sometimes LDFLAGS is passed directly to
gcc, and sometimes it's filtered through prefix-args first (by way of
ALL_LDFLAGS, when building temacs). If I set LDFLAGS to include, say,
"-rpath /dir", then gcc will complain when it sees that. If I set it
to include "-Wl,-rpath,/dir", then gcc won't complain, but the
prefix-args case will break, because gcc will see
"-Xlinker -Wl,-rpath,/dir", and do ld will see "-Wl,-rpath,/dir"
instead of "-rpath /dir".
I think prefix-args should be used only for flags specified by the
Makefile itself (and obviously, only when LD=$(CC)..., but that's
handled correctly AFAICT), not those given by the user. Maybe it
would be easiest to use prefix-args while generating the Makefile,
when only the self-supplied flags are at hand, instead of having the
Makefile rule apply it to possibly the wrong set of flags.
paul
prev parent reply other threads:[~2002-08-20 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 17:56 weird LD definition in src/Makefile Paul Jarc
2002-08-20 22:13 ` Paul Jarc [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
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=m3elctw53p.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 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).