On Tue, 8 Nov 2005, Simon J. Gerraty wrote:

>> I noticed it set some GNU_CONFIGURE switches even though GNU_CONFIGURE was
>
> GNU_CONFIGURE ?
>
> 'grep GNU_CONFIG *' returns nothing, did you mean CONFIGURE_ARGS ?

Sorry. I meant this was in the pkgsrc stuff. You can ignore this :)

>> Anyways ... I ran:
>>
>> cd /build/reed/tmp/pkgsrc/devel/bmake/work.reed && ./bmake/boot-strap
>>
>> and received:
>>
>> Usage:
>> ./bmake/boot-strap [--<configure_arg> ...][-s <srcdir>][-m <mksrc>][<prefix> [
>> [<srcdir>] [<mksrc>]]]
>> *** Error code 1
>
> That's odd.  On all the systems I tested on (NetBSD, FreeBSD, Linux,
> SunOS), the above just works.  Are you sure your bmake directory is
> complete and clean (ie only what came in bmake-*tgz ?)
>
>> What part is not optional?
>
> Don't know.  What do you get for
>
> MD5 (./bmake/boot-strap) = fbe5345e0f1cd8b02e28d257f960049a

Same file.

And the only files that are not in the tarball are my CVS/ files. All is 
the same. (I used DragonFly's cool cpdup(1) tool.)

I am doing this on DragonFly. This is strange. It runs from my home 
directory. But I can't run from a different directory. In my home it does 
the configure steps. The failing directory just does:

pkgbox:/home/pkgsrc/devel/bmake/bmake> ./boot-strap
Usage:
./boot-strap [--<configure_arg> ...][-s <srcdir>][-m <mksrc>][<prefix> 
[[<srcdir>] [<mksrc>]]]

diff -pruN shows they are identical. And I extracted via tar manually a 
few times to retest. Something strange going on this system ... I will 
troubleshoot it ... here is the diff of running both with "sh -x"

(I extracted bmake-20051105.tar.gz twice -- one to 
/home/pkgsrc/devel/bmake/bmake  and the other to /home/reed/bmake as you 
can see in this following diff.)

--- J	2005-11-08 22:29:50.000000000 -0800
+++ /home/reed/bmake/J	2005-11-08 22:30:03.000000000 -0800
@@ -41,7 +41,7 @@
  + export LN SHARE_ARCH TR
  + cd .
  + /bin/pwd
-+ Mydir=/home/pkgsrc/devel/bmake/bmake
++ Mydir=/home/reed/bmake
  + CONFIGURE_ARGS=
  + prefix=
  + srcdir=
@@ -50,29 +50,64 @@
  + quiet=:
  + :
  + break
-+ GetDir /bmake /home/pkgsrc/devel/bmake/bmake ./bmake.cat1 /home/pkgsrc/devel/bmake/bmake/../bmake /home/pkgsrc/devel/bmake/bmake/../bmake-20051105.tar.gz
++ GetDir /bmake /home/reed/bmake ./bmake.cat1 /home/reed/bmake/../bmake /home/reed/bmake/../bmake.diff.bz2
  + match=/bmake
  + shift
-+ [ -d /home/pkgsrc/devel/bmake/bmake ]
-+ echo /home/pkgsrc/devel/bmake/bmake
++ [ -d /home/reed/bmake ]
++ echo /home/reed/bmake
  + break
-+ srcdir=/home/pkgsrc/devel/bmake/bmake
-+ [ -d /home/pkgsrc/devel/bmake/bmake ]
-+ GetDir /mk ./mkdeps.sh /home/pkgsrc/devel/bmake/bmake/mkdeps.sh /home/pkgsrc/devel/bmake/bmake/../mk*
++ srcdir=/home/reed/bmake
++ [ -d /home/reed/bmake ]
++ GetDir /mk ./mkdeps.sh /home/reed/bmake/mkdeps.sh /home/reed/bmake/../mk
  + match=/mk
  + shift
  + [ -d ./mkdeps.sh ]
  + continue
-+ [ -d /home/pkgsrc/devel/bmake/bmake/mkdeps.sh ]
++ [ -d /home/reed/bmake/mkdeps.sh ]
  + continue
-+ [ -d /home/pkgsrc/devel/bmake/bmake/../mk* ]
-+ continue
-+ mksrc=
-+ [ -d /dev/null ]
-+ Usage
-+ [  ]
-+ echo Usage:
-Usage:
-+ echo boot-strap [--<configure_arg> ...][-s <srcdir>][-m <mksrc>][<prefix> [[<srcdir>] [<mksrc>]]]
-boot-strap [--<configure_arg> ...][-s <srcdir>][-m <mksrc>][<prefix> [[<srcdir>] [<mksrc>]]]
-+ exit 1
++ [ -d /home/reed/bmake/../mk ]
++ cd /home/reed/bmake/../mk
++ /bin/pwd
++ break
++ mksrc=/home/reed/mk
~++ [ -d /home/reed/mk ]
++ objdir=DragonFly
++ [ -d DragonFly ]
++ [ -d DragonFly ]
++ cd DragonFly
++ AddConfigure --prefix=
++ CONFIGURE_ARGS= --prefix=
++ AddConfigure --with-default-sys-path= /share/mk
++ CONFIGURE_ARGS= --prefix= --with-default-sys-path=/share/mk
++ [ /home/reed/mk ]
++ AddConfigure --with-mksrc= /home/reed/mk
++ CONFIGURE_ARGS= --prefix= --with-default-sys-path=/share/mk --with-mksrc=/home/reed/mk
++ /home/reed/bmake/configure --prefix= --with-default-sys-path=/share/mk --with-mksrc=/home/reed/mk
+checking for gcc... gcc
...


This is strange. My home directory had:

-rw-r--r--  1 reed  wheel  6887 Mar 22  2005 /home/reed/mk/own.mk

And when I moved it out of the way, then the ./boot-strap failed like the 
other. Here is the complete "sh -x ./boot-strap":

+ :
+ dirname ./boot-strap
+ Mydir=.
+ . ./os.sh
+ :
+ _OS_SH=:
+ uname
+ OS=DragonFly
+ uname -r
+ OSREL=1.3.7-DEVELOPMENT
+ IFS=.
+ set 1 3 7-DEVELOPMENT
+ echo 1
+ OSMAJOR=1
+ uname -m
+ MACHINE=i386
+ uname -p
+ MACHINE_ARCH=i386
+ K=
+ HOSTNAME=pkgbox.dragonflybsd.org
+ HOSTNAME=pkgbox.dragonflybsd.org
+ IFS=.
+ set -- pkgbox dragonflybsd org
+ echo pkgbox
+ HOST=pkgbox
+ TMP_DIRS=/tmp /var/tmp
+ MACHINE_ARCH=i386
+ SHARE_ARCH=DragonFly/1.X/i386
+ LN=ln
+ TR=tr
+ echo DragonFly1-i386
+ toLower
+ tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz
+ HOST_TARGET=dragonfly1-i386
+ export HOST_TARGET
+ echo -n .
+ N=-n
+ C=
+ export HOSTNAME HOST
+ export OS MACHINE MACHINE_ARCH OSREL OSMAJOR LOCAL_FS TMP_DIRS MAILER N C K PS_AXC
+ export LN SHARE_ARCH TR
+ cd .
+ /bin/pwd
+ Mydir=/home/reed/bmake
+ CONFIGURE_ARGS=
+ prefix=
+ srcdir=
+ mksrc=
+ objdir=
+ quiet=:
+ :
+ break
+ GetDir /bmake /home/reed/bmake ./bmake.cat1 /home/reed/bmake/../bmake /home/reed/bmake/../bmake.diff.bz2
+ match=/bmake
+ shift
+ [ -d /home/reed/bmake ]
+ echo /home/reed/bmake
+ break
+ srcdir=/home/reed/bmake
+ [ -d /home/reed/bmake ]
+ GetDir /mk ./mkdeps.sh /home/reed/bmake/mkdeps.sh /home/reed/bmake/../mk*
+ match=/mk
+ shift
+ [ -d ./mkdeps.sh ]
+ continue
+ [ -d /home/reed/bmake/mkdeps.sh ]
+ continue
+ [ -d /home/reed/bmake/../mk* ]
+ continue
+ mksrc=
+ [ -d /dev/null ]
+ Usage
+ [  ]
+ echo Usage:
Usage:
+ echo ./boot-strap [--<configure_arg> ...][-s <srcdir>][-m <mksrc>][<prefix> [[<srcdir>] [<mksrc>]]]
./boot-strap [--<configure_arg> ...][-s <srcdir>][-m <mksrc>][<prefix> [[<srcdir>] [<mksrc>]]]
+ exit 1

For what it is worth, I do have a ~/pkg/share/mk/ directory (that is under 
my pkgsrc LOCALBASE).

I also tried with  --prefix=/home/reed/pkg 
--with-default-sys-path=/home/reed/pkg/share/mk



  Jeremy C. Reed

  	  	 	 Media Relations and Publishing Services
 	  	 	 http://www.reedmedia.net/