ports/mc
ports/mc
1
1
Форкнуть 0
Код Релизы 2 Активность
mc/m4
История
Pavel Roskin cfcf9a76df * Makefile.am: Add m4 to SUBDIRS. Set ACLOCAL_AMFLAGS so that 
m4 directory is used by aclocal.
* m4/Makefile.am: New file.
* configure.in: Substitute m4/Makefile.
* autogen.sh: Don't copy any macro files, use m4 directory.
2002-09-17 16:13:25 +00:00
..
codeset.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
gettext.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
glib.m4
Add test for glib 1.2.x.
2002-09-17 15:50:29 +00:00
glibc21.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
iconv.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
intdiv0.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
inttypes_h.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
inttypes-pri.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
inttypes.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
isc-posix.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
lcmessage.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
lib-ld.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
lib-link.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
lib-prefix.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
Makefile.am
* Makefile.am: Add m4 to SUBDIRS. Set ACLOCAL_AMFLAGS so that
2002-09-17 16:13:25 +00:00
pkg.m4
Add test from pkgconfig 0.12.0.
2002-09-17 15:53:50 +00:00
progtest.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
README
README about the files in this directory.
2002-09-17 15:46:55 +00:00
stdint_h.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
uintmax_t.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00
ulonglong.m4
Macro files from gettext 0.11.5.
2002-09-17 15:47:19 +00:00

README 

This directory contains m4 macro files for GNU Midnight Commander,
Neither of those files is maintainted here.  Don't change those
files unless:

1) you are upgrading them from the latest version of the package where
they are maintained

OR

2) it's a fix that is needed right now AND this fix has been submitted
to the proper maintainer.

Otherwise, your changes will be lost.