From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v11 2/2] docker-engine: new package
Date: Thu, 28 Jul 2016 08:29:52 +0200 [thread overview]
Message-ID: <20160728082952.4a7872c5@free-electrons.com> (raw)
In-Reply-To: <068F07A4-A28B-4AA9-B57B-5524079EDFC9@gmail.com>
Hello,
On Wed, 27 Jul 2016 18:57:32 -0700, Khem Raj wrote:
> you would need atleast go 1.5+ for dynamic libraries support. If thats not an issue
> then simply change the build cmds to something like
>
> go build -linkshared ...
We have go 1.6.2, and it *does* link with dynamic libraries, see below:
> > $ arm-linux-gnueabihf-readelf -d output/target/usr/bin/dockerd | grep NEEDED
> > 0x00000001 (NEEDED) Shared library: [libpthread.so.0]
> > 0x00000001 (NEEDED) Shared library: [libdl.so.0]
> > 0x00000001 (NEEDED) Shared library: [libdevmapper.so.1.02]
> > 0x00000001 (NEEDED) Shared library: [libc.so.0]
However, it doesn't link some libraries as dynamic, and some others as
static, for some reason.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-28 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 21:10 [Buildroot] [PATCH v11 1/2] package/btrfs-progs: install to staging directory Christian Stewart
2016-07-24 21:10 ` [Buildroot] [PATCH v11 2/2] docker-engine: new package Christian Stewart
2016-07-24 21:25 ` Christian Stewart
2016-07-27 21:40 ` Thomas Petazzoni
2016-07-27 22:12 ` Christian Stewart
2016-07-28 1:57 ` Khem Raj
2016-07-28 6:29 ` Thomas Petazzoni [this message]
2016-07-24 21:48 ` [Buildroot] [PATCH v11 1/2] package/btrfs-progs: install to staging directory Thomas Petazzoni
2016-07-24 23:35 ` Christian Stewart
2016-07-25 7:47 ` Thomas Petazzoni
2016-07-27 21:38 ` Thomas Petazzoni
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=20160728082952.4a7872c5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 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.