From fnaumann@mail.cs.uni-magdeburg.de Mon Aug 23 23:51:18 2004 Message-ID: <412A657A.9070907@seznam.cz> Date: Mon, 23 Aug 2004 23:45:30 +0200 From: Standa Opichal User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mint@fishpool.com Subject: Re: [MiNT] Shared Libs References: <1093209407.25052.9.camel@localhost> <20040823223705.61ea9ae3.mandin.patrice@wanadoo.fr> In-Reply-To: <20040823223705.61ea9ae3.mandin.patrice@wanadoo.fr> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: opichals@seznam.cz Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel Hi Patrice! When I was thinking about it it seemed to me like that the .a archives (static libraries comprised of .o files) can serve as dynamicaly loadable library (for the case you don't need to share the code actually, of course, otherwise you would need -fPIC and other stuff to be fine, perhaps). It already contains (IMO) all information we need (symbol tables, relocation tables, ...). So why not to just modify the .PRG binary so that it can contain the library list to load 'and we are done' (although it might be quite piece of investigation for binutils newbie) for now... Later, when we have VM (if ever), we can also implement true .so libs if required. Perhaps a symlinks .so -> .a libs would be just enought to distinguis whether the ld can link dynamicaly or not for now. Opinions? Corrections? regards STanda Patrice Mandin wrote: > Le Sun, 22 Aug 2004 17:16:47 -0400 > Mark Duckworth a écrit: > > >>This is something we seriously need. We recently talked about it, but >>it seemed to die. You don't want me to work on this because I don't >>know what I'm doing ;-) Is anyone else working on it? I'd be willing >>to help in ANY WAY I can. > > > Well, at the moment, I want to write a document about how loadable > libraries could be done in MiNT (and maybe TOS if possible). The > "shareable" stuff needs MMU, so MiNT is mandatory. > > 1. Definition of the executable format that needs loadable libraries (i.e. > references to functions outside of the program file being run). > > 2. Definition of the format of those loadable libraries (maybe same as 1). > > 3. Definition of the work that has to be done by the "loader" which is run > by the program to load its needed libraries (i.e. a custom crt0.o). >