New nekoware packages with dual mips3/mips4 support

IRIX/Nekoware development, porting and related topics.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
dexter1
Moderator
Moderator
Posts: 2728
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

New nekoware packages with dual mips3/mips4 support

Unread postby dexter1 » Sat Sep 03, 2016 11:37 am

I have finished my first batch of dual mips3/mips4 nekoware packages:

neko_gettext-0.19.8.1.tardist
(36.66 MiB) Downloaded 23 times

neko_libiconv-1.14.tardist
(8.88 MiB) Downloaded 23 times

neko_make-3.82.tardist
(2.53 MiB) Downloaded 24 times

neko_zlib-1.2.8.tardist
(1.02 MiB) Downloaded 23 times

In these tardists, for each executable, object, shared and static archive there are two entries in the .idb: This is an excerpt from my new neko_gettext.idb:

Code: Select all

f 0755 root sys usr/nekoware/bin/envsubst usr/nekoware/bin/envsubst neko_gettext.sw.eoe mach(CPUARCH=R5000 CPUARCH=R8000 CPUARCH=R10000)
f 0755 root sys usr/nekoware/bin/envsubst home/frank/build/gettext/mips3/bin/envsubst neko_gettext.sw.eoe mach(CPUARCH=R4000)

I have built the mips3 versions on my R4400@175MHz Challenge S and the mips4 on my R12K@270MHz O2+. Both run IRIX 6.5.22m with MIPSPro 7.4.4 with latest patches + patch 5910

I make sure they always install in the /usr/nekoware destination folder so i can copy the mips3 objects into my home nfs folder to build the final tardist (have a script for that) This is mainly to avoid problems with rpath: I try to eliminate that piece of rubbish as much as possible with ./configure --disable-rpath but for some libraries libtool decided otherwise :(

These packages can be installed from the smallest/slowest R4000 Indigo up to a quad Tezro, provided they are running 6.5.22m or higher. I haven't actually tested these packages beyond IRIX 6.5.22 but for the above set of packages i do not expect any problems.

Note that the version number of these packages are higher than their previous mips4 and mips3 neko_ packages, even the beta versions, so inst should always regard them as an upgrade. Package dependencies are set to the latest version numbers.

In the long run we can then completely eliminate the nekoware-mips3 section when all mips3 packages have been replaced.


Do let me know if there are any problems with the packages so i can fix them.


As a upcoming teaser i've been looking at the neko_perl problem being stuck at version 5.8.9. The problem is that for building openssl-1.1.0 you need a perl-5.10.x version to run the test suite, but the perl 5.10.1 build fails a test in ../ext/Time-Piece/t/02core.t as pointed out by Jason Patterson in neko_perl.txt

Luckily i came accross this perlbug entry which list a build of 5.22RC1 on an IP35 (MIPSPro 7.4.x, most likely a Fuel) So i fired up a build of 5.22.2 on my O2 and after several hours i got this from 'make test':

Code: Select all

.
lib/vars ...................................................... ok
lib/vmsish .................................................... ok
lib/warnings .................................................. ok
All tests successful.
Elapsed: 10196 sec
u=158.80  s=39.42  cu=8304.02  cs=941.76  scripts=2211  tests=687949

Yup, it compiles and tests fine. Still have to work on 5.24.0 but there seems to be a bug in the Configure script, since the build will abort early.
With a recent perl in the Nekoware bag we can then advance in porting openssl/openssh to the latest versions (hopefully) and finally update the neko_ packages.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
foetz
Moderator
Moderator
Posts: 6529
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: New nekoware packages with dual mips3/mips4 support

Unread postby foetz » Sat Sep 03, 2016 4:30 pm

dexter1 wrote:The problem is that for building openssl-1.1.0 you need a perl-5.10.x version to run the test suite
...
With a recent perl in the Nekoware bag we can then advance in porting openssl/openssh to the latest versions (hopefully)

it builds fine without. see viewtopic.php?p=7377761#p7377761

User avatar
dexter1
Moderator
Moderator
Posts: 2728
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: New nekoware packages with dual mips3/mips4 support

Unread postby dexter1 » Sat Sep 03, 2016 5:47 pm

foetz wrote:
dexter1 wrote:The problem is that for building openssl-1.1.0 you need a perl-5.10.x version to run the test suite

it builds fine without. see viewtopic.php?p=7377761#p7377761

Well, i'm mentioning this because openssl-1.1.0, released ten days ago, has changed a few things in the build with regard to previous 1.0.x versions, which is why i'm not packaging it before having run the test suite. Did you run 'make test ' on your builds?
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
foetz
Moderator
Moderator
Posts: 6529
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: New nekoware packages with dual mips3/mips4 support

Unread postby foetz » Sat Sep 03, 2016 10:24 pm

sorry, i read 1.0.1. i didn't try 1.1.0 nor did i use "make test" ... ever, for anything :P
anyway the changelog reads
Remove support for MIPS o32 ABI on IRIX (and IRIX only).

going by that they still support n32/64 which also means they tried it at least once (i hope :P )

User avatar
dexter1
Moderator
Moderator
Posts: 2728
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: New nekoware packages with dual mips3/mips4 support

Unread postby dexter1 » Sun Sep 04, 2016 5:48 am

foetz wrote:
Remove support for MIPS o32 ABI on IRIX (and IRIX only).

going by that they still support n32/64 which also means they tried it at least once (i hope :P )

Ah, thanks for that o32 snippet, i missed that on reading the Changelog. This means openssl-1.0.2h (and future patches) should be end-of-the-line for IRIX R3K machines.
Perl 5.24.0 has built and passed all tests early this morning, so it is going to get packaged soon with dual mips support.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
Trippynet
Donor
Donor
Posts: 746
Joined: Thu Aug 15, 2013 6:22 am
Location: Aberdeen, Scotland, UK

Re: New nekoware packages with dual mips3/mips4 support

Unread postby Trippynet » Sun Sep 04, 2016 8:43 am

Outstanding, I'll enjoy a newer Perl build on my systems. Thanks again for the work here :)
Systems in use:
:Indigo2IMP: - Nitrogen: R10000 195MHz CPU, 384MB RAM, SolidIMPACT Graphics, 36GB 15k HDD & 300GB 10k HDD, 100Mb/s NIC, New/quiet fans, IRIX 6.5.22
:Fuel: - Lithium: R14000 600MHz CPU, 4GB RAM, V10 Graphics, 72GB 15k HDD & 300GB 10k HDD, 1Gb/s NIC, New/quiet fans, IRIX 6.5.30
Other system in storage: :O2: R5000 200MHz, 224MB RAM, 72GB 15k HDD, PSU fan mod, IRIX 6.5.30

User avatar
dexter1
Moderator
Moderator
Posts: 2728
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: New nekoware packages with dual mips3/mips4 support

Unread postby dexter1 » Tue Sep 06, 2016 8:13 am

Trippynet wrote:Outstanding, I'll enjoy a newer Perl build on my systems. Thanks again for the work here :)

Glad it's appreciated, but can you help me with a question?
I want to include 64 bit integer support while maintaining n32 ABI style for Nekoware. So i compiled perl 5.24.0 with

Code: Select all

sh Configure -Dcc='cc -n32' -Duse64bitint

The build script tells me that this might break compatibility with existing perl modules, but i seriously wonder if there are people in the wild which uses the neko_perl modules or have cooked their own stuff.

If so, i won't risk breaking compatibility with the perl modules still in nekoware and will build it without 64 bit support. I would be tempted to make a perl-64int binary but since i already have a split perl/thrperl next to the the mips3/mips4 split this might be taxing the Nekoware package build too much.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
Trippynet
Donor
Donor
Posts: 746
Joined: Thu Aug 15, 2013 6:22 am
Location: Aberdeen, Scotland, UK

Re: New nekoware packages with dual mips3/mips4 support

Unread postby Trippynet » Tue Sep 06, 2016 8:21 am

Interesting, although I think you actually forgot the question in there, unless you answered it yourself! :)

I don't think I use any of the other Perl modules in my scripts. They're usually pretty basic system management ones for file/folder manipulation and syncing, syncing date and time with my main PC, that sort of thing. Everything that Perl can handle by default in other words - and nothing of which needs 64bit support incidentally.

I think we might need someone who uses Perl in more complex scenarios to comment here. From my point of view, any way will work for the stuff I have.
Systems in use:
:Indigo2IMP: - Nitrogen: R10000 195MHz CPU, 384MB RAM, SolidIMPACT Graphics, 36GB 15k HDD & 300GB 10k HDD, 100Mb/s NIC, New/quiet fans, IRIX 6.5.22
:Fuel: - Lithium: R14000 600MHz CPU, 4GB RAM, V10 Graphics, 72GB 15k HDD & 300GB 10k HDD, 1Gb/s NIC, New/quiet fans, IRIX 6.5.30
Other system in storage: :O2: R5000 200MHz, 224MB RAM, 72GB 15k HDD, PSU fan mod, IRIX 6.5.30

User avatar
dexter1
Moderator
Moderator
Posts: 2728
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: New nekoware packages with dual mips3/mips4 support

Unread postby dexter1 » Tue Sep 06, 2016 8:34 am

Thanks Trippy,

Duh on my part, the second paragraph should have a question mark and some reformatting as well.
If i look at what modules we currently have I think it is most prudent to make the new perl behave the same as the old 5.8.9 perl, so no 64 bit integers.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

robespierre
Posts: 1538
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: New nekoware packages with dual mips3/mips4 support

Unread postby robespierre » Tue Sep 06, 2016 9:23 am

dexter1 wrote:I want to include 64 bit integer support while maintaining n32 ABI style for Nekoware. So i compiled perl 5.24.0 with

Code: Select all

sh Configure -Dcc='cc -n32' -Duse64bitint


I don't see how that's supposed to work: the only integer type that's allocated 64 bits with N32 is 'long long'.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:


Return to “SGI: Development”

Who is online

Users browsing this forum: No registered users and 2 guests