From: Matthias Klose <doko@ubuntu.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
GCJ-patches <java-patches@gcc.gnu.org>,
"libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: [patch] [libffi] do not install libffi library, headers and documentation
Date: Mon, 18 Feb 2013 17:03:00 -0000 [thread overview]
Message-ID: <51225EBE.1050509@ubuntu.com> (raw)
In-Reply-To: <CAFiYyc1u5t9YKY5Pi_uZvej6xy4ihW_CvgsoR=MqPjKoZ6=9_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Am 12.02.2013 13:45, schrieb Richard Biener:
> On Tue, Feb 12, 2013 at 1:44 PM, Richard Biener
> <richard.guenther@gmail.com> wrote:
>> On Tue, Feb 12, 2013 at 1:30 PM, Matthias Klose <doko@ubuntu.com> wrote:
>>> The libffi library, headers and documentation are still installed, although
>>> libffi provides separate releases for a long time. So do not install these
>>> anymore as part of a GCC install. Tested with a build and an install with go
>>> and java enabled (both using libffi_convenience). Ok for the trunk?
>>
>> openSUSE is using the GCC provided libffi, so no, this is not ok (not at this
>> stage anyway). Also proper not-installing libffi would work by disabling
>> the maybe-install-target-libffi at the toplevel, not changing libffi makfiles
>> (which are supposed to be imported from upstream, no?)
>
> Thus, add no_install= true; to the libffi target module
updated patch attached, checked with a make install that no ffi headers and
libraries are installed. If not ok for 4.8, ok for 4.9 when it opens?
Matthias
[-- Attachment #2: noinst.diff --]
[-- Type: text/x-diff, Size: 1720 bytes --]
* Makefile.def (target_modules): Don't install libffi.
* Makefile.in: Regenerate.
Index: Makefile.def
===================================================================
--- Makefile.def (Revision 196115)
+++ Makefile.def (Arbeitskopie)
@@ -138,7 +138,7 @@
missing=maintainer-clean; };
target_modules = { module= winsup; };
target_modules = { module= libgloss; no_check=true; };
-target_modules = { module= libffi; };
+target_modules = { module= libffi; no_install=true; };
target_modules = { module= libjava; raw_cxx=true;
extra_configure_flags="$(EXTRA_CONFIGARGS_LIBJAVA)"; };
target_modules = { module= zlib; };
Index: Makefile.in
===================================================================
--- Makefile.in (Revision 196115)
+++ Makefile.in (Arbeitskopie)
@@ -38710,13 +38710,8 @@
@if target-libffi
maybe-install-target-libffi: install-target-libffi
-install-target-libffi: installdirs
- @: $(MAKE); $(unstage)
- @r=`${PWD_COMMAND}`; export r; \
- s=`cd $(srcdir); ${PWD_COMMAND}`; export s; \
- $(NORMAL_TARGET_EXPORTS) \
- (cd $(TARGET_SUBDIR)/libffi && \
- $(MAKE) $(TARGET_FLAGS_TO_PASS) install)
+# Dummy target for uninstallable.
+install-target-libffi:
@endif target-libffi
@@ -38725,13 +38720,8 @@
@if target-libffi
maybe-install-strip-target-libffi: install-strip-target-libffi
-install-strip-target-libffi: installdirs
- @: $(MAKE); $(unstage)
- @r=`${PWD_COMMAND}`; export r; \
- s=`cd $(srcdir); ${PWD_COMMAND}`; export s; \
- $(NORMAL_TARGET_EXPORTS) \
- (cd $(TARGET_SUBDIR)/libffi && \
- $(MAKE) $(TARGET_FLAGS_TO_PASS) install-strip)
+# Dummy target for uninstallable.
+install-strip-target-libffi:
@endif target-libffi
next prev parent reply other threads:[~2013-02-18 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 12:30 Matthias Klose
2013-02-12 12:44 ` Richard Biener
2013-02-12 12:46 ` Richard Biener
2013-02-18 17:03 ` Matthias Klose [this message]
2013-02-19 9:13 ` Richard Biener
2013-03-26 20:04 ` [ping] " Matthias Klose
2013-03-26 20:28 ` Ian Lance Taylor
2013-03-26 20:48 ` Anthony Green
2013-03-30 11:26 ` Matthias Klose
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=51225EBE.1050509@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.org \
--cc=richard.guenther@gmail.com \
/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).