Hi,
Alexei Sholomitskiy wrote:
> i have run ./gnulib-tool --create-megatestdir --with-tests --dir=mybuild
>
> unforunately, process is very long
Yes, --create-megatestdir is only reasonable for a small set (say, at
most 10)
modules. Running it with all > 1800 modules of gnulib will likely take more
than a day and produce many GB of output.
> and I had interrupted it
>
>
> why there is no any checks on submodules directories existents in order
> to continue interruupted process?
Interrupting and restarting gnulib-tool (other than with Ctrl-Z and 'fg')
is not part of the expected workflow. You are supposed to erase the target
directory 'mybuild' before running the command a second time.
> Except this I see next error
>
> executing aclocal -I glm4
> configure.ac:119: error: `gltests' is already registered with
> AC_CONFIG_SUBDIRS.
> ../../lib/autoconf/status.m4:1097: AC_CONFIG_SUBDIRS is expanded from...
Did you get this at the first execution of the above command, or at the
second one?
> How I can try to solve described problems and commit to your savannah
> repository ?
First, discuss with us, to understand the problem. Then, think of a fix
and make sure the approach will find our approval. Then, prepare a patch
and submit it per mail, here.
We give savannah commit access to people who have submitted many good
patches and whom we trust.
Bruno
Alexei Sholomitskiy wrote:
Hi, Bruno!
Except this I see next error
> executing aclocal -I glm4
> configure.ac:119: error: `gltests' is already registered with
> AC_CONFIG_SUBDIRS.
> ../../lib/autoconf/status.m4:1097: AC_CONFIG_SUBDIRS is expanded from...
> Did you get this at the first execution of the above command, or at the
> second one?
The first time everything was excellent, without any bugs, but very-very
slow
this error i have got at second start
moreover, after that I removed whole gnulib directory, ran git clone ...
and after that got this error again
and the second time I have unexpected problems with patching
build-aux/test-driver in modules
I see that gnulib-tool apply to modules test-driver.diff or
test-driver-1.16.3.diff if first patch have run without success
module _Exit and others have "$@" >$log_file 2>&1 not at line patch expected
I believe, there is a way to replace patches by $(sed .... commands
my system:
alexei@Aspire:~/build/gnulib$ uname -a
Linux Aspire 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22
21:24:20 UTC 2022 x86_64 GNU/Linux
Linux Mint 20.3 Cinnamon
Cinnamon 5.2.7
CPU Intel Pentiun N3700
RAM 7.7 GB
Videocard Intel Corporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
пт, 14 июл. 2023 г. в 01:57, Bruno Haible <br...@clisp.org>:
