From: Paul Larson <paul.larson@canonical.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] fix lib6 test building
Date: Wed, 12 Aug 2009 10:13:14 -0500 [thread overview]
Message-ID: <4A82DC0A.3050502@canonical.com> (raw)
In-Reply-To: <364299f40908061022m926d148o661e1c8a2eb58a5@mail.gmail.com>
Garrett Cooper wrote:
> On Thu, Aug 6, 2009 at 7:52 AM, Paul Larson<paul.larson@canonical.com> wrote:
>> The lib6 tests seem to fail the first pass through building for me
>> because ranlib does not seem to get set correctly at any point. This
>> seems to fix it up for me.
>
> Fixed on HEAD moments ago:
>
> gcooper@orangebox /scratch/ltp-dev2/ltp $ cvs diff
> testcases/network/lib6/Makefile
> Index: testcases/network/lib6/Makefile
> ===================================================================
> RCS file: /cvsroot/ltp/ltp/testcases/network/lib6/Makefile,v
> retrieving revision 1.6
> diff -r1.6 Makefile
> 25a26,27
>> RANLIB ?= ranlib
The patch you checked in does not correct the build failure.
Thanks,
Paul Larson
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-12 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 14:52 [LTP] fix lib6 test building Paul Larson
2009-08-06 17:22 ` Garrett Cooper
2009-08-12 15:13 ` Paul Larson [this message]
2009-08-12 18:52 ` Henry Yei
2009-08-12 20:14 ` Garrett Cooper
2009-08-12 21:09 ` Paul Larson
2009-08-12 21:28 ` Garrett Cooper
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=4A82DC0A.3050502@canonical.com \
--to=paul.larson@canonical.com \
--cc=ltp-list@lists.sourceforge.net \
--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 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.