public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Jay Lan <jay.zen.lan@gmail.com>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: kexec@lists.infradead.org
Subject: Re: building makedumpfile 1.5.4 for sles11sp2?
Date: Tue, 05 Nov 2013 10:43:16 -0800	[thread overview]
Message-ID: <52793C44.80006@gmail.com> (raw)
In-Reply-To: <20131105133915.5fe7bc9f@hananiah.suse.cz>

On 11/05/2013 04:39 AM, Petr Tesarik wrote:
> V Mon, 04 Nov 2013 16:37:13 -0800
> Jay Lan <jay.zen.lan@gmail.com> napsáno:
>
>> Hi,
>>
>> It seems the makedumpfile.spec was written for fedora. It
>> probably would work in rhel, but I was not able to build it
>> in an sles11sp2 build environment...
>>
>> The spec file complained it needed elfutils-devel-static.
>> I tried to install elfutils-devel-static-0.156-5.fc19.x86_64.rpm
>> to an sles11sp2, it then complained more failed dependency.
>>
>> How do I build makedumpfile with community tarball in an
>> sles11sp2 environment? Thanks in advance!
> What prevents you from using the sources (or even the binary RPMs for
> your favourite SLES version) from
>
> https://build.opensuse.org/package/show/Kernel%3Akdump/makedumpfile

Hi Petr,

Lack of knowledge of existence of this site? ;-)

Thanks! The official release for sles11sp2 is 1.4.0, and I am
working on  porting 1.5.4 tarball based on the spec file of 1.4.0...
Beautiful! Thanks for your pointer!

Jay

>
> ?
>
> Petr T
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2013-11-05 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  0:37 building makedumpfile 1.5.4 for sles11sp2? Jay Lan
2013-11-05  2:25 ` Jingbai Ma
2013-11-05 12:39 ` Petr Tesarik
2013-11-05 18:43   ` Jay Lan [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=52793C44.80006@gmail.com \
    --to=jay.zen.lan@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=ptesarik@suse.cz \
    /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