[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

2484.0. "Small Event Sink becomes big executable" by TAEC::WEBER () Wed Mar 04 1992 13:22

    How can we avoid that a "simple" event sink, whose object file
    is 50 Ko to become a 1Mo executable when linked with the mcc
    libraries ?
    Is there a possibility to sort out the required libraries,
    link only to those without taking the risk of falling in a black hole
    due to undefined symbols ?
    Thanks to answer
    Florence

T.R Title User Personal
Name Date Lines

2484.1 TOOK::MINTZ Erik Mintz, DECmcc Development, dtn 226-5033 Wed Mar 04 1992 13:43 9

T.R	Title	User	Personal Name	Date	Lines
2484.1		TOOK::MINTZ	Erik Mintz, DECmcc Development, dtn 226-5033	`Wed Mar 04 1992 13:43`	9
	If the code is ending up in your executable, then there must be interdependencies in the library routines pulling them all in. Presumably your event sink is calling DECmcc kernel functions. If that is the case, then much of the overhead is necessary (threads routines, DNS conversion routines, etc). -- Erik

If the code is ending up in your executable, then there must be
interdependencies in the library routines pulling them all in.
Presumably your event sink is calling DECmcc kernel functions.
If that is the case, then much of the overhead is necessary
(threads routines, DNS conversion routines, etc).

-- Erik