From owner-freebsd-ports Wed Feb 27 12:49: 7 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id D2FF137B400; Wed, 27 Feb 2002 12:48:50 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g1RKmVll080772; Wed, 27 Feb 2002 15:48:31 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <86g03nl81i.wl@archon.musha.org> References: <200202251018.g1PAIqi02136@zaphod.euronet.nl> <200202251744.g1PHilj09014@zaphod.euronet.nl> <86g03nl81i.wl@archon.musha.org> Date: Wed, 27 Feb 2002 15:48:30 -0500 To: "Akinori MUSHA" From: Garance A Drosihn Subject: Re: Questions on bsd.ruby.mk (was: Request for changing bsd.port.mk ...) Cc: portmgr@FreeBSD.ORG, ports@FreeBSD.ORG, knu@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 4:04 PM +0900 2/27/02, Akinori MUSHA wrote: >At Mon, 25 Feb 2002, Garance A Drosihn wrote: > > This will seem a bit contorted, but it's a trap I fell into one >> time by mistake, and it took me quite awhile to figure out how >> I got there and how to get out of it... >> >> If you go into a port like 'portupgrade', and do a 'make', you >> will see some familiar-looking messages such as: >> >> Warning: Object directory not changed from original >> /usr/ports/sysutils/portupgrade/work/pkgtools-... > >I'm not following you... Are you saying that the warning is a >problem and it has something to do with bsd.ruby.mk? > >Portugprade has BSD-style Makefile's for build and install, and >that's why you see the same warning you see when building a >component of FreeBSD. The warning itself is not a problem. I am used to seeing it from other bsd-style makefiles. But the warning does definitely suggest that the user could do a 'make obj' for a ruby program -- and in fact they can do that. It will correctly create all the right things under /usr/obj. The problem is that once those directories (from 'make obj') exist, then the "port level" make will stop working. If you just follow the following list of commands, you should see the same errors I am talking about. Ignore for the moment *why* anyone would do this sequence of commands. The only important point is that it "should be" a legal thing to do, but it results in the port being impossible to build. And once you a port get into this condition, you can not fix it until you realize you need to remove the files under /usr/obj. The sequence is: cd /usr/ports/sysutils/portupgrade make clean make extract cd work/pkgtools-20020204 make obj cd ../.. # back to the sysutils/portupgrade level make I know *some* of the changes to make to /usr/ports/Mk/bsd.ruby.mk to fix the errors which happen at that last 'make', but I have not figured out all of them. (it also occurs to me that my changes may not really be *correct*, even though they did get me past some of the error messages). -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message