From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch --- ~sparc tests good.
Date: Wed, 8 Dec 2004 11:19:17 +0900 [thread overview]
Message-ID: <20041208021916.GB34157@lion.gg3.net> (raw)
In-Reply-To: <1102466296.11355.0.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 2122 bytes --]
maillog: 07/12/2004-16:38:16(-0800): Donnie Berkholz types
> On Wed, 2004-12-08 at 09:16 +0900, Georgi Georgiev wrote:
> > And to the attention of spyderous: kernel_is from linux-info returns a
> > valid exit code and outputs lots of einfos, therefore the [ $(kernel_is
> > ..) ] and the other $(kernel_is) must not be in a subshell whose output
> > is passed to the command line (hence the "Command '*' not understood").
>
> I'm accepting patches that retain the former functionality.
I posted it four levels up in this thread, but here it is again anyway:
--- /usr/portage/x11-base/xorg-x11/xorg-x11-6.8.0-r4.ebuild 2004-12-07 13:23:15.000000000 +0900
+++ ./xorg-x11-6.8.0-r4.ebuild 2004-12-07 17:59:24.000000000 +0900
@@ -670,7 +674,7 @@
fi
if ( [ -e "${ROOT}/usr/src/linux" ] \
- && [ ! $(kernel_is "2" "2") ] ) \
+ && !( kernel_is "2" "2" ) ) \
|| [ "$(uname -r | cut -d. -f1,2)" != "2.2" ]; then
echo "#define HasLinuxInput YES" >> ${HOSTCONF}
fi
@@ -794,7 +798,7 @@
echo "#define ModuleAsCmd CcCmd -c -x assembler -fno-pie -fno-PIE" >> ${HOSTCONF}
fi
if ( [ -e "${ROOT}/usr/src/linux" ] \
- && !( $(kernel_is "2" "6") ) ) \
+ && !( kernel_is "2" "6" ) ) \
|| [ "$(uname -r | cut -d. -f1,2)" != "2.6" ]; then
einfo "Building for kernels less than 2.6 requires special treatment"
echo "#define UseDeprecatedKeyboardDriver YES" >> ${HOSTCONF}
It is a bit off, because I also have a patch for xft that makes it
generate bold fonts. You can still apply it manually anyway.
--
) Georgi Georgiev ) The one charm of marriage is that it makes )
( chutz@gg3.net ( a life of deception a neccessity. -- Oscar (
) +81(90)6266-1163 ) Wilde )
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-12-08 2:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 10:48 [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch Donnie Berkholz
2004-12-06 15:42 ` Georgi Georgiev
2004-12-06 18:17 ` Donnie Berkholz
2004-12-06 18:54 ` Hans-Werner Hilse
2004-12-06 21:37 ` Georgi Georgiev
2004-12-06 22:06 ` Georgi Georgiev
2004-12-06 22:17 ` Georgi Georgiev
2004-12-06 23:10 ` Donnie Berkholz
2004-12-07 0:38 ` Donnie Berkholz
2004-12-07 1:01 ` Georgi Georgiev
2004-12-07 3:01 ` Donnie Berkholz
2004-12-07 2:17 ` Donnie Berkholz
2004-12-07 1:27 ` Georgi Georgiev
2004-12-07 1:37 ` [gentoo-dev] HOSTCONF in global scope Georgi Georgiev
2004-12-07 1:52 ` [gentoo-dev] Double stripping in strip_execs() Georgi Georgiev
2004-12-07 12:34 ` [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch -- ~sparc OK Ferris McCormick
2004-12-07 19:59 ` [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch --- ~sparc tests good Ferris McCormick
2004-12-07 22:52 ` Georgi Georgiev
2004-12-07 23:02 ` Georgi Georgiev
2004-12-07 23:36 ` Ferris McCormick
2004-12-08 0:16 ` Georgi Georgiev
2004-12-08 0:38 ` Donnie Berkholz
2004-12-08 2:19 ` Georgi Georgiev [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=20041208021916.GB34157@lion.gg3.net \
--to=chutz@gg3.net \
--cc=gentoo-dev@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