public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ljrittle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/56259] GCC's configure script has a hard-coded setting of 'with_gmp' for FreeBSD Date: Mon, 18 Feb 2013 22:25:00 -0000 [thread overview] Message-ID: <bug-56259-4-lweSp349eI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56259-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56259 Loren Rittle <ljrittle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ljrittle at gcc dot gnu.org --- Comment #2 from Loren Rittle <ljrittle at gcc dot gnu.org> 2013-02-18 22:25:27 UTC --- This block of code was added to handle a special case seen on FreeBSD: (a) on some versions of FreeBSD circa 2004, the system installed copy of gmp.h was too old to support gcc (b) by default, FreeBSD ports system installs into /usr/local I note that the claimed serious side effects only happen when one installed gmp from ports (or otherwise installed it into /usr/local) *and* one attempted to build a gcc with a copy of gmp co-located with gcc source. We need to think about the default user (which will likely not unpack gmp, mpfr and mpc) into the gcc source tree. We would need input from Gerald (assuming he still supports the official FreeBSD ports builds of gcc). Blinding accepting a patch to remove this block of configuration will likely break this downstream; even if it otherwise makes logical sense to do so. Regards, Loren
next prev parent reply other threads:[~2013-02-18 22:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-08 23:02 [Bug bootstrap/56259] New: " novulae at hotmail dot com 2013-02-10 12:25 ` [Bug bootstrap/56259] " rguenth at gcc dot gnu.org 2013-02-18 22:25 ` ljrittle at gcc dot gnu.org [this message] 2013-02-20 1:47 ` novulae at hotmail dot com 2021-08-16 23:15 ` pinskia at gcc dot gnu.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-56259-4-lweSp349eI@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).