Hi Andrew,

thanks for the testing and feedback. So it seems the outdated texinfo version 
was the problem, and the old m4 could have caused problems later on. Hence I 
have now fixed the autoconf and autoconf2.6 packages to depend on the latest 
versions of texinfo and m4, to make sure this problem won't pop up for other 
people.


Cheers,
Max

On 29.11.2012, at 15:57, Fowler, Andrew wrote:

> Hi Max,
> 
> Your last message caught me after I went home yesterday.
> 
> After realizing that I needed to install texinfo to get makeinfo, it's now
> at 4.13.
> 
> For the other:
> 
> [imac:~] afowler% ls -l /sw/bin/m4
> -rwxr-xr-x  1 root  admin  198328 Apr 27  2010 /sw/bin/m4*
> [imac:~] afowler% fink list m4
> Information about 12071 packages read in 2 seconds.
> (i)  m4               1.4.16-1     Advanced macro processing language
> 
> I'm leaving out all the irrelevant output from the last command. "which
> m4" points to /sw/bin/m4.
> 
> 
> OK, so I re-issued "fink -l rebuild autoconf2.6". There appear to be no
> errors, but I'm attaching the gzipped log file - a single file this time.
> 
> So I am correct in assuming this is a texinfo/makeinfo version problem?
> 
> Cheers,
> Andrew
> 
> 
> --
> C.  Andrew Fowler, Ph.D.    | University of Iowa
> Associate Director                | B291 CBRB, 500 Newton Rd.
> CCOM NMR Facility              | Iowa City, IA 52242
> 319-384-2937 (office)          | 319-335-7273 (fax)
> andrew-fow...@uiowa.edu
> 
> 
> 
> 
> On 11/28/12 7:26 PM, "Max Horn" <m...@quendi.de> wrote:
> 
>> Hi Andreas,
>> 
>> On 28.11.2012, at 19:28, Fowler, Andrew wrote:
>> 
>>> Hi again Max,
>>> 
>>> OK, here we go on the easy stuff:
>>> 
>>> [imac:main/finkinfo/devel] afowler% which makeinfo
>>> /sw/bin/makeinfo
>>> [imac:main/finkinfo/devel] afowler% makeinfo --version
>>> makeinfo (GNU texinfo) 4.8
>> 
>> That's a bit old, latest is 4.13. Can you please update to that and try
>> again? Also, there is another oddity, see below.
>> 
>>> 
>>> Copyright (C) 2004 Free Software Foundation, Inc.
>>> There is NO warranty.  You may redistribute this software
>>> under the terms of the GNU General Public License.
>>> For more information about these matters, see the files named COPYING.
>>> 
>>> As for the rest, I'd have replied sooner, but I wanted to re-grab the
>>> .info file to make sure I didn't re-insert the line incorrectly and the
>>> CVS servers have been swamped (switched to rsync). The rebuild aborted
>>> the
>>> same way as before and spit 2 files into /tmp, so they're both in the
>>> attached tarball.
>> 
>> Looking at this, I notice one odd things:
>> 
>> checking for GNU M4 that supports accurate traces... /usr/bin/m4
>> checking whether /usr/bin/m4 accepts --gnu... no
>> 
>> But autoconf2.6 depends on m4, so it should have found /sw/bin/m4. Hmm..
>> is that an old version of m4 you have? Or did you perhaps manually remove
>> /sw/bin/m4 ? What do these commands output:
>> ls -l /sw/bin/m4
>> fink list m4
>> 
>> 
>> Cheers,
>> Max
> 
> 
> 
> ________________________________
> Notice: This UI Health Care e-mail (including attachments) is covered by the 
> Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential 
> and may be legally privileged.  If you are not the intended recipient, you 
> are hereby notified that any retention, dissemination, distribution, or 
> copying of this communication is strictly prohibited.  Please reply to the 
> sender that you have received the message in error, then delete it.  Thank 
> you.
> ________________________________
> <fink-build-log_autoconf2.6_2.69-1_2012.11.29-08.54.31.gz>


------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
VERIFY Test and improve your parallel project with help from experts 
and peers. http://goparallel.sourceforge.net
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to