SCIENTIFIC-LINUX-DEVEL Archives

July 2007

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: SL50: m4 version, autoconf clash, rebuilding cups...
From:
Jon Peatfield <[log in to unmask]>
Reply To:
Jon Peatfield <[log in to unmask]>
Date:
Wed, 18 Jul 2007 23:45:57 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (17 lines) 
Just rebuilding autoconf on an SL50 machine does indeed seem to fix it:

$ rpm -q autoconf
autoconf-2.59-12.JSPTEST.noarch
$ rpm -ql autoconf | egrep m4f | xargs egrep 'frozen state file gen'
/usr/share/autoconf/autoconf/autoconf.m4f:# This is a frozen state file generated by GNU M4 1.4.5
/usr/share/autoconf/autotest/autotest.m4f:# This is a frozen state file generated by GNU M4 1.4.5
/usr/share/autoconf/m4sugar/m4sh.m4f:# This is a frozen state file generated by GNU M4 1.4.5
/usr/share/autoconf/m4sugar/m4sugar.m4f:# This is a frozen state file generated by GNU M4 1.4.5

and now the cups package seems to build as expected...  Was the autoconf 
built this way to work round some other problem?  I'm rather puzzled that 
I'd not hit it before but maybe packages using autoconf just don't often 
check for mkstemp.

  -- Jon

ATOM RSS1 RSS2