From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Albert Antony <albert@newtec.dk>
Subject: Re: [ptxdist] [PATCH] Enable "strip" install option handling for libraries
Date: Tue, 21 Jul 2015 15:14:39 +0200 [thread overview]
Message-ID: <201507211514.39191.jbe@pengutronix.de> (raw)
In-Reply-To: <CAHChq8N5iOkFgODt2YU4U8Ww+BsPV_XbmwYJ9ggZcQoL66MC+Q@mail.gmail.com>
Hi Albert,
On Tuesday 21 July 2015 14:04:02 Albert Antony wrote:
> Maybe I am not aware of the auto-detection feature. And from the looks of
> it I misunderstand the use-case for the strip y|n option altogether. So let
> me explain.
>
> Our requirement here is to install debug versions of certain libraries on
> the target, some of which are installed via install_lib, and some others
> like libpthread which are installed via install_copy_toolchain_lib. Since
> the strip y|n option to these calls seem to be getting ignored, I assumed
> this might be a missing feature. This is what prompted the patch. If there
> is a better way (maybe auto-detection?) to achieve the same then I guess
> there is no need for it. Could you point me to where I can find out more
> about auto-detection?
Why do you want to have libraries *with* debug information in your root
filesystem?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-21 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 12:04 Albert Antony
2015-07-21 13:14 ` Juergen Borleis [this message]
2015-07-21 14:03 ` Albert Antony
2015-07-21 14:34 ` Juergen Borleis
2015-07-22 8:31 ` Albert Antony
2015-07-22 9:29 ` Juergen Borleis
2015-07-22 13:28 ` Albert Antony
-- strict thread matches above, loose matches on Subject: below --
2015-07-21 10:09 Albert Antony
2015-07-21 10:26 ` Michael Olbrich
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=201507211514.39191.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=albert@newtec.dk \
--cc=ptxdist@pengutronix.de \
/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