bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: An issue with unlocked-io.h and bootstrapping.


From: Mats Erik Andersson
Subject: Re: An issue with unlocked-io.h and bootstrapping.
Date: Wed, 3 Nov 2010 11:18:34 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

onsdag den  3 november 2010 klockan 10:53 skrev Jim Meyering detta:
> Mats Erik Andersson wrote:
> > Hello,
> >
> > I have made a strange observation concerning
> >
> >     lib/unlocked-io.h
> >
> > which appears when running the bootstrap script
> > for GNU Inetutils.
> >

> [...]

> > remains, which is pointing at the non-existent
> > location
> >
> >     ../gnulib/unlocked-io.h
> 
> Thanks for the report.
> 
> There is already code in gnulib's bootstrap script designed to
> remove dangling symlinks from m4/ and lib/-style directories:
> 
>   # Remove any dangling symlink matching "*.m4" or "*.[ch]" in some
>   # gnulib-populated directories.  Such .m4 files would cause aclocal to fail.
>   # The following requires GNU find 4.2.3 or newer.  Considering the usual
>   # portability constraints of this script, that may seem a very demanding
>   # requirement, but it should be ok.  Ignore any failure, which is fine,
>   # since this is only a convenience to help developers avoid the relatively
>   # unusual case in which a symlinked-to .m4 file is git-removed from gnulib
>   # between successive runs of this script.
>   find "$m4_base" "$source_base" \
>     -depth \( -name '*.m4' -o -name '*.[ch]' \) \
>     -type l -xtype l -delete > /dev/null 2>&1
> 
> If it's not working for you, perhaps you've changed the definition
> of source_base or you're using an inadequate version of find.
> Otherwise, please investigate.

The bootstrapping is performed on Debian GNU/Linux testing/Squeeze,
so I doubt that "find" is at fault. I will try to dig further though.
It did not matter if I brought the tree using "rsync -Ca" to OpenBSD,
GNU/kFreeBSD, or GNU/Linux. The same error occurred.


Best regards.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]