GNU logs - #14579, boring messages

Message sent to bug-libtool@HIDDEN:

Subject: bug#14579: locking breaks across filesystems
Resent-From: Amitai Schlair <schmonz@HIDDEN>
Original-Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Sat, 08 Jun 2013 18:22:02 +0000
Resent-Message-ID: <handler.14579.B.13707156736811 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 14579 <at> debbugs.gnu.org
MIME-Version: 1.0
Date: Sat, 8 Jun 2013 14:06:57 -0400
Message-ID: <CA+pHapvmC6Z2MA0f=NoAshhPJ5V9mXo6PkGMVZpfk1GX2bCrqQ@HIDDEN>
From: Amitai Schlair <schmonz@HIDDEN>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: list
Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org

What I tried:

On Mac OS X 10.6.8 (Darwin 10.8.0) with Xcode 3.2.5, fetch and extract
pkgsrc into a dedicated disk partition. Using pkgsrc, build and
install libtool 2.4.2 to the root partition. Using pkgsrc, try
building and installing software that uses libtool.

What I expected to happen:

Succeed at building and installing software that uses libtool.

What actually happened:

Fail, like so (in this example, pkg-config):

[...]
  CC       gprintf.lo
  CC       glib-unix.lo
  CC       gthread-posix.lo
  CC       giounix.lo
  CC       gspawn.lo
  CCLD     libglib-2.0.la
libtool: link: Waiting for
/Volumes/pkgsrc/current/devel/pkg-config/work.ap-juicer/pkg-config-0.28/glib/glib/libcharset/.libs/libcharset.a.lock
to be removed
libtool: link: Waiting for
/Volumes/pkgsrc/current/devel/pkg-config/work.ap-juicer/pkg-config-0.28/glib/glib/libcharset/.libs/libcharset.a.lock
to be removed
libtool: link: Waiting for
/Volumes/pkgsrc/current/devel/pkg-config/work.ap-juicer/pkg-config-0.28/glib/glib/libcharset/.libs/libcharset.a.lock
to be removed
[repeats forever]

What I've figured out so far:

* The error message comes from func_extract_an_archive() (and not the
other occurrence of "to be removed").

* It's conditionalized on lock_old_archive_extraction being "yes",
which is true only on Darwin.

* It attempts to create a lockfile as a hardlink to libtool itself,
which fails when the installed libtool is not on the same filesystem
as the source being built.

* It assumes the only reason the hardlink could fail is the target
already existing.

* When it fails for any other reason, a wrong conclusion goes to
stderr, the real error goes to /dev/null, and we're stuck in an
infinite loop.

* If I set lock_old_archive_extraction=no, everything works as
expected in my limited testing.

What I haven't figured out, and am asking you to:

* What Darwin-specific problem is lock_old_archive_extraction trying
to prevent? I see that the variable was introduced 2009-06-10,
accompanied by an automated test to verify that convenience archive
extraction works concurrently. I couldn't figure out at a glance how
to run that test, so I'm not sure whether a working
lock_old_archive_extraction would have done me any good. What have I
broken on my Darwin system by setting it to "no"? In what context is
it still needed? (I'm guessing there is one, but if it turns out there
isn't, removing lock_old_archive_extraction and related codepaths
would solve my problem.)

* Can the locking code (if it needs to live) print the actual error
when there is one, so that future problems are less confusing?

* Can the locking code (if it needs to live) either work entirely
within the build area or not rely on hardlinks, so that it works in a
filesystem configuration like mine?

Thank you for libtool and for reading this bug report!

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Amitai Schlair <schmonz@HIDDEN>
Subject: bug#14579: Acknowledgement (locking breaks across filesystems)
Message-ID: <handler.14579.B.13707156736811.ack <at> debbugs.gnu.org>
References: <CA+pHapvmC6Z2MA0f=NoAshhPJ5V9mXo6PkGMVZpfk1GX2bCrqQ@HIDDEN>
X-Gnu-PR-Message: ack 14579
X-Gnu-PR-Package: libtool
Reply-To: 14579 <at> debbugs.gnu.org
Date: Sat, 08 Jun 2013 18:22:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-libtool@HIDDEN

If you wish to submit further information on this problem, please
send it to 14579 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
14579: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D14579
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-libtool@HIDDEN:

Subject: bug#14579: 
References: <CA+pHapvmC6Z2MA0f=NoAshhPJ5V9mXo6PkGMVZpfk1GX2bCrqQ@HIDDEN>
In-Reply-To: <CA+pHapvmC6Z2MA0f=NoAshhPJ5V9mXo6PkGMVZpfk1GX2bCrqQ@HIDDEN>
Resent-From: YaoCL <chunlinyao@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Thu, 15 Oct 2015 01:50:03 +0000
Resent-Message-ID: <handler.14579.B14579.144487379426447 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 14579 <at> debbugs.gnu.org
From: YaoCL <chunlinyao@HIDDEN>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <3DEE6825-BDAA-41B3-8529-032598FE4CA3@HIDDEN>
Date: Thu, 15 Oct 2015 09:44:50 +0800
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
 
 Content preview:  The same issue on Mac OS X 10.11 with home-brew installed
   libtool 2.4.6 I think the lock should support across filesystems. [...] 
 
 Content analysis details:   (1.3 points, 10.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -0.7 RCVD_IN_DNSWL_LOW      RBL: Sender listed at http://www.dnswl.org/, low
                             trust
                             [209.85.220.52 listed in list.dnswl.org]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (chunlinyao[at]gmail.com)
 -0.0 SPF_PASS               SPF: sender matches SPF record
  2.0 BLANK_SUBJECT          Subject is present but empty
  0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid

The same issue on Mac OS X 10.11 with home-brew installed libtool 2.4.6

I think the lock should support across filesystems.

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.