From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 16:19:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCB7116A404; Sun, 16 Apr 2006 16:19:09 +0000 (UTC) (envelope-from giffunip@asme.org) Received: from antivirus.cable.net.co (antivirus.cable.net.co [200.118.2.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 046CD43D45; Sun, 16 Apr 2006 16:19:08 +0000 (GMT) (envelope-from giffunip@asme.org) Received: from epicac.cable.net.co ([200.118.2.50]) by antivirus.cable.net.co with ESMTP; 16 Apr 2006 11:15:40 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= X-IronPort-AV: i="4.04,123,1144040400"; d="scan'208"; a="210664335:sNHT18669100" Received: from [69.79.218.227] by epicac.cable.net.co (Sun Java System Messaging Server 6.1 HotFix 0.09 (built Dec 14 2004)) with ESMTPA id <0IXS00AQBXAFQF10@epicac.cable.net.co>; Sun, 16 Apr 2006 11:13:28 +0500 (GMT) Date: Sun, 16 Apr 2006 11:19:06 -0500 From: "Pedro F. Giffuni" To: freebsd-hackers@FreeBSD.org Message-id: <44426E7A.9030301@asme.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ)" X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051013 X-Mailman-Approved-At: Sun, 16 Apr 2006 16:36:39 +0000 Cc: Subject: OpenWatcom [Fwd: Re: OW on FreeBSD] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 16:19:10 -0000 This is a multi-part message in MIME format. --Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Hi; The OpenWatcom on FreeBSD project is one day old but it has advanced greatly(see attached message for current status). FreeBSD experts are welcome. cheers, Pedro. --Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ) Content-type: message/rfc822; name="Re: OW on FreeBSD" Content-disposition: inline; filename="Re: OW on FreeBSD" Path: www-1.scitechsoft.com!not-for-mail X-Trace: www-1.scitechsoft.com 1145172236 9420 69.237.93.2 (16 Apr 2006 07:23:56 GMT) Date: Sun, 16 Apr 2006 00:24:11 -0700 From: Michal Necasek Subject: Re: OW on FreeBSD In-reply-to: Message-id: Organization: SciTech Software, Inc. X-Complaints-to: news@www-1.scitechsoft.com MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT NNTP-posting-date: Sun, 16 Apr 2006 07:23:56 +0000 (UTC) Newsgroups: openwatcom.contributors NNTP-posting-host: 69.237.93.2 References: User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.0.1) Gecko/20060129 SeaMonkey/1.0 Xref: www-1.scitechsoft.com openwatcom.contributors:17364 Okay, I've done some tweaks to the source code so that some of it builds on FreeBSD. Note that currently the build thinks it's targeting Linux, which will need to be fixed. Most of the tools don't really care as long as it's some sort of UNIX, but some do. There are two different ways to build: one uses the build.sh script and the other uses boot.sh. I would suggest concentrating on the latter. The "boot" build uses exclusively the native compiler and builds wmake, wlink, wdis, debugger, profiler, vi, and a few other odds and ends. Right now the rough status is: - wmake builds and appears to work without any problems - wlink builds and partially works but crashes in some situations - wdis builds and works on some objects but not others, apparently because of some ELF reloc type not seen previously - debugger user interface does not build due to Linux-specific ioctls which need replacing with BSD equivalents - trap file does not build because Linux-specific ptrace stuff needs to be modified - profiler doesn't build either for similar reasons - vi builds but crashes at startup because of insufficient error checking; the real problem is that a build ncurses it uses is configured for Linux and fails to init on FreeBSD The "regular" build manages to compile wasm and wcc386, both apparently functional (after I fixed a GCC-specific problem in wcc386). It seems likely that both could be used as cross-compilers as long as wlink works (which it doesn't quite appear to). Anyway I'm no UNIX expert and I've seen FreeBSD for the first time yesterday, so now some real FreeBSD expertise is needed. IMO the best course of action is to port the debugger first, because that has proven extremely useful on Linux. I would also like to have the Watcom vi available, just because I can use the exact same editor on Windows, DOS, OS/2, and Linux (the failing console support stuff is shared by vi, debugger, profiler, and one or two other tools). Since FreeBSD uses ELF+DWARF as far as I can tell, there should be little work needed on the file format support, just the OS debugging interface. The other line of work is adding FreeBSD support to the Watcom clib runtime; I expect this should not be terribly difficult for someone familiar with FreeBSD internals if the Linux clib is used as a starting point. In general, it may be helpful to have a Linux box handy for comparison, because all this works (or at least should work) on Linux. Michal --Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ)--