From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Thomas Morley Newsgroups: gmane.lisp.guile.user Subject: Re: Problem installing the intended version Date: Sat, 10 Aug 2019 20:39:28 +0200 Message-ID: References: <87k1bmfcrr.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="215970"; mail-complaints-to="usenet@blaine.gmane.org" Cc: guile-user@gnu.org To: Mark H Weaver Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sat Aug 10 20:40:31 2019 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hwWI2-000u4n-SL for guile-user@m.gmane.org; Sat, 10 Aug 2019 20:40:30 +0200 Original-Received: from localhost ([::1]:37700 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hwWI1-0008Fu-Tu for guile-user@m.gmane.org; Sat, 10 Aug 2019 14:40:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37305) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hwWHP-0008BI-Lr for guile-user@gnu.org; Sat, 10 Aug 2019 14:39:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hwWHK-0000ZH-RG for guile-user@gnu.org; Sat, 10 Aug 2019 14:39:49 -0400 Original-Received: from mail-wm1-x32e.google.com ([2a00:1450:4864:20::32e]:35787) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hwWHK-0000Xu-58 for guile-user@gnu.org; Sat, 10 Aug 2019 14:39:46 -0400 Original-Received: by mail-wm1-x32e.google.com with SMTP id l2so8395304wmg.0 for ; Sat, 10 Aug 2019 11:39:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=nV4UHQuZ0YsIq3GmX/w27Abd8M9rf6Y6jpPe86UFo7M=; b=PWtxMfAcg9c5Vj9G5blQmG8EKTBuCuMOt/RzZ9fhSk60y2THKwRpSXb65dCo1hUnUF lRvCkC0aBC/Bg0at8h+JDkgnfH7fbs/8A1dP6c56uCN3+dCuJcwVVXFWSdH8cnlpAC2+ 0qu43avYwwx1m5iOymKmz1bkj1sM9fPYN4imqKXchTLWDu3X5Y0NjUek2d9AJ7Rvz1hD QBVcr0661nOx2ZaH9SCWzOj+mrGnqzXUQnORlq4DCwT1VaJUgZY4l4nn1BxUxX74XuF0 OEAN5ZEmYn4X4CVku8Ff0307InW/7KgU22q4mGgwPO1rUOiX6IwX12aIBdwdEumbOSv1 1gkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=nV4UHQuZ0YsIq3GmX/w27Abd8M9rf6Y6jpPe86UFo7M=; b=aJne76WEH7+KrMZyS6AGqLCpKaAaKTHS9en5RbOuZiOiKoF2Iu3ciE7t9h0wVUaDIH ie7nWBuK2He0fFI3qryZwTmC2rJBWLNeLhbfm74zUbudY1BpMho+6s/l8+wKsOElTyor 7HEPz409q67bvOqp/kolrGv3pByGBV5mSWim43opl2MJwO3vOb53EpmglHQWAv6k+QVH IWtntjc5Rm0sI2SnR+z4yDJUen4mfCvgBoZtoQ5cgUh1NaZ8MUNawT3Ts6FAZCdsEc9i taOj1xC72WR0n6FUNhkDIdR2VzutbXU73Zbyc2sKL4G+BwgGV3pDx0AlQj6oVDHoQFXZ T3UA== X-Gm-Message-State: APjAAAWcxD48DCgR7fTTgWNnqTLKCI2vIsizSEhWW1g2o0Pm1beufQuh Vee6spEhmqHEpxd49A8V/Z7+LjrZ/AqKxkj/Z3Bgmn+9MPU= X-Google-Smtp-Source: APXvYqyt12LsXfvnxL4XBAgXF6lo9FsK6TC2Zy/HwdK72OHcJKm6cUBuXW/wbdHFfh0yq9xfRg255zJCn0v4Qlc7iSQ= X-Received: by 2002:a1c:4803:: with SMTP id v3mr18456836wma.49.1565462383787; Sat, 10 Aug 2019 11:39:43 -0700 (PDT) In-Reply-To: <87k1bmfcrr.fsf@netris.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::32e X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:15680 Archived-At: Hi Mark, Am Fr., 9. Aug. 2019 um 19:51 Uhr schrieb Mark H Weaver : > > Hi Thomas, > > Thomas Morley writes: > > > recently I tested building LilyPond against guile-2.2.6 without > > success[*] and tried to investigate whether the problem is on the > > guile-side or at LilyPond (there are some patches which may or may not > > cause the problem). > > > > Though I stumbled across a problem which may be caused by guile or my > > naivity ... > > > > I had built guile-2.2.6 from the git repository and installed it via > > `sudo make install=C2=B4 > > Then I did (in/for a fresh repo): > > > > git clone git://git.sv.gnu.org/guile.git ~/guile-2.2.4 > > cd guile-2.2.4/ > > git checkout v2.2.4 > > git checkout -b guile-2.2.4 > > sh autogen.sh > > ./configure > > make > > > > All successfull, then some tests: > > > > ./meta/guile --version > > --> guile (GNU Guile) 2.2.4 [...] > > ./meta/guile-config --version > > --> guile-config - Guile version 2.2.4 > > > > Then installed it systemwide > > > > sudo make install > > > > And made some testings: > > > > which guile > > --> /usr/local/bin/guile > > /usr/local/bin/guile --version > > --> guile (GNU Guile) 2.2.6.1-a69b5 > > > > Obviously 2.2.4 was _not_ installed but 2.2.6 from another repo. > > > > What am I missing? > > What's happening here is that although the executable > /usr/local/bin/guile is from 2.2.4, it is being dynamically linked to > the newer libguile-2.2.so.1.4.1 from 2.2.6 that you installed earlier. > The libguile from guile 2.2.4 is libguile-2.2.so.1.3.1. > > This happens because you never uninstalled the newer > libguile-2.2.so.1.4.1, and the library versioning information that we > assigned indicates that libguile-2.2.so.1.4.1 is a drop-in replacement > for libguile-2.2.so.1.3.1. In other words, to our knowledge, any > executable linked with libguile-2.2.so.1.3.1 should also work properly > when linked with libguile-2.2.so.1.4.1. That's because we added new > interfaces but did not change or remove any existing interfaces. many thanks for your analysis. I am used to switch guile versions between guile-1.8.8 (still LilyPond's default) guile-2.0.14 (previous guile-stable, but I didn't use it for some time, newer versions are superior) guile-2.2.x (current stable) guile-2.9.x (prereleases for upcoming stable-3.0) In the past I checked the last two only upstream, right now it's the first time I tried to downgrade for another micro-version. In the light of your explanations I think the current problem only occurs for _equal_ major/minor with _different_ micro versions. Correct? > If you want to prevent libguile-2.2.so.1.4.1 from guile 2.2.6 from being > used, you should delete it, and then run 'ldconfig' as root to update > the links and caches. Hopefully after that, libguile-2.2.so.1 and > libguile-2.2.so should be symlinks to libguile-2.2.so.1.3.1. > > A more thorough approach, to make sure that no components of 2.2.6 are > being used, would be to run "make uninstall" from the Guile 2.2.6 build > directory (if you still have it), then rerun "make install" from the > Guile 2.2.4 build directory, Doing "make uninstall" before installing a different micro-version solves the problem. > and finally "ldconfig" as root. Doing so I get: /sbin/ldconfig.real: /usr/local/lib/libguile-2.0.so.22.8.1-gdb.scm is not an ELF file - it has the wrong magic bytes at the start. /sbin/ldconfig.real: /usr/local/lib/libguile-2.2.so.1.3.1-gdb.scm is not an ELF file - it has the wrong magic bytes at the start. And I've got even more notifications of this kind before I started to do the "make uninstall"-thingy. Is this expected? See also https://lists.gnu.org/archive/html/guile-devel/2018-07/msg00036.html which is the most recent post about it, as far as I know. Thanks a lot again, right now I'm testing LilyPond against guile-2.2.4. If I remember correctly this should work, better to verify again, though. And then I can investigate further on both sides. Cheers, Harm