links vs include for config directory files

[Benjamin Kosnik]

Hey folks.

I'm preparing to add in a 

config/os/aix/bits/atomicity.h 

file as per Mr. Edelsohn's request.


Now, to make this work as src/Makefile.am is currently configured, 
src/Makefile.am

CONFIG_INCLUDES = \
	-I$(top_srcdir)/@cpu_include_dir@ \
	-I$(top_srcdir)/@ctype_include_dir@


would have to change to:

CONFIG_INCLUDES = \
	-I$(top_srcdir)/@os_include_dir@ \
	-I$(top_srcdir)/@cpu_include_dir@ 


This would add a dependency on the ording of the includes, as both
os_include_dir and cpu_include_dir would include a bits/atomicity.h
file.


This would be a drag, and if possible should be avoided.



To get around this, I'm thinking of taking out the CONFIG_INCLUDE bits
from src/Makefile.am, and adding in sym links for the files in the
config directory (as is currently done with the thread and io code,
for instance.)

This would remove potential ordering conflicts.

Thoughts?

Tom, this is pretty much the approach that libgcj takes, right?

-benjamin