This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ECOS] tcl in none standard place


>>>>> "Andrew" == Andrew Lunn <andrew.lunn@ascom.ch> writes:

    >> So it looks like the autoconfigure is broken somewhere. Its probably
    >> something trivial, but i don't understand all this stuff. Can anyone
    >> help?

    Andrew> Two steps forward, one step back.....

    Andrew> The root of the problem appears to be in
    Andrew> acsupport/acinclude.m4. Its correctly finding the library,
    Andrew> but then forgets to add the directory to the library path.
    Andrew> This patch fixes that problem....

    Andrew> But, you then need to rebuild all the configure scripts in
    Andrew> the tree. Is there any easy way to do that? Should the
    Andrew> configure scripts actually be part of CVS? Shouldn't they
    Andrew> really be build by autoconf every time?

I made this change, and a couple of others as well.

In an ideal world the configure scripts, the Makefile.in files, etc.
would all get updated by CVS via a commitinfo script when you check in
the corresponding source files configure.in/Makefile.am, or any of the
files they depend on. That is quite hard to get right. In practise
very few people do any work on the host-side configury, so usually it
is easier if I regenerate those files and check them in.

Note that if people start using different versions of autoconf or
automake then we may end up with spurious diffs. Those problems are
also avoided if I am always the one who regenerates the files that go
into CVS.

For people who want to work on acinclude.m4, the "acall" script below
may prove useful.

Bart

#! /bin/sh

# This script updates all configure etc. scripts in a directory tree.
# If invoked with no arguments it uses "find" to locate configure.in
# scripts and recursively invokes acall on them. If invoked with
# a single argument then that identifies a configure.in script,
# i.e. a recursive invocation, and the hard work is done.

if test "$#" = 0 ; then
    find . -name configure.in -exec acall {} \;
else
    cd `dirname ${1}`
    echo Updating `pwd`
    aclocal
    autoconf
    automake
fi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]