Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] target-finalize: fix libthread_db strip fix
Date: Sun, 28 Nov 2010 17:13:10 -0500	[thread overview]
Message-ID: <201011281713.11840.vapier@gentoo.org> (raw)
In-Reply-To: <8739ql177x.fsf@macbook.be.48ers.dk>

On Sunday, November 28, 2010 16:14:26 Peter Korsgaard wrote:
> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
>  Mike> On Sunday, November 28, 2010 05:09:06 Peter Korsgaard wrote:
>  >> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
>  Mike> The attempt to fix libthread_db for some targets broke others.  If
> 
>  >> you Mike> want to match more libs, you shouldn't do so by breaking
>  >> others. The Mike> correct SONAME is libthread_db.so.#.
>  >> 
>  >> Out of interest, what targets got broken, and how are the libthread_db
>  >> files called?
> 
>  Mike> i only care about Blackin targets.  we dont waste space on
>  Mike> symlinks and only install SONAMEs.
> 
> Ok, I naturally don't share this narrow viewpoint. It's not a use case
> for any of the supported archs, but ok, it's easy to support.
> 
> Again, I know this is probably just you being you, but do take care of
> your choice of words. To me, this commit message sounds quite
> aggressive, as if you're upset that Javier's fix broke your
> nonstandard/unsupported/undocumented setup, which is ofcause pretty
> silly considering that he clearly spent effort on verifying it with
> multiple toolchains and the original commit didn't even work for the
> default configuration.

my setup isnt any of these things.  i've been pushing patches to you but they 
havent been merged yet (i wonder when/if they will be).  ive seen other people 
doing the same thing with other distros/arches as well because it makes sense.  
verifying with two arm toolchains is grasping at "multiple toolchains".

>  Mike> btw, why is your quoting style so screwed up ?
> 
> It's just standard emacs supercite, like I've used for the last 10yrs or
> so. I find it handy in mailing lists when several people participate in
> a discussion.

fortunately ive only seen two people (including you) using this style.  it 
just falls apart with replies.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101128/d065f0a6/attachment.pgp>

  reply	other threads:[~2010-11-28 22:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 22:43 [Buildroot] [PATCH] target-finalize: fix libthread_db strip fix Mike Frysinger
2010-11-28 10:09 ` Peter Korsgaard
2010-11-28 17:36   ` Mike Frysinger
2010-11-28 21:14     ` Peter Korsgaard
2010-11-28 22:13       ` Mike Frysinger [this message]
2010-11-29  7:53         ` Peter Korsgaard
2010-11-29 11:21           ` Mike Frysinger
2010-11-29 11:41             ` Peter Korsgaard
2010-11-29 20:44               ` Mike Frysinger
2010-11-29 21:14                 ` Peter Korsgaard
2010-11-29 23:45                   ` Mike Frysinger
2010-11-28 22:25       ` Mike Frysinger
2010-11-29  7:57         ` Peter Korsgaard
2010-11-29 11:18           ` Mike Frysinger
2010-11-29 11:38             ` Peter Korsgaard

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=201011281713.11840.vapier@gentoo.org \
    --to=vapier@gentoo.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