Toni Mueller [EMAIL PROTECTED] wrote:
ok, thanks for the heads-up. I am more interested if it's intentional
behaviour that I _can't_ make makesum from the top directory when
Makefile includes bsd.port.subdir.mk instead of bsd.port.mk.
Only a subset of the bsd.port.mk targets are available at
.
can you think of a good reason why this would be necessary? supporting
makesum in bsd.port.subdir.mk also means you could do
cd ${PORTSDIR} make makesum
and mess up distinfo files just like that? i don't think it is needed.
steven
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Hello,
trying to tackle the PHP 4.4.2 stuff myself, I ran into the following
problem:
make fetch: ok... file was correctly downloaded
But make makesum:
# /usr/bin/make makesum
make: don't know how to make makesum. Stop in /home/obsd/ports/www/php4.
(PORTSDIR set correctly)
Looking into
On Thu, Feb 09, 2006 at 03:36:49PM +0100, Toni Mueller wrote:
Hello,
trying to tackle the PHP 4.4.2 stuff myself, I ran into the following
problem:
make fetch: ok... file was correctly downloaded
But make makesum:
# /usr/bin/make makesum
make: don't know how to make makesum.
Hi,
On Thu, 09.02.2006 at 16:22:06 +0100, steven mestdagh [EMAIL PROTECTED] wrote:
On Thu, Feb 09, 2006 at 03:36:49PM +0100, Toni Mueller wrote:
Trying this from the 'core' subdirectory produces a correct distinfo
one level above. Is this intentional behaviour?
I think so, since
