Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/devel
In directory 
sc8-pr-cvs5.sourceforge.net:/tmp/cvs-serv24391/10.3/unstable/main/finkinfo/devel

Modified Files:
        m4.info 
Added Files:
        m4.patch 
Log Message:
Add a fix from 1.4.9 that allows building with the buildfink script


Index: m4.info
===================================================================
RCS file: /cvsroot/fink/dists/10.3/unstable/main/finkinfo/devel/m4.info,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- m4.info     8 Mar 2007 15:28:03 -0000       1.8
+++ m4.info     28 Mar 2007 07:58:50 -0000      1.9
@@ -4,6 +4,9 @@
 Source: mirror:gnu:%n/%n-%v.tar.bz2
 Source-MD5: 6bbf917e5d8fab20b38d43868c3944d3
 SetCFLAGS: -mdynamic-no-pic -Os
+PatchFile: %n.patch
+PatchFile-MD5: 58493ebf613baf21f6a7e42bea84749c
+BuildDepends: fink (>= 0.24.12)
 CompileScript: <<
   CPP= ./configure %c
   make
@@ -21,6 +24,12 @@
   Enable self-tests...only take a minute or two, and would have
   caught the bugs we had to patch.
 <<
+DescPort: <<
+  Patch pulled in from version 1.4.9 that fixes building if
+  run via the script buildfink. See
+  http://www.nabble.com/'make-check'-from-system()-under-Python-t3170044.html
+  for more infos.
+<<
 Description: Advanced macro processing language
 License: GPL
 Homepage: http://www.seindal.dk/rene/gnu/

--- NEW FILE: m4.patch ---
diff -Naur m4-1.4.8_orig/doc/m4.texinfo m4-1.4.8/doc/m4.texinfo
--- m4-1.4.8_orig/doc/m4.texinfo        2007-03-27 17:14:46.000000000 +0200
+++ m4-1.4.8/doc/m4.texinfo     2007-03-27 17:17:23.000000000 +0200
@@ -4808,17 +4808,19 @@
 @comment exits normally rather than letting the signal terminate it).
 @comment Also, TERM is flaky, as it can also kill the running m4 on
 @comment systems where /bin/sh does not create its own process group.
[EMAIL PROTECTED] That leaves KILL and PIPE as the two signals tested.
[EMAIL PROTECTED] And PIPE is unreliable, since people tend to run with it 
[EMAIL PROTECTED] ignored, with m4 inheriting that choice.  That leaves KILL as 
[EMAIL PROTECTED] the only signal we can reliably test. 
 @example
 dnl This test assumes kill is a shell builtin, and that signals are
 dnl recognizable.
 ifdef(`__unix__', ,
       `errprint(` skipping: syscmd does not have unix semantics
 ')m4exit(`77')')dnl
-syscmd(`kill -13 $$')
+syscmd(`kill -9 $$')
 @result{}
 sysval
[EMAIL PROTECTED]
[EMAIL PROTECTED]
 esyscmd(`kill -9 $$')
 @result{}
 sysval


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-commits

Reply via email to