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

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

1587.0. "Re: ODE using platform include directory" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Jun 29 1995 12:23

Date Of Receipt: 	29-JUN-1995 10:41:30.54
From: 	SMURF::WASTED::"[email protected]" "29-Jun-1995 1039"
To: 	19.779::edp (Eric Postpischil (Always mount a scratch monkey.)    29-Jun-1995 0953)
CC: 	[email protected]
Subj: 	Re: ODE using platform include directory

Well actually there ARE some portions of the build that DO need to build 
locally because they then need to be executed on the build host to complete 
the build. If you have V2.0 as your host OS for example and you were to create 
a platinum binary from the backing tree, you couldn't be guaranteed that it 
would run.

If you intend to build on a machine, a REQUIREMENT is that you must have all 
the compiler/development subsets installed on that machine. You happened to 
find one of the places in the kernel where this is true - there are a few 
others as well.


		-Grant


| I am trying to do a kernel build in an ODE sandbox backed to
| v30supportos.nightly on my workstation, Mensa.  I am getting these errors:
| 
| makepath ssc/. && cd ssc &&  exec make 'RELEASE_OPTIONS=-idfile `genloc /src/
set
| up/osf1_idlist`'    MAKEFILE_PASS=BASIC dopass_all
| COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/ /bin/cc -I. -I/usr/include ../../../../..
/..
| /../src/kernel/io/cam/siop/ssc/main.c ../../../../../../../src/kernel/io/cam/
sio
| p/ssc/ytab.c ../../../../../../../src/kernel/io/cam/siop/ssc/scsi_lex.c ../..
/..
| /../../../../src/kernel/io/cam/siop/ssc/error.c -o ssc
| ../../../../../../../src/kernel/io/cam/siop/ssc/main.c:
| /usr/lib/cmplrs/cc/cfe: Error: ../../../../../../../src/kernel/io/cam/siop/ss
c/m
| ain.c: 32: Cannot open file string.h for #include
| 
| I did a "build include_" to populate the include area in the obj tree.  On
| Mensa, the compilers are not fully installed, so the /usr/include area does
| not have the standard include files.  However, I believe the build should
| not be using the include area on my workstation; it should be using the inclu
de
| area within the sandbox.
| 
| I created /usr/include/stdio.h and put in it the line:
| 
| 	#error You shouldn't be using this file.
| 
| After doing this, a build in the kernel area of my sandbox produced:
| 
| /usr/lib/cmplrs/cc/cfe: Warning: /usr/include/stdio.h: 1: #error You shouldn'
t b
| e using this file!
| 
| thus confirming that the build is using the platform's include area instead
| of the sandbox's.  Am I correct that the build should not be doing this?
| 
| 
| 				-- edp (Eric Postpischil)


				-Grant



T.RTitleUserPersonal
Name
DateLines
1587.1ODE using platform include directoryAOSG::FILTERAutomatic Posting Software - mail to flume::puckThu Jun 29 1995 13:3740
Date Of Receipt: 	29-JUN-1995 12:18:16.79
From: 	SMURF::ABYSS::"[email protected]"
To: 	abyss::odehelp
CC: 	
Subj: 	ODE using platform include directory

I am trying to do a kernel build in an ODE sandbox backed to
v30supportos.nightly on my workstation, Mensa.  I am getting these errors:

makepath ssc/. && cd ssc &&  exec make 'RELEASE_OPTIONS=-idfile `genloc /src/set
up/osf1_idlist`'    MAKEFILE_PASS=BASIC dopass_all
COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/ /bin/cc -I. -I/usr/include ../../../../../..
/../src/kernel/io/cam/siop/ssc/main.c ../../../../../../../src/kernel/io/cam/sio
p/ssc/ytab.c ../../../../../../../src/kernel/io/cam/siop/ssc/scsi_lex.c ../../..
/../../../../src/kernel/io/cam/siop/ssc/error.c -o ssc
../../../../../../../src/kernel/io/cam/siop/ssc/main.c:
/usr/lib/cmplrs/cc/cfe: Error: ../../../../../../../src/kernel/io/cam/siop/ssc/m
ain.c: 32: Cannot open file string.h for #include

I did a "build include_" to populate the include area in the obj tree.  On
Mensa, the compilers are not fully installed, so the /usr/include area does
not have the standard include files.  However, I believe the build should
not be using the include area on my workstation; it should be using the include
area within the sandbox.

I created /usr/include/stdio.h and put in it the line:

	#error You shouldn't be using this file.

After doing this, a build in the kernel area of my sandbox produced:

/usr/lib/cmplrs/cc/cfe: Warning: /usr/include/stdio.h: 1: #error You shouldn't b
e using this file!

thus confirming that the build is using the platform's include area instead
of the sandbox's.  Am I correct that the build should not be doing this?


				-- edp (Eric Postpischil)