From: Justin Madru <jdm64@gawab.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
Bryce Harrington <bryce@canonical.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Sun, 16 Mar 2008 18:28:10 -0700 [thread overview]
Message-ID: <47DDC92A.7000703@gawab.com> (raw)
In-Reply-To: <200803151035.23808.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> No problem, building X still isn't quite as easy as it should be, but it's
> only slightly more complicated than the typical './configure;make;make
> install' due to the dependencies between packages. You can check out the X
> wiki (wiki.x.org), there are some hints on building things there.
>
I'm just compiling the intel_reg_dumper right? I don't have to recompile
all of X to use it?
Bryce Harrington wrote:
> The following command will pull in all the dependencies you need for
> building -intel:
>
> sudo apt-get build-dep xserver-xorg-video-intel
Ok, got that. I tried to compile and I found out I also had to install
libpciaccess-dev, that's probably because I'm using the git tree and not
the one that Ubuntu 7.10 uses. But I still can't compile the
intel_reg_dumper I get the following error:
intel-driver/src/reg_dumper$ make
gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Wpointer-arith
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -fno-strict-aliasing -I./.. -DREG_DUMPER -g -O2 -MT
main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c
main.c: In function ‘main’:
main.c:72: warning: implicit declaration of function ‘pci_device_map_range’
main.c:72: warning: nested extern declaration of ‘pci_device_map_range’
main.c:75: error: ‘PCI_DEV_MAP_FLAG_WRITABLE’ undeclared (first use in
this function)
main.c:75: error: (Each undeclared identifier is reported only once
main.c:75: error: for each function it appears in.)
make: *** [main.o] Error 1
Justin
next prev parent reply other threads:[~2008-03-17 1:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 19:02 [Regression: 2.6.25-rc5: Blank Screen: Intel 945] Justin Madru
2008-03-12 19:36 ` Jesse Barnes
[not found] ` <47D8BF6A.9020905@gawab.com>
2008-03-13 17:09 ` Jesse Barnes
2008-03-14 4:22 ` Justin Madru
2008-03-14 17:29 ` Jesse Barnes
2008-03-15 3:48 ` Justin Madru
2008-03-15 17:35 ` Jesse Barnes
2008-03-15 18:16 ` Bryce Harrington
2008-03-17 1:28 ` Justin Madru [this message]
2008-03-18 19:07 ` Bryce Harrington
2008-03-18 20:00 ` Jesse Barnes
2008-03-18 20:53 ` Bryce Harrington
2008-03-18 21:14 ` Bryce Harrington
2008-03-18 21:17 ` Jesse Barnes
2008-03-19 23:38 ` Justin Madru
2008-03-19 23:48 ` Jesse Barnes
2008-03-20 2:00 ` Bryce Harrington
2008-03-25 3:07 ` Justin Madru
2008-03-25 20:08 ` Jesse Barnes
2008-03-26 18:32 ` Justin Madru
2008-03-31 19:24 ` Justin Madru
2008-04-01 20:22 ` Jesse Barnes
2008-04-09 4:56 ` Justin Madru
2008-04-09 15:24 ` Jesse Barnes
2008-04-14 3:46 ` Justin Madru
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=47DDC92A.7000703@gawab.com \
--to=jdm64@gawab.com \
--cc=bryce@canonical.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.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).