Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] samba4: bump to version 4.2.0
Date: Thu, 16 Apr 2015 22:09:43 +0200	[thread overview]
Message-ID: <20150416200943.GM27057@waldemar-brodkorb.de> (raw)
In-Reply-To: <5530145C.8000308@zacarias.com.ar>

Hi,
Gustavo Zacarias wrote,

> On 04/16/2015 04:55 PM, Waldemar Brodkorb wrote:
> 
> > It is not a missing or broken $ORIGIN support. As you posted, there
> > is no $ORIGIN used in RPATH.
> > I am really sure it is this commit and option which is solving the
> > runtime problem:
> > http://git.uclibc.org/uClibc/commit/?id=409f14d9b5e47513d5c939120a33965997c8ceb2
> > 
> > Will be part of uClibc-ng 1.0.2.
> 
> In any case it's just the comment that's wrong but the conditions are
> the same, current releases are not up to snuff.
> We can revisit that when there are newer releases, even though i think
> samba is a big enough package that any uclibc* space savings are
> pointless, after all it needs to share some storage besides the obvious
> firmware size and RAM requirements.

But you still have uClibc as default when using internal toolchain.
So it would be nice if more packages are working out of the box.
And you have users using uClibc for Kodi, which is even bigger than
samba ;)

best regards
 Waldemar

  reply	other threads:[~2015-04-16 20:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 20:44 [Buildroot] [PATCH 1/2] samba: deprecate package due to EOL Gustavo Zacarias
2015-03-05 20:44 ` [Buildroot] [PATCH 2/2] samba4: bump to version 4.2.0 Gustavo Zacarias
2015-03-05 22:29   ` Thomas Petazzoni
2015-03-06  0:11     ` Gustavo Zacarias
2015-03-06  8:40       ` Thomas Petazzoni
2015-03-06  9:04         ` Gustavo Zacarias
2015-03-06  9:26           ` Thomas Petazzoni
2015-03-06  9:34             ` Gustavo Zacarias
2015-03-06  9:40               ` Thomas Petazzoni
2015-03-06 10:32                 ` Gustavo Zacarias
2015-03-06 11:35                   ` Thomas Petazzoni
2015-03-06 13:13                     ` Gustavo Zacarias
2015-03-10 22:04                       ` Peter Korsgaard
2015-03-10 21:53                     ` Peter Korsgaard
2015-03-10 21:56                       ` Thomas Petazzoni
2015-03-10 22:08                         ` Peter Korsgaard
2015-03-10 21:49                   ` Peter Korsgaard
2015-03-10 21:35             ` Peter Korsgaard
2015-03-06 10:03   ` Thomas Petazzoni
2015-04-09 10:33   ` Bernd Kuhls
2015-04-09 10:49     ` Gustavo Zacarias
2015-04-09 20:20       ` Waldemar Brodkorb
2015-04-10 12:16         ` Gustavo Zacarias
2015-04-16 19:55           ` Waldemar Brodkorb
2015-04-16 19:58             ` Gustavo Zacarias
2015-04-16 20:09               ` Waldemar Brodkorb [this message]
2015-04-16 20:13                 ` Gustavo Zacarias
2015-04-16 20:19                 ` Bernd Kuhls
2015-03-05 21:53 ` [Buildroot] [PATCH 1/2] samba: deprecate package due to EOL Arnout Vandecappelle
2015-03-05 22:06   ` Thomas Petazzoni
2015-03-05 22:10     ` Arnout Vandecappelle
2015-03-05 22:23       ` Thomas Petazzoni
2015-03-06  0:11         ` Gustavo Zacarias
2015-03-06  8:19           ` Thomas Petazzoni
2015-03-06  9:07             ` Gustavo Zacarias

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=20150416200943.GM27057@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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