From: manfredu <manfredu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] gpsbabel: update to 1.7.0.
Date: Fri, 12 Feb 2021 08:48:23 +0100 [thread overview]
Message-ID: <20210212074823.hNXIIhXAlyAiD_NnZfhlFYqmwdt-fUiZJjWp9sqhG4g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21674@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
New comment by manfredu on void-packages repository
https://github.com/void-linux/void-packages/pull/21674#issuecomment-778036712
Comment:
> You need to identify the message `checking loader paths for Qt libs` and which binary `configure` actually tries to run there.
>
> Then you can either patch configure to get this information in some way which does not require running a target binary, or you can add `build_helper="qemu"` and try to patch configure to run that `somebinary` with `qemu-${XBPS_TARGET_QEMU_MACHINE}-static somebinary ...`.
It fails with "loader cannot find Qt library" when cross-compiling in the following part of configure:
```
OCPPFLAGS="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS -I$QT_INC"
OLIBS="$LIBS"
LIBS="$LIBS $QT_LIBS"
OLDFLAGS="$LDFLAGS"
LDFLAGS="$LDFLAGS -Wl,-rpath,$($QMAKE -query QT_INSTALL_LIBS)"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <QtCore/QtGlobal>
#include <cstring>
int main () {
return strcmp(QT_VERSION_STR, qVersion()) != 0;
}
_ACEOF
if ac_fn_cxx_try_run "$LINENO"; then :
...
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "loader cannot find Qt library
See \`config.log' for more details" "$LINENO" 5; }
LDFLAGS="$OLDFLAGS"
fi
```
For the time being I have disabled cross-compiling. Any other suggestion?
I'm still checking why one test is failing with i686 only...
next prev parent reply other threads:[~2021-02-12 7:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 7:05 [PR PATCH] gpsbabel: update to 1.6.0 manfredu
2020-05-06 22:07 ` manfredu
2020-05-06 22:18 ` [PR PATCH] [Updated] " manfredu
2020-05-07 10:07 ` pullmoll
2020-05-07 10:14 ` pullmoll
2020-05-07 10:14 ` pullmoll
2020-05-07 10:18 ` pullmoll
2021-01-29 0:50 ` ericonr
2021-01-29 8:06 ` manfredu
2021-02-09 22:13 ` [PR PATCH] [Updated] " manfredu
2021-02-10 6:25 ` [PR PATCH] [Updated] [WIP] gpsbabel: update to 1.7.0 manfredu
2021-02-10 22:49 ` manfredu
2021-02-11 23:22 ` manfredu
2021-02-12 0:42 ` manfredu
2021-02-12 0:51 ` manfredu
2021-02-12 3:43 ` [PR REVIEW] " ericonr
2021-02-12 7:48 ` manfredu [this message]
2021-02-12 7:50 ` manfredu
2021-02-12 8:14 ` [PR REVIEW] " manfredu
2021-02-12 9:58 ` manfredu
2021-02-12 15:24 ` ericonr
2021-02-12 23:46 ` [PR PATCH] [Updated] " manfredu
2021-02-13 14:34 ` manfredu
2021-02-13 14:49 ` manfredu
2021-02-13 14:54 ` manfredu
2021-02-13 15:19 ` manfredu
2021-02-13 15:21 ` [PR REVIEW] " manfredu
2021-02-13 21:28 ` ericonr
2021-02-13 21:29 ` [PR PATCH] [Merged]: " ericonr
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=20210212074823.hNXIIhXAlyAiD_NnZfhlFYqmwdt-fUiZJjWp9sqhG4g@z \
--to=manfredu@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).