freebsd stable - Feb 2004 - "make -C ..." causes error in net/tkabber/Makefile, line 17

I am running FreeBSD 4.8-p14; and the make(1) man page lists -C
option...

     -C directory
          Change to directory while running.


...However, "make -V PORTVERSION" in net/tkabber" produces
this...

  make: illegal option -- C
  usage: make [-Beiknqrstv] [-D variable] [-d flags] [-E variable] [-f makefile]
              [-I directory] [-j max_jobs] [-m directory] [-V variable]
              [variable=value] [target ...]
  "Makefile", line 17: warning: "make -C
/usr3/ports/net/tkabber/../../devel/tcllib -V PORTVERSION" returned
non-zero status
  0.9.6b


...the particular Makefile line 17 is...

  TCLLIBVER!=     ${MAKE} -C ${.CURDIR}/../../devel/tcllib -V PORTVERSION


...and yes, devel/tcllib does exist; running "make -V PORTVERSION"
there produces "1.4".

What could be the problem?

(The ports tree is up to date as of 2004.02.01.19.43.37 UTC.)


  - Parv

--

in message <20040201213549.GA93666@moo.holy.cow>,
wrote parv thusly...
>
> I am running FreeBSD 4.8-p14; and the make(1) man page lists -C
> option...
>
>      -C directory
>           Change to directory while running.
>
>
> ...However, "make -V PORTVERSION" in net/tkabber" produces
this...
>
>   make: illegal option -- C
>   usage: make [-Beiknqrstv] [-D variable] [-d flags] [-E variable] [-f
makefile]
>               [-I directory] [-j max_jobs] [-m directory] [-V variable]
>               [variable=value] [target ...]
...

On the second thought, could it be that man page & binary are out of
sync for some reason?  It is hard to believe though as -C option
parsing appears in src/usr.bin/make/main.c, line 185...

  178  #ifdef REMOTE
  179  # define OPTFLAGS "BD:E:I:L:PSV:Xd:ef:ij:km:nqrstv"
  180  #else
  181  # define OPTFLAGS "BD:E:I:PSV:Xd:ef:ij:km:nqrstv"
  182  #endif
  183  rearg:  while((c = getopt(argc, argv, OPTFLAGS)) != -1) {
  184                  switch(c) {
  185                  case 'C':
  186                          if (chdir(optarg) == -1)
  187                                  err(1, "chdir %s", optarg);
  188                          break;


...but is omitted from OPTFLAGS (lines 179 & 181).  Is that the reason
of make carping when presented w/ -C option?


  - Parv

--

I have no idea if this would help, just a total guess, but it can't hurt to 
try -- try making with 'gmake' ?

>From: parv <parv@pair.com>
>To: f-ports <freebsd-ports@freebsd.org>,f-stable 
><freebsd-stable@freebsd.org>
>Subject: Re: "make -C ..." causes error in net/tkabber/Makefile,
line 17
>Date: Sun, 1 Feb 2004 17:01:42 -0500
>
>in message <20040201213549.GA93666@moo.holy.cow>,
>wrote parv thusly...
> >
> > I am running FreeBSD 4.8-p14; and the make(1) man page lists -C
> > option...
> >
> >      -C directory
> >           Change to directory while running.
> >
> >
> > ...However, "make -V PORTVERSION" in net/tkabber"
produces this...
> >
> >   make: illegal option -- C
> >   usage: make [-Beiknqrstv] [-D variable] [-d flags] [-E variable] [-f
>makefile]
> >               [-I directory] [-j max_jobs] [-m directory] [-V
variable]
> >               [variable=value] [target ...]
>...
>
>On the second thought, could it be that man page & binary are out of
>sync for some reason?  It is hard to believe though as -C option
>parsing appears in src/usr.bin/make/main.c, line 185...
>
>   178  #ifdef REMOTE
>   179  # define OPTFLAGS "BD:E:I:L:PSV:Xd:ef:ij:km:nqrstv"
>   180  #else
>   181  # define OPTFLAGS "BD:E:I:PSV:Xd:ef:ij:km:nqrstv"
>   182  #endif
>   183  rearg:  while((c = getopt(argc, argv, OPTFLAGS)) != -1) {
>   184                  switch(c) {
>   185                  case 'C':
>   186                          if (chdir(optarg) == -1)
>   187                                  err(1, "chdir %s",
optarg);
>   188                          break;
>
>
>...but is omitted from OPTFLAGS (lines 179 & 181).  Is that the reason
>of make carping when presented w/ -C option?
>
>
>   - Parv
>
>--
>
>_______________________________________________
>freebsd-ports@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to
"freebsd-ports-unsubscribe@freebsd.org"
_________________________________________________________________
What are the 5 hot job markets for 2004? Click here to find out. 
http://msn.careerbuilder.com/Custom/MSN/CareerAdvice/WPI_WhereWillWeFindJobsIn2004.htm?siteid=CBMSN3006&sc_extcmp=JS_wi08_dec03_hotmail1

>> No..4.8 is not maintained except for security fixes.
> Even though man page & the binary will remain inconsistent w/ each
> other? 
The point Kris is making is that the RELENG_4_8 branch represents a point in
time in the development of 4-STABLE, and only critical security fixes are
applied to that release.  If the make document was wrong at the point in time
when 4.8-RELEASE was tagged, then it will be wrong for that release for ever 
(unless you can convince the security officer that the doc bug is a critical 
security fix.....)  

If you think you need these sort of evolutionary improvements, then perhaps
you should consider running a -STABLE version rather than a -RELEASE version.
The _whole point_ of -RELEASE versions is that they don't change like this!

Patches to fix 4-STABLE will be gladly accepted (if this hasn't already been
fixed, which I suspect it has), but that won't change the fact that
4.8-RELEASE
was wrong when it was released, and all the RELENG_4_8 versions for the rest of
forever will still be wrong.