From: Nate Straz <nate@refried.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: ltp-list@lists.sourceforge.net, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] LTP 20091031 Makefiles totally broken?!?
Date: Fri, 6 Nov 2009 14:43:35 -0500 [thread overview]
Message-ID: <20091106194335.GB32249@refried.org> (raw)
In-Reply-To: <20091106191343.GC819@basil.fritz.box>
On Nov 6 20:13, Andi Kleen wrote:
> > So yes, there are known issues with using make versions <3.81. The
>
> For me it seems more the known issue is in the Makefile. 3.80
> is a widely used Make version.
>
> > reason being that some macros and functions that I use to determine
> > absolute path, etc were not available in make 3.80.
>
> Most of my infrastructure in test systems is based on SUSE 10.0
> and it's impractical to upgrade make everywhere.
openSUSE 10.3 does include make-3.81. I hope upgrading to the latest
point release won't disrupt your test systems.
http://download.opensuse.org/distribution/10.3/repo/oss/suse/x86_64/make-3.81-66.x86_64.rpm
Nate
------------------------------------------------------------------------------
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-11-06 20:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 9:57 [LTP] LTP 20091031 Makefiles totally broken?!? Andi Kleen
2009-11-06 11:16 ` Mike Frysinger
2009-11-06 13:09 ` Andi Kleen
2009-11-06 13:21 ` Mike Frysinger
2009-11-06 18:04 ` Garrett Cooper
2009-11-06 18:23 ` Garrett Cooper
2009-11-06 19:09 ` Mike Frysinger
2009-11-06 19:17 ` Andi Kleen
2009-11-09 13:15 ` Cyril Hrubis
2009-11-06 23:02 ` Matt Helsley
2009-11-06 23:09 ` Mike Frysinger
2009-11-06 23:34 ` Matt Helsley
2009-11-07 0:23 ` Mike Frysinger
2009-11-07 0:52 ` Garrett Cooper
2009-11-07 0:54 ` Garrett Cooper
2009-11-08 2:09 ` Garrett Cooper
2009-11-08 20:02 ` Garrett Cooper
2009-11-09 18:01 ` Garrett Cooper
2009-11-06 19:13 ` Andi Kleen
2009-11-06 19:39 ` Mike Frysinger
2009-11-06 19:44 ` Garrett Cooper
2009-11-06 19:53 ` Mike Frysinger
2009-11-06 19:50 ` Andi Kleen
2009-11-06 19:58 ` Mike Frysinger
2009-11-06 20:04 ` Mike Frysinger
2009-11-06 19:43 ` Nate Straz [this message]
2009-11-06 19:59 ` Andi Kleen
2009-11-06 20:25 ` Garrett Cooper
2009-11-06 21:02 ` Andi Kleen
2009-11-06 21:12 ` Mike Frysinger
2009-11-06 21:45 ` Andi Kleen
2009-11-06 21:59 ` Garrett Cooper
2009-11-06 22:47 ` Andi Kleen
2009-11-06 23:03 ` Nate Straz
2009-11-06 22:46 ` Mike Frysinger
2009-11-06 21:47 ` Garrett Cooper
2009-11-06 21:57 ` Andi Kleen
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=20091106194335.GB32249@refried.org \
--to=nate@refried.org \
--cc=andi@firstfloor.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.org \
/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.