Re: gEDA-dev: Warnings from autogen.sh

[Dan McMahill <dan-at-NOSPAMmcmahill_dot_net>]

Peter Clifton wrote:
> Hi,
> 
> When running autogen.sh, I get these warnings:
> 
> find: warning: UNIX filenames usually don't contain slashes (though
> pathnames do). That means that '-name ./libgeda/CVS' will probably
> evaluate to false all the time on this system. You might find the
> '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if
> you are using GNU grep, you could use 'find ... -print0 | grep
> -FzZ ./libgeda/CVS'.
> 
> This is caused by:
> 
> for coin in `find $srcdir -name $srcdir/CVS -prune -o -name $configure_script -print`
> 
> 
> Avoiding the non-portable options, I suspect the right line to find is:
> 
> find $srcdir -name "CVS" -prune -false -o -name $configure_script -print
> 
> This ditches all "CVS" directories, not just the one in $srcdir though.
> The test isn't particularly useful though as the CVS directories don't
> contain "configure.ac" scripts... is that always true?
> 
> The attached patch implements this, and works for me.
> 
> Could anyone on non Linux/GNU systems give this a try please (Dan?)a

actually, it goes from sort of working to worse.


CHROOT (gEDA) mcmahill@mudshark 1844 % find ./gnetlist -name \
     ./gnetlist/CVS -prune -o -name configure -print
./gnetlist/configure
./gnetlist/geda-gnetlist-20070216/configure

CHROOT (gEDA) mcmahill@mudshark 1845 % find ./gnetlist -name CVS \
     -prune  -false -o -name configure -print
find: bad option -false
find: path-list predicate-list

your version without the "-false" works though:

CHROOT (gEDA) mcmahill@mudshark 1847 % find ./gnetlist -name CVS \
     -prune -o -name configure -print
./gnetlist/configure
./gnetlist/geda-gnetlist-20070216/configure

Actually, I think the whole "find" think is a bit of overkill in our 
case.  It is there so if you have multiple subdirectories that have 
their own configure.ac file (and hence need to have auto* run) that 
autogen.sh can find them all.  Instead what happens is that if you 
happen to have the result of a failed 'make distcheck' lying around 
(like I did a few days ago), autogen.sh will try to descend in there and 
run the auto* tools.

For reference, here is the autogen.sh we've been using for pcb.  Maybe 
it is missing something important, but it is sure a lot shorter....

#! /bin/sh
#
# $Id: autogen.sh,v 1.4 2006/03/24 00:32:12 danmc Exp $
#
# Run the various GNU autotools to bootstrap the build
# system.  Should only need to be done once.

# for now avoid using bash as not everyone has that installed
CONFIG_SHELL=/bin/sh
export CONFIG_SHELL

echo "Running aclocal..."
aclocal $ACLOCAL_FLAGS || exit 1
echo "Done with aclocal"

echo "Running autoheader..."
autoheader || exit 1
echo "Done with autoheader"

echo "Running automake..."
automake -a -c --foreign || exit 1
echo "Done with automake"

echo "Running autoconf..."
autoconf || exit 1
echo "Done with autoconf"

echo "You must now run configure"

echo "All done with autogen.sh"



_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev