From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de, Artur Wiebe <artur@4wiebe.de>
Subject: Re: [ptxdist] GLIB not building (ptxdist:2017-07, ArchLinux)
Date: Thu, 31 Aug 2017 19:17:36 +0100 [thread overview]
Message-ID: <74664198-36a5-498f-ab22-15ea85cc77ae@mev.co.uk> (raw)
In-Reply-To: <4f2c-59a67800-7d-63400f00@116065094>
On 30/08/17 09:32, Artur Wiebe wrote:
> Hi,
>
> On my ArchLinux GLIB from current PtxDist is not building.
>
> I get the error:
> ./.libs/libgio-2.0.so: undefined reference to `__dn_expand'
> ./.libs/libgio-2.0.so: undefined reference to `__res_query'
> collect2: error: ld returned 1 exit status
> make[5]: *** [Makefile:2285: glib-compile-resources] Error 1
>
> Does anyone have any idea?
>
> Best Regards,
> Artur
I attempted (and failed) to reproduce the problem by building
"DistroKit" for the "platform-v7a" BSP (see
<http://www.pengutronix.de/en/2017-08-28-distrokit-a-playground-bsp-for-ptxdist.html>)
in an up-to-date ArchLinux "Docker" container on my Debian "testing"
amd64 host. The build used the "OSELAS.Toolchain-2016.06.1" toolchain
for the "arm-v7a-linux-gnueabihf" target architecture and Arch Linux's
current native toolchain for the amd64 host.
I ran into a couple of known problems in ptxdist-2017.07.0 (due to the
host-ncurses and host-intltool packages needing fixes) but after fixing
those the build went smoothly.
If I run objdump -T on the built libgio-2.0.so.0.5200.1 file, it
contains both the '__dn_expand' and '__res_query' symbols in its .text
section as expected.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-08-31 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 8:32 Artur Wiebe
2017-08-31 13:30 ` Artur Wiebe
2017-08-31 18:17 ` Ian Abbott [this message]
2017-08-31 18:28 ` Ian Abbott
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=74664198-36a5-498f-ab22-15ea85cc77ae@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=artur@4wiebe.de \
--cc=ptxdist@pengutronix.de \
/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