------------------------- Tuesday, March 25, 2008, 4:39:44 PM, you wrote: > On Monday 24 March 2008 11:52, Peter Toye wrote: >> Best regards, >> >> Peter >> mailto:alsa@xxxxxxxxx >> www.ptoye.com >> >> ------------------------- >> >> Sunday, March 23, 2008, 4:05:58 PM, you wrote: >> > On Sunday 23 March 2008 16:14, Peter Toye wrote: >> >> Following my driver make problem, Lee Revell sorted me out, but I still >> >> had some problems. so decided to rebuild it all again. >> >> >> >> But when making the utils I got: >> >> >> >> Making install in po >> >> make[2]: Entering directory >> >> `/home/ptoye/ALSA/utils/alsa-utils-1.0.16/alsaconf/po' mv: cannot stat >> >> `t-ja.gmo': No such file or directory >> >> make[2]: *** [ja.gmo] Error 1 >> > Note sure about that. It's a while since I installed Kubuntu, and can't >> > remember what basic development packages were installed as part of the >> > Kubuntu install. Before I upgraded the alsa driver, I installed the >> > following packages: >> > kernel headers for the kernel (presuming the running kernel) that you are >> > upgrading the alsa driver against. >> > kernel-package >> > build essential (may be a hyphen between build, and essential) >> >> I'll check this out. But if you really have to know about large numbers of >> preconditions for installing a package, this should be in the README or >> INSTALL files for the package, not have to be winkled out of friendly users >> in its mail list! > The problem is, that apart from the kernel-headers, the other package/s that > need to be installed are distro specific. OIC >> > All the best. >> > >> > Nigel. >> > >> >> Thanks in advance, >> >> >> >> Peter Toye >> >> mailto:alsa@xxxxxxxxx >> >> www.ptoye.com > When I run ./configure for the alsa-utils, it checks for the package gawk. I'd > installed that a while back for something else I was installing, but I'd > install it, and also libasound2-dev. Another package I had installed was > binutils, and it may be worth installing that. I'm not trying to get you to > needlessly install packages, just for the sake of it, but am puzzled why when > doing sudo make install, the ja.gmo file can't be found. On the face of it, > it looks like configure hasn't done all it should do, and would explain why > the make install is failing. > Just a side note in addition to the suggested packages above. make sure with > synaptic that gettext, and gettext-base are installed. I think they are > installed as part of the initial install of Ubuntu/Kubuntu, but it's worth > checking. > Would you run ./configure, and paste the output in your reply, or attach it as > a .txt file. > You could also look in your alsa-utils-1.0.16 directory. Open the alsaconf/po > directory. You should see 2 files ja.gmo (japanese), and ru.gmo (russian) if > make install is doing it's job. Before you run ./configure (for the first > time), there are only 3 files in the alsaconf/po directory, as below: > ja.po > ru.po > Makefile.in > When you run ./configure, configure, at the end of it's run creates a bunch of > Makefiles, including one in alsaconf/po. Now you should see 4 files as below: > ja.po > ru.po > Makefile.in > Makefile (the new one) > Now an sudo make install should result in 2 extra files in alsaconf/po, as > below: > ja.gmo > ru.gmo > Both of these are identified as "type unknown", but should now exist for the > make install to run to completion. > Peter. I will send you offlist my ./configure output, and you can compare it > with yours. > All the best. > Nigel. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
