all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel <guix-devel@gnu.org>,
	Thomas Danckaert <post@thomasdanckaert.be>
Subject: Re: QT install and search paths
Date: Sat, 2 Sep 2017 18:40:44 +0200	[thread overview]
Message-ID: <0f97b74f-282d-9996-aa61-d3084e164b09@crazy-compilers.com> (raw)
In-Reply-To: <e8befb5a-1190-1da5-33fb-2f931d7f1b15@crazy-compilers.com>

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]

Am 27.08.2017 um 18:49 schrieb Hartmut Goebel:
> It is searched in several sub-directories of
> /tmp/guix-build-…/qtwayland-opensource-src-5.9.1/plugins/platforms/../../../
> (which is the /tmp/guix-build-qtwayland-5.9.1.drv-0 directory), but
> not in …/lib. I did not find out how to

Uff, I tracked this down in a heavy thinking session.

  *

    This search-path stems from the libraries RUNPATH, which was
    $ORIGIN/../../lib and is now only $ORIGIN/../../../

  *

    The RUNPATH is set in
    /gnu/store/…-qtbase-5.9.1/lib/qt5/mkspecs/features/qt.prf line 272,
    using the relative path from $$qtRelativeRPathBase (which equals
    $target.path, which is
    /gnu/store/…-qtbase-5.9.1/lib/qt5/plugins/platforms) to
    $QT_INSTALL_LIBS (which is /gnu/store/…-qtbase-5.9.1/lib).  This
    relative path obviously is ../../../ .

  *

    Prior to this patch we installed the plugins into
    …-qtbase-5.9.1/plugins, which results in the aforementioned relative
    path to be ../../lib and the RUNPATH to be set to $ORIGIN/../../lib.

Conclusions:

1. It's been pure luck that the qtwayland tests passed prior to this change.

2. Do make the tests pass, we need to set LD_LIBRARY_PATH prior to
running the tests

3. tests of other packages may fail for the same reason.

I'll take care of the packages in kde-frameworks.scm, I assume/hope
Thomas will take care of the ones in kde.scm.

宋文武, how can we coordinate the required changes? Should they go into one
patch? Or into a series?

-- 

Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |


[-- Attachment #2: Type: text/html, Size: 2667 bytes --]

  reply	other threads:[~2017-09-02 16:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 18:25 QT install and search paths Hartmut Goebel
2017-08-24 11:37 ` Thomas Danckaert
2017-08-25  7:32   ` Hartmut Goebel
2017-08-24 11:59 ` 宋文武
2017-08-25  7:06   ` Hartmut Goebel
2017-08-25 12:40     ` 宋文武
2017-08-25 16:04       ` 宋文武
2017-08-26  8:31         ` Hartmut Goebel
2017-08-27 16:49         ` Hartmut Goebel
2017-09-02 16:40           ` Hartmut Goebel [this message]
2017-09-03  4:58             ` 宋文武
2017-09-03 11:46               ` 宋文武
2017-09-03 12:39                 ` Hartmut Goebel
2017-09-03 14:04                 ` Hartmut Goebel
2017-09-03 14:46                   ` 宋文武
2017-09-04  7:44             ` Thomas Danckaert
2017-09-04  9:16               ` Hartmut Goebel
2017-09-07 13:38                 ` 宋文武
2017-09-19 16:30                   ` Hartmut Goebel
2017-09-22 12:59                     ` Hartmut Goebel
2017-10-06 12:22                   ` Hartmut Goebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f97b74f-282d-9996-aa61-d3084e164b09@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@member.fsf.org \
    --cc=post@thomasdanckaert.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.