Discussion:
Bug#474724: [DRE-maint] RC bug #474724
(too old to reply)
Antonio Terceiro
2008-05-10 20:40:09 UTC
Permalink
Hello everyone,
I am at a conference this week and also away for the weekend.
Could someone have a look at RC bug #474724 if you have the time?
Umh... Looks quite simple to solve - We would only have to add the
#if !defined POSH_CPU_STRING
# error POSH cannot determine target CPU
# define POSH_CPU_STRING "Unknown" /* this is here for Doxygen's benefit */
#endif
POSH_CPU_STRING is defined in the immediate preceding lines (421
#if defined ARM || defined __arm__ || defined _ARM
# define POSH_CPU_STRONGARM 1
# define POSH_CPU_STRING "ARM"
#endif
So we would only have to get (and I'm sorry, I'm completely lost in
this area) the proper CPU string for s390 and add it here. Blindly
asking Google makes me believe the proper string for the submitter's
environment (64-bit s390) is z900.
Besides #define'ing the proper symbols, there are issues like endianess
and other stuff that need to be properly defined for such architecture,
somewhere in posh.h, and it needs to be tested on an actual s390
machine.

I already tried hercules to emulate s390, but it's so slow that makes it
impractical (really). There is a s390 mainframe in my university's
datacenter, and I'm working together with its administrator to install
etch on it. We had no success yet, and these days I was on a trip. I
intend to try again on Monday morning.

If some DD with instant access to a s390 machine [1] could help, it
would be nice.

[1] http://db.debian.org/machines.cgi?host=raptor

I'm copying the debian-s390 list, in the case some of the porters want
and/or can help.
--
Antonio Terceiro <***@softwarelivre.org>
http://people.softwarelivre.org/~terceiro/
GnuPG ID: 0F9CB28F
--
To UNSUBSCRIBE, email to debian-bugs-dist-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Adam Thornton
2008-05-10 22:10:11 UTC
Permalink
Post by Antonio Terceiro
#if defined ARM || defined __arm__ || defined _ARM
# define POSH_CPU_STRONGARM 1
# define POSH_CPU_STRING "ARM"
#endif
So we would only have to get (and I'm sorry, I'm completely lost in
this area) the proper CPU string for s390 and add it here. Blindly
asking Google makes me believe the proper string for the submitter's
environment (64-bit s390) is z900.
Besides #define'ing the proper symbols, there are issues like
endianess
and other stuff that need to be properly defined for such
architecture,
somewhere in posh.h, and it needs to be tested on an actual s390
machine.
I already tried hercules to emulate s390, but it's so slow that makes it
impractical (really). There is a s390 mainframe in my university's
datacenter, and I'm working together with its administrator to install
etch on it. We had no success yet, and these days I was on a trip. I
intend to try again on Monday morning.
z900 is a particular model of a System z (64-bit) machine. I think
the generic architecture definitions are "s390" for 31-bit (which is
what Debian is), and "s390x" for 64-bit.

Adam
--
To UNSUBSCRIBE, email to debian-s390-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Loading...