From: "Joshua Kinard (kumba)" <kumba@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-devel/kgcc64: ChangeLog kgcc64-4.3.2.ebuild
Date: Sun, 26 Oct 2008 18:54:43 +0000 [thread overview]
Message-ID: <E1KuAl9-0002GN-Cu@stork.gentoo.org> (raw)
kumba 08/10/26 18:54:43
Modified: ChangeLog
Added: kgcc64-4.3.2.ebuild
Log:
Add ebuild for kgcc64-4.3.2 cross-compiler.
(Portage version: 2.2_rc12/cvs/Linux 2.6.27-mipsgit-20081010 mips64)
Revision Changes Path
1.21 sys-devel/kgcc64/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/kgcc64/ChangeLog?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/kgcc64/ChangeLog?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/kgcc64/ChangeLog?r1=1.20&r2=1.21
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-devel/kgcc64/ChangeLog,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- ChangeLog 4 Aug 2008 04:48:56 -0000 1.20
+++ ChangeLog 26 Oct 2008 18:54:43 -0000 1.21
@@ -1,6 +1,11 @@
# ChangeLog for sys-devel/kgcc64
# Copyright 1999-2008 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/sys-devel/kgcc64/ChangeLog,v 1.20 2008/08/04 04:48:56 halcy0n Exp $
+# $Header: /var/cvsroot/gentoo-x86/sys-devel/kgcc64/ChangeLog,v 1.21 2008/10/26 18:54:43 kumba Exp $
+
+*kgcc64-4.3.2 (26 Oct 2008)
+
+ 26 Oct 2008; Joshua Kinard <kumba@gentoo.org> +kgcc64-4.3.2.ebuild:
+ Add ebuild for kgcc64-4.3.2 cross-compiler.
04 Aug 2008; Mark Loeser <halcy0n@gentoo.org> Manifest:
Manifest out of date due to changes to toolchain eclass for gcj fixes
1.1 sys-devel/kgcc64/kgcc64-4.3.2.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/kgcc64/kgcc64-4.3.2.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/kgcc64/kgcc64-4.3.2.ebuild?rev=1.1&content-type=text/plain
Index: kgcc64-4.3.2.ebuild
===================================================================
# Copyright 1999-2008 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/sys-devel/kgcc64/kgcc64-4.3.2.ebuild,v 1.1 2008/10/26 18:54:43 kumba Exp $
case ${CHOST} in
hppa*) CTARGET=hppa64-${CHOST#*-};;
mips*) CTARGET=${CHOST/mips/mips64};;
powerpc*) CTARGET=${CHOST/powerpc/powerpc64};;
s390*) CTARGET=${CHOST/s390/s390x};;
sparc*) CTARGET=${CHOST/sparc/sparc64};;
i?86*) CTARGET=x86_64-${CHOST#*-};;
esac
export CTARGET
TOOLCHAIN_ALLOWED_LANGS="c"
GCC_TARGET_NO_MULTILIB=true
PATCH_VER="1.1"
ETYPE="gcc-compiler"
GCC_FILESDIR=${FILESDIR/${PN}/gcc}
inherit toolchain eutils
DESCRIPTION="64bit kernel compiler"
KEYWORDS="" #228115
# unlike every other target, hppa has not unified the 32/64 bit
# ports in binutils yet
DEPEND="hppa? ( sys-devel/binutils-hppa64 )
!sys-devel/gcc-hppa64
!sys-devel/gcc-mips64
!sys-devel/gcc-powerpc64
!sys-devel/gcc-sparc64"
pkg_postinst() {
cd "${ROOT}"/usr/bin
local x
for x in gcc cpp ; do
cat <<-EOF >${CTARGET%%-*}-linux-${x}
#!/bin/sh
exec ${CTARGET}-${x} "\$@"
EOF
chmod a+rx ${CTARGET%%-*}-linux-${x}
done
}
reply other threads:[~2008-10-26 18:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1KuAl9-0002GN-Cu@stork.gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--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