Using NetBSD's pkgsrc on IRIX

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
nekonoko
Site Admin
Site Admin
Posts: 8145
Joined: Thu Jan 23, 2003 1:31 am
Location: Pleasanton, California
Contact:

Unread postby nekonoko » Wed Sep 20, 2006 8:34 am

zizban wrote:This is excellent. Let me make this a sticky.

Edit: I can't. neko?


Hmm, I'm not sure we need it sticky. I have mixed feelings about this - sure it's great for those with compilers and development headers, but it really doesn't help the large majority which would rather just download a package and have it work. I'd like to see the lessons learned here go toward creating packages that everyone can enjoy.
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

User avatar
stuart
Posts: 912
Joined: Mon Aug 23, 2004 5:37 pm
Location: Cambridge, UK
Contact:

Unread postby stuart » Wed Sep 20, 2006 8:49 am

nekonoko wrote:I have mixed feelings about this - sure it's great for those with compilers and development headers, but it really doesn't help the large majority which would rather just download a package and have it work.


I see what you're saying - but this is the "IRIX: Development" thread...

Also, pkgsrc is just a framework within which software can be built - the actual source that's being built is stock, and so tricks and tips to get these packages building are equally applicable to building anything from source. I'd have thought that this'd make this thread useful to anyone porting a new application to IRIX - whether that be via pkgsrc or portage (if I even get it finished ;)) or in order to build a more widely usable tardist.

(My personal motivation is to build packages specifically targetted at my machine, to see if there are any real-world gains from doing so. The problem with this is that binaries produced aren't especially portable to other systems...)

User avatar
nekonoko
Site Admin
Site Admin
Posts: 8145
Joined: Thu Jan 23, 2003 1:31 am
Location: Pleasanton, California
Contact:

Unread postby nekonoko » Wed Sep 20, 2006 8:52 am

I understand where you're coming from too, but the bottom line is that very few are still developing new tardists and the "Cool software you would like to see ported ..." thread is 22 pages and growing :) I'd really like to see some more people help getting some of this out there for everyone to use, not a select few.

Anyway, that's neither here nor there - you can continue on, I just don't think it needs a sticky :)
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

User avatar
Nihilus
Posts: 310
Joined: Sat Dec 18, 2004 8:21 am
Location: Stockholm, Sweden
Contact:

Unread postby Nihilus » Thu Oct 12, 2006 5:47 pm

We don't want to use Mesa since this IS SGI, native OGL ftw!
Add to mk.conf:

Code: Select all

BUILTIN_PKG.Mesa=       Mesa-6.5.0
USE_BUILTIN.Mesa=       YES
BUILTIN_PKG.glu=        glu-6.5.0
USE_BUILTIN.glu=        YES
BUILTIN_PKG.glut=       glut-6.5.0
USE_BUILTIN.glut=       YES
BUILTIN_PKG.MesaLib=    MesaLib-6.5.0
USE_BUILTIN.MesaLib=    YES
SGI Systems: R4K :Indigo:/256MB/XS-24, R5K 150MHz :Indy:/160MB/XL-24, R10K 175MHz :O2:/640MB, R12K 400MHz :Octane2:/Vpro6/1GB & R4K 250 MHz :Indigo2IMP:/128 MB/XZ Extreme/GIO64 FDDI

"It's a UNIX system! I know this! "

User avatar
stuart
Posts: 912
Joined: Mon Aug 23, 2004 5:37 pm
Location: Cambridge, UK
Contact:

Unread postby stuart » Mon Oct 16, 2006 10:44 am

Do you know how this BUILTINS system works?

I'm trying to stop pkgsrc pulling in bash (since pkgsrc only seems to support a single compiler suite, and bash-3.x is fubar when built with MIPSpro), but the following lines:

Code: Select all

BUILTIN_PKG.bash=       bash-3.1
USE_BUILTIN.bash=       YES

... seem to do nothing. I've tried "bash-3.1" and "bash-3.1pl17" but there's no discernable difference.

Any clues?

(Or, have you worked out how to selectively build packages (such as bash) with gcc - that'd be great!)

User avatar
Nihilus
Posts: 310
Joined: Sat Dec 18, 2004 8:21 am
Location: Stockholm, Sweden
Contact:

Unread postby Nihilus » Sun Mar 11, 2007 9:44 am

To get pkgsrc to use MIPSPro Fortran Compiler instead of F2C add the following to you mk/compiler/mipspro.mk:

Code: Select all

.if exists(${MIPSPROBASE}/bin/f77)
LANGUAGES.mipspro+=     fortran
_MIPSPRO_VARS+=         FC
_MIPSPRO_FC=            ${_MIPSPRO_DIR}/bin/f77
_ALIASES.FC=            f77
FCPATH=                 ${MIPSPROBASE}/bin/f77
PKG_FC:=                ${_MIPSPRO_F77}
.endif

and comment out F2C like this:

Code: Select all

# Force the use of f2c-f77 for compiling Fortran.
#_MIPSPRO_USE_F2C=      no
#.if !exists(${FCPATH})
#_MIPSPRO_USE_F2C=      yes
#.endif
#.if !empty(_MIPSPRO_USE_F2C:M[yY][eE][sS])
#.  include "../../mk/compiler/f2c.mk"
#.endif
SGI Systems: R4K :Indigo:/256MB/XS-24, R5K 150MHz :Indy:/160MB/XL-24, R10K 175MHz :O2:/640MB, R12K 400MHz :Octane2:/Vpro6/1GB & R4K 250 MHz :Indigo2IMP:/128 MB/XZ Extreme/GIO64 FDDI

"It's a UNIX system! I know this! "

rumble
Posts: 101
Joined: Mon Aug 28, 2006 5:36 pm
Location: Palo Alto Junior College

Unread postby rumble » Tue Mar 27, 2007 8:01 pm

nekonoko wrote:Hmm, I'm not sure we need it sticky. I have mixed feelings about this - sure it's great for those with compilers and development headers, but it really doesn't help the large majority which would rather just download a package and have it work. I'd like to see the lessons learned here go toward creating packages that everyone can enjoy.


pkgsrc doesn't deal only with compiling from source. You may also install pre-compiled packages, which are simply tarballs with some special metadata files included.

I don't know how nekoware (or whatever its called) deals with things, but maintaining pkgsrc on IRIX would possibly provide a very powerful platform for doing bulk builds of thousands of programs. It seems like a pretty reasonable thing to leverage, and the pkgsrc folks will gladly take patches, I'm sure.

I think using pkgsrc could be a very big win. One could place the pkgsrc bootstrap utilities in a tardist for installation on bare IRIX, and the rest could be handled by the pkg_* utilities and pre-compiled packages.

gocram
Posts: 71
Joined: Wed Jul 30, 2014 7:15 am
Location: The Netherlands

Re: Using NetBSD's pkgsrc on IRIX

Unread postby gocram » Sun Nov 05, 2017 2:17 pm

rumble, that would indeed be interesting.

I've never tried pkgsrc for IRIX. What is the current situation? (Where can I possibly read more about it?)
:O2: 400/R12ᴋ, 1GB RAM, digvid (AV2), UW-SCSI PCI, 256GB SSD (int.) & 4×300GB 15ᴋ/U320 HDDs (ext.), DVD
:Indigo2IMP: 195/R10ᴋ, 1GB RAM, High IMPACT+TRAM, IMPACT Video, 256GB SSD, CD
LOOKING FOR:
HIGH IMPACT-AA or MAXIMUM IMPACT graphics board set (for IP28)

User avatar
Raion-Fox
Donor
Donor
Posts: 1383
Joined: Thu Jan 30, 2014 5:01 pm
Location: near King George, Virginia
Contact:

Re: Using NetBSD's pkgsrc on IRIX

Unread postby Raion-Fox » Sun Nov 05, 2017 4:33 pm

Holy threadomancy batman
:O3x02L: R16000 700MHz 8GB RAM kanna
:Octane: R12000 300MHz SI 896MB RAM yuuka
:Octane2: R12000A 400MHz V6 2.5GB RAM
:Indy: (Acclaim) R4600 133MHz XL Graphics 32MB RAM
:Indy: (Challenge S) R4600 133MHz (MIPS III Build Server)
Thinkpad W530 i7 3940XM 3GHz, 32GB, K1000M Windows 8.1 Embedded rin
Thinkpad R40 Pentium M 1.5GHz 2GB RAM kasha

Owner and operator of http://irix.pw


Return to “SGI: Development”

Who is online

Users browsing this forum: No registered users and 2 guests