/[gentoo-x86]/eclass/toolchain-funcs.eclass
Gentoo

Diff of /eclass/toolchain-funcs.eclass

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.64 Revision 1.68
1# Copyright 1999-2006 Gentoo Foundation 1# Copyright 1999-2007 Gentoo Foundation
2# Distributed under the terms of the GNU General Public License v2 2# Distributed under the terms of the GNU General Public License v2
3# $Header: /var/cvsroot/gentoo-x86/eclass/toolchain-funcs.eclass,v 1.64 2007/01/07 11:39:08 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/eclass/toolchain-funcs.eclass,v 1.68 2007/03/15 15:55:59 kevquinn Exp $
4# 4#
5# Author: Toolchain Ninjas <toolchain@gentoo.org> 5# Maintainer: Toolchain Ninjas <toolchain@gentoo.org>
6# 6#
7# This eclass contains (or should) functions to get common info 7# This eclass contains (or should) functions to get common info
8# about the toolchain (libc/compiler/binutils/etc...) 8# about the toolchain (libc/compiler/binutils/etc...)
9 9
10inherit multilib 10inherit multilib
89# A simple way to see if we're using a cross-compiler ... 89# A simple way to see if we're using a cross-compiler ...
90tc-is-cross-compiler() { 90tc-is-cross-compiler() {
91 return $([[ ${CBUILD:-${CHOST}} != ${CHOST} ]]) 91 return $([[ ${CBUILD:-${CHOST}} != ${CHOST} ]])
92} 92}
93 93
94# See if this toolchain is a softfloat based one.
95# The possible return values:
96# - only: the target is always softfloat (never had fpu)
97# - yes: the target should support softfloat
98# - no: the target should support hardfloat
99# This allows us to react differently where packages accept
100# softfloat flags in the case where support is optional, but
101# rejects softfloat flags where the target always lacks an fpu.
102tc-is-softfloat() {
103 case ${CTARGET} in
104 bfin*|h8300*)
105 echo "only" ;;
106 *)
107 [[ ${CTARGET//_/-} == *-softfloat-* ]] \
108 && echo "yes" \
109 || echo "no"
110 ;;
111 esac
112}
94 113
95# Parse information from CBUILD/CHOST/CTARGET rather than 114# Parse information from CBUILD/CHOST/CTARGET rather than
96# use external variables from the profile. 115# use external variables from the profile.
97tc-ninja_magic_to_arch() { 116tc-ninja_magic_to_arch() {
98ninj() { [[ ${type} == "kern" ]] && echo $1 || echo $2 ; } 117ninj() { [[ ${type} == "kern" ]] && echo $1 || echo $2 ; }
171} 190}
172# Returns the Micro version 191# Returns the Micro version
173gcc-micro-version() { 192gcc-micro-version() {
174 gcc-fullversion "$@" | cut -f3 -d. | cut -f1 -d- 193 gcc-fullversion "$@" | cut -f3 -d. | cut -f1 -d-
175} 194}
195# Returns the installation directory - internal toolchain
196# function for use by _gcc-specs-exists (for flag-o-matic).
197_gcc-install-dir() {
198 echo "$($(tc-getCC) -print-search-dirs 2> /dev/null |\
199 awk '$1=="install:" {print $2}')"
200}
201# Returns true if the indicated specs file exists - internal toolchain
202# function for use by flag-o-matic.
203_gcc-specs-exists() {
204 [[ -f $(_gcc-install-dir)/$1 ]]
205}
176 206
177# Returns requested gcc specs directive 207# Returns requested gcc specs directive unprocessed - for used by
208# gcc-specs-directive()
178# Note; later specs normally overwrite earlier ones; however if a later 209# Note; later specs normally overwrite earlier ones; however if a later
179# spec starts with '+' then it appends. 210# spec starts with '+' then it appends.
180# gcc -dumpspecs is parsed first, followed by files listed by "gcc -v" 211# gcc -dumpspecs is parsed first, followed by files listed by "gcc -v"
181# as "Reading <file>", in order. 212# as "Reading <file>", in order. Strictly speaking, if there's a
213# $(gcc_install_dir)/specs, the built-in specs aren't read, however by
214# the same token anything from 'gcc -dumpspecs' is overridden by
215# the contents of $(gcc_install_dir)/specs so the result is the
216# same either way.
182gcc-specs-directive() { 217_gcc-specs-directive_raw() {
183 local cc=$(tc-getCC) 218 local cc=$(tc-getCC)
184 local specfiles=$(LC_ALL=C ${cc} -v 2>&1 | awk '$1=="Reading" {print $NF}') 219 local specfiles=$(LC_ALL=C ${cc} -v 2>&1 | awk '$1=="Reading" {print $NF}')
185 ${cc} -dumpspecs 2> /dev/null | cat - ${specfiles} | awk -v directive=$1 \ 220 ${cc} -dumpspecs 2> /dev/null | cat - ${specfiles} | awk -v directive=$1 \
186'BEGIN { pspec=""; spec=""; outside=1 } 221'BEGIN { pspec=""; spec=""; outside=1 }
187$1=="*"directive":" { pspec=spec; spec=""; outside=0; next } 222$1=="*"directive":" { pspec=spec; spec=""; outside=0; next }
188 outside || NF==0 || ( substr($1,1,1)=="*" && substr($1,length($1),1)==":" ) { outside=1; next } 223 outside || NF==0 || ( substr($1,1,1)=="*" && substr($1,length($1),1)==":" ) { outside=1; next }
189 spec=="" && substr($0,1,1)=="+" { spec=pspec " " substr($0,2); next } 224 spec=="" && substr($0,1,1)=="+" { spec=pspec " " substr($0,2); next }
190 { spec=spec $0 } 225 { spec=spec $0 }
191END { print spec }' 226END { print spec }'
227 return 0
228}
229
230# Return the requested gcc specs directive, with all included
231# specs expanded.
232# Note, it does not check for inclusion loops, which cause it
233# to never finish - but such loops are invalid for gcc and we're
234# assuming gcc is operational.
235gcc-specs-directive() {
236 local directive subdname subdirective
237 directive="$(_gcc-specs-directive_raw $1)"
238 while [[ ${directive} == *%\(*\)* ]]; do
239 subdname=${directive/*%\(}
240 subdname=${subdname/\)*}
241 subdirective="$(_gcc-specs-directive_raw ${subdname})"
242 directive="${directive//\%(${subdname})/${subdirective}}"
243 done
244 echo "${directive}"
192 return 0 245 return 0
193} 246}
194 247
195# Returns true if gcc sets relro 248# Returns true if gcc sets relro
196gcc-specs-relro() { 249gcc-specs-relro() {

Legend:
Removed from v.1.64  
changed lines
  Added in v.1.68

  ViewVC Help
Powered by ViewVC 1.1.20