Well, I guess we all got smarter on the tripple -I. issue. Thanks! Otherwise, I'm also subscribed on the list, so no need to CC me in every post :-) . -- Miki Shapiro <[EMAIL PROTECTED]> Coder - Unixophile - Boarder - Quake God Aladdin Knowledge Systems --------------------------------------------- Tel: +972-(4)-8811403 ICQ: 3EE853 --------------------------------------------- C++ Berkeley Burton Tribes Have board. Will ride.
On 11/07/2002 01:54:55 PM CET Tim Van Holder wrote: > >On Thu, 2002-11-07 at 12:57, Alexandre Duret-Lutz wrote: >> >>> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes: >> >> Tim> On Wed, 2002-11-06 at 11:11, [EMAIL PROTECTED] wrote: >> >> DEFAULT_INCLUDES = -I. -I$(srcdir) -I. >> >> >> >> This raises 2 questions in itself: >> >> a. what's wrong with "DEFAULT_INCLUDES = -I. -I$(srcdir)" >> >> Tim> Don't know that, >> >> The third -I gives the search path for config.h. > >OK - good to know > >> Tim> There's no harm in -I . -I . -I . as far as I know. >> >> FWIW, spaces between `-I' and `.' are not portable. For instance >> in this case OSF's cc will handle `.' as a source file. > >OK OK - guess I should have phrased that as 'There's no harm in >using three consecutive -I options for the same directory, as far >as I know'. > >-- >Tim Van Holder <[EMAIL PROTECTED]> >Anubex > > > ******************************* IMPORTANT ! ********************************** The content of this email and any attachments are confidential and intended for the named recipient(s) only. If you have received this email in error please notify the sender immediately. Do not disclose the content of this message or make copies. This email was scanned by eSafe Mail for viruses, vandals and other malicious content. ******************************************************************************
