[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

8900.0. "usage of VPATH in Makefile" by TPOVC::SIMONLEE () Wed Feb 19 1997 22:59

    
    My customer's programs are dispersed into different directories, so make
    cannot find their programs in other directories except those within the
    current working directory. I told them to add a VPATH environment in
    the Makefile, so make can find the other programs. But they encountered
    another problem -- I was told on the phone and did not see the error
    message -- that the C compiler can't find system include file <*.h> and
    <sys/*.h>. This is what I can't understand. Supposedly, the compiler
    must be able to find those include file because they are built-in and
    reside in a fixed location /usr/include and /usr/include/sys. So is there
    anything wrong or do we have to do anything else when using VPATH? Please
    advise. I didn't find any descriptions in the manual or man pages. Thanks!
    
    /Simon
    
    
    
T.RTitleUserPersonal
Name
DateLines
8900.1VAXCPU::michaudJeff Michaud - ObjectBrokerThu Feb 20 1997 02:3711
	They aren't putting a -I (with no directory name following)
	on the command line are they?

	They could be doing this accidently if they have something like:

		CFLAGS=-I$(foo)

	and foo is an undefined macro.

	Using -I with no directory name following tells the compiler
	(preprocessor) to *not* search /usr/include ....