Re: Problem with configure

[Bob Proulx]

Priit Voolaid wrote:
> > > prefix=                 --prefix/opt
> > > The PREFIX is defined as --prefix/opt instead /opt. Why is that?
> > > Where can i search for source of this problem?
> 
> I have tryed, many times, with diffrenet packages and always with same
> result, ./configure generated Makefile is corrupt.

If it is true that you have tried many different packages then the
common piece of functionality is not any one package's ./configure
file but rather your operating system.  It sounds to me like your
shell is broken and cannot handle the script.

What shell are you using?  (I see you mentioned 2.4.22 so I will
assume GNU/Linux for the platform.)  You may have to explicitly run
the configure script through a shell which is known to work with
configure.

  bash ./configure

Does that improve your situation?

> It seems my problem is not package realeted. The above described problem
> shows up with autoconf 2.12/2.13 generated configure scripts.

Ew, 2.13 has has many bug fixes applied to it.  So many bugs have been
fixed that it is now up to version 2.59.

> When package includes with newer versions of autoconf, e.g. 2.57 created
> configure, then the Makefile will have correct prefix.

That sounds like an upstream bug.  I would report it to those
upstreams using the older autoconfs and urge them to upgrade to a
newer autoconf.

> Of course, i can bypass this problem when i run the autoconf by myself and
> generate new configure script. Does this mean, that i must run autoconf
> whenever the configure is created with older autoconf version than
> installed on my system?

You as a downstream should not need to do that.  The configure script
should be completely self-contained.  But if you have the capability
to make the modifications necessary then that is a fine solution.

> I have:
> kernel        2.4.22
> gcc   3.3.1
> autoconf 2.57
> automake 1.7.6

The versions of autoconf and automake are not significant when you are
running configure.  They are used to create the configure and not
during the execution of it.  The version the upstream creator of the
autoconf is significant and you noted that as 2.13.

Bob