Probably cause they're dynamically loadable and are therefore architecture specific:
tux:/usr/lib64/gconv # objdump -f ISO8859-1.so ISO8859-1.so: file format elf64-s390 architecture: s390:64-bit, flags 0x00000150: HAS_SYMS, DYNAMIC, D_PAGED start address 0x0000000000000b4c > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Rick Troth > Sent: Sunday, May 15, 2005 7:10 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: 64-bit Codepages on SLES8 > > I don't understand why CODE PAGES would differ > between 32-bit and 64-bit. Can someone enlighten me? > Or is it simply because someone decided to put them in .so? > (Perhaps that wasn't such a good idea? Or is/was there a reason?) > > -- R; > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access > instructions, send email to [EMAIL PROTECTED] with the > message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
