[patch #3872] locking in libtool

[Ralf Wildenhues]

Update of patch #3872 (project libtool):

                  Status:                    None => Need Info              
             Assigned to:                    None => rwild                  

    _______________________________________________________

Follow-up Comment #1:

Did you actually encounter this in practise?  Do you have a package whose
`configure' creates its own `libtool' or do you make use of a
system-installed libtool?  Which compiler actually needs the locking?  Note
the macro to find out whether locking is necessary is known to be quite
brittle, so it might hit a false positive.

I don't think your patch is ok as it is, because $LN_S may be `cp -p' and
thus won't fail if the file already exists.  The current code is not ok for
installed `libtool', however.

Regards,
Ralf

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?func=detailitem&item_id=3872>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/