Date: Sun, 16 Jul 2006 18:59:08 -0400 From: Bob Richards <bob@tamara-b.org> Cc: freebsd-hackers@freebsd.org Subject: Re: LinkLib Issues In freebsd Lazarus Message-ID: <44BAC4BC.2070401@tamara-b.org> In-Reply-To: <20060716221612.GA48425@troutmask.apl.washington.edu> References: <44BA98A9.9040903@tamara-b.org> <20060716202946.GA47862@troutmask.apl.washington.edu> <e9ed00$tlj$1@sea.gmane.org> <20060716221612.GA48425@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > > I realized this. However, the OP had 2 problems. > He had problems installing fpc because of library > issues. No, I had a problem compiling Lazarus because of an incorrect library call in FPC. FPC installed/compiled correctly from the freepascal _sources_ (Not available via ports). What's called sources in ports is nothing more than a collection of pre-built binaries and libs. To compile Lazarus, you need FPC-2.0.2 source tree, > lang/fpc will remove those problem. Whether or not the pre-built ports FPC has the proper libs compiled in or not is meaningless, since I need a good source tree. The only way to get one of those on freebsd is to manually patch the freepascal sources. Do you know of a freebsd-patched FPC-2.0.2 source? > 2nd problem was with Lazarus. If he had a working > coherent fpc, it may be easier to build Lazarus. > He could even submit a port. > I will submit a port if I can get Lazarus to compile. What's needed to compile Lazarus is a proper 2.0.2 source tree (binaries won't do), and a Lazarus source tree which properly calls for available/proper freebsd libs. Neither of which exist AFAIK. Bob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44BAC4BC.2070401>