mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Morand, Guy" <Guy.Morand@comet.ch>
Subject: Re: [ptxdist] .debug folders in release
Date: Tue, 10 May 2016 16:41:19 +0200	[thread overview]
Message-ID: <201605101641.19502.jbe@pengutronix.de> (raw)
In-Reply-To: <68AC191B3EB2874F99C36CD9CA3A6D422221C251@cgpmbx01.comet.ch>

Hi Guy,

On Tuesday 10 May 2016 15:11:05 Morand, Guy wrote:
> I noticed that in the built image, there libraries with debug symbols
> available, for example: -------------
> for f in $(find /usr/ /lib/ /sbin/ | grep debug$) ; do du -ks $f ; done |
> sort -n 72      /usr/lib/collectd/.debug
> 212     /lib/udev/.debug
> 352     /usr/libexec/sudo/.debug
> 368     /sbin/.debug
> 768     /usr/lib/lighttpd/.debug
> 2256    /usr/sbin/.debug
> 6568    /lib/.debug
> 8212    /usr/bin/.debug
> 11596   /usr/lib/.debug
> -------------
>
> I dindn't find any relevant option in menuconfig, is there a way to perform
> some cleanup before creating the ubi image?

Where did you search for these ".debug" folders? On your local harddisk 
in "platform-<yourplatfrom>/root" or on the final UBI at your target generated 
by PTXdist?

The ".debug" folders get created for NFSroot purposes only. They should not be 
part of the final images (UBI, EXT2 and so on).

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2016-05-10 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 13:11 Morand, Guy
2016-05-10 14:41 ` Juergen Borleis [this message]

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=201605101641.19502.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=Guy.Morand@comet.ch \
    --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