From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Eric Wong <e@80x24.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Ronald Wampler <rdwampler@gmail.com>,
git@vger.kernel.org, mackyle@gmail.com, reubenhwk@gmail.com,
sunshine@sunshineco.com
Subject: Re: [PATCH] config.mak.uname: define NEEDS_LIBRT under Linux, for now
Date: Mon, 11 Jul 2016 10:36:53 +0000 [thread overview]
Message-ID: <20160711103653.GA29598@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <20160710221644.GA4927@whir>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Sun, Jul 10, 2016 at 10:16:44PM +0000, Eric Wong wrote:
> My Debian wheezy LTS system is still on glibc 2.13; and LTS
> distros may use older glibc, still, so lets not unnecessarily
> break things out-of-the-box.
>
> We seem to assume Linux is using glibc in our Makefiles anyways,
> so I don't think this will introduce new breakage for users of
> alternative libc implementations.
This is a good idea. If it's broken with Debian wheezy, it will also be
broken for RHEL/CentOS 6. People who really want the slimmest linkage
can use the -Wl,--as-needed flag.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-07-11 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 20:45 [PATCH] Makefile: add NEEDS_LIBRT to optionally link with librt Ronald Wampler
2016-07-07 21:14 ` Junio C Hamano
2016-07-10 22:16 ` [PATCH] config.mak.uname: define NEEDS_LIBRT under Linux, for now Eric Wong
2016-07-11 10:36 ` brian m. carlson [this message]
2016-07-11 18:44 ` Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160711103653.GA29598@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mackyle@gmail.com \
--cc=rdwampler@gmail.com \
--cc=reubenhwk@gmail.com \
--cc=sunshine@sunshineco.com \
/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://80x24.org/mirrors/git.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).