On Sun, Jan 16, 2011 at 04:22:48AM +0200, Nikos Chantziaras wrote:
> On 01/16/2011 03:27 AM, Mike Frysinger wrote:
> > On Saturday, January 15, 2011 17:29:12 Nikos Chantziaras wrote:
> >> I need to call the "libtoolize" utility before "eautoreconf"
> >
> > why ?  `eautoreconf` should take care of things automatically.
> 
> Unfortunately, it doesn't.  If I don't run libtoolize first, eautoreconf 
> aborts with:
> 
> 
> ---------------
>   * Running eautoreconf in 
> '/var/tmp/portage/dev-util/gpuocelot-9999/work/gpuocelot-9999' ...
>   * Running aclocal -I m4 ... 
>                                                                    [ !! ]
> 
>   * Failed Running aclocal !
>   *
>   * Include in your bugreport the contents of:
>   *
>   *   /var/tmp/portage/dev-util/gpuocelot-9999/temp/aclocal.out
> ---------------
> 
> 
> The contents of aclocal.out:
> 
> 
> ---------------
> ***** aclocal *****
> ***** PWD: /var/tmp/portage/dev-util/gpuocelot-9999/work/gpuocelot-9999
> ***** aclocal -I m4
> 
> aclocal-1.11: couldn't open directory `m4': No such file or directory
> ---------------

Perhaps the gpuocelot people forgot to create an m4/.keep file, which
can be fixed by running ``mkdir m4'' before calling eautoreconf?

-- 
binki

Look out for missing apostrophes!