lir03-22b -lasound(32) in Ubuntu 10.04_64 --- (Re: lir03-22a (32/64) on Ubuntu-10.04_64 --- Re: [Linrad] Update for Linux
'Zaba' OH1ZAA
Leif-san!
The 32-bit library problem maybe an Ubuntu-issue in 10.04_64
I noticed that I can find some libraries much more clearly (in plain language) in the Ubuntu Software Center (Applications Tab).
Software center claims that that both 32/64-bit libasound are already present, but ./configure --with-help differs in opinion.
/usr/bin/ld: skipping incompatible ... libasound.so when searching for -lasound
Four messages of that sort ... finally /usr/bin/ld: cannot find -lasound
Then it explains how to apt-get install the ALSA ... but it is already there (confirmed by apt-get and Ubu Soft Center)
I do not remember in what order I installed various packages in Ubuntu 10.10_64, but there were no problems like this.
Cheers/73, "Zaba" OH1ZAA
'Zaba' OH1ZAA [za...@dlc.fi] wrote:
>
> Hi Leif,
>
>
> Compiled 03-22b both 32/64 on Ubuntu 10.04_64. Both work in some way on laptop MB-audio.
>
>
> /configure mentions libasound 32-bits missing indeed, but I remembered it installed.
>
>
> And with apt-get install libasound2-dev it suggests indeed zero need for additional files.
>
>
> However, once (just once) it suggested a manual install (?) despite being present.
>
>
> /configure mentions still a long list of messages for 32-bit libasound.so (too many to
> quickly comprehend for a newcomer, also mention about symbolic links, etc.).
>
>
> Too late or early for additional experiments .... zzzz... 73, "Zaba" OH1ZAA
>
>
> P.S. In early days of Linrad spent some money on (4-Front?) OSS-software; therefore
> thought that Ubuntu was alsa only these days (and surprised about alsa-oss option).
>
>
> Generally speaking also wondering about requirement for installing -ljack before pa
> (and how to know and correct if reversed; so it is not only about dependencies...).
>
>
> CPU is TL-58 by the way (just for precision.. not TL-65)
>
>
> Leif Asbrink [le...@sm5bsz.com] wrote:
>
> > Hi Zaba,
> >
> > > Thanks for the 03-22a update; also xsys.c seems repaired now.
> > > Compiling without protest.
> > >
> > >
> > > Removed all old versions from the laptop, and compiled first
> > > xlinrad64 - then xlinrad
> > >
> > >
> > > First run with ./xlinrad64 ---- configured audio and changed
> > > (Y) from alsa-oss to native alsa.
> > Oooh! That was not the way I intended it.
> >
> > Even very simple things tend to go wrong when I make just
> > a little change without really testing it.
> >
> > I have now uploaded 03.22b
> >
> > > Then ran ./xlinrad and configured audio. It says it is
> > > running alsa-oss but there is no option
> > > (Y-parameter in U menu) to change to native alsa. Is
> > > there still something missing here?
> > The 32 bit libasound.so could be missing. If so,
> > the configure script should give that info.
> >
> >
> > > Resulting audio spectra look slightly different on both versions.
> > ?????????
> > Spectra should be identical. Very important!!!!
> >
> > 73
> >
> > Leif
> >
>
>
Leif Asbrink
> Software center claims that that both 32/64-bit
> libasound are already present, but ./configure --with-help differs in opinion.
>
>
> /usr/bin/ld: skipping incompatible ... libasound.so when searching for -lasound
Try to run ldconfig
If that does not help, please use this:
locate libasound.so
(You may have to run sudo updatedb first)
Maybe Ubuntu has moved the file to a new location.....
These are the directories that Linrad looks in:
char *dirs[]={"/lib"
"/lib32",
"/lib64",
"/usr/lib",
"/usr/lib32",
"/usr/lib64",
"/usr/lib32/lib",
"/usr/local/lib",
"/usr/local32/lib",
"/emul/ia32-linux/lib",
"/emul/ia32-linux/usr/lib",
"/usr/PCBSD/local/lib",
"/usr/X11R6/lib",
"X"};
Add any new directory invented by Ubuntu to this list
in libfind1.c ("X" has to be the last line) and try
configure again.
73
Leif / SM5BSZ
'Zaba' OH1ZAA
Hi Leif,
Steno: ldconfig is taken silently in console without response (good sign?)
libasound.so in /usr/lib found by locate before and after updatedb
The directory listing is exactly the same as your libfind1.c contents and libasound.so in in one of these
No change in ./configure or xlinrad after new compilation... any need for symbolic links?
Cheers/73, "Zaba" OH1ZAA
Leif Asbrink
> Steno: ldconfig is taken silently in console without response (good sign?)
I have never seen it report anything.
> libasound.so in /usr/lib found by locate before and after updatedb
That is the 64 bit version.
There should be one more. In one of these directories (or elsewhere)
/lib32
/usr/lib32
/usr/lib32/lib
/usr/local32/lib
/emul/ia32-linux/lib
/emul/ia32-linux/usr/lib
There should be symbolic links like this on both places:
libasound.so -> libasound.so.2.0.0
libasound.so.2 -> libasound.so.2.0.0
libasound.so.2.0.0
The easiest way to install the 32 bit package libxyz is like this:
1) Arrange for two partitions (or more) on your hard disk.
(or have them on separate computers)
2) Install the 32 bit OS on one and the 64 bit OS on the other.
3) Upgrade both installations to the latest state (or some other
well defined state)
4) Install libxyz on both partitions
5) copy the 32 bit libxyz.so.2.0.2 to the appropriate lib32/ia32
directory of the 64 bit installation and create the two symbolic
links there.
This also works for things that you have to install from source code.
libperseus, libusb-1.0, libsoft66, svgalib and others.
73
Leif / SM5BSZ