Re: [patch #3872] locking in libtool

Marcin, * Marcin Siennicki wrote on Thu, Mar 31, 2005 at 02:31:11PM CEST: > > >>>But the problem was on my machine (I moved to gcc-3.4, and I > >>>had rpm macros with deprecated options, so I get: > > > >OK. Easiest workaround would be to remove these options. > > > I've fixed it already. I've

Re: [patch #3872] locking in libtool

But the problem was on my machine (I moved to gcc-3.4, and I had rpm macros with deprecated options, so I get: OK. Easiest workaround would be to remove these options. I've fixed it already. I've found it after I saw that you were amazed why I had locking enabled. So I started to look

Re: [patch #3872] locking in libtool

I am Cc:ing this to the libtool-patches list. I showed you where it is archived, its public archive mangles email addresses, and anyway the patch posts on savannah are crossposted there. I have reordered your mail for convenience. * Marcin Siennicki wrote on Thu, Mar 31, 2005 at 12:19:55PM CEST:

[patch #3872] locking in libtool

Update of patch #3872 (project libtool): Privacy: Public => Private ___ Follow-up Comment #2: Setting to private. Please refer to http://lists.gnu.org/archive/html/libtool-patches/ for fu

[patch #3872] locking in libtool

Update of patch #3872 (project libtool): Status:None => Need Info Assigned to:None => rwild ___ Follow-up Comment #1: Did you actually

[patch #3872] locking in libtool

URL: Summary: locking in libtool Project: GNU Libtool Submitted by: None Submitted on: Wed 03/30/2005 at 20:33 Category: None Priority: 5 - Nor