Conference smurf::buildhelp

2323.0. "build for v32D failing - sending again due to mail failure" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Jun 04 1996 13:55

Date Of Receipt: 	 4-JUN-1996 12:30:53.74
From: 	ALPHA::amilicia "Anne Milicia bossec"
To: 	buildhelp@DEC:.zko.alpha
CC: 	
Subj: 	build for v32D failing - sending again due to mail failure

Hi,
I sent this to odehelp but the mailer couldn't handle the long record so I'm
breaking it up and resending.
Anne

Forwarded message:
From daemon Tue Jun  4 12:16:40 1996
Date: Tue, 4 Jun 1996 09:16:05 -0700
From: [email protected] (Mail Delivery Subsystem)
Subject: Returned mail: Service unavailable
Message-Id: <[email protected]>
To: [email protected]

   ----- Transcript of session follows -----
While talking to /usr/bin/mail11v3:
>>> DATA
<<< 400-ali; %MAIL-E-READERR, error reading 
<<< 554-ali; -RMS-W-RTB, 415 byte record too large for user's buffer
<<< 554
554 decwet::jo,decwet::jordan,decwet::ali... Service unavailable


Hi,
I'm working on a backlog reduction CLD and the customer has 3.2D installed
so I want to build a fix for that version.  I created a sandbox backed to
v32de1supportos.nightly and tried to build a kernel.  When I tried
"build setup" I got the following errors and the build quit:

mkdata: created directory
env - COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/ /usr/bin/cc   -EL -c  -DBSD44 -DMSG  
-D__WCHAR_T_LEN=4 -Wf,-wchar32  -DMACH -DCMU -DOSF  -Dalpha -D__alpha__ 
-D__alpha -Dunix -D__unix__      -O2 -Olimit 5000    -DCMU -D_NO_PROTO 
-Dconst=      `genpath -I.` `genpath  -I../../include -I/usr/include ` 
-I/usr/include  /usr/sde/osf1/build/v32de1supportos.nightly/src/kernel/src/mkdata/mkdata.c
cc: Error: /usr/include/string.h, line 164: In the declaration of "__R", a funct
ion may not return a function type.
extern char    * __R(basename) __((char  *));
-----------------^
cc: Warning: /usr/include/string.h, line 164: In the declaration of "__R", a fun
ction declarator has an identifier list but is not part of a function definition
.  Extraneous parameter names are ignored.
extern char    * __R(basename) __((char  *));
-----------------^
cc: Error: /usr/include/string.h, line 165: In the declaration of "__R", a funct
ion may not return a function type.
extern char    * __R(dirname) __((char  *));
-----------------^
cc: Warning: /usr/include/string.h, line 165: In the declaration of "__R", a fun
ction declarator has an identifier list but is not part of a function definition
.  Extraneous parameter names are ignored.
extern char    * __R(dirname) __((char  *));
-----------------^
cc: Error: /usr/include/stdlib.h, line 169: In the declaration of "__R", a funct
ion may not return a function type.
extern long     __R(a64l) __((const char *));
----------------^
cc: Warning: /usr/include/stdlib.h, line 169: In the declaration of "__R", a fun
ction declarator has an identifier list but is not part of a function definition
.  Extraneous parameter names are ignored.
extern long     __R(a64l) __((const char *));
----------------^
cc: Error: /usr/include/stdlib.h, line 170: In the declaration of "__R", a funct
ion may not return a function type.
extern char     * __R(l64a) __((long));
------------------^
cc: Warning: /usr/include/stdlib.h, line 170: In the declaration of "__R", a fun
ction declarator has an identifier list but is not part of a function definition
.  Extraneous parameter names are ignored.
extern char     * __R(l64a) __((long));
------------------^
cc: Error: /usr/include/stdlib.h, line 171: In the declaration of "__R", a funct
ion may not return a function type.
extern int      __R(ttyslot) __((void));
----------------^
cc: Warning: /usr/include/stdlib.h, line 171: In the declaration of "__R", a fun
ction declarator has an identifier list but is not part of a function definition
.  Extraneous parameter names are ignored.
extern int      __R(ttyslot) __((void));
----------------^
*** Exit 1
Stop.
*** Exit 1
Stop.
*** Exit 1
Stop.
*** Exit 1
Stop.


Am I getting something set in the compiler for this environment that I don't
want?  Did workon set everything up right?

(The following is broken up for the mailer.)
$ echo $PATH
/work1/sandboxes/v32de1/tools/alpha/hostbin:
/work1/sandboxes/v32de1/tools/alpha/bin:
/work1/sandboxes/v32de1/tools/alpha/acc:
/usr/sde/osf1/build/v32de1supportos.nightly/tools/alpha_OSF1/alpha/hostbin:
/usr/sde/osf1/build/v32de1supportos.nightly/tools/alpha_> OSF1/alpha/bin:
/usr/sde/osf1/build/v32de1supportos.nightly/tools/alpha_OSF1/alpha/acc:
/usr/sde/ode3.0/tools/alpha_ace/bin:/usr/ucb:/bin:/usr/bin:/sbin:/usr/sbin

Thanks for the help.
Anne

Date Of Receipt: 	 4-JUN-1996 12:53:05.93
From: 	FLUME::"[email protected]" "04-Jun-1996 1246"
To: 	Anne Milicia bossec <[email protected]>
CC: 	[email protected], [email protected]
Subj: 	Re: build for v32D failing - sending again due to mail failure

Bet you're running 4.0 trying to build 3.2, no?  At present this doesn't work. 
The giveaway is the COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/ /usr/bin/cc.

To get this to work you'll need to submit the following changes to the support 
pool as analyzed and defined by Fred Cantor in the following mail:


| As you know I had trouble building a sandbox backed by hw6os.bl6 on
| my workstation running V4.0. The errors were in three files:
| 	src/kernel/src/mkdata/mkdata.c
| 	src/kernel/src/mkeisadata/mkeisadata.c
| 	src/kernel/src/mktcdata/mktcdata.c
| 
| The errors were caused by mixing and matching problems with the string.h
| header file. These error should be fixed before UHS developers convert
| their workstations to V4.0 and encounter them. There are two options
| for fixing this:
| 
| 1) Remove the #include of string.h and stdlib.h from the above files.
|    They build if these #includes are removed.
| 
| 2) Modify the Makefile for the above .c files as follows:

| 	41c41
| 	< INCFLAGS              = -I/usr/include -I../../include
| 	---
| 	> INCFLAGS              = -I../../include -I/usr/include
| 
| Searching /usr/include first makes sure the compiler sees the matching
| version of the header files (i.e., the ones from the build machine).
| Option 2 seems cleaner to me.
| 
| Fred


			-Grant





> Hi,
> I'm working on a backlog reduction CLD and the customer has 3.2D installed
> so I want to build a fix for that version.  I created a sandbox backed to
> v32de1supportos.nightly and tried to build a kernel.  When I tried
> "build setup" I got the following errors and the build quit:
> 
> mkdata: created directory
> env - COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/ /usr/bin/cc   -EL -c  -DBSD44 -DMSG  
> -D__WCHAR_T_LEN=4 -Wf,-wchar32  -DMACH -DCMU -DOSF  -Dalpha -D__alpha__ 
> -D__alpha -Dunix -D__unix__      -O2 -Olimit 5000    -DCMU -D_NO_PROTO 
> -Dconst=      `genpath -I.` `genpath  -I../../include -I/usr/include ` 
> -I/usr/include  /usr/sde/osf1/build/v32de1supportos.nightly/src/kernel/src/mkdata/mkdata.c
> cc: Error: /usr/include/string.h, line 164: In the declaration of "__R", a funct
> ion may not return a function type.
> extern char    * __R(basename) __((char  *));
> -----------------^
> cc: Warning: /usr/include/string.h, line 164: In the declaration of "__R", a fun
> ction declarator has an identifier list but is not part of a function definition
> .  Extraneous parameter names are ignored.
> extern char    * __R(basename) __((char  *));
> -----------------^
> cc: Error: /usr/include/string.h, line 165: In the declaration of "__R", a funct
> ion may not return a function type.
> extern char    * __R(dirname) __((char  *));
> -----------------^