From owner-freebsd-ports Sun Jan 24 17:20:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20345 for freebsd-ports-outgoing; Sun, 24 Jan 1999 17:20:17 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20311 for ; Sun, 24 Jan 1999 17:20:15 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id RAA01930; Sun, 24 Jan 1999 17:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 24 Jan 1999 17:20:03 -0800 (PST) Message-Id: <199901250120.RAA01930@freefall.freebsd.org> To: freebsd-ports@FreeBSD.ORG From: "Eugene M. Kim" Subject: Re: ports/9665: cannot start apache server Reply-To: "Eugene M. Kim" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/9665; it has been noted by GNATS. From: "Eugene M. Kim" To: Ying-Chieh Liao Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: ports/9665: cannot start apache server Date: Sun, 24 Jan 1999 15:14:26 -0800 (PST) Attached is a patch file which should fix this problem. Put the file in apache13/patches and rebuild the port. NB: not only this, but a *lot* of ports are broken on -4.0 because their configuration scripts (notably autoconf) not knowing how to deal with the `unknown' FreeBSD 4.0. The only fix seems to be using individual patch files until the scripts are fixed in the distribution. Grrrr. Eugene --------------------------------- snip --------------------------------- begin 644 patch-za M*BHJ('-R8R]#;VYF:6=U+BIF "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message