Conference smurf::buildhelp

Date Of Receipt: 	21-SEP-1993 14:54:15.07
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: anyone know the answer to Mike's question?

With the exception of the files in src/usr/lib/makefiles which
all OSF Makefiles need access to, it ought to build without
anything else from the usr space. Some pains have been taken
over the last few years to ensure that is true. If you find
that is not true, we had better take a look at why.

The reverse however is not true. usr space needs include files
etc from kernel space.

	-Grant

| 
| 
| Sarah,
| 
| 	Is it specifically intended that the kernel can
| build without any help from the /usr files in the source
| pool?
| 
| 	(It doesn't--/usr/makefiles/standard.mk is used.)
| 
| Just curious,
| - -mike
| 
| 
| ------- End of Forwarded Message
| 
| 

Date Of Receipt: 	17-JAN-1995 16:03:15.33
From: 	SMURF::WASTED::harinder "Harinder Bhasin USG"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	Question?

Hi!  I am trying to add a definition (-DACTIVE) on the command line for the
build process.  For example:

	% build CFLAGS=-DACTIVE BINARY_ MAKE_ARGS="vol.o"

This command does not add -DACTIVE to the CFLAGS during the compilation of the
vol.c.  Could someone please let me know whats wrong with the syntax.

				Thanx!

								Harinder.

Date Of Receipt: 	17-JAN-1995 16:37:08.17
From: 	SMURF::WASTED::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	harinder odehelp
CC: 	
Subj: 	Re:  Question?
According to the example in /usr/sde/osf1/doc/kernel-build-rules: 	

    build MAKE_ARGS="-DACTIVE vol.o" BINARY_


	From harinder  Tue Jan 17 16:02:26 1995
	Delivery-Date: Tue, 17 Jan 95 16:02:29 -0500
	Return-Path: harinder
	Received: from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
		id AA05091; Tue, 17 Jan 1995 16:02:26 -0500
	Received: by wasted.zk3.dec.com; (5.65/1.1.8.2/22Dec94-1214PM)
		id AA07774; Tue, 17 Jan 1995 16:02:07 -0500
	From: Harinder Bhasin USG <harinder>
	Message-Id: <[email protected]>
	Subject: Question?
	To: odehelp
	Date: Tue, 17 Jan 1995 16:02:07 -0500 (EST)
	Organization: DIGITAL (DEC), Unix Eng. Group, Base OS
	Phone: 603-881-1499
	Dtn: 381-1499
	X-Mailer: ELM [version 2.4 PL20]
	Content-Type: text
	Content-Length: 340       
	
	
	Hi!  I am trying to add a definition (-DACTIVE) on the command line for the
	build process.  For example:
	
		% build CFLAGS=-DACTIVE BINARY_ MAKE_ARGS="vol.o"
	
	This command does not add -DACTIVE to the CFLAGS during the compilation of the
	vol.c.  Could someone please let me know whats wrong with the syntax.
	
					Thanx!
	
									Harinder.
	
	

Date Of Receipt: 	17-JAN-1995 16:43:17.70
From: 	SMURF::FLUME::jmcg "Jim McGinness"
To: 	harinder@DEC:.zko.flume
CC: 	buildhelp@DEC:.zko.flume
Subj: 	Re:  Question?

There's a handoff between the kernel Makefile and the BINARY Makefile;
it does not convey the CFLAGS argument.  You should be able to get it
to go across by saying

  build BINARY_ MAKE_ARGS="CDEBUGOPTS=-DACTIVE vol.o"

You might also get the result you want by compiling with

  build BINARY_ MAKE_ARGS="CFLAGS=-DACTIVE vol.o"

but not if vol.c depends on any of the "normal" CFLAGS components.

 -- jmcg

Date Of Receipt: 	18-JAN-1995 08:32:33.08
From: 	SMURF::WASTED::harinder "Harinder Bhasin USG"
To: 	buildhelp@DEC:.zko.wasted
CC: 	
Subj: 	Question?

Hi!  I would like to know how does a module (ptos) gets linked in the vmunix when we
invoke "build FLAMINGO_vmunix".  I am in the process of building a module that I DON'T
want to include in the vmunix.  This module will just stay in the BINARY directory.
In addition, how do I checkout the Makefile in the BINARY directory to modify it and
check back in.  Do I need special permissions?  According to the notes only ODE group
is authorized to modify makefiles.

					Thanx!
									Harinder.

Date Of Receipt: 	18-JAN-1995 09:26:35.66
From: 	SMURF::FLUME::jmcg "Jim McGinness"
To: 	harinder@DEC:.zko.flume
CC: 	buildhelp@DEC:.zko.flume
Subj: 	Re:  Question?

Were you able to get vol.o compiled with the -DACTIVE flag using one of the
command lines I suggested?

The Makefile in BINARY is generated by the config step, so it's not
possible to modify it directly.  You can propose a change to a Makefile,
but there's been enough trouble in the past that the proposal will receive
quite a bit of scrutiny.  I'm not sure it's possible to cause an object
file to be generated in the BINARY directory without it _ever_ being linked
into a kernel.  What would be the point?  You could specify the file in
the files file as being "optional something Binary" and, as long as no
normal config file defines the "something", the file would not be linked
into a target kernel in the normal customer build...but it might get
linked into a BINARY/vmunix by the nightly build or a sandbox build.

	-- jmcg