From: stan <stanl@cox.net>
To: Thierry Vignaud <tvignaud@mandriva.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Jaroslav Kysela <perex@suse.cz>
Subject: Re: compilation faillure
Date: Fri, 31 Aug 2007 10:14:00 -0700 [thread overview]
Message-ID: <46D84C58.8090800@cox.net> (raw)
In-Reply-To: <m2veavhlt5.fsf@vador.mandriva.com>
Thierry Vignaud wrote:
> Jaroslav Kysela <perex@suse.cz> writes:
>
>
>> Oops, configure script does not detected location of python C header files.
>> Fixed in HG.
>>
>> You may disable building of python code with --disable-python and wait for
>> 1.0.15rc2.
>>
>
> --disable-python has no effect
> --disable-python & --enable-python breaks at the exact same point...
> _______________________________________________
>
>
Hi,
When I compile the snapshots on Fedora they fail with python errors
unless I go to the /usr/include directory and create a symbolic link: ln
-s python2.5 python
i.e. create a generic python link to the version specific include
directory. Your system might need something similar.
next prev parent reply other threads:[~2007-08-31 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 9:14 ALSA 1.0.15rc1 Jaroslav Kysela
2007-08-31 10:02 ` Thierry Vignaud
2007-08-31 10:05 ` Thierry Vignaud
2007-08-31 10:39 ` Jaroslav Kysela
2007-08-31 13:31 ` Thierry Vignaud
2007-08-31 12:25 ` compilation faillure (was: Re: ALSA 1.0.15rc1) Thierry Vignaud
2007-08-31 13:19 ` Takashi Iwai
2007-08-31 13:22 ` compilation faillure Thierry Vignaud
2007-08-31 13:25 ` Jaroslav Kysela
2007-08-31 13:24 ` compilation faillure (was: Re: ALSA 1.0.15rc1) Jaroslav Kysela
2007-08-31 13:32 ` compilation faillure Thierry Vignaud
2007-08-31 14:42 ` Takashi Iwai
2007-08-31 17:14 ` stan [this message]
2007-08-31 15:23 ` ALSA 1.0.15rc1 Elimar Riesebieter
2007-08-31 17:49 ` Elimar Riesebieter
2007-09-01 8:07 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46D84C58.8090800@cox.net \
--to=stanl@cox.net \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
--cc=tvignaud@mandriva.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox