From: "Bernhard R. Link" <brlink@debian.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 4/4] Makefile: Don't pass $(ALL_CFLAGS) to the linker
Date: Sun, 27 Jun 2010 11:44:34 +0200 [thread overview]
Message-ID: <20100627094433.GA21771@pcpool00.mathematik.uni-freiburg.de> (raw)
In-Reply-To: <4C264019.6030408@ramsay1.demon.co.uk>
* Ramsay Jones <ramsay@ramsay1.demon.co.uk> [100626 20:02]:
> Really? I thought that the general scheme was something like:
>
> - LDFLAGS is for options which only affects the operation of
> the linker (e.g. -L).
> - CPPFLAGS is for options which only affects the operation of
> the C pre-processor (e.g. -I, -D, -U)
> - CFLAGS is for options which only affects the operation of
> the compiler proper.
I think the problem are options like -g or -m64 and the like which
you also want to give to the linker on some systems, so it is quite
common and I'd say recommended to have the compiling stage get
CPPFLAGS and CFLAGS and the linking stage getting CFLAGS and LDFLAGS
(and link using the compiler, otherwise you might miss libraries anyway).
I do not know if automake started with this, or if it is older.
> Also, the last time I was forced to use automake (yuck), I noticed that
> it passed CPPFLAGS to the linker; I consider this to be a bug in
> automake. :-P
Huh? Never heared of that bug, it must be more than 15 years ago. Are
you sure it was not CFLAGS it passed to the linker?
Bernhard R. Link
No need to CC me, I'm subscribed...
next prev parent reply other threads:[~2010-06-27 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 19:48 [PATCH 4/4] Makefile: Don't pass $(ALL_CFLAGS) to the linker Ramsay Jones
2010-06-23 21:08 ` Jonathan Nieder
2010-06-26 17:59 ` Ramsay Jones
2010-06-26 18:19 ` Jonathan Nieder
2010-06-30 19:40 ` Ramsay Jones
2010-06-30 21:16 ` Andreas Schwab
2010-06-27 9:44 ` Bernhard R. Link [this message]
2010-06-24 15:30 ` Peter Harris
2010-06-25 20:24 ` Ramsay Jones
2010-06-27 20:45 ` Peter Harris
2010-06-30 19:52 ` Ramsay Jones
2010-07-01 21:27 ` Peter Harris
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=20100627094433.GA21771@pcpool00.mathematik.uni-freiburg.de \
--to=brlink@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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.
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 NNTP newsgroup(s).