From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <alves.ped@gmail.com>
Subject: Re: [RFC] a script to update our gnulib import...
Date: Mon, 19 Dec 2011 07:57:00 -0000 [thread overview]
Message-ID: <20111219065256.GR21915@adacore.com> (raw)
In-Reply-To: <201112121153.19159.pedro@codesourcery.com>
Hi Pedro,
> The last import is recorded at the top of gnulib/Makefile.am:
>
> # Generated by gnulib-tool.
> # Reproduce by: gnulib-tool --import --dir=. --lib=libgnu --source-base=gnulib --m4-base=gnulib/m4 --doc-base=doc --tests-base=tests --aux-dir=gnulib/extra --no-libtool --macro-prefix=gl --no-vc-files memmem
Yeah, I had noticed that, which is where I started from...
> memmem pulls in other modules we rely on as dependency, like e.g., stdint.
> It'd be better to list them explicitly. "memmem stdint wchar" does sounds
> right. The dependencies in current git may have changed since the last
> import, so just pulling memmem today may not bring in all we currently have.
OK. I will also look at Alfred's suggestion (Alfred: to answer your
question, I just don't know enough about gnulib, and the documentation
still still quite sketchy - plus, we don't use automake in GDB, so
that adds an extra layer of interpretation).
--
Joel
next prev parent reply other threads:[~2011-12-19 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 0:25 Joel Brobecker
2011-12-12 1:22 ` Alfred M. Szmidt
2011-12-12 12:53 ` Pedro Alves
2011-12-19 7:57 ` Joel Brobecker [this message]
2011-12-19 19:09 ` Alfred M. Szmidt
2011-12-20 10:42 ` Joel Brobecker
2011-12-20 23:31 ` Alfred M. Szmidt
2011-12-21 17:25 ` Tom Tromey
2011-12-21 21:30 ` Alfred M. Szmidt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111219065256.GR21915@adacore.com \
--to=brobecker@adacore.com \
--cc=alves.ped@gmail.com \
--cc=gdb-patches@sourceware.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