Mail Archives: djgpp-workers/2002/01/30/12:56:57
> From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
> Date: 30 Jan 2002 15:29:17 +0100
>
> > I'd rather try to convince Autoconf maintainers to undo the change
> > they did for OS/2, and solve the OS/2 problem in some other way. For
> > example, they could set SHELL to /bin/sh for OS/2 only. No one said
> > DJGPP has to be broken for OS/2's sake.
>
> In general, I agree, and I did try to have the patch undone. One is
> that they do not want to rely on $SHELL (which is why CONFIG_SHELL
> was introduced in the first place). Another is that /bin/sh is an
> absolute path, so PATH should have NO bearing on whether it's found or
> not.
/bin/sh after hash-bang is a magic string interpreted by the ``system
kernel'', so it's IMHO wrong on the part of Autoconf maintainers to
assume that it is interpreted as if it were typed at the shell prompt.
In any case, it's wrong to fix one port by breaking another.
Would they agree to doing two tests, once with /bin/sh, the other
with $SHELL, as before?
I could think about other possibilities to have the cake and eat it,
too, provided that the Autoconf maintainers are ready to listen. Are
they?
> That is why I suggested bash be changed to always look in
> $DJDIR/bin for those lookups (as that directory is our equivalent of
> /bin, /usr/bin, etc.).
That would break if $DJGPP is not set.
- Raw text -