public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Mitani" <mitani@ryobi.co.jp>
To: 'Garrett Cooper' <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net, "當座 健市" <toza@ryobi.co.jp>
Subject: Re: [LTP] Realtime test failure
Date: Thu, 18 Nov 2010 10:25:23 +0900	[thread overview]
Message-ID: <000001cb86bf$78f99850$6aecc8f0$@co.jp> (raw)
In-Reply-To: <AANLkTi=V85s0-9tzTvdXtqedgQFABJWvW3pjQQ+F7DcM@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

> -----Original Message-----
> From: Garrett Cooper [mailto:yanegomi@gmail.com]
> Sent: Thursday, November 18, 2010 9:30 AM
> To: Mitani
> Cc: ltp-list@lists.sourceforge.net
> Subject: Re: [LTP] Realtime test failure
> 
> > Thank you for your response.
> >
> > I tried to build with "ltp-66d67b5.tar.gz", but it failed in configure.
> > Therefore, I tried with older git "ltp-92dfd5b.tar.gz", and it succeeded
> > in RHEL5.5-x86 and RHEL4.8-x86 systems.
> >
> > From "ltp-92dfd5b.tar.gz" to "ltp-66d67b5.tar.gz", new probrem occured.
> >
> > New revisions are released in sequence. Therefore I intend to build
> > with the latest version again.
> 
> Huh...? What do you mean failed in configure? Logs please (PS the
> latest snapshot is different from that)!
> Thanks,
> -Garrett


I send configure's logs.

I tried with "ltp-92dfd5b.tar.gz", "ltp-66d67b5.tar.gz" and
"ltp-86209d2.tar.gz".
Only "ltp-92dfd5b.tar.gz" succeeded.

> the latest snapshot is different from that

Yes. latest snapshot is  "ltp-86209d2.tar.gz". But it failed, too.
I send two logs just in case.

  - ltp-86209d2_configure.txt --- result of "ltp-86209d2.tar.gz"
  - ltp-66d67b5_configure.txt --- result of "ltp-66d67b5.tar.gz"


Thank you--


-Tomonori Mitani

[-- Attachment #2: configure_logs.zip --]
[-- Type: application/x-zip-compressed, Size: 3670 bytes --]

[-- Attachment #3: Type: text/plain, Size: 369 bytes --]

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

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

  reply	other threads:[~2010-11-18  1:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  2:54 [LTP] Realtime test failure Mitani
     [not found] ` <AANLkTimGi4v_OHzZAD8BbyGKsuVzpBcokEECezPeTC8e@mail.gmail.com>
2010-11-15  4:58   ` Mitani
2010-11-15  5:20     ` Garrett Cooper
2010-11-15  6:29       ` Mitani
2010-11-15 15:57         ` Garrett Cooper
2010-11-16  8:28           ` Mitani
2010-11-16 17:03             ` Garrett Cooper
2010-11-17  2:59               ` Mitani
2010-11-17  3:17                 ` Garrett Cooper
2010-11-18  0:21                   ` Mitani
2010-11-18  0:30                     ` Garrett Cooper
2010-11-18  1:25                       ` Mitani [this message]
2010-11-19  7:40                       ` Mitani

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='000001cb86bf$78f99850$6aecc8f0$@co.jp' \
    --to=mitani@ryobi.co.jp \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=toza@ryobi.co.jp \
    --cc=yanegomi@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