From owner-freebsd-ports Wed Oct 18 14:56:47 2000 Delivered-To: freebsd-ports@freebsd.org Received: from relay3.mail.uk.psi.net (relay3.mail.uk.psi.net [154.32.109.6]) by hub.freebsd.org (Postfix) with ESMTP id 78FDF37B4C5 for ; Wed, 18 Oct 2000 14:56:44 -0700 (PDT) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay3.mail.uk.psi.net with smtp (Exim 2.12 #2) id 13m1CL-0007YV-00; Wed, 18 Oct 2000 22:56:33 +0100 Received: from virgo.software.plasmon ([193.115.4.42]) by mail.plasmon.co.uk (Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) with SMTP id 8025697C.0078ADA0; Wed, 18 Oct 2000 22:58:07 +0100 Received: from mail by virgo.software.plasmon with local-esmtp (Exim 2.12 #1) id 13m15Q-0006Qb-00 (FreeBSD); Wed, 18 Oct 2000 22:49:24 +0100 Received: from dobbo by penfold.software.plasmon with local (Exim 3.12 #1) id 13m15P-0000z6-00 (Debian); Wed, 18 Oct 2000 22:49:23 +0100 Date: Wed, 18 Oct 2000 22:49:23 +0100 From: Steve Dobson To: "Koster, K.J." Cc: "'ob-users@ooc.com'" , "'ejc@bazzle.com'" , 'Steve Dobson' , "'freebsd-ports@freebsd.org'" Subject: Re: ORBacus 4.0 for FreeBSD patches Message-ID: <20001018224923.B3714@penfold.software.plasmon> References: <59063B5B4D98D311BC0D0001FA7E4522026D794B@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D794B@l04.research.kpn.com>; from K.J.Koster@kpn.com on Wed, Oct 18, 2000 at 03:34:17PM +0100 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 18, 2000 at 03:34:17PM +0100, Koster, K.J. wrote: > Dear OOC, ejc@bazzle.com, Steve Dobson and ports mailing list, > > I have written a few patches to get ORBacus 4.0.3 to compile and run on > FreeBSD 4.0. I hope that you will find them useful. > > If you look at the patches in ob.patch, you will find that my patch to > ob/demo/chat/X11/Makefile.in does not carry over to other platforms. Someone > with more "make" knowledge than I should have a look at this. > > Since JThreads/C++ is not available for FreeBSD, these patches are for > single-threaded versions of ORBacus only. > > For those who want to use fully automatic installation, I have also added > the scripts that would otherwise be generated by "runconfig". > > Kees Jan I am working on a set of patches that will allow JTC to run on FreeBSD. From work I did a few months ago I managed to get JTC to pass all its tests! Unfortunatly that work was lost DOH (I either did it on an old JTC tree [1.0.10] or on a machine which disk got re-installed, either way DOH!!!) From memory I had only to make three changes to make to Thread.cpp. 1) Add an entry for task priorities in levelMap. 2) Fake the {get/set}Priority as priorities don't seem to be started in FreeBSD. 3) Slightly modify the initilisation of a Thread{Group}. I have done 1, and belive that I have done 2. I am currently compling DDD so I can run through one of the programs and fix the fix the initialisation for 3. When I have completed this I will be releasing a patch. I would expect to do this in the next few days (probably tomorrow). OOC people would be willing to add FreeBSD to your list of supported platforms? Kess Jan, I think that modifing OB is the wrong way to get ORBacus to work on FreeBSD. As ORBacus already compiles with out JTC on FreeBSD (see /usr/ports/ORBacus) why are you doing this hack? If you need the event service (as we do) then you must be doing some serious re-design of that part of the code. As soon as I can get JTC to pass all its test on FreeBSD then OB should compile without issue. What are your thoughs. Please note that for the rest of this week I am working from home, so please include my home e-mail address (steve@dobson.org) in any futher communications with me as I may get those emails quicker. Steve -- Steve Dobson E-mail: sdobson@allstor-sw.com Unix Architect Tel (Direct): +44 1763 264441 Allstor Software Ltd. (R'tion): +44 1763 262963 Whiting Way Fax: +44 1763 264444 Melbourn, Herts, UK SG8 6EN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message