From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71539 invoked by alias); 23 Dec 2019 07:19:43 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 71530 invoked by uid 89); 23 Dec 2019 07:19:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-26.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HTo:U*libffi-discuss, retrieved, toolexeclibdir, sk:print-m X-HELO: mail-wr1-f68.google.com Received: from mail-wr1-f68.google.com (HELO mail-wr1-f68.google.com) (209.85.221.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 23 Dec 2019 07:19:41 +0000 Received: by mail-wr1-f68.google.com with SMTP id y17so15587053wrh.5 for ; Sun, 22 Dec 2019 23:19:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=qDUQB0cgizqfCcZfx05tvVZQ92t8s/en0RmVg68jAxc=; b=sojsuvUrUFJowSsyESTfxItPKGo5RcUWa5InfMAq+XStt0mGXEYhOQFQ1N87ZbcsSY H7IDxYqF5WA/RujjNfNJqa/ne/QGSw+gebPLkDFA5gdAIywEEl5dGXTslkPUBzpbRuvi txvpAroGi5BydKhQE+cva/FdbP8JIWCjazdYmAX5Ym1v6ApELYJcMRmkq46nSzzcy3H+ aG1FnD90FZiLaKv+4Yt/7eUgcnKXV9qSxP7C2+oy6GTkTgmGs3SS6HAAbDUFbgTZmOWN eOQaep+0KefMl+m950EcCK+Ws0PnnSu8Fzk8KTVMBkfnjQnsJnOQz15ner5afJ1b08KP i49Q== Return-Path: Received: from kali.home (lfbn-ren-1-602-70.w81-53.abo.wanadoo.fr. [81.53.179.70]) by smtp.gmail.com with ESMTPSA id x18sm19686114wrr.75.2019.12.22.23.19.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 22 Dec 2019 23:19:38 -0800 (PST) From: Fabrice Fontaine To: libffi-discuss@sourceware.org Cc: Fabrice Fontaine , Thomas Petazzoni , =?UTF-8?q?J=C3=B6rg=20Krause?= Subject: [PATCH] Fix installation location of libffi Date: Mon, 23 Dec 2019 07:19:00 -0000 Message-Id: <20191223072023.3983012-1-fontaine.fabrice@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2019/txt/msg00097.txt.bz2 The libffi is currently declared as toolexeclib_LTLIBRARIES. In many cases, toolexeclib libraries will be installed in /usr/lib, so it doesn't make any difference. However, with multilib toolchains, they get installed in a subdirectory of /usr/lib/. For example, with a Sourcery CodeBench PowerPC toolchain, if the e500mc multilib variant is used, the libffi library gets installed in /usr/lib/te500mc/. This is due to the following code in the configure script: multi_os_directory=`$CC -print-multi-os-directory` case $multi_os_directory in .) ;; # Avoid trailing /. *) toolexeclibdir=$toolexeclibdir/$multi_os_directory ;; esac Once the library is installed in /usr/lib/te500mc/, nothing works because this installation location is inconsistent with the installation location declared in libffi.pc. So, instead of using this bizarre toolexeclib_LTLIBRARIES, simply use the more standard lib_LTLIBRARIES, which ensures that the libffi library is always installed in /usr/lib. Signed-off-by: Thomas Petazzoni [unfuzz for 3.2.1] Signed-off-by: Jörg Krause [Patch retrieved from: https://git.buildroot.net/buildroot/tree/package/libffi/0001-Fix-installation-location-of-libffi.patch] Signed-off-by: Fabrice Fontaine --- Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index 27a11b2..f83e444 100644 --- a/Makefile.am +++ b/Makefile.am @@ -35,7 +35,7 @@ MAKEOVERRIDES= pkgconfigdir = $(libdir)/pkgconfig pkgconfig_DATA = libffi.pc -toolexeclib_LTLIBRARIES = libffi.la +lib_LTLIBRARIES = libffi.la noinst_LTLIBRARIES = libffi_convenience.la libffi_la_SOURCES = src/prep_cif.c src/types.c \ -- 2.24.0