From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 10:29:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34D8416A41C; Thu, 30 Jun 2005 10:29:29 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2BF43D1F; Thu, 30 Jun 2005 10:29:28 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 715A11F87BEE; Thu, 30 Jun 2005 12:29:24 +0200 (CEST) Date: Thu, 30 Jun 2005 12:29:24 +0200 From: Roman Neuhauser To: David O'Brien Message-ID: <20050630102924.GA71895@isis.sigpipe.cz> References: <42BC8310.9040501@cse.unl.edu> <20050626042355.GA41119@misty.eyesbeyond.com> <20050629221047.GC20836@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050629221047.GC20836@dragon.NUXI.org> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: sript (Perl) test code needed (was: How to build JDK15 on AMD64 with FreeBSD?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 10:29:29 -0000 # obrien@freebsd.org / 2005-06-29 15:10:47 -0700: > On Sat, Jun 25, 2005 at 10:23:56PM -0600, Greg Lewis wrote: > > and follow the instructions. There is one caveat on amd64 -- one of the > > build commands will fail strangely (this is a bug in the Linux emulation > > on amd64 as far as I can determine). > > I know this should be trivial to do in perl and maybe someone here has the > time to hack it up. I want a small test script (actually some other > scripting language than perl preferred). > > The script should run the following commands until an error is returned: > > ls > ls . > ls ./ > ls ./. > ls ././ > ls ././. > ls ./././ > etc... > > and when the error occurs print out the length of the command line. > I want to get the bottom of the "command too long" issue that causes too > much trouble deploying Java on FreeBSD/AMD64. This prints the length of the argument (add 3 for "ls "), works in zsh: setopt ksh_arrays p=; i=0; c=(. /); while ls $p; do p=$p${c[i++ % 2]}; done >/dev/null 2>&1; echo $i ${#p} -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991