From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37117] New: configure fails in git/master
Date: Wed, 11 May 2011 11:04:33 -0700 (PDT) [thread overview]
Message-ID: <bug-37117-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=37117
Summary: configure fails in git/master
Product: DRI
Version: XOrg CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: libdrm
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: David.Ronis@McGill.CA
I just updated my drm sources, ran autogen.sh, and then
configure --prefix=/usr --enable-radeon-experimental-api
--enable-nouveau-experimental-api
Configure dies with:
checking for alloca... yes
./configure: line 5129: syntax error near unexpected token `2.2'
./configure: line 5129: `LT_PREREQ(2.2)'
A typo in configure.ac?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-11 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 18:04 bugzilla-daemon [this message]
2013-01-23 2:20 ` [Bug 37117] configure fails in git/master bugzilla-daemon
2013-09-21 0:28 ` bugzilla-daemon
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=bug-37117-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).