Please add the files
codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

To make myself more clear, I have ALL of the dependencies listed in the README installed. They are much higher versions than the requirements, I'm running the stable tree but I think Gentoo's software is a bit greener than the other distros this already works on.

I have experience with OSS software, but it tends to be grails/java rather than linux-native.

Sorry, this is my first attempt at making an ebuild of any sort, I will probably be a bit higher maintenance than we would all like

I will try to RTFM as much as possible, just need a nudge in the right direction here.

Actually, the problem is exactly that they are much higher.
Due to the way automake wrapper works, it doesn't work well for you.
Try running with Want_AUTOMAKE=1.11 - as long as automake files are compatible, it should help.

I don't know what exactly they're trying to do with that line, when you pipe to /dev/null on my system there is no more output. The way I read that, if it returns a nonzero result it dies.

Exactly. They run automake --version and discard any output that might be generated, including the subshell printing that it cannot find automake. If automake was found and understood the option --version, it should exit 0. If the child exits non-zero, either because automake was not found or the file found did not understand --version, then the error message is printed.

config.status: executing default-1 commands
config.status: executing libtool commands
Now type `make' to compile libuictlutf2
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.

Well, I'll tell you something - just for the kicks, I've downloaded the tarball.
Most of it didn't built for me, as I didn't have libbuftool, but I did get through configure phase...
though I didn't run that script, just 'autoreconf -f --install' in every dir with a configure.{in,ac} - only place were I needed more
was/were the dirs were the script required glib-gettextize.

If you have it working by hand, then it is time to record your work in an ebuild so that it is repeatable and can be managed by Portage. Your first post in the thread mentions an older ebuild, so we can use that as a starting point. Could you post that, including any changes you have made to it, and a record of all the commands you need to run starting from unpacking the source up through where you would run make install, including any arguments you might need to pass to make install? Given that, we can adjust the ebuild to include those commands at the right phases.

I cannot say for sure whether you installed it until you tell us exactly what commands you have run, what their output was, and whether or not you ran them as root. From your terse messages, I think you have not yet installed it.

A quick question with regards to your script: Where (e.g. what package) can we find debuild in the portage tree or any overlay for use with your script?

I have already installed dpkg, debianutils and debhelper and I still don't have debuild available.

I'm trying to get printing going to a Canon imageCLASS MF7470. I have gotten the source code compiled and installed (using all the techniques described in this thread; I used "WANT_AUTOMAKE=1.11 autoreconf -f --install" in each directory with a configure.[in,ac], updated the debian/control file with "amd64", uncommented the "dh_makeshlibs" line in debian/rules file and deleted all instances of "--enable-static", "--disable-static", "--enable-shared", and "--disable-shared" in the allgen.sh script), but any of the drivers I use from the UFRII package leaves me with a printout that only says:

Canon imageCLASS MF7470 wrote:

**** Unable to open initial device, quitting.

I'm pretty sure that something likely got missed, skipped or changed from the steps I took to get their code to compile, and would appreciate any help in getting this going.

TIA._________________________________________

"Three minutes' thought would suffice to find this out;
but thought is irksome and three minutes is a long time."

Still not seeing where the issue actually lies yet, but I just pulled the full debug output from trying to do a print of a CUPS test page, so I will see if I can find what device or file it thinks it's missing.

Until then, I will go back to the Canon imageRunner 7105 foomatic/pxlmono driver that will allow me to print one copy of one job at a time.

Interesting to note: When searching Google for "linux CUPS 'unable to open initial device'", the two manufacturers that come up are the two that have both put out their own driver code; HP & Canon. Unfortunately for me, HP seems to exhibit the behavior more often than Canon.

I'll let you know what I find._________________________________________

"Three minutes' thought would suffice to find this out;
but thought is irksome and three minutes is a long time."

I know it's been a while since there was any activity on this thread, but I had to revisit this issue again and am happy to report that thanks to pacho and the folks down at support-au.canon.com.au, we have working ebuilds for these drivers...