From: Brian Parkhurst <brianp@spamcop.net>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] Need X testers on Alpha. I think we've got it this time.
Date: Sat, 10 Oct 2009 23:31:47 -0700 [thread overview]
Message-ID: <4AD17BD3.9020803@spamcop.net> (raw)
In-Reply-To: <b4198de60910080652g1210cf61i15e6907f9ce3da67@mail.gmail.com>
Okay had some time today. I'm working on the autounmask of
xorg-xserver-9999 (running now).
What is your recommended kernel for this build?
I've been working to bring the server up to current (emerge -uv world) &
revdep-rebuild (been about 4 months since I've updated packages)
Should hopefully be able to build the Kernel and Xorg-Server tomorrow.
Just to answer your last question. I've been running Gentoo on my
alpha(s) for about 6 years (migrated to the DS20E earlier this year from
an older alpha 800). I had contributed a bit to the livecd (2004
release) to support booting alpha with DEC Mylex 960 Raid controller
(just identified the firmware levels of the DEC OEM version).
Matt Turner wrote:
> On Thu, Oct 8, 2009 at 9:35 AM, Brian Parkhurst <brianp@spamcop.net> wrote:
>> How do you recommend I download your repo for compiling under gentoo?
>
> The easiest/best way is to first install layman (emerge layman) and
> with it add the 'x11' overlay.
>
> See here for instructions wrt layman:
> http://en.gentoo-wiki.com/wiki/Overlay#Layman
>
> Unmask/keyword =x11-base/xorg-server-9999 and its dependencies. (You
> might want to use app-portage/autounmask to make this a more automated
> task.)
>
> Copy the xorg-server-9999.ebuild from your layman overlay to your
> local overlay (/usr/local/portage/x11-base/xorg-server/). Edit the
> file and change this line:
>
> EGIT_REPO_URI="git://anongit.freedesktop.org/git/xorg/xserver"
> to
> EGIT_REPO_URI="git://anongit.freedesktop.org/~mattst88/xserver"
> In the folder where this new ebuild exists, run `ebuild
> xorg-server-9999.ebuild digest`
>
> At this point you should run `emerge =x11-base/xorg-server-9999` and
> sit back and wait. When this has finished, emerge whatever X11 drivers
> you need (xf86-input-evdev, xf86-video-{ati,glint}) and do some
> testing.
>
> I don't know what your level of proficiency with Gentoo is, but if
> it's not high then this process will sound hard--trust me, it's really
> not. The alternative would be much more complicated.
>
> Thanks,
> Matt
>
next prev parent reply other threads:[~2009-10-11 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 22:52 [gentoo-alpha] Need X testers on Alpha. I think we've got it this time Matt Turner
2009-10-07 23:06 ` Brian Parkhurst
2009-10-07 23:23 ` Matt Turner
2009-10-08 13:35 ` Brian Parkhurst
2009-10-08 13:52 ` Matt Turner
2009-10-11 6:31 ` Brian Parkhurst [this message]
2009-10-11 16:14 ` Matt Turner
[not found] ` <4AF746FC.9020403@spamcop.net>
2009-11-09 1:55 ` Matt Turner
2010-03-17 23:03 ` [gentoo-alpha] GCC-4.3.4 Build fails on new Install Ian Las
2010-03-17 23:05 ` Raúl Porcel
[not found] ` <b1cd107d0910080549u3ec72bf9q8cbfdb0d7c48f9e5@mail.gmail.com>
2009-10-08 13:56 ` [gentoo-alpha] Need X testers on Alpha. I think we've got it this time Matt Turner
[not found] ` <4ACDF02F.8080508@redhat.com>
2009-10-08 14:05 ` Matt Turner
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=4AD17BD3.9020803@spamcop.net \
--to=brianp@spamcop.net \
--cc=gentoo-alpha@lists.gentoo.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