All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: srikanth007m@gmail.com
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP make failed
Date: Thu, 30 Jul 2015 03:51:02 -0400 (EDT)	[thread overview]
Message-ID: <1851015047.604153.1438242662396.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CANKSX+FRJcg3xmc2BbWiDzmSqT2NC+hQib-UsWA4yoWTq8fB3g@mail.gmail.com>


----- Original Message -----
> Can you tell me what kind of steps you followed to cross compile LTP
> for arm? Does it make any difference from the configure what i am
> using and you.
> 
> memtest suite? can you point me to the location

http://pyropus.ca/software/memtester/

---
Li Wang

> 
> On Thu, Jul 30, 2015 at 1:15 AM, Cyril Hrubis <chrubis@suse.cz> wrote:
> > Hi!
> >> FYI, Here is my host configuration.
> >> Linux srikanth-linux 3.15.0-031500rc2-generic #201404201435 SMP Sun
> >> Apr 20 18:36:18 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> >>
> >> @Cyril - libkerntest.a got generated with your suggested changes. Does
> >> that make any difference between INTERNAL_LIB to LIB? Should i need to
> >> change any other files to unblock the compilation?
> >
> > The only difference between INTERNAL_LIB and LIB is one ifneq and
> > variable assigment in the lib.mk. So if that does not work for you, you
> > either hit bug in make, libc, kernel or hardware. Changing it from
> > INTERNAL_LIB to LIB only works around that bug.
> >
> > I've just recompiled LTP for arm without a problem. In your case I would
> > try to run memtest over night on your machine first. Otherwise you may
> > spend hours trying to catch something that in reality is a hardware bug.
> >
> > --
> > Cyril Hrubis
> > chrubis@suse.cz
> 
> 
> 
> --
> Thanks & Regards,
> M.Srikanth Kumar.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2015-07-30  7:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 13:32 [LTP] LTP make failed $rik@nth 
2015-07-29 14:30 ` Jan Stancek
2015-07-29 14:45 ` Cyril Hrubis
     [not found]   ` <CANKSX+ETp0jdXp+zSUtUPn8SWUQaCh1bETYzcpF_C8kZpPtGdQ@mail.gmail.com>
2015-07-29 15:29     ` Cyril Hrubis
     [not found]       ` <1186607709.563342.1438184803657.JavaMail.zimbra@redhat.com>
2015-07-29 15:50         ` Cyril Hrubis
     [not found]           ` <CANKSX+EukvUBmjMf7TMxTzcsMXmzfGb+FYqrdo7vKnEiLb6wyg@mail.gmail.com>
2015-07-29 19:45             ` Cyril Hrubis
     [not found]               ` <CANKSX+FRJcg3xmc2BbWiDzmSqT2NC+hQib-UsWA4yoWTq8fB3g@mail.gmail.com>
2015-07-30  7:45                 ` Cyril Hrubis
2015-07-30  7:51                 ` Li Wang [this message]
2015-07-30 16:25                   ` $rik@nth 
2015-07-30 16:33                     ` Cyril Hrubis

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=1851015047.604153.1438242662396.JavaMail.zimbra@redhat.com \
    --to=liwang@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=srikanth007m@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.