#9 aclocal

[Jon]

You've hardcoded aclocal-1.6 into the make...*?#! Thus,
it bombs out. Whatever version of automake you happen
to be running will install a duplicate file called
'aclocal'.. Actually, 'aclocal-$VERSION' is a hardlink
to 'aclocal'... Checking for 'aclocal' is sufficent...

[root@jaguar ~/ ] ls /usr/bin/aclocal*
/usr/bin/aclocal /usr/bin/aclocal-1.9

Also, after working around that, I get:

In file included from ccd2iso.c:28:
clonecd.h:32: warning: `packed' attribute ignored
clonecd.h:39: warning: `packed' attribute ignored
clonecd.h:57: warning: `packed' attribute ignored

on the make... I'm sure it's not too big of a deal..
Don't know.

gcc-3.4.4
glibc-2.3.4
linux-libc-headers-2.6.8.1
linux-2.6.11.11

[Jon]

Logged In: YES
user_id=999600

Additionally, I made with:

cd src/
gcc -o ccd2iso ccd2iso.c

It seemed the quickest way to bypass your aclocal oversight

[Nobody/Anonymous]

Logged In: NO

I also ran into the aclocal problem but putting a soft link
to aclocl-1.6 from aclocl-1.9 gives tons of warnings.

Then it bombs out looking for automake-1.6 arggg.

[Nobody/Anonymous]

Logged In: NO

Here's the cure for this problem;

In both Makefiles /ccd2iso and src edit the MAkefiles
and remove -1.6 from the ACLOCAL and AUTOMAKE variables.
Then congiure and make... done

[Nobody/Anonymous]

Logged In: NO

No, it's not "hardcoded". It's just that when he
bootstrapped the project, he used automake 1.6. My Dapper
has automake 1.4 by default, see.

The autotools use some configuration files for the project.
If it were hardcoded, it'd be there in the configure.in
file, which apparently isn't.

So you can just do:
aclocal
autoconf
automake
./configure
make
make install

Yeah, you'll need the automake, autoconf and autotool
packages to run this.

[Nobody/Anonymous]

Logged In: NO

Oops, silly me, it's libtool, not autotools =D.

Autotool projects use also the Makefile.am files too for
configuration, just in case you're curious.