./configure generates 'command not found' errors

Michael Wood esiotrot at gmail.com
Sun May 1 17:34:46 MDT 2011

On 1 May 2011 19:41, John Smith <lbalbalba at gmail.com> wrote:
> On Sun, May 1, 2011 at 7:36 PM, Kai Blin <kai at samba.org> wrote:
>> Ok, and which of the configure calls threw the "command not found"
>> errors? The config.log looks sane for all I can see.
> Here's the complete output of './configure.developer' for samba-3.5.8.

Just a guess, but does it help if you do this:

$ bash configure

instead of

$ ./configure

Or change the shebang line in configure to #!/bin/bash instead of #!/bin/sh.

Michael Wood <esiotrot at gmail.com>

More information about the samba-technical mailing list