This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Attached 3-lines patch changes libgfortran/Makefile.am so that libgfortranbegin.a, a small static library linked with all gfortran programs, is installed into /usr/lib/gcc/target/4.2.0/ rather than the system-wide /usr/lib.
The automake magic is from Tom Tromey, but I'd like to have the opinion of a build machinery specialist before commiting: can someone confirm that the compiler libraries directory is indeed where libgfortranbegin.a should go?
Thanks, FX
Attachment:
libgfortranbegin.ChangeLog
Description: Binary data
Index: Makefile.am =================================================================== --- Makefile.am (revision 117225) +++ Makefile.am (working copy) @@ -6,11 +6,11 @@ ## May be used by toolexeclibdir. gcc_version := $(shell cat $(top_srcdir)/../gcc/BASE-VER) -toolexeclib_LTLIBRARIES = libgfortran.la libgfortranbegin.la - +toolexeclib_LTLIBRARIES = libgfortran.la libgfortran_la_LDFLAGS = -version-info `grep -v '^\#' $(srcdir)/libtool-version` -lm $(extra_ldflags_libgfortran) -## This should really go in the compiler lib dir, not the system lib dir. +myexeclib_LTLIBRARIES = libgfortranbegin.la +myexeclibdir = $(libdir)/gcc/$(target_alias)/$(gcc_version) libgfortranbegin_la_SOURCES = fmain.c libgfortranbegin_la_LDFLAGS = -static
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |