From: Cliff Wickman <cpw@sgi.com>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: kumagai-atsushi@mxc.nes.nec.co.jp,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
kexec@lists.infradead.org
Subject: Re: makedumpfile 1.5.4, 734G kdump tests
Date: Wed, 10 Jul 2013 13:27:28 -0500 [thread overview]
Message-ID: <20130710182728.GA13240@sgi.com> (raw)
In-Reply-To: <CAJGZr0L7GBqJHaPzgpFxhpF_jmAZfDJYU_=MFxATxnLk13ni4g@mail.gmail.com>
On Wed, Jul 10, 2013 at 04:37:20PM +0400, Maxim Uvarov wrote:
> thanks. I also have a question about static support of snappy in
> makedumpfile.
>
> Dynamic linking works ok. But static link confuses snappy C++ library and
> C, and fails with:
> undefined reference to `__gxx_personality_v0' and undefined reference to
> new[].
>
> Is there workaround for that?
> gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC)
I think you'll have to install the libstdc++ devel rpm, such as
libstdc++-devel-4.4.7-3.el6.x86_64.rpm, to get libstdc++.a
And probably add -lstdc to the Makefile
LIBS := -lsnappy -lstdc++ $(LIBS)
> Maxim.
>
> 2013/7/10 HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
>
> > (2013/07/10 17:33), Maxim Uvarov wrote:
> >
> >> does crash tool read snappy compressed files?
> >>
> >>
> > Yes, but you need to specify libraries at build.
> >
> > http://people.redhat.com/**anderson/crash.changelog.html<http://people.redhat.com/anderson/crash.changelog.html>
> >
> > 6.0.9 - Fix for building on host machines that have glibc-2.15.90
> > installed,
> > <cut>
> >
> > - Add support for reading compressed kdump dumpfiles that were
> > compressed by the snappy compressor. This feature is disabled
> > by
> > default. To enable this feature, build the crash utility in the
> > following manner:
> > (1) Install the snappy libraries by using the host system's
> > package
> > manager or by directly downloading libraries from author's
> > website. The packages required are:
> > - snappy
> > - snappy-devel
> > The author's website is: http://code.google.com/p/**snappy<http://code.google.com/p/snappy>
> > (2) Create a CFLAGS.extra file and an LDFLAGS.extra file in
> > top-level
> > crash sources directory:
> > - enter -DSNAPPY in the CFLAGS.extra file
> > - enter -lsnappy in the LDFLAGS.extra file.
> > (3) Build crash with "make" as always.
> >
> > 6.0.7 - Enhanced the "search" command to allow the searched-for value
> > <cut>
> > - Add support to for reading dumpfiles compressed by LZO using
> > makedumpfile version 1.4.4 or later. This feature is disabled
> > by
> > default. To enable this feature, build the crash utility in the
> > following manner:
> > (1) Install the LZO libraries by using the host system's package
> > manager or by directly downloading libraries from author's
> > website. The packages required are:
> > - lzo
> > - lzo-minilzo
> > - lzo-devel
> > The author's website is: http://www.oberhumer.com/**
> > opensource/lzo <http://www.oberhumer.com/opensource/lzo>
> > (2) Create a CFLAGS.extra file and an LDFLAGS.extra file in
> > top-level
> > crash sources directory:
> > - enter -DLZO in the CFLAGS.extra file
> > - enter -llzo2 in the LDFLAGS.extra file.
> > (3) Build crash with "make" as always.
> >
> > --
> > Thanks.
> > HATAYAMA, Daisuke
> >
> >
>
>
> --
> Best regards,
> Maxim Uvarov
--
Cliff Wickman
SGI
cpw@sgi.com
(651) 683-3824
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-07-10 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 16:24 makedumpfile 1.5.4, 734G kdump tests Cliff Wickman
[not found] ` <CAJGZr0JPrBB3cVyVdwJdd6cEUfnXNMuRijb9EOoSy+XmRupv7A@mail.gmail.com>
2013-07-10 9:07 ` HATAYAMA Daisuke
[not found] ` <CAJGZr0L7GBqJHaPzgpFxhpF_jmAZfDJYU_=MFxATxnLk13ni4g@mail.gmail.com>
2013-07-10 18:27 ` Cliff Wickman [this message]
2013-07-11 13:06 ` Vivek Goyal
2013-07-12 16:14 ` Cliff Wickman
2013-07-12 16:42 ` Vivek Goyal
2013-07-16 9:22 ` HATAYAMA Daisuke
2013-07-16 14:15 ` Vivek Goyal
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=20130710182728.GA13240@sgi.com \
--to=cpw@sgi.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=muvarov@gmail.com \
/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