[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: patch

From: Torbjorn Granlund
Subject: Re: patch
Date: 04 Jan 2001 23:31:36 +0100
User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.6

Alexandre Oliva <address@hidden> writes:

  On Jan  4, 2001, Torbjorn Granlund <address@hidden> wrote:
  > It is well-known that many old Unix systems reject scripts with a
  > apace.  En example is SunOS 4.x.
  This is not well-known to me.  And I've just tested SunOS 4.1.3 and
  4.1.4, and both can run executable shell-scripts starting with `#! 
  /bin/sh' without any problem.  Which SunOS are you talking about?
I used SunOS 4.1.3 and SunOS 4.1.4 too.

This problem is more complicated that I thought.  I had

  "#! /home/tf/bin/SunOS/sun4m/bash2"

as the first line in the libtool scripts here.  (I needed an exlicit
CONFIG_SHELL for working around a /bin/sh bug that causes segfault in
autoconf generated configure scripts.)  With the space, libtool cannot
be executed.  By removing the space, libtool works.

But I also cannot reproduce this when using /bin/sh.  Some
trial-an-error shows that there is a 32-byte limit in SunOS for the
entire "#! <interpreter>" construct.  With a space, I has 33 bytes.
Removing the space brought the line down to exactly 32 bytes.  Fun.

(I am absolutely sure some old Unix systems reject scripts with a
space in position 3.  These are probably no longer in use, though.
Unices from the early eighties had this problem.)

  I'd really appreciate some further investigation before having this
  patch installed.
Done.  I retract my patch.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]