Re: Toto, I don't think were in /usr/ports/??? any more!

[Chuck Gagnon <gagnocg@ev1.net>]

"Josh A. Strickland" wrote:
> 
> On Thu, 30 Sep 1999, Chuck Gagnon wrote:
> 
> >
> > # make install
> > install -c -o root -g bin -m 444 bsd.README bsd.doc.mk bsd.dep.mk
> > bsd.lib.mk bsd.man.mk bsd.nls.mk  bsd.obj.mk bsd.own.mk bsd.port.mk
> > bsd.port.subdir.mk bsd.prog.mk  bsd.subdir.mk bsd.sys.mk sys.mk
> > bsd.lkm.mk  /mk
> > usage: install [-bCcpSs] [-B suffix] [-f flags] [-g group] [-m mode] [-o
> > owner] file1 file2
> >        install [-bCcpSs] [-B suffix] [-f flags] [-g group] [-m mode] [-o
> > owner] file1 ... fileN directory
> >        install  -d   [-g group] [-m mode] [-o owner] directory ...
> > *** Error code 64
> >
> > Stop in /usr/local.
> > # pwd
> > /usr/local
> >
> >
> > basically I was working on the gnome port and jumping back and forth
> > between directories,
> > when I ran make install in the wrong directory (you probably knew this
> > already), but
> > my poor timing does not explain this message.  Did I catch some default
> > tag in the
> > mk tree?
> 
> you have to update make first. cvs up src/usr.bin; cd
> /usr/src/usr.bin/make; make; make install;
> then cd /usr/ports/infrastructure/mk; make install
> 

People are missing my point here, I'm not trying to install the mk
files,
I was trying to install a test port I'm working on.  The problem is not 
that I can't install, but that if you accidentally type make install in
a directory where there is no makefiles you should get a message like:

    make: don't know how to make install. Stop

not a message telling me it is trying to install the mk files (try cd
/tmp;make install).

Look carfully at the make install ooutput and the pwd output above!

-cgg