From: Mattia Dongili <malattia-k2GhghHVRtY@public.gmane.org>
To: Berthold Cogel <cogel-F8dkAKZEjLURtNtAH2Wc8g@public.gmane.org>
Cc: ACPI Development
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Building the latest acpica on debian
Date: Sun, 23 Oct 2005 16:33:25 +0200 [thread overview]
Message-ID: <20051023143325.GD5314@inferi.kami.home> (raw)
In-Reply-To: <435B96DA.8040602-F8dkAKZEjLURtNtAH2Wc8g@public.gmane.org>
On Sun, Oct 23, 2005 at 03:57:46PM +0200, Berthold Cogel wrote:
> Hello!
>
> I'm trying to build the latest acpica package (acpica-unix-20050930) on
> my debian system using flex-old (flex version 2.5.4). I'm getting some
> warnings and I wonder if I have to be worried about them. I've attached
> the output of make. I've compiled iasl with gcc-3.3, gcc-3.4 and gcc-4.
> Especially the bison (bison (GNU Bison) 1.875d) warnings don't look
> good. Do I have to be aware of any problems if I use the compiled iasl?
Well, I'm not aware of any at the moment. If you find any feel free to
report them.
BTW: I uploaded the acpica-unix package in Debian's NEW queue some days
ago, the iasl package will hopefully be available soon
--
mattia
:wq!
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
prev parent reply other threads:[~2005-10-23 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 13:57 Building the latest acpica on debian Berthold Cogel
[not found] ` <435B96DA.8040602-F8dkAKZEjLURtNtAH2Wc8g@public.gmane.org>
2005-10-23 14:33 ` Mattia Dongili [this message]
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=20051023143325.GD5314@inferi.kami.home \
--to=malattia-k2ghghhvrty@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=cogel-F8dkAKZEjLURtNtAH2Wc8g@public.gmane.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