Re: ARM 64 bit support (aarch64) starting with autoconf 2.69
On Nov 24, 2013, at 2:21 PM, Robert Scheck wrote: > Hello Jeff, > > On Sun, 24 Nov 2013, Jeffrey Johnson wrote: >> There's perhaps portability issues moving to later AutoFu >> (but I use autoconf 2.69 all the time in popt). >> >> Likely the easiest fix is to rerun autogen.sh (or use autoreconf): >> you could just do that on aarch64 as well. >> >> Will that work? > > yes, that will work. I just got this report by the aarch64 team - with the > pointer that I ideally should work with upstream to get this upstream done > for the future. It's up to you, I can run autoreconf on downstream as well > if you like that more. > Heh. POPT needs portability: aarch64 forcing autoconf 2.69 is gonna need much much more work than in popt upstream, and advocacy isn't enuf. 73 de Jeff __ POPT Library http://rpm5.org Developer Communication List popt-devel@rpm5.org
Re: ARM 64 bit support (aarch64) starting with autoconf 2.69
Hello Jeff, On Sun, 24 Nov 2013, Jeffrey Johnson wrote: > There's perhaps portability issues moving to later AutoFu > (but I use autoconf 2.69 all the time in popt). > > Likely the easiest fix is to rerun autogen.sh (or use autoreconf): > you could just do that on aarch64 as well. > > Will that work? yes, that will work. I just got this report by the aarch64 team - with the pointer that I ideally should work with upstream to get this upstream done for the future. It's up to you, I can run autoreconf on downstream as well if you like that more. Greetings, Robert pgpEj1USlzPSz.pgp Description: PGP signature
Re: ARM 64 bit support (aarch64) starting with autoconf 2.69
On Nov 24, 2013, at 1:43 PM, Robert Scheck wrote: > Hello all, > > support for the ARM 64 bit CPU architecture (aarch64) was introduced > in autoconf 2.69. popt appears to use an earlier version of autoconf, > preventing its being built. > > Is there a realistic chance to bump AC_PREREQ() from AC_PREREQ(2.57) > to AC_PREREQ(2.69)? But that might be heavy just for aarch64. Or can > whoever creates the release somehow else ensure that autoconf 2.69 or > later is used to create upcoming release tarballs? > There's perhaps portability issues moving to later AutoFu (but I use autoconf 2.69 all the time in popt). Likely the easiest fix is to rerun autogen.sh (or use autoreconf): you could just do that on aarch64 as well. Will that work? 73 de Jeff > > Greetings, > Robert __ POPT Library http://rpm5.org Developer Communication List popt-devel@rpm5.org
