| Date Of Receipt: 13-MAY-1993 16:28:09.78
From: WASTED::"mad@zk3.dec.com" "Madeline Barcia-Asmus AOSG"
To: 32.594::wolfe
CC: odehelp@zk3.dec.com, whatgem@zk3.dec.com
Subj: Re: problems building notepad in ode environment
>>
>>
>>Hello buildhelp,
>>
>>I am trying to build notepad for agxmaint. I have a sandbox, did a mklinks,
>>copied down a few changed .c files that I want to build with and did
>>a make (since Motif stuff uses the Makefiles). I immediately get an
>>error message:
>>
>>Aleta> make
>>Make: Don't know how to make /usr/sde/osf1/build/agxmaint.bld/tools/alpha_osf1/c
>>c/usr/include/sys/param.h. Stop.
>>
>>The problem seems to be agxmaint.bld. That is not a valid directory. I am
>>backed against agxmaint.nightly (vs. agxmaint) because, for reasons
>>that I do not understand, agxmaint does not have the X11 directory and there
fore
>>none of the required H files.
>>
>>
>>Here is the output from currentsb:
>> Aleta> currentsb -all
>>ootb Peter_Wolfe_ootb /usr/users/wolfe/sandboxes . /usr/users/wolfe/sandboxes/oo
>>tb/rc_files/local /usr/sde/disks/darla_ra114c/agxmaint.nightly
>>
>>
>>Please help,
>>
>> pete
>>
>>
agxmaint , is a submit tree, which by definition of submit tree we do
not "build" in it.
X11 is a result of a build.
As for the reference to agxmaint.bld, this is a known feature. The build occurs in
a place called agxmaint.bld and then the results get populated into
agxmaint.nightly.
As a result, the path is explicitly expanded in the imake files to
/usr/sde/osf1/build/agxmaint.bld/....
so the solution 'X' folks have used thus far is the following :
mkdir /usr/build/osf1/
in there make a link
ln -s agxmaint.bld --> where you find the agxmaint.nightly is mounted
on your machine .
-Madeline
|
| Date Of Receipt: 13-FEB-1995 19:53:37.55
From: SMURF::ALPHA::shashi "Shashi Mangalat USG"
To: jones@zso.dec.com
CC: buildhelp@DEC:.zko.alpha
Subj: Re: nm
>Do you
>guys know an easy way to do this? The only way I know of is to run nm
>against every .o using find, collect the output in a file, and search the
>file for the symbol then page up or down to identify the file.
I don't know of a better way, but this might help a little. There is
new option '-A' to nm which prepends the file name to each symbol.
So you could nm all .o's and pipe it through grep.
--shashi
|