Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!shelby!agate!usenet.ins.cwru.edu!odin!chet
From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Newsgroups: comp.sys.next
Subject: Re: Library function redefinition
Message-ID: <1991Mar3.232546.3547@usenet.ins.cwru.edu>
Date: 3 Mar 91 23:25:46 GMT
References: <1991Feb28.190319.22658@usenet.ins.cwru.edu> <1991Mar1.143756.12400@usenet.ins.cwru.edu> <1383@toaster.SFSU.EDU>
Sender: news@usenet.ins.cwru.edu
Reply-To: chet@po.CWRU.Edu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 33
Nntp-Posting-Host: odin.ins.cwru.edu

I wrote:
>>It seems that the NeXT/Mach ld simply maps the library into my process's
>>address space, and damn any symbols that I already defined.

And Eric Scott replied:
>Aww, poor baby.  Betcha don't use System V or SunOS 4.1+ either.

Think before you answer next time.  Sun (and AT&T) chose not to break
traditional Unix semantics -- Bash builds just fine on my Sparcs running
both SunOS 4.1 and 4.1.1 without using -Bstatic.  I haven't heard any
complaints from people testing it out on System V release 4, and the two
systems have very similar shared library implementations (built atop
`mmap').

This version of Bash runs on a number of System V.3 systems, with the
original System V shared library implementation, and has no trouble
compiling there either.

>>What I would like is a switch to cc or ld that restores the traditional
>>behavior, even in the presence of shared libraries.  If it can't be done,
>>that's OK, too.
>
>-Dgetenv=my_incompatible_replacement_for_getenv

OK, it can't be done.  Thank you.

Chet
-- 
Chet Ramey				``Now, somehow we've brought our sins
Network Services Group			  back physically -- and they're
Case Western Reserve University		  pissed.''
chet@ins.CWRU.Edu		My opinions are just those, and mine alone.