From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000350]: Alsa Installation probleme
Date: Tue, 29 Jun 2004 18:27:13 +0200 [thread overview]
Message-ID: <c3d50bcb662348cb49676bdc23227975@bugtrack.alsa-project.org> (raw)
The following bug has been SUBMITTED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000350
======================================================================
Reported By: miro911
Assigned To: perex
======================================================================
Project: ALSA - driver
Bug ID: 350
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution:
Kernel Version:
======================================================================
Date Submitted: 06-29-2004 18:27 CEST
Last Modified: 06-29-2004 18:27 CEST
======================================================================
Summary: Alsa Installation probleme
Description:
hi everbody.Hi have try to install the news version of alsa on mandarake
10.0 and i have a probleme during the configure sripts some one cane help
my ??
error:[mathieu@mathieu alsa]$ ./configure
checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
Into Config.log:
## --------- ##
## Platform. ##
## --------- ##
hostname = mathieu
uname -m = i686
uname -r = 2.6.3-7mdksmp
uname -s = Linux
uname -v =
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000001 SMP
Wed Mar 17 14:24:28 CET 2004
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/bin
PATH: /bin
PATH: /usr/bin
PATH: /usr/local/bin
PATH: /usr/X11R6/bin/
PATH: /usr/games
PATH: /home/mathieu/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1309: checking for gcc
configure:1338: result: no
configure:1389: checking for cc
configure:1418: result: no
configure:1431: checking for cc
configure:1477: result: no
configure:1530: checking for cl
configure:1559: result: no
configure:1573: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
======================================================================
Bug History
Date Modified Username Field Change
======================================================================
06-29-04 18:27 miro911 New Bug
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-06-29 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 16:27 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 10:15 [ALSA - driver 0000350]: Alsa Installation probleme noreply
2004-09-24 11:31 bugtrack
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=c3d50bcb662348cb49676bdc23227975@bugtrack.alsa-project.org \
--to=noreply@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.