From owner-freebsd-ports Mon Jul 20 23:20:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22952 for freebsd-ports-outgoing; Mon, 20 Jul 1998 23:20:26 -0700 (PDT) (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 XAA22932 for ; Mon, 20 Jul 1998 23:20:23 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id XAA13072; Mon, 20 Jul 1998 23:20:01 -0700 (PDT) Date: Mon, 20 Jul 1998 23:20:01 -0700 (PDT) Message-Id: <199807210620.XAA13072@freefall.freebsd.org> To: freebsd-ports@FreeBSD.ORG From: Thomas Gellekum Subject: Re: ports/7346: The Python port fails to compile on -stable Reply-To: Thomas Gellekum Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/7346; it has been noted by GNATS. From: Thomas Gellekum To: doconnor@gsoft.com.au Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: ports/7346: The Python port fails to compile on -stable Date: 21 Jul 1998 08:16:32 +0200 "Daniel O'Connor" writes: > >Description: > The python port does not compile if the patches downloaded are used. They also have > incorrect checksums. If you disable the PATCHFILES lines then it works fine. The > compiled version done this way seems to work OK (I didn't test it much tho). I can't reproduce this. Please fetch the latest port and try again, there may have been some changes to the official patches since you got your port. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message