Re: Patch for cygwin: autoupdate and objdump

[Ralf Wildenhues]

Hi Charles,

* Charles Wilson wrote on Fri, Apr 25, 2008 at 09:58:56PM CEST:
> Charles Wilson wrote:
> http://lists.gnu.org/archive/html/libtool-patches/2008-04/msg00098.html
>
>> 2008-04-19  Charles Wilson  <...>
>>         Yaakov Selkowitz  <...>
>>
>>     * libltdl/m4/libtool.m4 (_LT_DECL_OBJDUMP): new macro ensures
>>     that $OBJDUMP is always defined sanely.
>>     (_LT_SYS_DYNAMIC_LINKER): call it.
>>     (_LT_CHECK_MAGIC_METHOD): call it.
>>     (AU_DEFUN[AC_PROG_LIBTOOL]): replace AU_ALIAS[AC_PROG_LIBTOOL];
>>     call both LT_INIT and LT_OUTPUT. Warn user to remove LT_OUTPUT
>>     if not necessary for their package.
>>     (AU_ALIAS[AM_PROG_LIBTOOL]): direct to AC_PROG_LIBTOOL above,
>>     not LT_INIT.
>
> Ping?  It's been more than 72 hours, but I still don't have git fully  
> working, so I'd appreciate it if somebody could check this in for me.

The OBJDUMP parts of this are ok, and I will check them in tomorrow.
The rest has received negative feedback here:
<http://thread.gmane.org/gmane.comp.gnu.libtool.general/9238/focus=9267>

Sorry for not having put you in Cc: on that discussion.

> Also, if somebody has the time, it would be great if this page:
>    http://www.gnu.org/software/libtool/contribute.html
> and the various documentation files in the repository, like
>    HACKING  README.alpha  etc
> could be updated (e.g. scrubbed of references to CVS and updated with  
> appropriate instructions relevant to git).

Will check tomorrow, too.

> I really don't know what I'm doing with git. When I clone the master,  
> should I create a local branch and work in that, or treat it like my  
> private CVS checkouts and work directly in the original clone?

FWIW, I always work in a read-only checkout, and only use the write one
for commits.  But that's just habit.  You can easily have your
development branches and just merge or cherry-pick them into master when
they are ok.

> This page;
> http://savannah.gnu.org/maintenance/UsingGit
> is a little generic, and the links embedded therein to various tutorials  
> are nice, but not libtool-specific.  What are the *libtool* accepted  
> practices and recommendations?

Listed e.g. in this thread:
<http://thread.gmane.org/gmane.comp.gnu.libtool.patches/8320>
Still needs to be put in HACKING.

Cheers,
Ralf