From owner-freebsd-questions@FreeBSD.ORG Mon Aug 4 09:59:44 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D3A637B401 for ; Mon, 4 Aug 2003 09:59:44 -0700 (PDT) Received: from out8.mx.nwbl.wi.voyager.net (out8.mx.nwbl.wi.voyager.net [169.207.3.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F61843F3F for ; Mon, 4 Aug 2003 09:59:43 -0700 (PDT) (envelope-from dragoncrest@voyager.net) Received: from mail5.mx.voyager.net (mail5.mx.voyager.net [216.93.66.204]) by out8.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id CFEF73C00F for ; Mon, 4 Aug 2003 11:59:42 -0500 (CDT) Received: from localhost.localdomain (nm1.mx.lnng.mi.voyager.net [216.93.38.227]) by mail5.mx.voyager.net (8.12.9/8.10.2) with ESMTP id h74GxgxT007741 for ; Mon, 4 Aug 2003 12:59:42 -0400 (EDT) Message-Id: <200308041659.h74GxgxT007741@mail5.mx.voyager.net> From: "Dragoncrest" To: Freebsd-questions@freebsd.org X-Mailer: CoreCommMail X-IPAddress: 209.153.128.248 Date: Mon, 4 Aug 2003 12:20:29 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Well, we're getting closer. Still having issues installing BitTorrent. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 16:59:44 -0000 Ok, first off I want to send out thanks to whoever submitted the bug report on the python numeric port issue. Problem is, we've got a new one. When building for BitTorrent it looks for the port "py23-imaging-1.1.3" and tries to install it, but instead gets this: ===> Building for py23-imaging-1.1.3 `Makefile' is up to date. cc -fPIC -O -pipe -I/usr/local/include/python2.3 -I/usr/local/include/python2.3 @DEFS@ -IlibImaging -I/usr/local/include -c ././_imaging.c -o ./_imaging.o cc: cannot specify -o with -c or -S and multiple compilations *** Error code 1 Anyone know if this is another bug issue needing to be reported or is this something that I can fix on my end?