From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: use cvs udftools means what
Date: 24 Oct 2003 15:15:04 -0600 [thread overview]
Message-ID: <1067030104.16779.22.camel@patehci2> (raw)
In-Reply-To: <1066929415.2276.52.camel@patehci2>
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
$
---
prev parent reply other threads:[~2003-10-24 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 17:16 use cvs udftools means what Pat LaVarre
2003-10-24 21:15 ` Pat LaVarre [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1067030104.16779.22.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox