From owner-freebsd-ports@FreeBSD.ORG Fri Apr 30 14:47:09 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E7A516A4CF for ; Fri, 30 Apr 2004 14:47:09 -0700 (PDT) Received: from hexagon.stack.nl (hexagon.stack.nl [131.155.140.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id A61C343D31 for ; Fri, 30 Apr 2004 14:47:08 -0700 (PDT) (envelope-from marcov@stack.nl) Received: from toad.stack.nl (zen.stack.nl [IPv6:2001:610:1108:5010::130]) by hexagon.stack.nl (Postfix) with ESMTP id 7592352E4; Fri, 30 Apr 2004 23:47:07 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 816) id 53AA4114; Fri, 30 Apr 2004 23:47:07 +0200 (CEST) In-Reply-To: <408A7D55.6030906@earthlink.net> "from Walter at Apr 24, 2004 09:44:37 am" To: Walter Date: Fri, 30 Apr 2004 23:47:07 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20040430214707.53AA4114@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) cc: ports@FreeBSD.org cc: marco@freepascal.org Subject: Re: FreeBSD Port: fpc-devel-1.9.2_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Apr 2004 21:47:09 -0000 > Is fpc-devel-1.9.2 available for FreeBSD 5.2.1 as it is for 4.9? FPC and the files it generates don't use any userland libraries, so in general it is independant of 4.9<>5.2 until one starts to link in userland libraries. Only the FPC patched startupcode must be updated for 5.2 I think, because an ELF identifier was edit, at least for basic operation to avoid COMPAT_4. A simple script could do this. Running http://www.stack.nl/~marcov/fpcfpc19 should fix that, but I couldn't test this on a short notice. that's why backing up $PREFIX/lib/fpc/1.9.2/units/freebsd/rtl/cprt0.o could be wise. I postponed adding such changes to the port in anticipation of the next beta, 1.9.4, but because x86_64 and Mac OS X support is being merged in, this is delayed. (x86_64 support for linux only atm, but as soon as that is halfwhat stable I'll start a FreeBSD port too, expect to do that rather quickly)