Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFC] a script to update our gnulib import...
Date: Mon, 12 Dec 2011 00:25:00 -0000	[thread overview]
Message-ID: <20111212001426.GG2748@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]

Hello,

My ultimate goal is to import gnulib's update-copyright to the list
of gnulib modules we import in the GDB sources. This is in preparation
for the 2012 Start of Year procedure which is going to come soon...
I thought I'd do it in two steps:

  1. Refresh our gnulib import to the latest sources;
  2. Add/import update-copyright.

This way, I know that the patch for the step 1 is a pure refresh.
And that the patch for step 2 is a pure import of a new module.

But the thing is, the import procedure is not completely obvious
to me. I eventually managed to make it work (meaning it built on
x86_64-linux) but I'm not sure I didn't break something on another
more exotic platform. Also, it's not clear to me which modules we
have imported so far.

This is why I thought the whole process should be somewhat done
by a script which anyone can run to do an update, or to add a new
module.  Attached is a first attempt at the script.

gdb/ChangeLog:

        * update-gnulib.sh: New script.

Still to be done/discussed:

 (a) Is the list of modules complete? I listed the three that I could
     figure out.  I deleted the whole gnulib/ subdirectory and
     recreated it using the script and GDB seems to build. Nothing
     seems to be deleted except some files in gnulib/extra
     (arg-nonnull.h, c++defs.h, warn-on-use.h). Are we using those?

 (b) Is the update procedure to regenerate configure, Makefiles et al
     complete? Right now, after the gnulib-tool is called, we do
     the following:

        aclocal -Ignulib/m4 &&
        autoconf &&
        automake

     Do we need to call autoheader, aclocal without argument, etc?

Thoughts?

Thanks,
-- 
Joel

PS: The suggestion to use gnulib's update-copyright was made because
    it handles more files than our emacs-based copyright.sh script
    does.  And it will hopefully be much faster as well.

[-- Attachment #2: update-gnulib.sh --]
[-- Type: application/x-sh, Size: 3153 bytes --]

             reply	other threads:[~2011-12-12  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12  0:25 Joel Brobecker [this message]
2011-12-12  1:22 ` Alfred M. Szmidt
2011-12-12 12:53 ` Pedro Alves
2011-12-19  7:57   ` Joel Brobecker
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=20111212001426.GG2748@adacore.com \
    --to=brobecker@adacore.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