Re: [GD-DEVEL] release creation

On Thu, Apr 18, 2013 at 11:20 PM, Mike Frysinger <[email protected]> wrote:
> On Thursday 18 April 2013 17:02:32 Pierre Joye wrote:
>> On Thu, Apr 18, 2013 at 10:21 PM, Mike Frysinger wrote:
>> > i don't think checking in pregenerated files is the answer as timestamps
>> > can easily get skewed, and the tools one dev has on their system vs
>> > another can vary greatly.  thus everytime someone generates autotools on
>> > their system, they get a repo full of modified files.
>>
>> I agree, my only problem is that I have to find a way to get autoconf
>> 2.69 or later on my dev boxes so I can build releases. This version is
>> required to support newest ARM as far as I know (there is an issue
>> about it). Do you know if it is available somewhere for debian 6? If I
>> can avoid building it myself :)
>
> ah, it's unfortunate this misinformation has been spreading.  you do not need
> autoconf-2.69 to support aarch64.  in fact, it has nothing to do with
> autoconf.  you just need up-to-date GNU config snapshots.  if anyone tells you
> different, you should also tell them to stop spreading such misinformation :).
>
> in Gentoo, we do this by grabbing snapshots from the GNU config projects and
> then linking all versions of automake & libtool to that.  a quick check on a
> Debian box shows that they do a similar thing.
>
> so just run `autoreconf -f -i` like normal.  then grep for aarch64 in the
> config/config.{sub,guess} files.  if you see some hits, then you're fine.  if you
> don't, then you can update things manually on your end:
>
>         git clone git://git.sv.gnu.org/config.git
>         for d in /usr/share/automake*/ /usr/share/libtool/config ; do
>                 sudo cp config/config.{sub,guess} $d/
>         done
>
> don't worry about clobbering your installed files.  these config.{sub,guess}
> fragments are completely standalone.

Can you add a comment/explanation here please?
https://bitbucket.org/libgd/gd-libgd/issue/36/migrate-to-autoconf-269-for-arm-64-support

I should also commit a README.RELEASE+script too so we don't forget
how it works (or you can :)

Cheers,
--
Pierre

@pierrejoye | http://www.libgd.org