Date: Wed, 27 Feb 2002 15:48:30 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: "Akinori MUSHA" <knu@iDaemons.org> Cc: portmgr@FreeBSD.ORG, ports@FreeBSD.ORG, knu@FreeBSD.ORG Subject: Re: Questions on bsd.ruby.mk (was: Request for changing bsd.port.mk ...) Message-ID: <p05101409b8a2ee0efe5b@[128.113.24.47]> In-Reply-To: <86g03nl81i.wl@archon.musha.org> References: <200202251018.g1PAIqi02136@zaphod.euronet.nl> <p0510142ab8a026dad48c@128.113.24.47> <200202251744.g1PHilj09014@zaphod.euronet.nl> <p0510142cb8a02e6899d7@128.113.24.47> <86g03nl81i.wl@archon.musha.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101409b8a2ee0efe5b>