From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/9] dumb-init: new package
Date: Sat, 3 Mar 2018 23:10:30 +0100 [thread overview]
Message-ID: <20180303221030.GA16780@scaer> (raw)
In-Reply-To: <20180301230214.lkzpfyad6m7p43jq@tarshish>
Baruch, All,
On 2018-03-02 01:02 +0200, Baruch Siach spake thusly:
> On Thu, Mar 01, 2018 at 11:23:42PM +0100, Yann E. MORIN wrote:
> > On 2018-03-01 23:04 +0100, Thomas Petazzoni spake thusly:
> > > On Thu, 01 Mar 2018 18:21:53 +0100, Peter Korsgaard wrote:
> > > > >> dumb-init doesn't depend on any libraries, so the only issue is static
> > > > >> linking with glibc, right?
> >
> > One can do a static link with glibc, as long as one does not do any name
> > resolution (username, hostname, etc...). But basically, static linking
> > with glibc has long been frowned upon...
>
> This has changed a little recently. Toolchain support is still limited though.
> glibc NEWS for 2.27 says:
>
> * The GNU C Library can now be compiled with support for building static
> PIE executables (See --enable-static-pie in INSTALL). These static PIE
> executables are like static executables but can be loaded at any address
> and provide additional security hardening benefits at the cost of some
> memory and performance. When the library is built with --enable-static-pie
> the resulting libc.a is usable with GCC 8 and above to create static PIE
> executables using the GCC option '-static-pie'. This feature is currently
> supported on i386, x86_64 and x32 with binutils 2.29 or later, and on
> aarch64 with binutils 2.30 or later.
Ah, interesting, thanks! :-)
I always wondered why pie and static were mutually exclusive...
Afterall, semantically they mean two orthogonal things.
Incidentally, I also always wondered why code was not
position-indpendent by default...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-03-03 22:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 7:20 [Buildroot] [PATCH v2 0/9] upgrade docker-engine and associated components Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 1/9] tini: new package Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 2/9] dumb-init: " Christian Stewart
2018-03-01 9:02 ` Thomas Petazzoni
2018-03-01 15:51 ` Peter Korsgaard
2018-03-01 16:08 ` Thomas Petazzoni
2018-03-01 17:21 ` Peter Korsgaard
2018-03-01 22:04 ` Thomas Petazzoni
2018-03-01 22:23 ` Yann E. MORIN
2018-03-01 23:02 ` Baruch Siach
2018-03-03 22:10 ` Yann E. MORIN [this message]
2018-03-01 22:32 ` Peter Korsgaard
2018-03-01 17:58 ` Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 3/9] docker-engine: add support for init processes Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 4/9] docker-engine: select static for tini and dumb-init Christian Stewart
2018-03-01 8:59 ` Thomas Petazzoni
2018-03-01 15:52 ` Peter Korsgaard
2018-03-01 17:59 ` Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 5/9] docker-proxy: new package Christian Stewart
2018-03-30 21:30 ` Peter Korsgaard
2018-03-01 7:20 ` [Buildroot] [PATCH v2 6/9] docker-engine: add dependency on docker-proxy Christian Stewart
2018-03-30 21:30 ` Peter Korsgaard
2018-03-01 7:20 ` [Buildroot] [PATCH v2 7/9] runc: bump to 9f9c96235cc Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 8/9] docker-containerd: bump to v1.0.2 Christian Stewart
2018-03-01 7:20 ` [Buildroot] [PATCH v2 9/9] docker-engine: bump to v18.03.0-ce-rc1 Christian Stewart
2018-03-01 10:15 ` [Buildroot] [PATCH v2 0/9] upgrade docker-engine and associated components Peter Korsgaard
2018-03-01 17:54 ` Christian Stewart
2018-03-01 18:15 ` Peter Korsgaard
2018-03-01 19:06 ` Christian Stewart
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=20180303221030.GA16780@scaer \
--to=yann.morin.1998@free.fr \
--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