[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 |
742.0. "Forwarding to buildhelp" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Thu May 26 1994 18:55
Date Of Receipt: 17-MAY-1994 13:46:54.54
From: FLUME::"[email protected]" "Grant Van Dyck"
To: [email protected]
CC: [email protected]
Subj: Forwarding to buildhelp
Subject: Linking with start-up code modules other than crt0.o
Requests are coming in from people who want to build programs
with -p and -pg in their sandboxes so they can be profiled.
Under normal conditions, these switches cause the program to
be linked with mcrt0.o or gcrt0.o.
The problem is that ODE overrides the name of the start-up
code module that would be linked with the program when the
- -p or -pg switches are used.
It forces programs to be linked with crt0.o all the time.
All I've tried so far is setting CC_OPT_LEVEL to -p or -pg &
doing a build of a utility.
Are there other environment variables I can use to work around
this?
BTW, the mcrt0.o and gcrt0.o modules aren't currently put in
the export area. I've made the necessary Makefile changes to
correct this.
Thanks for any info -
Linda
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|