Hello community,

here is the log from the commit of package minicom for openSUSE:Factory checked 
in at 2012-05-31 17:07:09
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/minicom (Old)
 and      /work/SRC/openSUSE:Factory/.minicom.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "minicom", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/minicom/minicom.changes  2012-01-04 
07:25:13.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.minicom.new/minicom.changes     2012-05-31 
17:07:24.000000000 +0200
@@ -1,0 +2,6 @@
+Tue May 29 12:31:16 UTC 2012 - [email protected]
+
+- fix build with automake-1.12
+  - add: automake-1.12.patch
+
+-------------------------------------------------------------------

New:
----
  automake-1.12.patch

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ minicom.spec ++++++
--- /var/tmp/diff_new_pack.F3iDXc/_old  2012-05-31 17:07:26.000000000 +0200
+++ /var/tmp/diff_new_pack.F3iDXc/_new  2012-05-31 17:07:26.000000000 +0200
@@ -37,6 +37,7 @@
 Patch5:         minicom-2.4-norootsetup.diff
 # PATCH-FIX-UPSTREAM increase permitted length of serial device (bnc#707860) 
 Patch6:         minicom-2.5-serial_device_path_length.patch
+Patch7:         automake-1.12.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 
 %description
@@ -55,6 +56,7 @@
 %patch4
 %patch5 -p1
 %patch6 -p1
+%patch7 -p1
 
 %build
 autoreconf --force --install

++++++ automake-1.12.patch ++++++
Index: minicom-2.6/configure.in
===================================================================
--- minicom-2.6.orig/configure.in
+++ minicom-2.6/configure.in
@@ -191,7 +191,6 @@ AC_CHECK_HEADERS(stdarg.h varargs.h term
 
 dnl Checks for typedefs, structures, and compiler characteristics.
 AC_C_CONST
-AM_C_PROTOTYPES
 AC_TYPE_UID_T
 AC_TYPE_MODE_T
 AC_TYPE_PID_T
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to