| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 497.1 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 12:33 | 31 |
| Date Of Receipt: 3-JAN-1994 16:14:24.23
From: US2RMC::"johnf@zk3.dec.com" "John Flanagan"
To: naresh@zk3.dec.com
CC: buildhelp@zk3.dec.com, darrell@zk3.dec.com, johnf@zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
Naresh,
The problem is this line:
sh: /usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/gcc/cc
There is no gcc directory under alpha. Do you have any variables set in your
.cshrc or .login that would pass in this variable? In your workon, if you
could type "sbinfo" and forward the output of that along to us that would
help. There are a couple of variables that I can see that would use this
path. They are A_OUT_GCC_EXEC_PREFIX and COFF_GCC_EXEC_PREFIX. You don't
have any of those in use, do you?
John
% Received: by us2rmc.bb.dec.com; id AA03658; Mon, 3 Jan 94 16:11:49 -0500
from localhost by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA01352; Mon, 3 Jan 1994 16:14:19 -050
% Message-Id: <9401032114.AA01352@flambe.zk3.dec.com>
% To: naresh@zk3.dec.com
% Cc: buildhelp@zk3.dec.com, darrell@zk3.dec.com, johnf@zk3.dec.com
% Subject: Re: fwd: Unable to build goldos.2wk
% In-Reply-To: Your message of "Mon, 03 Jan 94 16:05:53 EST." <9401032105.AA06476@longbow.zk3.dec.com>
% Date: Mon, 03 Jan 94 16:14:19 -0500
% From: John Flanagan <johnf@zk3.dec.com>
% X-Mts: smtp
|
| 497.2 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 12:34 | 134 |
| Date Of Receipt: 3-JAN-1994 16:23:10.78
From: US2RMC::"naresh@zk3.dec.com" "Naresh Dharnidharka USG"
To: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com
CC: buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
I did notice that A_OUT_GCC_EXEC_PREFIX and COFF_GCC_EXEC_PREFIX use
the gcc directory but I haven't modified any of the Makefiles to use
this path. I don't have a problem building against bl7. In any case,
I'll include the output of sbinfo in this message.
Thanks for looking into this.
#Naresh
Description of rc_file for tlaser sandbox:
The following environment variables were set:
host_machine=alpha
host_os_type=OSF1
BCSDIRECTORY=/usr/sde/ode2.0
BCSPORT=548
PATH=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/hostbin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/bin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/hostbin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/bin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc:/usr/sde/ode2.0/tools/alpha_ace/bin:/usr/ucb:/bin:/usr/bin:/sbin:/usr/sbin
BCSHEADERS=/usr/sde/alpha/headers
target_os_type=osf1
machine=alpha
TARGET_MACHINE=ALPHA
target_machine=alpha
NEW=GOLDOS;AGOSMINOR_BL7;AGOSMAINT_BL6;alpha_bl012;<>
LATEST=ALPHA;<99/12/31,23:59:59
PROJECT_NAME=ALPHA
project_name=alpha
SITE=OSF
OWNER=bin
GROUP=bin
MAKEFILEPATH=${MAKETOP}/usr/lib/makefiles
BACKED_SOURCEDIR=/usr/naresh/sandboxes/tlaser/src:/usr/sde/osf1/build/goldos.2wk/src
SOURCEDIR=/usr/sde/osf1/build/goldos.2wk/src
BACKED_PATH=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/hostbin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/bin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc:/usr/sde/ode2.0/tools/alpha_ace/bin:/usr/ucb:/bin:/usr/bin:/sbin:/usr/sbin
EXPORTBASE=/usr/naresh/sandboxes/tlaser/export/alpha
INCDIRS=-I/usr/naresh/sandboxes/tlaser/export/alpha/usr/include -I/usr/sde/osf1/build/goldos.2wk/export/alpha/usr/include
SHLIBDIRS=-L/usr/naresh/sandboxes/tlaser/export/alpha/usr/shlib -L/usr/sde/osf1/build/goldos.2wk/export/alpha/usr/shlib
MIGCOM=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/hostbin/migcom
LEXER=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/lib/ncform
YACCPAR=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/lib/yaccpar
ULT_INCDIRS=-I/usr/include
ULT_LIBDIRS=-L/usr/lib -L/lib
C_COMPILER=cc
COMP_HOST_ROOT=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc
COMP_TARGET_ROOT=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc
LIBDIRS=-L/usr/naresh/sandboxes/tlaser/export/alpha/usr/ccs/lib -L/usr/sde/osf1/build/goldos.2wk/export/alpha/usr/ccs/lib
OBJECT_FORMAT=COFF
COFF_GCC_EXEC_PREFIX=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/gcc/
submit_defect_check=true
SUBMIT_REVIEW=/usr/sde/osf1/submit_review
SOURCEBASE=/usr/naresh/sandboxes/tlaser/src
BSUBMIT_CONFIG_MAIL=jmf@wasted.zk3.dec.com,zap@wasted.zk3.dec.com,johnf@krisis.zk3.dec.com
TARGET_OS_TYPE=OSF1
CC_SUITE=ACC
cc_suite=acc
MACHO_GCC_EXEC_PREFIX=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/macho/
A_OUT_GCC_EXEC_PREFIX=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/gcc/
COFF_ACC_EXEC_PREFIX=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc/
COFF_MCC_EXEC_PREFIX=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/mcc/
TARGET_EXEC_PREFIX=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/hostbin/
COMP_HOST_ROOT_M64=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/mcc/
COMP_TARGET_ROOT_M64=/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/mcc/
RELEASE_OPTIONS=-idfile `genloc /src/setup/osf1_idlist`
OBJECTDIR=../obj/alpha
The following environment variables were removed:
The following directives are defined in the rc file:
rcs_host: buffer.zk3.dec.com
submit_host: buffer.zk3.dec.com
copyright_list: DEC_COPYRIGHT;DEC_COPYRIGHT_MIN;DEC_COPYRIGHT_MAX;DEC_COPYRIGHT_FSF
build_base: /usr/sde/osf1/build
sandbox_base: /usr/naresh/sandboxes/tlaser
tools_base: /usr/naresh/sandboxes/tlaser/tools/alpha
ode_base: /usr/sde/ode2.0/tools/alpha_ace
ode_path: /usr/sde/ode2.0/tools/alpha_ace/bin
src_control_init: /usr/sde/ode2.0/tools/alpha_ace/bin/bco
rcs_base: /usr/sde/osf1/rcs/os/src
rcs_cover: /usr/sde/ode2.0/tools/alpha_OSF1/lib/rcsauth
source_cover: /usr/sde/ode2.0/tools/alpha_OSF1/lib/srcauth
rcs_owner: devrcs
default_build: goldos
default_set: GOLDOS
submit_base: /usr/sde/osf1/build/goldos/logs
submit_cover: /usr/sde/ode2.0/tools/alpha_OSF1/lib/subauth
submit_owner: devbld
submit_defect: true
build_list: /usr/sde/build_list
check_out_config: GOLDOS_2WK;GOLDOS_ALT;AGOSMINOR_BL7;AGOSMAINT_BL6;alpha_bl012;<93/01/24,16:21:32
build_makeflags: -cF
source_base: /usr/naresh/sandboxes/tlaser/src
object_base: /usr/naresh/sandboxes/tlaser/obj/alpha
export_base: /usr/naresh/sandboxes/tlaser/export/alpha
release_base: /usr/naresh/sandboxes/tlaser/export/alpha
release_cover: /bin/echo
release_owner: root
release_lock: /usr/naresh/sandboxes/tlaser/export/alpha/release_lock
stage:
alpha alpha norm
default default norm
system_path: /usr/ucb:/bin:/usr/bin:/sbin:/usr/sbin
tools_path: /usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/hostbin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/bin:/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc
>
>
>Naresh,
>
>The problem is this line:
>
>sh: /usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/gcc/cc
>
>There is no gcc directory under alpha. Do you have any variables set in your
>.cshrc or .login that would pass in this variable? In your workon, if you
>could type "sbinfo" and forward the output of that along to us that would
>help. There are a couple of variables that I can see that would use this
>path. They are A_OUT_GCC_EXEC_PREFIX and COFF_GCC_EXEC_PREFIX. You don't
>have any of those in use, do you?
>
>John
>
% Received: by us2rmc.bb.dec.com; id AA04079; Mon, 3 Jan 94 16:20:35 -0500
from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA01600; Mon, 3 Jan 1994 16:21:49 -050
by wasted.zk3.dec.com; id AA12128; Mon, 3 Jan 1994 16:21:49 -0500
% Date: Mon, 3 Jan 1994 16:21:49 -0500
% From: Naresh Dharnidharka USG <naresh@zk3.dec.com>
% Message-Id: <9401032121.AA12128@wasted.zk3.dec.com>
% To: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com
% Subject: Re: fwd: Unable to build goldos.2wk
% Cc: buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
|
| 497.3 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 12:36 | 43 |
| Date Of Receipt: 3-JAN-1994 16:23:19.69
From: US2RMC::"vandyck@cardinal.zk3.dec.com" "Grant Van Dyck"
To: naresh@cardinal.zk3.dec.com
CC: johnf@cardinal.zk3.dec.com, buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
It would appear that you have the environment variable 'cc_suite' set to
gcc. This would happen if you have a custom file in your sandbox/rc_files
to override the default of:
replace setenv cc_suite acc
Can you do an "sbinfo cc_suite"
-Grant
|
| Naresh,
|
| The problem is this line:
|
| sh: /usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/gcc/cc
|
| There is no gcc directory under alpha. Do you have any variables set in your
| .cshrc or .login that would pass in this variable? In your workon, if you
| could type "sbinfo" and forward the output of that along to us that would
| help. There are a couple of variables that I can see that would use this
| path. They are A_OUT_GCC_EXEC_PREFIX and COFF_GCC_EXEC_PREFIX. You don't
| have any of those in use, do you?
|
| John
% Received: by us2rmc.bb.dec.com; id AA04084; Mon, 3 Jan 94 16:20:39 -0500
from cardinal.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA01637; Mon, 3 Jan 1994 16:22:00 -050
from localhost by cardinal.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA22430; Mon, 3 Jan 1994 16:21:59 -050
% Message-Id: <9401032121.AA22430@cardinal.zk3.dec.com>
% To: naresh@cardinal.zk3.dec.com
% Cc: johnf@cardinal.zk3.dec.com, buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.co
% Subject: Re: fwd: Unable to build goldos.2wk
% In-Reply-To: Your message of "Mon, 03 Jan 94 16:14:19 EST." <9401032114.AA01352@flambe.zk3.dec.com>
% Date: Mon, 03 Jan 94 16:21:59 -0500
% From: Grant Van Dyck <vandyck@cardinal.zk3.dec.com>
% X-Mts: smtp
|
| 497.4 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 18:50 | 26 |
| Date Of Receipt: 3-JAN-1994 16:37:51.78
From: US2RMC::"johnf@zk3.dec.com" "John Flanagan"
To: Naresh Dharnidharka USG <naresh@zk3.dec.com>
CC: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com, buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com, johnf@zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
Naresh,
Can you send me the command sequences you were using to build out
of your sandbox...
i.e. cd kernel/whatever
build...
John
% Received: by us2rmc.bb.dec.com; id AA04527; Mon, 3 Jan 94 16:35:17 -0500
from localhost by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA02338; Mon, 3 Jan 1994 16:37:48 -050
% Message-Id: <9401032137.AA02338@flambe.zk3.dec.com>
% To: Naresh Dharnidharka USG <naresh@zk3.dec.com>
% Cc: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com, buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com, johnf@zk3.dec.c
% Subject: Re: fwd: Unable to build goldos.2wk
% In-Reply-To: Your message of "Mon, 03 Jan 94 16:21:49 EST." <9401032121.AA12128@wasted.zk3.dec.com>
% Date: Mon, 03 Jan 94 16:37:47 -0500
% From: John Flanagan <johnf@zk3.dec.com>
% X-Mts: smtp
|
| 497.5 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 18:51 | 38 |
| Date Of Receipt: 3-JAN-1994 16:43:13.82
From: US2RMC::"naresh@zk3.dec.com" "Naresh Dharnidharka USG"
To: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com
CC: buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
The command sequence I used was as follows:
% workon -sb tlaser
% build all
(Due to an error in one of my C files the BINARY build failed, I fixed the
C file and then)
% build BINARY_vmunix
% build SAS_vmunix ( or any of the other kernels and it always fails)
Hope this helps
Thanks
#Naresh
>
>Naresh,
>
>Can you send me the command sequences you were using to build out
>of your sandbox...
>
>i.e. cd kernel/whatever
> build...
>
>John
>
% Received: by us2rmc.bb.dec.com; id AA04654; Mon, 3 Jan 94 16:40:33 -0500
from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA02452; Mon, 3 Jan 1994 16:43:05 -050
by wasted.zk3.dec.com; id AA13671; Mon, 3 Jan 1994 16:43:05 -0500
% Date: Mon, 3 Jan 1994 16:43:05 -0500
% From: Naresh Dharnidharka USG <naresh@zk3.dec.com>
% Message-Id: <9401032143.AA13671@wasted.zk3.dec.com>
% To: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com
% Subject: Re: fwd: Unable to build goldos.2wk
% Cc: buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
|
| 497.6 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 18:51 | 20 |
| Date Of Receipt: 3-JAN-1994 16:46:39.29
From: US2RMC::"naresh@zk3.dec.com" "Naresh Dharnidharka USG"
To: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com
CC: buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
One more thing, I am using "bash" as my shell. I'm not sure if it
matters.
#Naresh
% Received: by us2rmc.bb.dec.com; id AA04741; Mon, 3 Jan 94 16:44:04 -0500
from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA02511; Mon, 3 Jan 1994 16:46:35 -050
by wasted.zk3.dec.com; id AA13931; Mon, 3 Jan 1994 16:46:35 -0500
% Date: Mon, 3 Jan 1994 16:46:35 -0500
% From: Naresh Dharnidharka USG <naresh@zk3.dec.com>
% Message-Id: <9401032146.AA13931@wasted.zk3.dec.com>
% To: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com
% Subject: Re: fwd: Unable to build goldos.2wk
% Cc: buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com
|
| 497.7 | Re: fwd: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 18:52 | 25 |
| Date Of Receipt: 3-JAN-1994 17:01:59.15
From: US2RMC::"johnf@zk3.dec.com" "John Flanagan"
To: Naresh Dharnidharka USG <naresh@zk3.dec.com>
CC: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com, buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com, johnf@zk3.dec.com
Subj: Re: fwd: Unable to build goldos.2wk
Naresh,
I can't find anything that is giving you the gcc path. I don't know anything
about the "bash" shell so I can't offer any help there.
Anyone else on buildhelp have any advice?
John
% Received: by us2rmc.bb.dec.com; id AA05259; Mon, 3 Jan 94 16:59:25 -0500
from localhost by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA02926; Mon, 3 Jan 1994 17:01:56 -050
% Message-Id: <9401032201.AA02926@flambe.zk3.dec.com>
% To: Naresh Dharnidharka USG <naresh@zk3.dec.com>
% Cc: johnf@flambe.zk3.dec.com, naresh@flambe.zk3.dec.com, buildhelp@flambe.zk3.dec.com, darrell@flambe.zk3.dec.com, johnf@zk3.dec.c
% Subject: Re: fwd: Unable to build goldos.2wk
% In-Reply-To: Your message of "Mon, 03 Jan 94 16:43:05 EST." <9401032143.AA13671@wasted.zk3.dec.com>
% Date: Mon, 03 Jan 94 17:01:56 -0500
% From: John Flanagan <johnf@zk3.dec.com>
% X-Mts: smtp
|
| 497.8 | Re: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 18:52 | 16 |
| Date Of Receipt: 4-JAN-1994 00:23:11.31
From: FLUME::jmcg "Jim McGinness"
To: flume::naresh
CC: flume::buildhelp
Subj: Re: Unable to build goldos.2wk
I logged on to taichi an did a "workon -rc ~naresh/.sandboxrc -sb tlaser"
(as myself, with /bin/csh as the shell) and found that cc_suite was picked
up properly as "acc". It used to be that cc_suite was set to "gcc" in
some alpha.bl012 file, either rc_files/shared or
src/usr/lib/makefiles/standard.mk I think, but that dependency chain doesn't
appear in this sandbox.
I'm stumped, but suggest that you could probably make progress if you
could stomach using one of the unrepentent shells to do your build.
|
| 497.9 | Re: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 18:53 | 22 |
| Date Of Receipt: 4-JAN-1994 02:07:09.27
From: FLUME::jmcg "Jim McGinness"
To: flume::naresh
CC: flume::buildhelp
Subj: Re: Unable to build goldos.2wk
Second thoughts...ignore that last message.
After your BINARY build failed during a "build all", you tried to
do "build xxxxxx_vmunix" on all the trials afterwards. This may be
the cause of your problem: there may be some setup steps done by the
"build all" in each of the specific kernel directories that weren't
done when your "build all" failed. It looks like you've already blown
away the object tree in this sandbox, so your next "build all" ought
to correct the problem.
I still can't figure out why something was trying to use a gcc tool,
though. It's not on the PATH, the cc_suite variable is set to "acc"
in both the ODE context and in the template.mk, ....
-- jmcg
|
| 497.10 | Re: Unable to build goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 19:05 | 16 |
| Date Of Receipt: 5-JAN-1994 08:52:00.94
From: WASTED::naresh "Naresh Dharnidharka USG"
To: jmcg@flume.zk3.dec.com, naresh@zk3.dec.com
CC: buildhelp@zk3.dec.com
Subj: Re: Unable to build goldos.2wk
I blew away the obj tree in the tlaser sandbox as I needed the disk
space for a new sandbox tlaser1. I did not have any problems building
the kernel in this sandbox.
Thanks for looking into this problem. It was definitly something I screwed
up but as things seem to be working in the new sandbox I'll ignore
the old one.
Thanks
#Naresh
|
| 497.11 | goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Mar 10 1994 13:11 | 17 |
| Date Of Receipt: 10-MAR-1994 09:33:08.08
From: WASTED::haeck "Debby Haeck"
To: buildhelp@wasted:zko.dec
CC: haeck@wasted:zko.dec
Subj: goldos.2wk
Hi
I thought goldos.2wk was a stable tree? Yesterday I was backed by goldos.bl8.
I did an "rm -rf obj/*" and then "resb -verbose goldos.2wk" and then a
"build" from src/kernel. The build had errors while while compiling in
BINARY.
Where did I go wrong?
Debby
|
| 497.12 | Re: goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Mar 10 1994 13:12 | 8 |
| Date Of Receipt: 10-MAR-1994 09:35:50.61
From: ALPHA::bstevens "Brian Stevens 10-Mar-1994 0935"
To: Debby Haeck <haeck@DEC:.zko.alpha>
CC: buildhelp@DEC:.zko.alpha
Subj: Re: goldos.2wk
did you have anything in src/kernel?
|
| 497.13 | Re: goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Mar 10 1994 13:13 | 22 |
| Date Of Receipt: 10-MAR-1994 09:46:08.46
From: WASTED::"haeck@solvit.mko.dec.D5NET.dec.com"
To: WASTED::bstevens
CC: WASTED::BUILDHELP, HAECK@wasted:zko.dec
Subj: Re: goldos.2wk
Yes I did:
./conf/alpha/ALFFA1
./conf/alpha/BINARY
./conf/alpha/files
./conf/alpha/ALFFA1.list
./io/dec/vme/vba_generic.c
./io/dec/vme/vba_tc.c
./io/dec/vme/vbareg.h
./io/dec/vme/vba_generic.h
./io/dec/vme/Makefile
./io/dec/Makefile
./data/Makefile
./data/vba_data.c
./include/io/dec/Makefile
./include/io/dec/vme/Makefile
|
| 497.14 | Re: goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Mar 10 1994 13:13 | 14 |
| Date Of Receipt: 10-MAR-1994 09:58:09.59
From: WASTED::"bstevens@alpha.zko.dec.D5NET.dec.com"
To: haeck@dec:.mko.solvit (Debby Haeck)
CC: WASTED::BUILDHELP
Subj: Re: goldos.2wk
This is most likely your problem. If these files were based on an older
backing tree, you need to 'merge them up' when the backing tree is updated.
Some of them will most likely haven't been changed in the backing tree, but
for files like conf/alpha/files, there might have been several changes that
could break you build.
Brian
|
| 497.15 | goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Fri Apr 01 1994 03:49 | 40 |
| Date Of Receipt: 31-MAR-1994 23:25:51.26
From: WASTED::haeck "Debby Haeck"
To: buildhelp@wasted:zko.dec
CC: haeck@wasted:zko.dec
Subj: goldos.2wk
Hi
I am trying to build a kernel in the following sandbox:
sandbox: generic_vme
set: Debra_Haeck_generic_vme
base directory: /home/haeck/sand
default set directory: .
sandbox rc file: /home/haeck/sand/generic_vme/rc_files/local
backing tree of sandbox: /tmp_mnt/lastin/share/lastin/build/goldos.dsk4/goldos.2wk
I am getting an error on the ld phase as follows:
.
.
.
/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc/cc -I -I. -I.. -I../include -DIDENT=FLAMINGO -DDEC3000_500 -DSWAPTYPE=1 -DMACH -DOSF -DCOMPAT_43 -DUFS -DTRN -DKERNEL -D_KERNEL -D_BSD -c vers.c
rm -f vmunix vmunix.sys
loading vmunix.sys
/usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc/ld:
Error: Undefined:
lw_init
*** Exit 1
Stop.
*** Exit 1
Stop.
An nm of the .o files in obj/alpha/kernel/FLAMINGO shows that lw_init is in
pmap_init.o, which is, I think, a standard file.
So..... What am I doing wrong?
Debby
|
| 497.16 | Re: goldos.2wk | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Mon Apr 04 1994 19:34 | 65 |
| Date Of Receipt: 1-APR-1994 10:26:43.07
From: FLUME::"vandyck@zk3.dec.com" "Grant Van Dyck"
To: Debby Haeck <haeck@zk3.dec.com>
CC: buildhelp@zk3.dec.com
Subj: Re: goldos.2wk
What steps did you take for this build?
clean sandbox?
mklinks?
build what???
lw_init is in:
cardinal ~ [34] comet lw_init
/usr/sde/osf1/build/goldos/./src/kernel/arch/alpha/pmap_lw.h
/usr/sde/osf1/build/goldos/./src/kernel/arch/alpha/pmap_init.c
Did you build both of these? setup phase for the .h and a pmap_init.o
in BINARY?
Any old junk or .o files in your sandbox?
-Grant
| Hi
|
| I am trying to build a kernel in the following sandbox:
|
| sandbox: generic_vme
| set: Debra_Haeck_generic_vme
| base directory: /home/haeck/sand
| default set directory: .
| sandbox rc file: /home/haeck/sand/generic_vme/rc_files/local
| backing tree of sandbox: /tmp_mnt/lastin/share/lastin/build/goldos.dsk4/goldo
s.2wk
|
|
| I am getting an error on the ld phase as follows:
| .
| .
| .
| /usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc/cc -I -I. -I.. -I..
/include -DIDENT=FLAMINGO -DDEC3000_500 -DSWAPTYPE=1 -DMACH -DOSF -DCOMPAT_43 -
DUFS -DTRN -DKERNEL -D_KERNEL -D_BSD -c vers.c
| rm -f vmunix vmunix.sys
| loading vmunix.sys
| /usr/sde/osf1/build/goldos.2wk/tools/alpha_OSF1/alpha/acc/ld:
| Error: Undefined:
| lw_init
| *** Exit 1
| Stop.
| *** Exit 1
| Stop.
|
| An nm of the .o files in obj/alpha/kernel/FLAMINGO shows that lw_init is in
| pmap_init.o, which is, I think, a standard file.
|
| So..... What am I doing wrong?
|
| Debby
|
|
| 497.17 | unable to build | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Fri Aug 18 1995 00:55 | 45 |
| Date Of Receipt: 17-AUG-1995 20:06:22.59
From: SMURF::GURU::arvidson "Bill Arvidson USEG 17-Aug-1995 2005"
To: odehelp@dec:.zko.guru
CC: arvidson@dec:.zko.guru
Subj: unable to build
Hello ,
I can build v32 kernels in v32 sandboxes.
I can build v3.0 kernels with my CUTTER config file in any v30 sandbox.
I can not build v3.0 kernels with my SMPFIX config file.
It worked before I went on vacation two weeks ago.
Same error:
PAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL -D_BSD -signed -no_excpt
-Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha -Umips -UMIPS -O2
../io/cam/sim_config.c
/usr/sde/osf1/build/v30supportos.nightly/tools/alpha_OSF1/alpha/acc/cc -c -O2
-DLANGUAGE_C -g3 -G 4 -I -I. -I.. -I../include -DIDENT=SMPFIX -DDEC2100_A500
-DSWAPTYPE=1 -DUERF -DOSF -DCOMPAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL
-D_BSD -signed -no_excpt -Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha -Umips
-UMIPS ../data/cbus2_data.c
/usr/sde/osf1/build/v30supportos.nightly/tools/alpha_OSF1/alpha/acc/cc -c -O2
-DLANGUAGE_C -g3 -G 4 -I -I. -I.. -I../include -DIDENT=SMPFIX -DDEC2100_A500
-DSWAPTYPE=1 -DUERF -DOSF -DCOMPAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL
-D_BSD -signed -no_excpt -Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha -Umips
-UMIPS ../data/cam_data.c
libmld: Error: cannot write cur table
*** Exit 1
Stop.
*** Exit 1
Stop.
Bill
*********************************************************************
Bill Arvidson
OSSE (Operating System Support Engineering) Phone: (603) 881-1630
Enet: guru::arvidson DTN: 381-1630
Internet: arvidson@zk3.dec.com Mailstop: ZK03-2/T43
*********************************************************************
|
| 497.18 | unable to build | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Fri Aug 18 1995 00:56 | 67 |
| Date Of Receipt: 17-AUG-1995 20:27:21.02
From: SMURF::GURU::arvidson "Bill Arvidson USEG 17-Aug-1995 2026"
To: odehelp@dec:.zko.guru
CC: arvidson@dec:.zko.guru
Subj: unable to build
I emptied my v30 obj tree and retried the CUTTER config file.
It now dies.
Bill
------- Forwarded Message
Return-Path: arvidson
Message-Id: <9508180005.AA31546@guru.zk3.dec.com>
To: odehelp
Cc: arvidson
Subject: unable to build
Date: Thu, 17 Aug 95 20:05:09 -0400
From: arvidson
X-Mts: smtp
Hello ,
I can build v32 kernels in v32 sandboxes.
I can build v3.0 kernels with my CUTTER config file in any v30 sandbox.
I can not build v3.0 kernels with my SMPFIX config file.
It worked before I went on vacation two weeks ago.
Same error:
PAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL -D_BSD -signed -no_excpt
- -Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha -Umips -UMIPS -O2
../io/cam/sim_config.c
/usr/sde/osf1/build/v30supportos.nightly/tools/alpha_OSF1/alpha/acc/cc -c -O2
- -DLANGUAGE_C -g3 -G 4 -I -I. -I.. -I../include -DIDENT=SMPFIX -DDEC2100_A500
- -DSWAPTYPE=1 -DUERF -DOSF -DCOMPAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL
- -D_BSD -signed -no_excpt -Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha
-Umips
- -UMIPS ../data/cbus2_data.c
/usr/sde/osf1/build/v30supportos.nightly/tools/alpha_OSF1/alpha/acc/cc -c -O2
- -DLANGUAGE_C -g3 -G 4 -I -I. -I.. -I../include -DIDENT=SMPFIX -DDEC2100_A500
- -DSWAPTYPE=1 -DUERF -DOSF -DCOMPAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL
- -D_BSD -signed -no_excpt -Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha
-Umips
- -UMIPS ../data/cam_data.c
libmld: Error: cannot write cur table
*** Exit 1
Stop.
*** Exit 1
Stop.
Bill
*********************************************************************
Bill Arvidson
OSSE (Operating System Support Engineering) Phone: (603) 881-1630
Enet: guru::arvidson DTN: 381-1630
Internet: arvidson@zk3.dec.com Mailstop: ZK03-2/T43
*********************************************************************
------- End of Forwarded Message
|