Hello, A number of very confusing things are noticeable in the build files with respect to regparm support:
- the setting is written to a file but is also checked automatically .... This is done in the (seemingly) os independend setupdirs.sh script but is only valid for linux ... - access to the differently compiled objects is sometimes via symbolic link, sometimes via variable in a script and sometimes directly .. - default behaviour is to compile both versions, but this is done by pretending to be a sub directory i.s.o being on the same hierarchical level, so the makefile ends up calling a copy of itself... After figuring out that (non-arm) 2.6 kernels (even my antiquated FC3 2.6.9 kernel) are by default compiled with CONFIG_REGPARM, complexity went down a notch by specifying --regparm to the configure script. Is it still necessary to compile both types ? I understood that 2.4 kernels are not supported anymore anyway and I believe there are more elegant ways to treat the arm case. This way only the one corresponding to the target system is built. Only looking to simplify things, Sven Sven Biebaut +32 2 391 2362 sven.bieb...@be.thalesgroup.com ----------------------------------------------------------------------------- T COMMUNICATIONS BELGIUM Rue des Frères Taymans 28, B-1480 Tubize, Belgium Phone: +32 (0)2 3912211, fax: +32 (0)2 3912300
_______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
