On 03/10/2010 11:41:49 AM, Alon Bar-Lev wrote:
> On Wed, Mar 10, 2010 at 7:39 PM, Karl O. Pinc <k...@meme.com> wrote:
> > In other words ./configure is not expected to be run under normal
> > circumstances.
> >
> > The whole point of autoconf is to produce something that can
> > be made into a tarball that only requires "make; make install"
> > to compile and install.
>
> You do not understand the tools. Nor the common use of them.
>
> You *MUST* run ./configure when compiling from sources.
You are right, on all of the above. I don't use them every
day.
But, you _don't_ have to run ./configure every time. You
yourself wrote that you do the ./configure on the _new_
machine, and then move the tarball to the old machine
and recompile. This is often the situation, or at least
I found so, when making rpm spec files.
You are quite correct in pointing out that ./configure
should be able to be run on the old machine, which
means that it can be executed within the build portion
of the spec file.
Thanks for the correction and please tell me if I'm
wrong again.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
