public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tony.theodore at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/60981] New: lto-plugin configuration doesn't test for -static-libgcc (OSX gcc -> clang)
Date: Mon, 28 Apr 2014 06:00:00 -0000	[thread overview]
Message-ID: <bug-60981-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60981

            Bug ID: 60981
           Summary: lto-plugin configuration doesn't test for
                    -static-libgcc (OSX gcc -> clang)
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tony.theodore at gmail dot com

Created attachment 32690
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32690&action=edit
lto-plugin -static-libgcc configure.ac test

Hi,

When building on OSX, gcc is a symlink to clang and doesn't accept the
-static-libgcc option.

The attached patch basically copies the "have_static_libs" test from the top
level configure.ac:1253 to the lto-plugin/configure.ac (removing the c++ parts)
- it hasn't been tested as I don't have the right version of autoconf, but
copying and modifying the corresponding section from configure works.

Cheers,

Tony


             reply	other threads:[~2014-04-28  6:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  6:00 tony.theodore at gmail dot com [this message]
2014-04-28  6:03 ` [Bug lto/60981] " tony.theodore at gmail dot com
2014-05-08 12:38 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-05-09 19:16 ` tony.theodore at gmail dot com
2014-05-13 13:47 ` ro at gcc dot gnu.org
2014-05-13 13:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-05-14  8:33 ` ro at gcc dot gnu.org
2014-05-15  9:53 ` ro at gcc dot gnu.org
2014-05-15  9:56 ` ro at gcc dot gnu.org
2014-05-15  9:57 ` ro 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-60981-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: link
Be 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).