From fnaumann@mail.cs.uni-magdeburg.de Wed Feb 11 12:33:28 2004 Message-ID: <402A1272.6090801@imperia.net> Date: Wed, 11 Feb 2004 12:30:58 +0100 From: Guido Flohr User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: de, ru, ar, en-us, en, fr MIME-Version: 1.0 To: Mint List Subject: Re: [MiNT] Mintlib bug? References: <1076369996.32057.6.camel@llama> In-Reply-To: <1076369996.32057.6.camel@llama> Content-Type: text/plain; charset=ISO-8859-15; format=flowed X-Virus-Scanned: by amavisd-new using F-Secure Antivirus at imperia.net Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: guido@imperia.net Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i1BBXPt08168 Hi, Mark Duckworth wrote: > Hello guys, > > I've compiled the tar specs that were already available against the new > mintlib and had some issues as previously discussed. A refresher: > > root@washi:/root>tar ztvf st157n.tar.gz > tar (child): Cannot exec gzip: No such file or directory > tar (child): Error is not recoverable: exiting now > tar: Child returned status 2 > tar: Error exit delayed from previous errors Try to locate the origin of the error message "Cannot exec %s" in the tar sources. It will be in the child branch of a call to fork(). Then find out the exact arguments that exec*() is called with. It would also be helfpul if you partially dump out the environment of the parent and the child process (at least the variables PATH and UNIXMODE) before and after fork(). Ciao Guido -- Imperia AG, Development Leyboldstr. 10 - D-50354 Hürth - http://www.imperia.net/