(header complete to Brian, Kurt, Bastian, BTS)
On 7 April 2006 at 13:40, Prof Brian Ripley wrote:
| On Fri, 7 Apr 2006, Prof Brian Ripley wrote:
|
| > On Fri, 7 Apr 2006, Kurt Hornik wrote:
| >
| >> More later ...
| >
| > We have in configure.ac
| >
| > case "${host_cpu}" in
| > ## Sparc has only an 8k global object table, 1024 entries on 64-bit.
| > ## PowerPC has 32k, not enough on ppc64 for the ca6200 entries in libR.so
| > ## The only other platform where this is said to matter is m68k, which
| > ## has 32k and so can use -fpic.
| > sparc*|ppc64)
| > cpicflags="-fPIC"
| > ;;
| > *)
| > cpicflags="-fpic"
| > ;;
| > esac
| >
| > so we just need to know the magic to add s390 in there and similar.
(Probably
| > s390*, looking at configure, so I'll update using that.)
That sounds sensible to me. Bastian, can you comment on why you think a
global option is better? Plus, are there reference on what other system
(libtool comes to mind...) do?
Dirk
| > Note: man gcc says
| >
| > -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, PowerPC and SPARC.
| >
| > so the (reasonable) assumption made was that it does not make a difference
on
| > s390 (and in fact that it does not even say it is supported on s390).
|
| And if that analysis is correct and the Debian docs say the same I think
| the original reporter should file a documentation bug report for gcc on
| s390 and perhaps s390x (I have no way of knowing about the latter).
|
| (My gcc docs are from the GNU 4.1.0 sources, so current.)
|
| --
| Brian D. Ripley, [EMAIL PROTECTED]
| Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
| University of Oxford, Tel: +44 1865 272861 (self)
| 1 South Parks Road, +44 1865 272866 (PA)
| Oxford OX1 3TG, UK Fax: +44 1865 272595
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
