public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/18512] make install failure with overridden prefix
Date: Wed, 10 Jun 2015 19:46:00 -0000	[thread overview]
Message-ID: <bug-18512-131-42zxYSlGHj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18512-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18512

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Martin Sebor from comment #3)
> In section 7.2.5 Variables for Installation Directories, the GNU Coding
> Standard describes the prefix fix variable as the mechanism expected to be
> used to override the standard installation directory.  If GLIBC doesn't
> supported this use case (which I would find understandable), I propose
> mentioning it in GLIBC documentation (i.e., in the INSTALL file and online).
> In fact, I already have a patch for INSTALL to that effect but have been
> waiting for feedback on this issue before submitting it.  With the patch
> accepted I think the issue can be resolved.

You are correct, it is indeed in the GNU Coding Standards, and while we strive
to adhere to the standard where possible, in this particular case we don't have
the infrastructure to support installing to an alternate prefix without a
recompilation. To do so would require a data-driven approach to determe the
prefix at runtime, and while such an approach would actually be interesting for
testing, nobody has implemented it yet (chroot, containers, or vm's are used
instead).

I would support a patch to INSTALL to correct this. Though I would like it even
more if `make install prefix=/foo` failed if /foo didn't match the configure's
prefix argument.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-06-10 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 23:31 [Bug build/18512] New: " msebor at redhat dot com
2015-06-10 18:44 ` [Bug build/18512] " carlos at redhat dot com
2015-06-10 19:04 ` msebor at redhat dot com
2015-06-10 19:46 ` carlos at redhat dot com [this message]
2015-07-02  1:22 ` msebor at redhat dot com

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=bug-18512-131-42zxYSlGHj@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).