Re: config.rpath conflict

[Jim Meyering]

Bruno Haible wrote:
...
> Would it help to have an option for gnulib-tool that avoids running
> configure, knowing that it will be run afterwards anyway? Currently
> gnulib-tool invokes configure and make for generating distributed
> built files (i.e. running bison, gperf, or similar unusual tools).

Good idea.
I would welcome such an option and would use it in nearly every package
for which I set up the build process, since they either run configure
explicitly or require that the user do so after running bootstrap.