fix in config.site (WMaker 0.70 with GNUstep)

[Laurent Julliard]

Last Friday I have upgraded WMaker from 0.65 to the 0.70 (latest
version). I just wanted to report that there is a little problem in the
"make install". WMaker are not installed at the right place in the
GNUstep hierarchy.

The reason is because WMaker is now using autoconf 2.52 whereas GNUstep
is still at 2.13 (right ?). In 2.52 the "target" parameter is no longer
preset to "NONE" as in 2.13. It is simply left empty.

When the windowmaker configure script calls the GNUstep config.site to
determine the GNUstep location and settings it fails because the $target
is empty.

A quick hack consist in changing one line in
/opt/GNUstep/System/share/config.site

from
if test "$target" = NONE ; then

to
if test -z "$target" -o "$target" = NONE; then

Hope this helps
Laurent
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: Problem Installing WM 0.70 with GNUstep
>
>
>
>
> Date: 
>
> Fri, 5 Oct 2001 22:57:03 +0300 (EEST)
>
>
>
>
> This has nothing to do with wmaker. that variable was added to configure
> by autoconf2.13 while newer autoconf2.5x no longer use it. It's not
> defined anywhere by us and it's beyond our control. We can't define it
> ourselves without messing the internal state of autoconf.
>
> Probably your problem comes from the fact wmaker uses autoconf2.52
> while config.site probably uses the obsoleted $target variable as it
> was defined in autoconf2.13 which is no longer available.
>
> you need to update your config.site to do a test like:
>
> if test -z "$target" -o "$target" = NONE; then
> ....
> fi
>
> this will allow to work in both cases (target=NONE or not defined)
>
> On  5 Oct, Laurent Julliard wrote:
> > Dan,
> > 
> > I'm a GNUStep developer. This morning I decided to upgrade from 0.65 to
> > 0.70. Compilation went fine but I noticed that the install stage does
> > not go well. The WM files are not installed where it should be.
> > 
> > It looks like the problem comes from configure. In the one used in WM
> > 0.65 the "target" argument is initialized to NONE where as it isn't in
> > the configure script of WM 0.70 this causes the GNUstep config.site
> > script to fail because the target argument is a null string
> > 
> > Adding
> > 
> > target=NONE
> > 
> > in line 284 of the configure script solves the problem
> > 
> > Not being a specialist of autoconf and not being involved in the
> > development activities of WM I thought you would redirect this bug to
> > the right person in the development team
> > 
> > Laurent
> > 
>
> -- 
> Dan
>
>
>
> --- End Message ---