From: Andi Kleen <andi@firstfloor.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: ltp-list@lists.sourceforge.net, Andi Kleen <andi@firstfloor.org>,
Nate Straz <nate@refried.org>
Subject: Re: [LTP] LTP 20091031 Makefiles totally broken?!?
Date: Fri, 6 Nov 2009 22:45:58 +0100 [thread overview]
Message-ID: <20091106214558.GJ819@basil.fritz.box> (raw)
In-Reply-To: <200911061612.11199.vapier@gentoo.org>
On Fri, Nov 06, 2009 at 04:12:10PM -0500, Mike Frysinger wrote:
> On Friday 06 November 2009 16:02:25 Andi Kleen wrote:
> > I'm also highly surprised that this doesn't work with autoconf -- I thought
> > the whole point of autoconf was to generate portable makefiles, but
> > in this case it seems to especially generate a non portable Makefile.
>
> that is not the point of autoconf at all; it has nothing to do with makefiles.
> that is the point of automake -- which we specifically are not using. there
> are way too many Makefiles that would need to be generated.
True. So you guys just managed to write a very non portable Makefile on your
own. Congratulations.
I tried to debug the problem, but it's such a maze that I gave up.
It seems to be related to abs_top_builddir not getting expanded correctly.
I suspect simply expanding some of the filter magic rules manually
might fix it.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
------------------------------------------------------------------------------
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 21:46 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
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 [this message]
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=20091106214558.GJ819@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=nate@refried.org \
--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.