bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: bug-gnulib@gnu.org
Subject: Module dependencies
Date: Thu, 26 Mar 2020 12:00:15 -0400	[thread overview]
Message-ID: <CAH8yC8=DsuLZ7Gd1rvRO_mK8dK1a6K8aDi=ykEbcg2JP4wN+cQ@mail.gmail.com> (raw)

Hi Everyone,

There are 1700+ modules according to --list. At 3 minutes (est.) a
test that would take 85 hours to complete.

I _think_ a speedup is, if module A uses B and C, then we can scratch
three off the list at a time. The problem I am having is, I'm having
trouble understand the output from --extract-dependencies and
--extract-recursive-dependencies.

What is the difference between these:

CASE 1:
./gnulib-tool --create-testdir --dir="${TEST_DIR}" iconv
Module list with included dependencies (indented):
    absolute-header
    accept
    accept-tests
    alloca
    alloca-opt
    alloca-opt-tests
    ...

CASE 2:
$ ./gnulib-tool --extract-dependencies iconv
havelib

CASE 3:
$ ./gnulib-tool --extract-recursive-dependencies iconv
havelib
iconv

In Case 1 there's a rich list of modules. Case 2 and Case 3 seem to be
missing dependencies. For example, --list shows:

$ ./gnulib-tool --list
...
alloca
alloca-opt
allocator
...

So Case 1 says alloca and alloca-opt are included and tested with
iconv. Case 2 and Case 3 say alloca and alloca-opt are not included
and therefore not tested with iconv.

What is the difference in outputs?

Jeff


             reply	other threads:[~2020-03-26 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 16:00 Jeffrey Walton [this message]
2020-03-26 20:36 ` Module dependencies Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8yC8=DsuLZ7Gd1rvRO_mK8dK1a6K8aDi=ykEbcg2JP4wN+cQ@mail.gmail.com' \
    --to=noloader@gmail.com \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).