From: Matthias Klose <doko@ubuntu.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: GCJ-patches <java-patches@gcc.gnu.org>,
"libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: [patch] [libffi] do not install libffi library, headers and documentation
Date: Tue, 12 Feb 2013 12:30:00 -0000 [thread overview]
Message-ID: <511A35DC.7060207@ubuntu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
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?
Matthias
[-- Attachment #2: noinst.diff --]
[-- Type: text/x-diff, Size: 1775 bytes --]
2013-02-12 Matthias Klose <doko@ubuntu.com>
* Makefile.am: Do not install texinfo documentation and the
libffi library.
* include/Makefile.am: Do not install header files.
* man/Makefile.am: Do not install man pages.
* Makefile.in, include/Makefile.in, man/Makefile.in: Regenerate.
Index: Makefile.am
===================================================================
--- Makefile.am (Revision 195973)
+++ Makefile.am (Arbeitskopie)
@@ -49,7 +49,7 @@
# Defines info, dvi, pdf and html targets
MAKEINFOFLAGS = -I $(srcdir)/../gcc/doc/include
-info_TEXINFOS = doc/libffi.texi
+noinst_info_TEXINFOS = doc/libffi.texi
# AM_CONDITIONAL on configure option --generated-files-in-srcdir
if GENINSRC
@@ -130,8 +130,7 @@
MAKEOVERRIDES=
-toolexeclib_LTLIBRARIES = libffi.la
-noinst_LTLIBRARIES = libffi_convenience.la
+noinst_LTLIBRARIES = libffi.la libffi_convenience.la
libffi_la_SOURCES = src/prep_cif.c src/types.c \
src/raw_api.c src/java_raw_api.c src/closures.c
Index: include/Makefile.am
===================================================================
--- include/Makefile.am (Revision 195973)
+++ include/Makefile.am (Arbeitskopie)
@@ -9,4 +9,4 @@
gcc_version := $(shell cat $(top_srcdir)/../gcc/BASE-VER)
toollibffidir := $(libdir)/gcc/$(target_alias)/$(gcc_version)/include
-toollibffi_HEADERS = ffi.h ffitarget.h
+noinst_HEADERS = ffi.h ffitarget.h
Index: man/Makefile.am
===================================================================
--- man/Makefile.am (Revision 195973)
+++ man/Makefile.am (Arbeitskopie)
@@ -4,5 +4,5 @@
EXTRA_DIST = ffi.3 ffi_call.3 ffi_prep_cif.3 ffi_prep_cif_var.3
-man_MANS = ffi.3 ffi_call.3 ffi_prep_cif.3 ffi_prep_cif_var.3
+noinst_man_MANS = ffi.3 ffi_call.3 ffi_prep_cif.3 ffi_prep_cif_var.3
next reply other threads:[~2013-02-12 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 12:30 Matthias Klose [this message]
2013-02-12 12:44 ` Richard Biener
2013-02-12 12:46 ` Richard Biener
2013-02-18 17:03 ` Matthias Klose
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=511A35DC.7060207@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.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).