public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chimeranet89 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug build/14089] New: Error while installing glibc to another drive (e.g.: not in /) Date: Thu, 10 May 2012 13:27:00 -0000 [thread overview] Message-ID: <bug-14089-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14089 Bug #: 14089 Summary: Error while installing glibc to another drive (e.g.: not in /) Product: glibc Version: 2.15 Status: NEW Severity: minor Priority: P2 Component: build AssignedTo: unassigned@sourceware.org ReportedBy: chimeranet89@gmail.com CC: carlos@systemhalted.org Classification: Unclassified Issuing a 'make install' command on a glibc build configured with install parameters (prefix, includedir, etc...) pointing to another drive (I'm installing it onto another disk for testing purposes) issues an installation error from the makefile "nss/Makefile", which contains a path that directly points to /var/db/Makefile despite the prefix configuration variable. I easily fixed it by editing nss/Makefile and overwriting the path manually. -- 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.
next reply other threads:[~2012-05-10 13:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-10 13:27 chimeranet89 at gmail dot com [this message] 2012-05-10 14:38 ` [Bug build/14089] " carlos_odonell at mentor dot com 2012-05-10 16:22 ` chimeranet89 at gmail dot com 2012-05-10 16:45 ` carlos_odonell at mentor dot com 2012-05-10 17:09 ` chimeranet89 at gmail dot com 2012-05-10 17:14 ` carlos_odonell at mentor dot com 2014-06-25 11:04 ` 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-14089-131@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: linkBe 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).