bug-gnulib
[Top][All Lists]
Advanced

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

Re: gnulib-tool: warnings of type "module --automake-subdir doesn't exis


From: Bruno Haible
Subject: Re: gnulib-tool: warnings of type "module --automake-subdir doesn't exist"
Date: Sun, 23 Jan 2022 00:28:30 +0100

Bjarni Ingi Gislason wrote:
>   Command: gnulib-tool --add-import
> 
>   Output with a warning:
> 
> gnulib-tool: warning: module --automake-subdir doesn't exist
> gnulib-tool: warning: module --aux-dir=build-aux doesn't exist
> gnulib-tool: warning: module --doc-base=doc doesn't exist
> gnulib-tool: warning: module --lib=libgnu doesn't exist
> gnulib-tool: warning: module --local-dir=gl doesn't exist
> gnulib-tool: warning: module --m4-base=gnulib_m4/ doesn't exist
> gnulib-tool: warning: module --makefile-name=gnulib.mk doesn't exist
> gnulib-tool: warning: module --no-changelog doesn't exist
> gnulib-tool: warning: module --source-base=lib/ doesn't exist
> gnulib-tool: warning: module --tests-base=tests doesn't exist

If this is with groff, you are not supposed to use 'gnulib-tool --add-import'.
You are supposed to add new modules in bootstrap.conf, and then
run './bootstrap' with arguments.

If this is not with groff, your gnulib-cache.m4 is broken. Fix it by hand,
or restore it from version control.

Bruno






reply via email to

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