public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "peb at mppmu dot mpg dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/30859] New: libiberty.a is installed in very bad locations Date: Mon, 19 Feb 2007 15:05:00 -0000 [thread overview] Message-ID: <bug-30859-748@http.gcc.gnu.org/bugzilla/> (raw) The x86_64-linux-gnu bi-arch compiler installs the 64-Bit version of libiberty.a in /usr/lib/ (destroying any perfectly good 32-Bit version) and possibly the 32-Bit version in /usr/lib/32/. If these libraries should be installed at all (which I doubt), then in /usr/lib64/ and /usr/lib/, i.e., the make target "install_to_libdir" should install the library in "$(libdir)$(MULTIOSDIR)" instead of "$(libdir)$(MULTISUBDIR)". I'm not sure where to install the headers (if at all). -- Summary: libiberty.a is installed in very bad locations Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: peb at mppmu dot mpg dot de GCC build triplet: x86_64-linux-gnu GCC host triplet: x86_64-linux-gnu GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30859
next reply other threads:[~2007-02-19 15:05 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-19 15:05 peb at mppmu dot mpg dot de [this message] 2007-02-19 18:11 ` [Bug other/30859] " ebotcazou at gcc dot gnu dot org
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-30859-748@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).