Tim Prince wrote:
Kai Ruottu wrote:
Yes, Debian and the RHL-ES seem still to support Itanium... No
evidence about SuSE, nothing seen
about 'ia64', not even about 'x86_64' on their "SuSE Linux 10" pages, a
http://gcc.gnu.org/ml/gcc-testresults/2006-11/msg00689.html
Andreas continues with active gcc testing on ia64-suse-linux.
On the OpenSuSE 10.1 download page there was a link to SGI and at :
ftp://oss.sgi.com/projects/opensuse/download/inst-source/suse/ia64
was downloadable RPMs for 'ia64-suse-linux', like a recent glibc-2.5 for
ia64 :
-------------- clip -------------------
GNU C Library stable release version 2.5 (20061011), by Roland McGrath
et al.
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Configured for ia64-suse-linux.
Compiled by GNU CC version 4.1.2 20061115 (prerelease) (SUSE Linux).
Compiled on a Linux 2.6.18 system on 2006-11-16.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
GNU libio by Per Bothner
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
Thread-local storage support included.
-------------- clip -------------------
This text seen via 'strings' for the 'lib/libc-2.5.so'... BUT this was
almost the only
thing what one could see from the SGI-built glibc :-( Usual things like :
Dell:/opt/host-SuSE10.1_ia64/lib # ia64-suse-linux-nm libc-2.5.so
ia64-suse-linux-nm: libc-2.5.so: File format not recognized
made with the SuSE10.1 provided 'distcc' ia64-target binutils or with
self-made ones,
told that there is something weird in the SGI-SuSE Linux binary format...
The "readelf -h" command however gave something :
-------------- clip -------------------
Dell:/opt/host-SuSE10.1_ia64/lib # ia64-suse-linux-readelf -h libc-2.5.so
ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: Intel IA-64
Version: 0x1
Entry point address: 0x23ca0
Start of program headers: 64 (bytes into file)
Start of section headers: 2421576 (bytes into file)
Flags: 0x10, 64-bit
Size of this header: 64 (bytes)
Size of program headers: 56 (bytes)
Number of program headers: 10
Size of section headers: 64 (bytes)
Number of section headers: 75
Section header string table index: 72
-------------- clip -------------------
But it seems that currently producing any crosstoolchains for the SGI's
'ia64-linux-gnu'
distro by using its original libraries would meet some serious problems :-(
Producing crosstoolchains for the Debian's 'ia64-linux-gnu' with its
'glibc-2.3.6' then
shouldn't be hard, the Debian packages for ia64 seemed to be quite
standard Linux/ia64
stuff...
Does someone know what on earth is the idea in the SGI's SuSE
Linux/ia64, why its
stuff is totally in some non-standard format?
