This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFC] a script to update our gnulib import...


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: update-gnulib.sh
Description: Bourne shell script


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]