Skip to contentSkip to conversation

: AM_PATH_ALSA does not set prefix properly

ALSA - utils 0000936 [email protected] 1 participant 1 message Jul 8, 2005

lore
Share & tools
lore
#0 lore raw

The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=936>
======================================================================
Reported By: starling
Assigned To:
======================================================================

Project:                    ALSA - utils
Issue ID:                   936
Category:                   aconnect
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Resolution:                 won't fix
Fixed in Version:           
======================================================================
Date Submitted:             02-23-2005 22:39 CET
Last Modified:              07-08-2005 10:38 CEST

======================================================================
Summary: AM_PATH_ALSA does not set prefix properly
Description:
When configure calls AM_PATH_ALSA, it wrongly assumes that --with-alsa-prefix specifies the location of the library, not the prefix of alsa. In addition, --with-alsa-inc-prefix does not properly modify CFLAGS. The result is that every configure where alsa-lib is installed outside the hardcoded include/lib paths fails unconditionally.
======================================================================

----------------------------------------------------------------------
starling - 02-26-05 03:31
----------------------------------------------------------------------
I'm not sure how the number of bits per character would break my patch. As for it being an incompatible configure option, I don't see how the current configure can work at all. With the current (unpatched) alsa.m4, any installation outside of /usr, of alsa-utils will fail. With the patch applied it changes the interface, but installations into /usr (or /usr/local depending on your compiler) will not fail because they are checked regardless of which -I/-L flag is passed to the compiler. So the only configurations that would not be backwards compatible, and would become 'broken', are the configurations that do not work in the first place (for no good reason). Nothing to worry about.

Unless you know something I don't, which is likely. 64-bit whosamawhudda?
You mean like Unicode paths?

Oh... and anyone downloading alsa-lib would get the new alsa.m4, so I think it's not /too/ much trouble for people to get it. :) That's the nice thing about aclocal: even people who don't have the patched alsa.m4 will still be able to use the AM_PATH_ALSA macro the same way, complete with the current inability to install into non hard coded compiler prefixes.

----------------------------------------------------------------------
tiwai - 03-09-05 19:09
----------------------------------------------------------------------
--with-alsa-prefix is the path of alsa-library, and --with-alsa-inc-prefix is the path of alsa headers.
So, you can simply pass like

   ./configure --with-alsa-prefix=/somehwere/lib \
      --with-alsa-inc-prefix=/another/include

So, it does work. Only its option name is weird.

But changing the option name is not a good idea since this macro is already used widely as I wrote. Imagine if you change the option and you
write a configure to run both new and slightly-old ALSA versions? Such
an incompatibility is indeed a big problem!

About 64bit: it's a path for 64bit binaries to avoid conflict with 32bit ones. See LSB for details.

Issue History
Date Modified Username Field Change
======================================================================

02-23-05 22:39 starling       New Issue                                    
02-23-05 22:39 starling       File Added: alsa.diff                        
02-24-05 22:02 tiwai          Note Added: 0003726                          
02-26-05 03:28 starling       Note Added: 0003738                          
02-26-05 03:31 starling       Note Edited: 0003738                         
03-09-05 19:09 tiwai          Note Added: 0003844                          
03-31-05 20:39 jdthood        Status                   new => resolved     
03-31-05 20:39 jdthood        Resolution               open => won't fix   
07-08-05 10:38 perex          Status                   resolved => closed  

======================================================================

-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar