Re: Include paths: no "-I." please

2005-07-01 Thread overbored
I figured out the problem: for some reason, I couldn't just specify the 
option in the top-level Makefile.am. I had to specify it in the src 
directory's Makefile.am. (How come?)


Thus spake Ralf Wildenhues on 6/30/2005 6:29 PM:

* overbored wrote on Fri, Jul 01, 2005 at 12:44:38AM CEST:


Thus spake Ralf Wildenhues on 6/30/2005 7:23 AM:


Quoting the manual:
| `nostdinc'
|  This option can be used to disable the standard `-I' options which
|  are ordinarily automatically provided by Automake.


It's not working, -I. is still getting passed in. I re-ran the entire chain:

aclocal && autoconf && automake && ./configure && make

But I still see the two -I. arguments getting passed in.



I cannot reproduce this with a small example.  Could you try to provide
a small example package where this fails?

Regards,
Ralf









Re: Include paths: no "-I." please

2005-06-30 Thread overbored

Thus spake Ralf Wildenhues on 6/30/2005 7:23 AM:

* overbored wrote on Thu, Jun 30, 2005 at 03:07:35AM CEST:


How do I tell automake not to pass "-I." to g++/gcc? Thanks in advance.



Quoting the manual:
| `nostdinc'
|  This option can be used to disable the standard `-I' options which
|  are ordinarily automatically provided by Automake.



It's not working, -I. is still getting passed in. I re-ran the entire chain:

aclocal && autoconf && automake && ./configure && make

But I still see the two -I. arguments getting passed in.




Include paths: no "-I." please

2005-06-30 Thread overbored

How do I tell automake not to pass "-I." to g++/gcc? Thanks in advance.

(The problem is that this project has a string.h, which conflicts with 
the standard string.h. Besides, why "-I." in the first place? Is it 
because some people prefer #include  over #include "blah" for 
their own header files as well?)