| 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 |
Date Of Receipt: 30-AUG-1994 17:39:26.70
From: FLAMBE::"[email protected]" "30-Aug-1994 1737"
To: [email protected]
CC:
Subj: Doing KERNEL test builds
I have worked with the ODE toolset for non-kernel work for a while now, but
this week I am in crunch mode to fix a piece of code in the kernel. I have gotten
a lot of help from Mark Warren with the basics, but I am at the point where builds
are taking forever and repeating steps that I don't really need repeated.
The only way I know so far for building the test kernel is to go to the src/kernel
directory in my sandbox and type "build"... this works, but it always reruns the
dependency generation ("make depends" and co.). I am only changing one .c
file, so it sure would be nice to avoid all this extra activity.
I am also running out of disk space in /var/tmp during the dependency build
process. This time around, it was:
awk 'BEGIN { DOL=36; printf("flint:\t%c{LINTFILES}\n", DOL);
printf("\t@%c{ECHO} \"%c{LINT} %c{LINTFLAGS} *.ln > linterrs 2>&1\"\n",
DOL, DOL, D
OL); printf("\t@%c{LINT} %c{LINTFLAGS} %c{LINTOBJS} %c{LINTOBJS1} >
linterrs 2>&1\n", DOL, DOL, DOL, DOL); printf("\n") }' /dev/null >> makelint
awk '{ DOL=36; printf("%s.ln: %s\n", $2, $1); printf("\t-%c{LINT} -c
%c{LINTFLAGS} %s | \\\n", DOL, DOL, $1); printf("\t\t(%c{LINTFILTER} ; exi
t 0) > %s.lint 2>&1\n\n", DOL, $2) }' makelintfiles >> makelint
echo '/^# DO NOT DELETE THIS LINE/+1,$d' >eddep
echo '$r makelint' >>eddep;
echo '$r makedep' >>eddep
echo 'w' >>eddep
cp Makefile Makefile.bak
ex - Makefile < eddep
/var: write failed, file system is full
"/var/tmp/Ex05584" No space left on device
rm -f eddep makedep1 makedeperrs
[ performing kernel library operations ]
Kernel libraries are not used in alpha.
cd BINARY && make -cF
KCC=/usr/sde/osf1/build/v30supportos.nightly/tools/alpha_OSF1/alpha/acc/cc
LD=/usr/sde/osf1/build/v30supportos.nightly/too
Is there a way I can point the tools to use /tmp, which has loads of space? I have tried
setting the TEMP environment variable, but that does not seem to have fixed this one?
Finally, I am doing most of my testing with only the FLAMINGO kernel. Is there a
way to build only that single kernel?
Thanks for your help,
Marc
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 926.1 | Re: Doing KERNEL test builds | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Aug 30 1994 21:51 | 18 |
Date Of Receipt: 30-AUG-1994 20:35:29.87 From: FLAMBE::"[email protected]" To: [email protected], [email protected] CC: Subj: Re: Doing KERNEL test builds marc, what kind of system are you building on? how much system memory? what kind of disks and type of filesystems are you using? which operating system and rev are you running on the above hardware? the above info would be useful in suggesting performance tips. /sb | |||||
| 926.2 | Re: Doing KERNEL test builds | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Aug 30 1994 23:54 | 65 |
Date Of Receipt: 30-AUG-1994 22:42:15.63 From: FLUME::jmcg "Jim McGinness" To: [email protected] CC: buildhelp@DEC:.zko.flume, odehelp@DEC:.zko.flume Subj: Re: Doing KERNEL test builds 1. If your /var filesystem doesn't have much space, I suggest you simply replace /var/tmp with a link to /tmp. A number of things assume that /var/tmp has plenty of space vs /tmp which might be on a root file system. 2. The environment variable TMPDIR is the one you have to set to move where the compiler suite puts its temporary files. Other commands may respect this, too. 3. Set up your kernel area initially by saying "build" (which is equivalent to "build build_all"). It's possible to chop out some of the extra building that goes on, but it's a lot simpler to just say "build". Each time you change your backing tree, it's necessary to blow away your obj/alpha/kernel directory and redo the "build". 4. If all you are changing is one .c file, most of the time you can get a new kernel in under 5 minutes with the command: build FLAMINGO_vmunix MAKEARGS=xxxxx.o This will work as long as the file you have changed is not one of the ones that gets copied to the obj area. -- jmcg > To: [email protected] > Subject: Doing KERNEL test builds > Date: Tue, 30 Aug 94 17:37:20 -0400 > From: [email protected] > I have worked with the ODE toolset for non-kernel work for a while > now, but this week I am in crunch mode to fix a piece of code in > the kernel. I have gotten a lot of help from Mark Warren with the > basics, but I am at the point where builds are taking forever and > repeating steps that I don't really need repeated. > The only way I know so far for building the test kernel is to go > to the src/kernel directory in my sandbox and type "build"... > this works, but it always reruns the dependency generation ("make > depends" and co.). I am only changing one .c file, so it sure > would be nice to avoid all this extra activity. > I am also running out of disk space in /var/tmp during the > dependency build process. This time around, it was: > . > . > . > Is there a way I can point the tools to use /tmp, which has loads > of space? I have tried setting the TEMP environment variable, but > that does not seem to have fixed this one? > Finally, I am doing most of my testing with only the FLAMINGO > kernel. Is there a way to build only that single kernel? > Thanks for your help, Marc | |||||