public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrnieder at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/14664] changing prefix breaks "make check-abi-libc"
Date: Wed, 03 Oct 2012 20:28:00 -0000	[thread overview]
Message-ID: <bug-14664-131-RShg7kEBxz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14664-131@http.sourceware.org/bugzilla/>


http://sourceware.org/bugzilla/show_bug.cgi?id=14664

Jonathan Nieder <jrnieder at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #2 from Jonathan Nieder <jrnieder at gmail dot com> 2012-10-03 20:28:28 UTC ---
Are you saying that changing the prefix is not supported?  configure
should refuse to set the prefix and error out in that case.

Or are you saying that programs will break due to _nl_default_dirname
changing size?  Perhaps _nl_default_dirname should not change based on
the prefix then?

I can't see how unexplained build failures when passing --prefix would
not be a bug, so I'm reopening the report.  I'll be happy to mark the
bug as invalid myself if I have made a mistake.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-10-03 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 19:18 [Bug build/14664] New: " jrnieder at gmail dot com
2012-10-03 20:24 ` [Bug build/14664] " schwab@linux-m68k.org
2012-10-03 20:28 ` jrnieder at gmail dot com [this message]
2012-10-27  7:43 ` siddhesh at redhat dot com
2014-06-17  4:11 ` fweimer 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-14664-131-RShg7kEBxz@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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. 
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).