public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4345] Logic in frysk-common.ac to determine 64-bit library location is flawed Date: Wed, 11 Apr 2007 02:48:00 -0000 [thread overview] Message-ID: <20070411024755.17190.qmail@sourceware.org> (raw) In-Reply-To: <20070411030621.4345.kris.van.hees@oracle.com> ------- Additional Comments From cagney at redhat dot com 2007-04-11 03:47 ------- (In reply to comment #0) > 1) The first line will not have the desired result for any host where the > PKG_CONFIG_PATH has a non-standard path at the beginning of the list, > which is commonly done for local overrides. I'm not sure I follow. The intent here is to provide an additional system-like default. If the user modifies PKG_CONFIG_PATH then the user's override should take precident. > 2) The PKG_CONFIG_PATH environment variable should not require a specific > Frysk component for building Frysk, given that we can (and should be able > to) build Frysk on a system where Frysk is not yet installed. As such, > there should not be any need to have this line in common/frysk-common.ac at > all. On RHEL 4 the frysk.rpm first builds and then installs into /usr/lib/frysk newer but unsupported gnome and other libraries that are prereq's to building frysk. Consequently, for someone building CVS frysk from scratch, the recommended approach is to first install the frysk.rpm (getting the prereq's for free :-) and then build frysk. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4345 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-04-11 2:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-11 2:06 [Bug general/4345] New: " kris dot van dot hees at oracle dot com 2007-04-11 2:48 ` cagney at redhat dot com [this message] 2007-04-11 3:18 ` [Bug general/4345] " kris dot van dot hees at oracle dot com 2007-04-12 4:53 ` cagney at redhat dot com 2007-04-12 11:19 ` kris dot van dot hees at oracle 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=20070411024755.17190.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@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: 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).