httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@engelschall.com (Ralf S. Engelschall)
Subject Re: [PATCH] Hide symbols to avoid namespace conflicts (take 2)
Date Wed, 04 Mar 1998 07:04:16 GMT

In article <Pine.LNX.3.96dg4.980303113534.11757B-100000@twinlark.arctic.org> you wrote:
> On Tue, 3 Mar 1998, Ralf S. Engelschall wrote:

>> Hmmm... I don't know what 'start' actually is. Seems it is together with 'end'
>> one of the standard compiler symbols, because I found them under Solaris, too.
>> I've added it to the exclusion list. BUT, nevertheless it doesn't make
>> problems or hurts something. Because as long as we do not use this symbol in
>> our sources it doesn' hurt is.

> A (unix) executable is linked so that:
> start
>     all your text sections fit here (code)
> etext
>     all your data sections fit here (statically initialized data)
> edata
>     all your bss sections fit here (uninitialized data -- zero filled data)
> end
>[...]

Fine, we already exclude these in the helpers/UpdateHide script.
Thanks for making clear what they actually are.

>[...]
> One way around all of this is to use nm on each of our .o and .a files,
> then you're guaranteed to get only stuff we define rather than stuff
> which is put into the executable.

Hmmmm... good idea, yes. But this makes the "updatehide" Target really complex
because in the src/Makefile.tmpl we have to complete list of object files. I
think we should keep the current approach where we "nm httpd" unless we get
really bitten by it.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message