From: Nathan Phillip Brink <ohnobinki@ohnopublishing.net>
To: Nikos Chantziaras <realnc@arcor.de>
Cc: gentoo-devhelp@lists.gentoo.org
Subject: Re: [gentoo-devhelp] Re: How do I call libtoolize in ebuild?
Date: Sat, 15 Jan 2011 21:57:58 -0500 [thread overview]
Message-ID: <20110116025757.GT9191@ohnopublishing.net> (raw)
In-Reply-To: <igtkpb$bfn$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
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!
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-01-16 2:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 22:29 [gentoo-devhelp] How do I call libtoolize in ebuild? Nikos Chantziaras
2011-01-16 1:27 ` Mike Frysinger
2011-01-16 2:22 ` [gentoo-devhelp] " Nikos Chantziaras
2011-01-16 2:57 ` Nathan Phillip Brink [this message]
2011-01-16 3:19 ` Mike Frysinger
2011-01-16 22:33 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110116025757.GT9191@ohnopublishing.net \
--to=ohnobinki@ohnopublishing.net \
--cc=gentoo-devhelp@lists.gentoo.org \
--cc=realnc@arcor.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox