Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!xlink.net!news.belwue.de!iptc!newsserv.zdv.uni-tuebingen.de!jkizi01
From: jkizi01@appserv.zdv.uni-tuebingen.de (Hans-Joachim Wittmann)
Newsgroups: comp.os.386bsd.development
Subject: FreeBSD with NetBSD-shared-libraries !?!
Date: 22 Nov 93 16:17:52 GMT
Organization: InterNetNews at ZDV Uni-Tuebingen
Lines: 42
Message-ID: <jkizi01.753985072@appserv.zdv.uni-tuebingen.de>
NNTP-Posting-Host: appserv.zdv.uni-tuebingen.de
Hello,
Just some Questions about the implementaition of the shared
libraries in NetBSD-current.
What I have don up to now: grabbed the sources and plugged
it into my FreeBSD-1.0 system. After some fiddling around,
almost everything seems to work. Just some oddities left...
1. the program ld.so (the runtime-linker) seems only to work
if the Stack-limit is set to unlimited or >8MB, else
the sbrk-function in rtld.c maps-memory in that is not
accessable by ld.so. Bug or Feature? (Just to say, if
a shared-program drops core, this file is >8MB :-( )
Is this the expected beahavior?
2. After building libc, i get errors when dynamicly linking some
programs like:
RRS text relocation at 0x171e (symbol ___sF)
the symbols that cause problems are: ___sF (stdio/findfp.c)
_optind (stdlib/getopt.c)
__ctype_ (stdio/ctype_.c)
These symbols contain global initialized data. Is this allowed
for this type of shared libraries? Who to fix?
3. I do have problems in building libXaw, libXmu ...
Who should these libraries be built dynamiclly?
Any comment? Please no ***bsd is better war ;-)
Micha
--------------------------------------------------------------------------
michael class jkizi01@mailserv.zdv.uni-tuebingen.de
hauptstr. 83 jkizi01@appserv.zdv.uni-tuebingen.de
72127 wankheim
--------------------------------------------------------------------------