public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alfred.minarik.1 at aon dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/64296] New: link failure of libgccjit.so for "in tree" gmp/mpc/mpfr/isl
Date: Sat, 13 Dec 2014 10:23:00 -0000	[thread overview]
Message-ID: <bug-64296-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64296

            Bug ID: 64296
           Summary: link failure of libgccjit.so for "in tree"
                    gmp/mpc/mpfr/isl
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: jit
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: alfred.minarik.1 at aon dot at

using "in tree" gmp/mpc/mpfr/isl (as following contrib/download_prerequisites)
does not work with building jit.

gcc is correctly configured with --enable-host-shared but this information is
obviously not transferd into (or ignored by ?) gmp/mpc/mpfr/isl. Those static
libraries are still build without -fPIC,resulting in relocation failures while
linking libgccjit.so.

am@linux:~/tools/gcc> LANG=C gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local2/gcc_4.9.2/lib/gcc/x86_64-unknown-linux-gnu/4.9.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /home/am/tools/gcc/gcc/configure
--prefix=/usr/local2/gcc_4.9.2 --enable-languages=all,ada,go,obj-c++
Thread model: posix
gcc version 4.9.2 (GCC) 

LANG="C" $GCCSRC_/configure --prefix=/usr/local2/gcc_exp
--enable-languages=c,c++,jit --disable-multilib --enable-checking=release
--enable-host-shared


             reply	other threads:[~2014-12-13 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 10:23 alfred.minarik.1 at aon dot at [this message]
2014-12-21 17:47 ` [Bug jit/64296] " alfred.minarik.1 at aon dot at
2015-04-13 23:26 ` redi at gcc dot gnu.org
2021-05-04 12:32 ` rguenth 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-64296-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).