I have encountered a problem with aclocal for a long time and have always wondered if there are any reasons for its behavior.
If aclocal is installed in /abc/bin and aclocal is ran with : "-I /abc/share/aclocal" it will emit a warning for every macro found because it will scan the /abc/share/aclocal directory twice. Is there a reason for this behavior ? Couldn't it verify that the "internal directory" is passed in the -I flag and ignore it ? This is a problem because if you are automating a build, the success of such build is dependent on the location of the installed aclocal. [I've just subscribed to the mailing list, could not find the answer on the web, if this has been answered before, feel free to point me to the right location] thanks, Chema
