| 1 |
grobian 09/06/01 08:42:01 |
| 2 |
|
| 3 |
Modified: gnustep-funcs.eclass |
| 4 |
Log: |
| 5 |
update texts on ffi, these functions are actually not used anywhere (I know of) |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.14 eclass/gnustep-funcs.eclass |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/gnustep-funcs.eclass?rev=1.14&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/gnustep-funcs.eclass?rev=1.14&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/gnustep-funcs.eclass?r1=1.13&r2=1.14 |
| 13 |
|
| 14 |
Index: gnustep-funcs.eclass |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo-x86/eclass/gnustep-funcs.eclass,v |
| 17 |
retrieving revision 1.13 |
| 18 |
retrieving revision 1.14 |
| 19 |
diff -u -r1.13 -r1.14 |
| 20 |
--- gnustep-funcs.eclass 8 Dec 2007 20:28:43 -0000 1.13 |
| 21 |
+++ gnustep-funcs.eclass 1 Jun 2009 08:42:01 -0000 1.14 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
# Copyright 1999-2004 Gentoo Technologies, Inc. |
| 24 |
# Distributed under the terms of the GNU General Public License v2 |
| 25 |
-# $Header: /var/cvsroot/gentoo-x86/eclass/gnustep-funcs.eclass,v 1.13 2007/12/08 20:28:43 voyageur Exp $ |
| 26 |
+# $Header: /var/cvsroot/gentoo-x86/eclass/gnustep-funcs.eclass,v 1.14 2009/06/01 08:42:01 grobian Exp $ |
| 27 |
|
| 28 |
# THIS ECLASS IS DEPRECATED. PLEASE DO NOT USE IT. |
| 29 |
|
| 30 |
@@ -294,8 +294,7 @@ |
| 31 |
} |
| 32 |
|
| 33 |
objc_not_available_info() { |
| 34 |
- einfo "gcc must be compiled with Objective-C support! See the objc USE flag." |
| 35 |
- einfo "NOTE: if you have to recompile gcc anyway, now may be the time to also add the 'gcj' use flag, so that libffi will also be compiled. Any gcc-3 version with 'gcj' should work, however, if you are testing >=gcc-3.4.3-r1 'objc' USE flag on should also install libffi." |
| 36 |
+ einfo "gcc must be compiled with Objective-C support, see the objc USE flag" |
| 37 |
} |
| 38 |
|
| 39 |
ffi_available() { |
| 40 |
@@ -313,18 +312,13 @@ |
| 41 |
|
| 42 |
local available |
| 43 |
available="yes" |
| 44 |
- # XXX |
| 45 |
- # Support dev-libs/libffi until it is deprecate |
| 46 |
- # (not that these -I and -L really matter |
| 47 |
eval $(tc-getCC) ${FFI_TEST} -o ${FFI_TEST}-out -lffi || available="no" |
| 48 |
|
| 49 |
echo ${available} |
| 50 |
} |
| 51 |
|
| 52 |
ffi_not_available_info() { |
| 53 |
- einfo "Your FFI libraries and headers seem to be installed incorrectly." |
| 54 |
- einfo "This is not as bad as it sounds -- not many projects use libffi at the moment, and gcc may have installed the headers in an inavailable place. Especially check for 'ffi.h' in your /usr/lib/gcc/\"\$CHOST\"/\"gcc-version\"/include directory, and that any other ffi related files it #include's (e.g. 'ffitarget.h') are in that directory as well; this can be solved by moving the files, or with a symlink. This is a quick fix, and newer ebuilds of gcc should install the files in the correct places, but for now, it could save you a recompilation of gcc." |
| 55 |
- einfo "If this still fails for you, consider not using the 'gcc-libffi' USE flag and letting dev-libs/libffi build as a dependency. It is important that either 'gcj' is a USE flag for gcc, or 'gcj' or 'objc' for >=gcc-3.4.3-r1." |
| 56 |
+ einfo "please install virtual/libffi" |
| 57 |
} |
| 58 |
|
| 59 |
########################################################################### |
Archives