Re: [LTP] LTP 20091031 Makefiles totally broken?!?

[Andi Kleen <andi@firstfloor.org>]

On Fri, Nov 06, 2009 at 12:25:23PM -0800, Garrett Cooper wrote:
>     You can actually cross-compile, use out-of-build-tree and
> bootstrap the system so it can effectively netboot with LTP installed.
> This is something that we're doing in Cisco today, and it's something
> I highly recommend doing -- especially if you have higher quality
> hardware with newer OS'es doing the building for you.

The hardware I'm using for testing is perfectly capable of
building LTP itself.

>     Granted, it does require more work setting everything up from
> scratch, but once the work is done, it's a lot easier as far as
> long-term maintenance is concerned if you're developing regularly on a
> particular revisioned code-base.

I would prefer to not get into any cross compiling mess. It would
require either static linking or maintenance of a separate build
tree with own libraries, both have many drawbacks.

>     I'm more than happy to provide solutions, but they need to be
> functional, stable, and easy-to-maintain longterm. Providing hacks for
> make 3.80 isn't necessarily a good thing for the project to support

What hacks?

make 3.80 has build whole distributions with millions of LOCs, it's unclear 
to me why it shouldn't be able to build LTP too.

I'm pretty sure that not supporting older distributions is very 
necessarily a bad thing.

> and it may not even solve your problem 100% (you may run into
> stability issues using $(shell readlink -f "") instead of $(abspath ).

I did a quick test of readlink -f and it seems to work here.

> Then it comes back to tools -- I'm basically going to have to write
> checks in autoconf to make sure that readlink does as planned (isn't
> broken), and it's going to be more painful for you performance wise to
> have this hack in place, as opposed to just having an upgraded version
> of make, which also has resolved several bugs between 3.80 and 3.81.

I don't understand: the key is not to test for commands used
by makefiles, but simply only use features which are generally available.

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.

I suspect it's actually not a autoconf problem by itself, but
something that's in the LTP templates.

-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