[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: config.rpath conflict
From: |
Bruno Haible |
Subject: |
Re: config.rpath conflict |
Date: |
Sun, 4 Oct 2009 22:58:15 +0200 |
User-agent: |
KMail/1.9.9 |
Jim Meyering 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.
Oops, I spoke too soon. gnulib-tool invokes configure for this purpose
only in --create-testdir and --test modes, not with --import or --update.
'bootstrap' does not do it either. So there is nothing I can optimize here.
Bruno