public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "teodori.serge at hotmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13890] New: make install does not consider prefix Date: Thu, 22 Mar 2012 04:09:00 -0000 [thread overview] Message-ID: <bug-13890-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13890 Bug #: 13890 Summary: make install does not consider prefix Product: glibc Version: 2.15 Status: NEW Severity: critical Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: teodori.serge@hotmail.com CC: drepper.fsp@gmail.com Classification: Unclassified When building glibc-2.15 for tool chain environment, glibc "make install" complains that "/var/db" cannot be accessed. I think the "prefix" is not applied. After creating the directory, it worked. "/var/db" now contains a "Makefile". I used as "prefix" "/opt/toolchaine", so it has to be "/opt/toolchaine/var/db". It contains as first line: DATABASES = $(wildcard /etc/passwd /etc/group /etc/ethers /etc/protocols \ /etc/rpc /etc/services /etc/shadow /etc/gshadow \ /etc/netgroup) -- 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-03-22 2:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-22 4:09 teodori.serge at hotmail dot com [this message] 2012-03-22 15:19 ` [Bug libc/13890] " ppluzhnikov at google dot com 2012-03-22 22:52 ` teodori.serge at hotmail dot com 2012-03-26 10:23 ` aj at suse dot de 2014-06-13 14:07 ` 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-13890-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).