From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] turbovnc: new package
Date: Thu, 02 Nov 2017 23:21:45 +0200 [thread overview]
Message-ID: <59FB8C69.7050108@petroprogram.com> (raw)
In-Reply-To: <20171101105305.1cd82e60@windsurf>
Hi Thomas
1.11.2017, 11:53, Thomas Petazzoni kirjoitti:
> Why does it bundle freetype? Can it use an external Freetype instead?
>>> + bzip2 license (bzip2), Zlib (zlib)
> The SPDX license code for bzip2 license is bzip2-1.0.5 or bzip2-1.0.6,
> see https://spdx.org/licenses/.
>
> Also, why does it bundle Zlib ?
I honestly have not the faintest idea why it want's to use it's own,
bundled versions of bzip2,freetype2 and zlib.
On my 64-bit Intel box these are produced under lib directory:
libbzip2.a libfontenc.a librandr.a libXau.a libxkb.a
libcomposite.a libfreetype2.a librender.a libXdmcp.a libXNVCtrl.a
libdamage.a libmain.a libsha1.a libXext-server.a libzlib.a
libdamageext.a libmi.a libsync.a libxfixes.a
libdix.a libos.a libvnc.a libXfont.a
libfb.a libpixman.a libvncauth.a libXi.a
But then doing ldd for Xvnc binary gives this:
Xvnc:
linux-vdso.so.1 (0x00007fffbbffe000)
libturbojpeg.so.0 => /usr/lib64/libturbojpeg.so.0
(0x00007f1d221b8000)
libm.so.6 => /lib64/libm.so.6 (0x00007f1d21eba000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1d21c9e000)
libpam.so.0 => /lib64/libpam.so.0 (0x00007f1d21a90000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f1d2188c000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f1d21683000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f1d21466000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f1d21124000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f1d20f12000)
libc.so.6 => /lib64/libc.so.6 (0x00007f1d20b76000)
/lib64/ld-linux-x86-64.so.2 (0x00007f1d2242b000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f1d20971000)
libbsd.so.0 => /usr/lib64/libbsd.so.0 (0x00007f1d2075b000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f1d20532000)
librt.so.1 => /lib64/librt.so.1 (0x00007f1d2032a000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f1d20126000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f1d1ff20000)
So it builds a static versions of libXau.a libXdmcp.a for example, but
then does not use them anyway in the final link but instead the system
wide versions ?
I posted question to github if bzip2, freetype2 and zlib can be external
dependencies or if they contain some TurboVNC specific stuff.
-S-
next prev parent reply other threads:[~2017-11-02 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 12:40 [Buildroot] [PATCH v2 1/1] turbovnc: new package Stefan Fröberg
2017-11-01 6:06 ` Baruch Siach
2017-11-01 9:53 ` Thomas Petazzoni
2017-11-02 21:21 ` Stefan Fröberg [this message]
2017-11-02 21:28 ` Thomas Petazzoni
2017-11-02 23:20 ` Stefan Fröberg
2017-11-03 22:17 ` Stefan Fröberg
2017-11-06 13:13 ` Stefan Fröberg
2017-11-06 19:59 ` Baruch Siach
2017-11-06 20:05 ` Thomas Petazzoni
2017-11-06 22:19 ` Arnout Vandecappelle
2017-11-06 22:38 ` Thomas Petazzoni
2017-11-07 13:28 ` Stefan Fröberg
2017-11-01 19:18 ` Stefan Fröberg
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=59FB8C69.7050108@petroprogram.com \
--to=stefan.froberg@petroprogram.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox