public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/64708] libgccjit installed twice Date: Mon, 26 Jan 2015 17:56:00 -0000 [thread overview] Message-ID: <bug-64708-4-2PnUsqcoV2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64708-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64708 --- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> --- [david@c64 install]$ ll $(find -name "libgccjit.so*") -rwxr-xr-x. 1 david david 78637910 Jan 26 12:59 ./libexec/gcc/x86_64-unknown-linux-gnu/5.0.0/libgccjit.so lrwxrwxrwx. 1 david david 14 Jan 26 12:59 ./lib/libgccjit.so -> libgccjit.so.0 lrwxrwxrwx. 1 david david 18 Jan 26 12:59 ./lib/libgccjit.so.0 -> libgccjit.so.0.0.1 -rwxr-xr-x. 1 david david 78637910 Jan 26 12:59 ./lib/libgccjit.so.0.0.1 The libdir one is from gcc/jit/Make-lang.in: jit.install-common: installdirs $(INSTALL_PROGRAM) $(LIBGCCJIT_FILENAME) \ $(DESTDIR)/$(libdir)/$(LIBGCCJIT_FILENAME) (...snip...) The libexec one is from gcc/Makefile.in: # Install the compiler executables built during cross compilation. install-common: native lang.install-common installdirs for file in $(COMPILERS); do \ if [ -f $$file ] ; then \ rm -f $(DESTDIR)$(libexecsubdir)/$$file; \ $(INSTALL_PROGRAM) $$file $(DESTDIR)$(libexecsubdir)/$$file; \ else true; \ fi; \ done (...snip...) since COMPILERS contains "libgccjit.so".
next prev parent reply other threads:[~2015-01-26 17:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-21 12:05 [Bug jit/64708] New: " doko at gcc dot gnu.org 2015-01-26 17:56 ` dmalcolm at gcc dot gnu.org [this message] 2015-01-26 20:30 ` [Bug jit/64708] " dmalcolm at gcc dot gnu.org 2015-01-26 20:33 ` dmalcolm 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-64708-4-2PnUsqcoV2@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).