Thanks. I know .a links into app.
When build lfs I configure many packges with --disable-static in chapt
6. some work, some failed, and some still create .a
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above in
preference. Nothing on a running system uses them. Some programs are
specifically coded to only link against .a files (which can be changed
by editing makefiles).
I would recommend reading about the difference between shared and
static libraries before you make your decision.
On Fri, Jul 9, 201
Then is it safe to del all .a libraries. I've found clfs did this.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On Thu, Jul 8, 2010 at 6:29 AM, xinglp wrote:
> lfs svn 6.62. Stripping Again
>
>
/tools/bin/find /{,usr/}{bin,lib,sbin} -type f -exec /tools/bin/strip
--strip-debug '{}' ';'
If disk space is very tight, the --strip-all option can be used on the
binaries in /{,usr/}{bin,sb
lfs svn 6.62. Stripping Again
>>> /tools/bin/find /{,usr/}{bin,lib,sbin} -type f -exec /tools/bin/strip
>>> --strip-debug '{}' ';'
>>> If disk space is very tight, the --strip-all option can be used on the
>>> binaries in /{,usr/}{bin,sbin} to gain several more megabytes.
>>> Do not use this
