* [gentoo-devhelp] How do I call libtoolize in ebuild?
@ 2011-01-15 22:29 Nikos Chantziaras
2011-01-16 1:27 ` Mike Frysinger
0 siblings, 1 reply; 6+ messages in thread
From: Nikos Chantziaras @ 2011-01-15 22:29 UTC (permalink / raw
To: gentoo-devhelp
I need to call the "libtoolize" utility before "eautoreconf". However,
I get a QA warning:
* QA Notice: 'libtoolize' called by src_unpack: dev-util/gpuocelot-9999
* Use autotools.eclass instead of calling 'libtoolize' directly.
I though I could call "elibtoolize", but that won't work.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-devhelp] How do I call libtoolize in ebuild?
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
0 siblings, 1 reply; 6+ messages in thread
From: Mike Frysinger @ 2011-01-16 1:27 UTC (permalink / raw
To: gentoo-devhelp; +Cc: Nikos Chantziaras
[-- Attachment #1: Type: Text/Plain, Size: 197 bytes --]
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.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-devhelp] Re: How do I call libtoolize in ebuild?
2011-01-16 1:27 ` Mike Frysinger
@ 2011-01-16 2:22 ` Nikos Chantziaras
2011-01-16 2:57 ` Nathan Phillip Brink
2011-01-16 3:19 ` Mike Frysinger
0 siblings, 2 replies; 6+ messages in thread
From: Nikos Chantziaras @ 2011-01-16 2:22 UTC (permalink / raw
To: gentoo-devhelp
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
---------------
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [gentoo-devhelp] Re: How do I call libtoolize in ebuild?
2011-01-16 2:22 ` [gentoo-devhelp] " Nikos Chantziaras
@ 2011-01-16 2:57 ` Nathan Phillip Brink
2011-01-16 3:19 ` Mike Frysinger
1 sibling, 0 replies; 6+ messages in thread
From: Nathan Phillip Brink @ 2011-01-16 2:57 UTC (permalink / raw
To: Nikos Chantziaras; +Cc: gentoo-devhelp
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-devhelp] Re: How do I call libtoolize in ebuild?
2011-01-16 2:22 ` [gentoo-devhelp] " Nikos Chantziaras
2011-01-16 2:57 ` Nathan Phillip Brink
@ 2011-01-16 3:19 ` Mike Frysinger
2011-01-16 22:33 ` Nikos Chantziaras
1 sibling, 1 reply; 6+ messages in thread
From: Mike Frysinger @ 2011-01-16 3:19 UTC (permalink / raw
To: gentoo-devhelp; +Cc: Nikos Chantziaras
[-- Attachment #1: Type: Text/Plain, Size: 627 bytes --]
On Saturday, January 15, 2011 21:22:48 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:
>
> aclocal-1.11: couldn't open directory `m4': No such file or directory
this is a bug in aclocal that ive talked to upstream about in the past. do as
Nathan says and simply run `mkdir m4`.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-devhelp] Re: How do I call libtoolize in ebuild?
2011-01-16 3:19 ` Mike Frysinger
@ 2011-01-16 22:33 ` Nikos Chantziaras
0 siblings, 0 replies; 6+ messages in thread
From: Nikos Chantziaras @ 2011-01-16 22:33 UTC (permalink / raw
To: gentoo-devhelp
On 01/16/2011 05:19 AM, Mike Frysinger wrote:
> On Saturday, January 15, 2011 21:22:48 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:
>>
>> aclocal-1.11: couldn't open directory `m4': No such file or directory
>
> this is a bug in aclocal that ive talked to upstream about in the past. do as
> Nathan says and simply run `mkdir m4`.
Thanks Nathan and Mike. Creating the m4 directory manually solved the
issue.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-01-16 22:35 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-01-16 3:19 ` Mike Frysinger
2011-01-16 22:33 ` Nikos Chantziaras
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox