compile problems
Greetings all! I've tried this question in the "alsa user" group without success, but was pointed in the direction of this mailing list. Currently I'm trying to compile the alsa packages to get it compiled for a custom Linux distro. I'm not having any problems compiling the alsa-lib package, but when I try to compile alsa-utils, I keep getting the following error:
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.
To provide more details about the situation, I'm using an existing distro (Kubuntu 9.10) to build the alsa packages and are using the /opt/staging/alsa directory to compile and "install" to (using the DESTDIR parameter). Seeing as how this is a staging directory and not the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the /opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?
Thanks,
Dave
On 27/06/2011, David Henderson <[email protected]> wrote:
[...]
Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.
Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Signature · 4 lines
Adrian. http://ovejafm.com http://elesquinazotango.com.ar http://www.elarteylatecnologia.com.ar
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?
Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version >= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/ alisp.h asoundef.h asoundlib.h conf.h control_external.h control.h error.h global.h hwdep.h iatomic.h input.h mixer_abst.h mixer.h output.h pcm_external.h pcm_extplug.h pcm.h pcm_ioplug.h pcm_old.h pcm_plugin.h pcm_rate.h rawmidi.h seq_event.h seq.h seqmid.h seq_midi_event.h sound/ timer.h version.h
Thoughts? Thanks - Dave
Quoted 1 line · David Henderson
On 06/27/2011 09:35 AM, Adrian Pardini wrote:
[...]
Quoted 11 lines
Quoted 3 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for libasound headers version >= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/
My bad, here it works using ./configure --with-alsa-inc-prefix=/usr/include/alsa/ so I think you should use ./configure --with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa/.
If you are not in a hurry I can try to replicate your directory
structure when I get back to home. Also you may have to set the LDFLAGS environment variable to point to where your libraries are being installed under /opt
Signature · 4 lines
Adrian. http://ovejafm.com http://elesquinazotango.com.ar http://www.elarteylatecnologia.com.ar
On 27/06/2011, Adrian Pardini <[email protected]> wrote:
[...]
Quoted 3 lines
Also you may have to set the
LDFLAGS environment variable to point to where your libraries are being installed under /opt
--with-alsa-prefix looks more suitable. Maybe --with-alsa-prefix=opt/staging/alsa/var/ is all you need.
Signature · 4 lines
Adrian. http://ovejafm.com http://elesquinazotango.com.ar http://www.elarteylatecnologia.com.ar
Quoted 13 lines · Adrian Pardini
Quoted 1 line · David Henderson
On 06/27/2011 09:35 AM, Adrian Pardini wrote:
[...]
Quoted 10 lines
Quoted 3 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/
Quoted 8 lines
My bad, here it works using ./configure --with-alsa-inc-prefix=/usr/include/alsa/ so I think you should use ./configure --with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa/.
If you are not in a hurry I can try to replicate your directory
structure when I get back to home. Also you may have to set the LDFLAGS environment variable to point to where your libraries are being installed under /opt
Thanks for the continued help Adrian. I tried the adjusted configure parameter value, but it's still giving the same error message. Currently I'm in no rush, so let me know once you're able to get home. Also, if you need my compiled version of the alsa-lib package (or any other info), let me know.
Thanks,
Dave
Quoted 9 lines · Adrian Pardini
On 27/06/2011, Adrian Pardini<[email protected]> wrote:
[...]Quoted 3 lines
Also you may have to set the
LDFLAGS environment variable to point to where your libraries are being installed under /opt--with-alsa-prefix looks more suitable. Maybe --with-alsa-prefix=opt/staging/alsa/var/ is all you need.
Ok, I tried using this configure parameter instead of the --with-alsa-inc-prefix, but it's still bombing. I even tried compiling using each sub-directory as the value until the actual value was the entire path to where the header files were stored - each providing the same error message. One thing I did notice was by using the different configure parameter, the output was slightly different:
using --with-alsa-inc-prefix=...
<snip>
checking for ALSA CFLAGS... -I/opt/staging/alsa/var checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version >= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.
using --with-alsa-prefix=...
<snip>
checking for ALSA CFLAGS...
checking for ALSA LDFLAGS... -L/opt/staging/alsa/var -lasound -lm -ldl -lpthread
checking for libasound headers version >= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.
Do I still need to adjust the LDFLAGS variable since it looks like it's passing that value to it already?
Thanks,
Dave
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 68 lines · David Henderson
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version >= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.
Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/
Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's /opt/staging/alsa/var/share/include.
But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Takashi
Quoted 70 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 66 lines · David Henderson
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/
Quoted 8 lines
Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Takashi
Thanks for the additional help Takashi! I've tried that as well without any luck - still errors out at the same place and with the same message. I know that some of the paths are non-traditional, but there were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...
Dave
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 79 lines · David Henderson
Quoted 77 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 66 lines · David Henderson
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Quoted 5 lines
Quoted 1 line
Takashi
Thanks for the additional help Takashi! I've tried that as well without any luck - still errors out at the same place and with the same message.
Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.
Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that /opt/staging/alsa is a prefix for some build-root. But /var/share is weird. If any, it should be /usr/share.
Takashi
Quoted 94 lines · Takashi Iwai
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 74 lines · David Henderson
Quoted 73 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 66 lines · David Henderson
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.Quoted 8 lines
Quoted 5 lines
But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Takashi
Thanks for the additional help Takashi! I've tried that as well without any luck - still errors out at the same place and with the same message.
Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...
Quoted 7 lines
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that
/opt/staging/alsais a prefix for some build-root. But/var/shareis weird. If any, it should be/usr/share.Takashi
I checked in the log file, but I didn't notice anything that gave an indication as to the failure. Is there any spot in particular to look as the log just ends with "configure: exit 1", but everything above it just appears to be bash-styled variable assignments.
I ended up using the following configure parameters, but with the same results:
--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa
--with-alsa-prefix=/opt/staging/alsa/lib
and I've confirmed that the appropriate files reside in the passed directories.
Obviously the traditional directory layout is /usr/share, but the distro doesn't have a /usr directory. As a result, the directories that were under that parent directory had to be moved. The chosen spot for some of them was /var (although the header files could have been moved to /lib/... perhaps). At any rate, that's where the files are located.
Dave
At Mon, 27 Jun 2011 12:30:40 -0400,
Quoted 104 lines · David Henderson
Quoted 94 lines · Takashi Iwai
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 74 lines · David Henderson
Quoted 73 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 66 lines · David Henderson
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.Quoted 8 lines
Quoted 5 lines
But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Takashi
Thanks for the additional help Takashi! I've tried that as well without any luck - still errors out at the same place and with the same message.
Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...Quoted 7 lines
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that
/opt/staging/alsais a prefix for some build-root. But/var/shareis weird. If any, it should be/usr/share.Takashi
Quoted 8 lines
I checked in the log file, but I didn't notice anything that gave an indication as to the failure. Is there any spot in particular to look as the log just ends with "configure: exit 1", but everything above it just appears to be bash-styled variable assignments.
I ended up using the following configure parameters, but with the same results:
--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa
No, it must be /opt/staging/alsa/var/share/include
Takashi
Quoted 122 lines · David Henderson
Quoted 101 lines · Takashi Iwai
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 84 lines · David Henderson
Quoted 83 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 72 lines · David Henderson
Quoted 20 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 12 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore
mentioned problem because the alsa-utils package is looking under /...
for the header files instead of the/opt/staging/alsa/... directory. Is
there a compile-time parameter that I can use so that alsa-utils looks
in the staging directory for the header files - just during the compile
phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Quoted 5 lines
Quoted 1 line
Takashi
Thanks for the additional help Takashi! I've tried that as well without
any luck - still errors out at the same place and with the same message.Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...Quoted 7 lines
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that
/opt/staging/alsais a prefix for some build-root. But/var/shareis weird. If any, it should be/usr/share.Takashi
I checked in the log file, but I didn't notice anything that gave an indication as to the failure. Is there any spot in particular to look as the log just ends with "configure: exit 1", but everything above it just appears to be bash-styled variable assignments.
I ended up using the following configure parameters, but with the same results:
--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa
--with-alsa-prefix=/opt/staging/alsa/lib
and I've confirmed that the appropriate files reside in the passed directories.
Quoted 8 lines
Obviously the traditional directory layout is
/usr/share, but the distro doesn't have a /usr directory. As a result, the directories that were under that parent directory had to be moved. The chosen spot for some of them was /var (although the header files could have been moved to/lib/... perhaps). At any rate, that's where the files are located.Dave
bump for help
At Tue, 28 Jun 2011 10:12:16 -0400,
Quoted 131 lines · David Henderson
Quoted 129 lines · David Henderson
Quoted 101 lines · Takashi Iwai
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 84 lines · David Henderson
Quoted 83 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 72 lines · David Henderson
Quoted 20 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 12 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore
mentioned problem because the alsa-utils package is looking under /...
for the header files instead of the/opt/staging/alsa/... directory. Is
there a compile-time parameter that I can use so that alsa-utils looks
in the staging directory for the header files - just during the compile
phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Quoted 5 lines
Quoted 1 line
Takashi
Thanks for the additional help Takashi! I've tried that as well without
any luck - still errors out at the same place and with the same message.Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...Quoted 7 lines
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that
/opt/staging/alsais a prefix for some build-root. But/var/shareis weird. If any, it should be/usr/share.Takashi
I checked in the log file, but I didn't notice anything that gave an indication as to the failure. Is there any spot in particular to look as the log just ends with "configure: exit 1", but everything above it just appears to be bash-styled variable assignments.
I ended up using the following configure parameters, but with the same results:
--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa
--with-alsa-prefix=/opt/staging/alsa/lib
and I've confirmed that the appropriate files reside in the passed directories.Obviously the traditional directory layout is
/usr/share, but the distro doesn't have a /usr directory. As a result, the directories that were under that parent directory had to be moved. The chosen spot for some of them was /var (although the header files could have been moved to/lib/... perhaps). At any rate, that's where the files are located.
Quoted 3 lines
Quoted 1 line
Dave
bump for help
Did you read my last post?
Takashi
Quoted 131 lines · Takashi Iwai
At Tue, 28 Jun 2011 10:12:16 -0400,
Quoted 129 lines · David Henderson
Quoted 128 lines · David Henderson
Quoted 101 lines · Takashi Iwai
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 84 lines · David Henderson
Quoted 83 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 72 lines · David Henderson
Quoted 20 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 12 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore
mentioned problem because the alsa-utils package is looking under /...
for the header files instead of the/opt/staging/alsa/... directory. Is
there a compile-time parameter that I can use so that alsa-utils looks
in the staging directory for the header files - just during the compile
phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Quoted 5 lines
Quoted 1 line
Takashi
Thanks for the additional help Takashi! I've tried that as well without
any luck - still errors out at the same place and with the same message.Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...Quoted 7 lines
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that
/opt/staging/alsais a prefix for some build-root. But/var/shareis weird. If any, it should be/usr/share.Takashi
I checked in the log file, but I didn't notice anything that gave an indication as to the failure. Is there any spot in particular to look as the log just ends with "configure: exit 1", but everything above it just appears to be bash-styled variable assignments.
I ended up using the following configure parameters, but with the same results:
--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsa
--with-alsa-prefix=/opt/staging/alsa/lib
and I've confirmed that the appropriate files reside in the passed directories.Obviously the traditional directory layout is
/usr/share, but the distro doesn't have a /usr directory. As a result, the directories that were under that parent directory had to be moved. The chosen spot for some of them was /var (although the header files could have been moved to/lib/... perhaps). At any rate, that's where the files are located.
Quoted 6 lines
Quoted 2 lines
Quoted 1 line
Dave
bump for help
Did you read my last post?
Takashi
Yes I did - as well as provide answers and questions in my reply above.
Dave
Am Dienstag, den 28.06.2011, 10:44 -0400 schrieb David Henderson:
Quoted 7 lines · Takashi Iwai
Quoted 4 lines
Quoted 1 line · David Henderson
bump for help
Did you read my last post?
Yes I did - as well as provide answers and questions in my reply above.
Takashi pointed out an error in your command and you did not reply to this message as far as I remember. Please take a look at the Web archive and fix your mail setup.
Thanks,
Paul
Quoted 6 lines · Paul Menzel
Am Dienstag, den 28.06.2011, 10:44 -0400 schrieb David Henderson:
Quoted 5 lines · Takashi Iwai
Quoted 3 lines
Quoted 1 line · David Henderson
bump for help
Did you read my last post?
Yes I did - as well as provide answers and questions in my reply above.
Quoted 8 lines
Takashi pointed out an error in your command and you did not reply to this message as far as I remember. Please take a look at the Web archive and fix your mail setup.
Thanks,
Paul
Ah! So he did! Must have gotten over looked - sorry!
Dave
Quoted 109 lines · Takashi Iwai
At Mon, 27 Jun 2011 12:30:40 -0400,
Quoted 107 lines · David Henderson
Quoted 94 lines · Takashi Iwai
At Mon, 27 Jun 2011 11:31:18 -0400,
Quoted 74 lines · David Henderson
Quoted 73 lines · Takashi Iwai
At Mon, 27 Jun 2011 09:56:37 -0400,
Quoted 66 lines · David Henderson
Quoted 14 lines · Adrian Pardini
On 27/06/2011, David Henderson<[email protected]> wrote:
[...]Quoted 5 lines
checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 7 lines
Seeing as how this is a staging directory and not
the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the/opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?Quoted 4 lines
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script.
Thanks for the help Adrian. I tried passing that parameter to the configure script and here's the below output:
checking for a BSD-compatible install...
/usr/bin/install-c checking whether build environment is sane... yes checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt.../usr/bin/msgfmt
checking for gmsgfmt.../usr/bin/msgfmt
checking for xgettext.../usr/bin/xgettext
checking for msgmerge.../usr/bin/msgmerge
checking for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu
checking for ld used by GCC.../usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for a BSD-compatible install.../usr/bin/install-c checking whether ln -s works... yes
checking for ALSA CFLAGS... -I/opt/staging/alsa checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.Quoted 2 lines
I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/Pass the root path to alsa/*.h to --with-alsa-inc-prefix option, i.e. in your case, it's
/opt/staging/alsa/var/share/include.Quoted 8 lines
Quoted 5 lines
But, the path is really odd and almost kidding (/share under /var...?) Is it really correct?
Takashi
Thanks for the additional help Takashi! I've tried that as well without any luck - still errors out at the same place and with the same message.
Then you should check config.log at the place error occurred. It contains more details.
I guess you'll have to pass also --with-alsa-prefix pointing to the path where your local libasound.so.2 is placed.Quoted 5 lines
I know that some of the paths are non-traditional, but there
were certain guidelines that had to be met with this custom distro. As a result, some of the directories had to get moved. That shouldn't be adding to the problem right? Since we're telling configure exactly where to locate the files...Quoted 7 lines
Well, it's still very strange path. The share sub-directory definitely doesn't belong under /var. I'd understand that
/opt/staging/alsais a prefix for some build-root. But/var/shareis weird. If any, it should be/usr/share.Takashi
I checked in the log file, but I didn't notice anything that gave an indication as to the failure. Is there any spot in particular to look as the log just ends with "configure: exit 1", but everything above it just appears to be bash-styled variable assignments.
Quoted 7 lines
Quoted 3 lines
I ended up using the following configure parameters, but with the same results:
--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include/alsaNo, it must be
/opt/staging/alsa/var/share/includeTakashi
Ok, I corrected the parameter value per your instructions above Takashi, but ended up with another compile error. I researched it online and found the resolution and it appears as though the source code compiled correctly. Thanks for your help (and everyone else who contributed)!
Sincerely,
Dave Henderson