Re: [Valgrind-developers] Rearranging the tree

[Dirk M. <dm...@gm...>]

On Thursday 08 January 2004 22:04, Jeremy Fitzhardinge wrote:

> 	i386-linux	machine-specific linux stuff
> 	i386-freebsd	machine-specific freebsd stuff
> 	common-linux	general linux stuff
> 	common-freebsd	general freebsd stuff

yes, common is needed. is there any need to rename x86 to i386 ? I'm not sure 
how "stable" uname -i is going to be (or if the next release of gentoo 
hyperpatched will return i586 somewhen), and it didn't really save any code 
as far as I can see. 

> if it doesn't work out, I'm happy to throw it away.  But I'd like to get
> something like this in place as I merge the FreeBSD port (or before, and
> merge FreeBSD into it).

Yeah, thats what I started to do here locally already. 

> BTW: I put some stuff in the Makefile.am files which doesn't look good,
> and surely can't be right - there seems to be a lot of duplication.  How
> can I fix this?  Maybe something to do with aclocal?

I think it should be handled with AC_SUBSTs, seems the cleanest solution to 
me. 

regarding Nicholas' question: I think putting all those nasty things in an 
arch/ subdir is the best solution, since we're going to have many subdirs and 
the extra subdir allows a very neat linking-together of the xxx-common and 
the common-xxx convenience libs into something that is then used for the 
coregrind targets. 


Dirk