From: galiza.ceive@gmail.com (Johám-Luís Miguéns Vila)
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: stumpwm users .. need help with failed emerge
Date: Sun, 16 Nov 2008 23:19:32 +0100 [thread overview]
Message-ID: <871vxb8gaz.fsf@galiza_ceive.gnu-linux.org> (raw)
In-Reply-To: <87bpwf5s3r.fsf@newsguy.com> (Harry Putnam's message of "Sun, 16 Nov 2008 14:32:56 -0600")
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
Harry Putnam <reader@newsguy.com> writes:
> galiza.ceive@gmail.com (Johám-Luís Miguéns Vila) writes:
>> And regarding cmucl build error, there's a bug report on b.g.o. with a
>> patch that seems to fix it [2].
>
> I've downloaded that but not used it yet.
> But I seem to recall that when you change an ebuild, you can't just
> install it then ... but have to create a new ebuild or some such?
>
Yes, you should create a new ebuild with an additional epatch line
aiming to downloaded b.g.o. patch, and put it on an overlay (if not, changes will
dissappear when syncing portage tree next time).
Look at the cmucl ebuild source, and you'll see it's pretty straightforward.
--
<spyderous> kurt needs to allow sudo /usr/bin/nano
<seemant> talk to him then :P
<spyderous> i tried =P
<spyderous> he said, be a man
<seemant> HA!
- This message may be digitally signed: GPG KeyID:0x9D2FD6C8 || FNMT SSL cert
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
prev parent reply other threads:[~2008-11-16 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 16:35 [gentoo-user] stumpwm users .. need help with failed emerge Harry Putnam
2008-11-16 9:58 ` Johám-Luís Miguéns Vila
2008-11-16 10:10 ` Johám-Luís Miguéns Vila
2008-11-16 20:32 ` [gentoo-user] " Harry Putnam
2008-11-16 22:19 ` Johám-Luís Miguéns Vila [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=871vxb8gaz.fsf@galiza_ceive.gnu-linux.org \
--to=galiza.ceive@gmail.com \
--cc=gentoo-user@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