On Thu, 25 Apr 2013 10:30:31 -0400
Richard Hipp wrote:
> > The configure script is typically generated by a build machine that
> > has autotools installed, and included in a distribution tarball.
> > The user unpacks the tarball and runs the configure script. He
> > doesn't
On Thu, Apr 25, 2013 at 10:22 AM, James K. Lowden
wrote:
> On Wed, 24 Apr 2013 19:17:32 -0700
> Dimiter 'malkia' Stanev wrote:
>
> > > Why keep autoconf output in the source code repository?
> >
> > Maybe it's simply to guard from generating different
On Wed, 24 Apr 2013 19:17:32 -0700
Dimiter 'malkia' Stanev wrote:
> > Why keep autoconf output in the source code repository?
>
> Maybe it's simply to guard from generating different ./configure
> files on each machine depending on what autotools were installed (I
> have very
On 4/23/2013 3:22 PM, James K. Lowden wrote:
On Tue, 23 Apr 2013 09:26:20 -0400
Richard Hipp wrote:
I really dislike changing autoconf versions since any autoconf upgrade
results in a massive change in the generated "configure" script,
which is
On Tue, 23 Apr 2013 09:26:20 -0400
Richard Hipp wrote:
> I really dislike changing autoconf versions since any autoconf upgrade
> results in a massive change in the generated "configure" script,
> which is annoying to audit before each release, and which results in
> exceedingly
On Mon, Apr 22, 2013 at 8:26 AM, Jan Staněk wrote:
> Hello,
> support for the ARM 64 bit CPU architecture (aarch64) was introduced in
> autoconf 2.69. sqlite appears to use an earlier version of
> autoconf, preventing its being built.
Can you be more specific about what
Hello,
support for the ARM 64 bit CPU architecture (aarch64) was introduced in
autoconf 2.69. sqlite appears to use an earlier version of
autoconf, preventing its being built. Would it be possible to migrate
sqlite to new version of autoconf?
Thanks for answer,
Jan Stanek
7 matches
Mail list logo