[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
1359.0. "Re: do you know why is ld barfing on the -O2 option" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Mar 23 1995 17:06
Date Of Receipt: 23-MAR-1995 16:26:43.96
From: SMURF::FLUME::jmcg "Jim McGinness"
To: [email protected]
CC: buildhelp@DEC:.zko.flume
Subj: Re: do you know why is ld barfing on the -O2 option
We just had a conversation about this error on the buildhelp list a few
weeks ago. The construct
`genloc /obj/alpha/usr/shlib/alpha/so_locations`
is not returning a string, probably because the backing tree does
not have the obj tree supped. The -O2 that follows it is being
eaten as a file name...which yields the error message you see.
One way to get around this is to build the so_locations file first:
mkdir -p usr/shlib/alpha
cd usr/shlib/alpha
build
This is one of those extra-ordinary dependencies which our Makefiles
don't try to record.
For purposes of testing the shared object on your own workstation, you could
just as well create a symlink:
ln -s /usr/shlib/so_locations ../obj/alpha/usr/shlib/alpha/so_locations
[All relative pathnames here are relative to the src directory in your
sandbox, the default place a workon takes you.]
-- jmcg
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|