From 780714db008339c4c38102711fbd74aa16e08c74 Mon Sep 17 00:00:00 2001 From: maho Date: Fri, 19 Mar 2004 04:20:12 +0000 Subject: Backout previous change of PICFLAG, since behaviour of -fPIC and -fpic are different. Here is the comment form obrien: -- "-fpic" is a [minor?] optimization for machines that can handle it: -fpic Generate position-independent code (PIC) suitable for use in a shared library, if supported for the target machine. Such code accesses all constant addresses through a global offset table (GOT). The dynamic loader resolves the GOT entries when the program starts (the dynamic loader is not part of GCC; it is part of the operating system). If the GOT size for the linked executable exceeds a machine-specific maximum size, you get an error message from the linker indicating that -fpic does not work; in that case, recompile with -fPIC instead. (These maximums are 16k on the m88k, 8k on the SPARC, and 32k on the m68k and RS/6000. The 386 has no such limit.) -fPIC If supported for the target machine, emit position-independent code, suitable for dynamic linking and avoiding any limit on the size of the global offset table. This option makes a difference on the m68k, m88k, and the SPARC. Thanks to: obrien --- biology/pymol/Makefile | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'biology') diff --git a/biology/pymol/Makefile b/biology/pymol/Makefile index 7f3895d..d532141 100644 --- a/biology/pymol/Makefile +++ b/biology/pymol/Makefile @@ -28,7 +28,13 @@ USE_PYTHON= yes .include +.if !defined(PICFLAG) +.if ${MACHINE_ARCH} == "sparc64" PICFLAG=-fPIC +.else +PICFLAG=-fpic +.endif +.endif pre-patch: @${INSTALL_DATA} ${WRKSRC}/setup/Rules.linux ${WRKSRC}/Rules.make -- cgit v1.1