From owner-freebsd-ports Thu Mar 2 18:34:38 2000 Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 079A237BC1E; Thu, 2 Mar 2000 18:34:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 05A5B2E815E; Thu, 2 Mar 2000 18:34:37 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 2 Mar 2000 18:34:36 -0800 (PST) From: Kris Kennaway To: John Hay Cc: freebsd-ports@freebsd.org Subject: Re: Mk/bsd.port.mk a little broken In-Reply-To: <200003021312.PAA85288@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 2 Mar 2000, John Hay wrote: > The current bsd.port.mk file is a little broken if you try to use a port > that define USE_OPENSSL on a fairly new -current machine without libcrypto. > The makefile will then have echo commands outside a target. Here is a > patch that try to fix it the same way it is done in other places. Satoshi finally committed my patch which did this. Sorry :) > One question that I have is, is it the intention to require that you > have libcrypto on -current machines even if you only want to do a > "make readmes" in the ports? I have a -current machine without the > crypto stuff in the base system that build daily releases (with > crypto in them), but it is failing now in ports when trying to do > "make readmes". It wasn't intentional, but I don't know how easy it would be to solve. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message