Re: [Alsa-user] Problem Installing ALSA 0.9.1 on Redhat 7.0--unresolved symbol
Brought to you by:
perex
From: Gain P. M. <the...@sl...> - 2005-03-23 09:57:02
|
Clemens Ladisch wrote: >Gain Paolo Mureddu wrote: > > >>Hmmm, an observation: The CC variable is only affecting the >>./configure script. >> >> > >And the configure script writes the CC definition into its makefiles, >so it does affect the subsequent compiler invocations. > >Where did you observe it using the another compiler? (This would be a >bug.) > > >Regards, >Clemens > > > > > > Back in the Fedora Core 1 days, the distro came with two compilers, regular gcc 3.3 (gcc command) and gcc 3.2 (gcc32). Problem was that the kernel was built with gcc 3.2 and calling naturally ./configure would set gcc (3.3) as the compiler, this ended in those dreaded unresolved symbols. However setting CC="gcc32" solved this problem with the official Fedora kernels (unless, of course, you built a kernel [or recompiled the official one] with gcc 3.3). As unlikely as this may sound, I had several times problems if I just set CC="gcc32" for ./configure. The driver would compile using gcc instead of gcc32 for some reason, so I had to actually export that variable *before* running ./configure. Call it a bug in the distro (I'm sure it was some of that) or in gmake or autogen or auto-make or whatever, but at least *I* had this problem recurrently (can't say about others, though). |