Conference smurf::buildhelp

Date Of Receipt: 	17-MAY-1994 13:55:37.69
From: 	FLUME::jmcg "Jim McGinness"
To: 	flume::lsw
CC: 	flume::buildhelp
Subj: 	Re:  Linking with start-up code modules other than crt0.o

Please check with Ken Lesniak about making the extra *crt0.o
modules available.  They're not in the tools subtree currently,
because he no longer puts them in the compiler kit.  The reasons
for not doing this may affect you.

standard.mk currently has a variable _ansi_LDFLAGS which insists
on using a bare crt0.o module.  Until someone changes this, you
will need to override this variable, in addition to supplying
CC_OPT_LEVEL.

Copying to "buildhelp", since this is not really an "odehelp"
problem.

	-- jmcg
===========================================================================
From lsw Tue May 17 13:41:53 1994
To: odehelp
Cc: lsw
Subject: Linking with start-up code modules other than crt0.o
Date: Tue, 17 May 94 13:41:01 -0400
From: lsw

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

Date Of Receipt: 	17-MAY-1994 14:22:54.32
From: 	QUARRY::lsw "Linda Sue Wilson USG  17-May-1994 1422"
To: 	[email protected] (Jim McGinness)
CC: 	[email protected], [email protected]
Subj: 	Re: Linking with start-up code modules other than crt0.o

Jim -
Thanks for the quick response.  I've checked with Ken & we've
agreed the profiling start-up code doesn't belong in the tools
area.  Having the start-up code & profiling libs available in 
the export area will be enough to meet the needs of internal
developers.  Once the forced-crt0 link issue is resolved, we'll
be all set.

Linda