From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: Re: use cvs udftools means what Date: 24 Oct 2003 15:15:04 -0600 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1067030104.16779.22.camel@patehci2> References: <1066929415.2276.52.camel@patehci2> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out1.iomega.com ([147.178.1.82]:1518 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S262627AbTJXVP0 (ORCPT ); Fri, 24 Oct 2003 17:15:26 -0400 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id 30F6A1F10 for ; Fri, 24 Oct 2003 15:15:25 -0600 (MDT) To: linux-fsdevel@vger.kernel.org In-Reply-To: <1066929415.2276.52.camel@patehci2> List-Id: linux-fsdevel.vger.kernel.org Success! Kindly offline I received notice: Since at least today (2003-10-24), cvs udftools have included a udftools/bootstrap script, designed to construct a `configure` script for you which then in turn will construct your 'Makefile'. Make success follows directly, as you can see in the following tty log. Kindly offline I'm assured, letting udfct bomb out for now is ok. Pat LaVarre --- 1. At a host whose firewall passes thru cvs: $ export CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-udf $ cvs login (Logging in to anonymous@cvs.sourceforge.net) CVS password: $ cvs co udftools ... $ cvs logout ... $ mv -i udftools/ udftools-cvs/ $ tar -czf udftools-cvs.tar.gz udftools-cvs/ $ --- 2. Thereafter in places where that .tar.gz goes: $ tar -xzf udftools-cvs.tar.gz $ $ ln -s udftools-cvs udftools-cvs $ $ cd udftools-cvs $ $ find . -perm +111 -type f ./bootstrap ./deb/rules $ $ cat ./bootstrap #!/bin/sh find . \( -name autom4te.cache -o -name libtool \) -exec rm -r {} \; aclocal libtoolize --force --copy autoheader automake --add-missing --copy autoconf $ $ ./bootstrap ... $ $ ./configure ... $ $ make Making all in libudffs ... Making all in mkudffs ... Making all in cdrwtool ... Making all in pktsetup ... Making all in udffsck ... Making all in wrudf ... Making all in doc make[1]: Entering directory `/home/pat/k/udftools-cvs/doc' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/pat/k/udftools-cvs/doc' Making all in udfct make[1]: Entering directory `/home/pat/k/udftools-cvs/udfct' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/pat/k/udftools-cvs/udfct' make[1]: Entering directory `/home/pat/k/udftools-cvs' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/home/pat/k/udftools-cvs' $ $ find . -perm +111 -type f | grep -v '^..config' ./bootstrap ./cdrwtool/cdrwtool ./deb/rules ./mkudffs/mkudffs ./pktsetup/pktsetup ./udffsck/udffsck ./wrudf/wrudf ./libtool $ --- 3. Thereafter when $PATH includes mkudffs and udfct udf_test $ sudo dd of=dd.bin if=/dev/zero bs=1M seek=255 count=1 1+0 records in 1+0 records out $ $ sudo losetup /dev/loop0 dd.bin $ $ sudo mkudffs /dev/loop0 start=0, blocks=16, type=RESERVED ... start=131071, blocks=1, type=ANCHOR $ $ sudo udf_test -udf 2.01 /dev/loop0 | egrep -i '(error|warning|note|count):' Error count: 0 total occurrences: 0 Warning count: 0 total occurrences: 0 $ $ sudo losetup -d /dev/loop0 $ ---