From: Mike Frysinger <vapier@gentoo.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH] memusagestat: use local glibc when linking [BZ #18465]
Date: Mon, 01 Jun 2015 15:55:00 -0000 [thread overview]
Message-ID: <20150601150158.GT4496@vapier> (raw)
In-Reply-To: <alpine.DEB.2.10.1506011436080.15677@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
On 01 Jun 2015 14:39, Joseph Myers wrote:
> On Sun, 31 May 2015, Andreas Schwab wrote:
> > Mike Frysinger <vapier@gentoo.org> writes:
> > > On 30 May 2015 22:20, Andreas Schwab wrote:
> > >> Mike Frysinger <vapier@gentoo.org> writes:
> > >> > The memusagestat is the only binary that has its own link line which
> > >> > causes it to be linked against the existing installed C library. It
> > >> > has been this way since it was originally committed in 1999, but I
> > >> > don't see any reason as to why.
> > >>
> > >> Probably because $(objpfx)memusagestat.o is compiled specially.
> > >
> > > how so ?
> >
> > # The configure.ac check for libgd and its headers did not use $SYSINCLUDES.
> > # The directory specified by --with-headers usually contains only the basic
> > # kernel interface headers, not something like libgd. So the simplest thing
> > # is to presume that the standard system headers will be ok for this file.
> > $(objpfx)memusagestat.o: sysincludes = # nothing
>
> One option is splitting out memusagestat and other installed executables
> not depending on glibc internals or required by the glibc testsuite into a
> separate package, built using an installed C library, as I suggested in
> <https://sourceware.org/ml/libc-alpha/2012-05/msg00682.html> and
> <https://sourceware.org/ml/libc-alpha/2012-11/msg00367.html>.
that makes sense to me, but doesn't preclude my patch ...
we could create a top level dir like "utils" and everything in there would be
standalone. the release scripts would create a small glibc-utils-xxx.tar.bz2 at
the same time.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-01 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 14:05 Mike Frysinger
2015-05-31 18:36 ` Andreas Schwab
2015-05-31 19:11 ` Mike Frysinger
2015-05-31 20:47 ` Andreas Schwab
2015-05-31 22:01 ` Mike Frysinger
2015-06-01 14:58 ` Joseph Myers
2015-06-01 15:24 ` Siddhesh Poyarekar
2015-06-01 15:55 ` Mike Frysinger [this message]
2015-06-01 16:22 ` Siddhesh Poyarekar
2019-04-24 12:16 ` Florian Weimer
2019-04-25 9:09 ` Florian Weimer
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=20150601150158.GT4496@vapier \
--to=vapier@gentoo.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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.
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).