Re: atk build problem

[Malcolm Tredinnick <malcolm ws14 commsecure com au>]

On Tue, 2003-05-27 at 10:13, Bill Haneman wrote:
> This is a common complaint.  The newer versions of the GNOME build tools
> require that the environment variable $SED is defined in your shell.
> 
> Setting $SED=sed should do it.

That may be *a* solution, but it is not the root cause of the problem
(partial proof being that I do not have $SED set in my environment and
yet do not see this problem unless I am trying to trigger it). With a
"normally" (for some definition of the word) configured build setup,
libtool will just work; we are, after all, only talking about version
1.4.3 here -- nothing too bleeding edge. That is small comfort to those
seeing the problem, though, so let me expand a little bit...

However, some people seem to see this strange behaviour which is a
direct result of SED not being defined. Normally, SED is defined as part
of the libtool script and things work nicely. If that is not happening,
we really need to work out what the root cause is. I have seen this
problem occur when $PATH is not set correctly and you are rebuilding in
a non-standard prefix: your package contains links to scripts like
ltmain.sh, which try to call subsidiary scripts which end up coming from
another libtool installation.

I am slowly closing in on the various ways of triggering this problem,
with a view to building some checks into the standard autogen.sh to see
if we can bail out earlier with an error message, rather than
progressing to the odd libtool error. For those interested in tracking
progress, look in on bug #112348
(http://bugzilla.gnome.org/show_bug.cgi?id=112348) from time to time and
I will update it as I make more progress.

Cheers,
Malcolm