public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jimis at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/49970] New: "make prefix=... install" doesn't work Date: Wed, 03 Aug 2011 17:48:00 -0000 [thread overview] Message-ID: <bug-49970-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49970 Summary: "make prefix=... install" doesn't work Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: jimis@gmx.net On a multilib x86_64 config, I tried doing "make prefix=$HOME/mydir install". Installation failed in directory "x86_64-unknown-linux-gnu/32/libgfortran/" because it tried writing to some dir under /usr/local. Looking into the generated Makefile in that path I can see that the default prefix, /usr/local, was hardcoded in several points. Shouldn't it be ${prefix} instead of /usr/local?
next reply other threads:[~2011-08-03 17:48 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-03 17:48 jimis at gmx dot net [this message] 2011-08-03 18:49 ` [Bug libfortran/49970] " kargl at gcc dot gnu.org 2011-08-03 19:02 ` jimis at gmx dot net 2011-08-03 19:04 ` joseph at codesourcery dot com 2011-08-03 19:09 ` sgk at troutmask dot apl.washington.edu 2011-08-03 19:32 ` jimis at gmx dot net 2011-08-04 9:36 ` rguenth at gcc dot gnu.org 2012-07-08 3:26 ` jimis at gmx dot net 2012-07-08 3:30 ` jimis at gmx dot net 2012-07-08 8:20 ` joseph at codesourcery dot com 2012-07-08 8:26 ` schwab@linux-m68k.org 2012-07-08 11:05 ` redi at gcc dot gnu.org 2012-07-09 9:53 ` jimis at gmx dot net
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-49970-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: 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).