SCIENTIFIC-LINUX-DEVEL Archives

October 2010

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:
From:
Alex Owen <[log in to unmask]>
Reply To:
Alex Owen <[log in to unmask]>
Date:
Sun, 17 Oct 2010 22:12:52 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (78 lines)
Alan Bartlett wrote:
> On 17 October 2010 16:55, Alex Owen <[log in to unmask]> wrote:
>
>   
>> Ah...  I seem to have hit an issue with a slightly schizophrenic SL build
>> system!
>> Joy!
>>
>> Please Please Please can we try and avoid this or at least document simmilar
>> issues for SL6???
>>
>> Is seems that m4 in SL5 is version 1.4.5-3.el5.1 but that there is an SL5
>> SRPM at version 1.4.8-1 which
>> has been used to build autoconf 2.59-12.
>>
>> According to [1] rebuilding autoconf srpm against m4-1.4.5-3.el5.1 seems to
>> fix things.
>> According to [2] perhaps I should install m4-1.4.8-1.
>>
>> Perhaps someone with an upstream RHEL5 could run the comand from [1] and
>> post the output to this thread.
>> rpm -ql autoconf | egrep m4f | xargs egrep 'frozen state file gen'
>>     
>
> [ajb@Build32R5 ~]$ 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
> [ajb@Build32R5 ~]$
>
> [ajb@Build64R5 ~]$ 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
> [ajb@Build64R5 ~]$
>
> As requested, the above is the output returned by 32- & 64-bit RHEL 5.5
>
> Alan.
>   
Thanks for that Alan. That confirms that CentOS and RHEL build autoconf 
against M4 1.4.5
 
This is a grep form an rpm2cpio unpacked SL5 autoconf rpm
find ./ |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.8
./usr/share/autoconf/autotest/autotest.m4f:# This is a frozen state file 
generated by GNU M4 1.4.8
./usr/share/autoconf/m4sugar/m4sh.m4f:# This is a frozen state file 
generated by GNU M4 1.4.8
./usr/share/autoconf/m4sugar/m4sugar.m4f:# This is a frozen state file 
generated by GNU M4 1.4.8


Thus SL autoconf is built against M4 1.4.8 not M4 1.4.5 like upstream 
ans so I think that confirms a bug in SL.
The solution to the bug seems to be to build autoconf on a clean SL5 
install (containing the standard SL m4 rpm).

Now of course I am intrigued as to why the build system has a newer m4 
version on it at all??

Regards
Alex Owen

ATOM RSS1 RSS2