From owner-freebsd-ports Sat Jan 13 19:24:29 2001 Delivered-To: freebsd-ports@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 0F21D37B400; Sat, 13 Jan 2001 19:24:10 -0800 (PST) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.9.3/8.9.3) with SMTP id WAA65661; Sat, 13 Jan 2001 22:23:35 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <004201c07dd9$a4091dd0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: , "Lars Eighner" Cc: References: <86u273uef4.fsf@dumpster.io.com> Subject: Re: Trouble with ports? Try this Date: Sat, 13 Jan 2001 22:25:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Recently I have discovered many ports that do not build, fail to build > with various mysterious messages, or appear to build but do not work. > > Here is the secret: a number of ports require imake, but they don't > say so if you just try to make them. You have to read the Makefile > to discover it. Some of them will appear to build and install, but > won't work. Some of them fail to build with messages which don't > mention imake. If you find ports that require imake, but don't have USE_IMAKE set in the port Makefile, please report them to the -ports mailing list (which a more appropriate place than -questions, and may be the reason why you never received valid responses to your queries in the first place.) If USE_IMAKE is set and your system doesn't have it, imake will be added to the build dependency list and as such, will be built and installed before the port, so you should never have the problems that you describe. However, it appears that this functionality is broken for some reason or another. I've created a fix for this problem and submitted it. See PR #24317 (http://www.freebsd.org/cgi/query-pr.cgi?pr=24317) to track the progress of this fix. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message