Alex Owen wrote:
> Alex Owen wrote:
>> Hello,
>> I need to patch  xorg-x11-server-1.1.1-48.76.el5_5.2.src.rpm for a 
>> mouse bug:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=492129
>> https://bugzilla.redhat.com/show_bug.cgi?id=529717
>>
>>
>> As a first step I have tried building the above src.rpm on SL5.5 by 
>> (all as
>> root) installing the src.rpm then:
>>
>> # cd /usr/src/redhat/SPECS
>> # rpmbuild -ba xorg-x11-server.spec
>>
>> I seem to hit a autoreconfig error.
>>
>> Any hints?? Am I doing something obviously stupid in trying to 
>> rebuild this on
>> SL5.5?
>>
>> (I will probably add more info on Monday as I know this is sketchy 
>> but I'm
>> sure anyone who has encountered this problem will recognise what I am 
>> describing!)
>>
>> Have a good weekend.
>>
>> Alex Owen
>>
>>   
> 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'
>

unpacking the centos  autoconf rpm (with rpm2cpio etc) I find:

$ 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.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

So if CentOS are doing the same as TUV then we have a binary bug in out 
m4 rpm.
The fix appears to be a src.rpm rebuild on a plain SL5 machine.

Regards
Alex Owen

> That would tell us what TUV has done so we can be bug for bug 
> compatible!!!
>
>
> My gut instinct is that a linux distribution should be selfo 
> consistent and self hosting and so I'm attempting the solution from [1].
>
> Regards
>
> Alex Owen
>
>
>
>
>
> [1]
>
> Date: Wed, 18 Jul 2007 23:45:57 +0100 (BST)
> From: Jon Peatfield <[log in to unmask]>
> Subject: Re: SL50: m4 version, autoconf clash, rebuilding cups...
> In-reply-to: <[log in to unmask]>
> Sender: [log in to unmask]
> To: Jon Peatfield <[log in to unmask]>
> Cc: [log in to unmask]
> Message-id: <[log in to unmask]>
> References: <[log in to unmask]>
>
> 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
>
>
>
>
> [2]
>
> Date: Fri, 15 Jun 2007 16:07:02 -0500 (CDT)
> From: Connie Sieh <[log in to unmask]>
> Subject: Re: m4
> In-reply-to: <[log in to unmask]>
> Sender: [log in to unmask]
> To: Urs Beyerle <[log in to unmask]>
> Cc: [log in to unmask]
> Message-id: <[log in to unmask]>
> References: <[log in to unmask]>
>
> On Fri, 15 Jun 2007, Urs Beyerle wrote:
>> Hi,
>> because I had a similar problem (I tried to rebuild kdebase) as
>> described in the SL-Users mail list topic "Any hint on 'builtin
>> `mkstemp' requested by frozen file is not supported'?"
>>
>> Is there a reason why m4-1.4.8-1 from SL is only in the SRPMS
>> repository, but not in the RPM repositories?
>> ftp://ftp.scientificlinux.org/linux/scientific/50/SRPMS/SL/m4-1.4.8-1.src.rpm 
>>
>> ftp://ftp.scientificlinux.org/linux/scientific/50/i386/SL/m4-1.4.5-3.el5.1.i386.rpm 
>>
>>
>> I know RHEL5 has only m4-1.4.5-3.el5.1.
>
> Yes that is the reason.
> I have it in SRPMS so others that do building have a m4 that works 
> better.
> -Connie Sieh
>
>>
>> Urs
>>