Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/6] temporary hack to fix linking error
Date: Mon, 21 Apr 2014 12:04:01 -0300	[thread overview]
Message-ID: <53553361.80008@zacarias.com.ar> (raw)
In-Reply-To: <1397382423-4939-6-git-send-email-wbx@openadk.org>

On 04/13/2014 06:47 AM, Waldemar Brodkorb wrote:

> See here for more info:
> https://sourceware.org/ml/libc-help/2014-04/msg00020.html
> 
> Still working on the issue.

This patch works, but by it being temporary/hacky it should be
conditionally applied just for microblaze since you probably have no
idea how it can affect other architectures.

By the way, how is it that we're not interested in fixing things or
something like that?
(https://sourceware.org/ml/libc-help/2014-04/msg00027.html)
I'm using my (volunteer/spare) time looking at your patchset and testing
it, so i think that's not a fair assessment, and disabling eglibc
because "no time to test" and saying that at the same time sounds pretty
much like double-standards.
I'm not saying this to get you angry or anything like that, it's just
that you're stating it in a very public mailing list and it seems
utterly unfair to many BR contributors. Many people do what they can
when they can.

Now with that out of the way, care to respin this patch with the
consideration i mentioned above?
Regards.

  reply	other threads:[~2014-04-21 15:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  9:46 [Buildroot] [PATCH 0/6] Microblaze fixes Waldemar Brodkorb
2014-04-13  9:46 ` [Buildroot] [PATCH 1/6] use default binutils for microblaze Waldemar Brodkorb
2014-04-21 15:02   ` Gustavo Zacarias
2014-04-28 20:10   ` Peter Korsgaard
2014-04-13  9:46 ` [Buildroot] [PATCH 2/6] use default gcc 4.8.2 " Waldemar Brodkorb
2014-04-21 15:03   ` Gustavo Zacarias
2014-04-28 20:15   ` Peter Korsgaard
2014-04-13  9:47 ` [Buildroot] [PATCH 3/6] upstream glibc 2.18/2.19 works fine with microblaze Waldemar Brodkorb
2014-04-21 15:03   ` Gustavo Zacarias
2014-04-28 19:08     ` William Welch
2014-04-28 19:18       ` Gustavo Zacarias
2014-04-28 19:45         ` William Welch
2014-04-28 19:53           ` Gustavo Zacarias
2014-04-29  7:18           ` Waldemar Brodkorb
2014-04-29 13:14             ` Gustavo Zacarias
2014-04-29 13:27               ` Mike Zick
2014-04-28 20:17   ` Peter Korsgaard
2014-04-13  9:47 ` [Buildroot] [PATCH 4/6] disable eglibc, no time to test Waldemar Brodkorb
2014-04-21 15:03   ` Gustavo Zacarias
2014-04-13  9:47 ` [Buildroot] [PATCH 5/6] temporary hack to fix linking error Waldemar Brodkorb
2014-04-21 15:04   ` Gustavo Zacarias [this message]
2014-04-22 17:49     ` Waldemar Brodkorb
2014-04-22 18:29       ` Gustavo Zacarias
2014-04-13  9:47 ` [Buildroot] [PATCH 6/6] update to 3.14 Waldemar Brodkorb
2014-04-21 15:04   ` 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=53553361.80008@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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