use cvs udftools means what

use cvs udftools means what

[Pat LaVarre]

Anybody here know how to make the cvs udftools without error?

Bonehead newbie me, I fell into at least Three revolting kluges:

1) Into the cvs udftools/ I copy configure and config/ from
udftools-1.0.0b2/.

2) Also I copy all six of the files named Makefile.in.

3) Also I begin by accepting unchanged the Makefile initially composed
by `./configure`, but then after the first try at `make` fails with the
side effect of revising the Makefile, I then reestablish a line of the
original Makefile:

-SUBDIRS = libudffs mkudffs cdrwtool pktsetup udffsck wrudf doc udfct
+SUBDIRS = libudffs mkudffs cdrwtool pktsetup doc

Pat LaVarre

----- cvsudfmake script

tar -xzf udftools-cvs.tar.gz

mv -i udftools udftools-cvs

cd udftools-1.0.0b2
cp -idpr config configure ../udftools-cvs/
f=./Makefile.in; cp -idpr $f ../udftools-cvs/$f
f=./libudffs/Makefile.in; cp -idpr $f ../udftools-cvs/$f
f=./mkudffs/Makefile.in; cp -idpr $f ../udftools-cvs/$f
f=./cdrwtool/Makefile.in; cp -idpr $f ../udftools-cvs/$f
f=./pktsetup/Makefile.in; cp -idpr $f ../udftools-cvs/$f
f=./doc/Makefile.in; cp -idpr $f ../udftools-cvs/$f

cd ../udftools-cvs
./configure
grep '^SUBDIRS =' Makefile
SUBDIRS = libudffs mkudffs cdrwtool pktsetup doc
make
grep '^SUBDIRS' Makefile
cp -ip Makefile Makefile.old
<Makefile.old sed 's/^SUBDIRS.*/SUBDIRS = libudffs mkudffs cdrwtool
pktsetup doc/' >Makefile
diff -0 -u Makefile.old Makefile
make
make dist
ls -lrt *.tar.*

-----

That udftools-cvs.tar.gz you see mentioned I got thru a different
firewall via:

setenv CVSROOT :pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-udf
cvs login
cvs co udftools
cvs logout

Those four hints I got from my own "Re:  Fwd: udf folders pointing to
self and above" post:
http://marc.theaimsgroup.com/?l=linux-fsdevel&m=106691164821008

Re: use cvs udftools means what

[Pat LaVarre]

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
$

---