public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matthew at linuxfromscratch dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/56780] New: --disable-install-libiberty still installs libiberty.a Date: Fri, 29 Mar 2013 13:24:00 -0000 [thread overview] Message-ID: <bug-56780-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56780 Bug #: 56780 Summary: --disable-install-libiberty still installs libiberty.a Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: matthew@linuxfromscratch.org I'd like to build GCC with --disable-install-libiberty so that the version of libiberty.a provided by Binutils that is already installed will not be overwritten. However, the libiberty.a library is still installed even with that flag specified. My full configure invocation (run from within ~/gcc-build) is: ../gcc-4.8.0-version;/configure --prefix=/usr \ --libexecdir=/usr/lib \ --enable-shared \ --enable-threads=posix \ --enable-__cxa_atexit \ --enable-clocale=gnu \ --enable-languages=c,c++ \ --disable-multilib \ --disable-bootstrap \ --disable-install-libiberty \ --with-system-zlib Additionally, libiberty's configure script's help output states: ' --enable-install-libiberty Install headers for end users' For clarity, that should probably read: 'Install headers and static library for end users'. That way, it's in agreement with what is also mentioned in libiberty.texi. Thanks, Matt.
next reply other threads:[~2013-03-29 13:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-29 13:24 matthew at linuxfromscratch dot org [this message] 2013-04-03 14:04 ` [Bug other/56780] " matthew at linuxfromscratch dot org 2013-05-13 16:40 ` redi at gcc dot gnu.org 2013-05-14 11:54 ` matthew at linuxfromscratch dot org 2013-06-04 14:14 ` palves at redhat dot com 2013-06-04 19:26 ` yselkowitz at users dot sourceforge.net 2013-06-04 20:10 ` yselkowitz at users dot sourceforge.net 2013-08-05 10:14 ` 2013.bugzilla.gcc.gnu.org at ingomueller dot net 2014-01-06 8:49 ` knrstaj at gmail dot com 2014-01-06 18:23 ` vapier at gentoo 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-56780-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).