IRIX and Software

Hey all, been awhile since I have had the chance to visit my IRIX box. I was wondering if there was a procedure or list or outline on how to install all this neat stuff. I would be a happy test user of said documents. I would like to see, and would help validate a procedure for....

1. Installing the Neckoware software. (Which tardists first?)
2. Setting Library and paths up correctly for stuff to run
3. Installing a Neckoware compiling environment.

It sure would be nice to see some sort of giudeline on how to setup a 6.5.x ~ R10K and above machine to compile your own software and run all the kick-butt stuff already compiled and ported, in one nice document. I know that this information is here, but it seems like a bitchkitty to find in several different documents.

I would be happy to run though someone elses work to validate it working, but I havent the skill to do it on my own.

For example, the firefox builds(eventhough not a nekoware release), if one does not know any better (ie: Me)
1. Download
2. Extract into correct place
3 Set Library paths and such
4 enjoy

Right now my experience since I am such a n00b is:
1. Download
2. extract into correct path
3. try to run and get half an xterm full of failed dependencies
4. give up and switch over to the Gentoo box.


For what it's worth, I can test any procedures with the following HW
1 R12K 300 EXMI-EVO Octane 36Gb RO drive
1 2xR12K 300 EXMI Octane 3x36GB
1 R10K 195 Max-impact I2 18Gb
1 R4 200? Teal I2 4.5 Gb
1 R4 ?Mhz Purple Non-impact I2. 4.5GB

All machines run 6.5.22f and I have MipsPro 7.3.1.3 or can get it.

If anyone is interested, let me know. And THANK YOU all for your hard work providing IRIX idiots like me with help and software.

Also, for a lazy man like myself, compiling is difficult because the stuff bombs so often.

As a side note, Can someone compile Pan?

Thanks
SoonerFan

Soonerfan wrote: Hey all, been awhile since I have had the chance to visit my IRIX box. I was wondering if there was a procedure or list or outline on how to install all this neat stuff. I would be a happy test user of said documents. I would like to see, and would help validate a procedure for....

1. Installing the Neckoware software. (Which tardists first?)

hello,

just get the whole bunch and extract all into one folder.
from there start 'swmgr -f .'

2. Setting Library and paths up correctly for stuff to run

nekoware defaults to /usr/nekoware.
older packages are in /usr/local but this should be in your paths anyway.

3. Installing a Neckoware compiling environment.

that isn't possible. you have to install the irix dev-stuff and after this be sure to install the header files
from the nekowares.
but be careful, most nekoware is gcc and some are not useable for building stuff with mipspro.

It sure would be nice to see some sort of giudeline on how to setup a 6.5.x ~ R10K and above machine to compile your own software and run all the kick-butt stuff already compiled and ported, in one nice document. I know that this information is here, but it seems like a bitchkitty to find in several different documents.

this is because this is general unix stuff and neither irix nor nekoware specific.
there's no general cheat sheet for compiling stuff. every app can be a special case...

For example, the firefox builds(eventhough not a nekoware release), if one does not know any better (ie: Me)
1. Download
2. Extract into correct place
3 Set Library paths and such
4 enjoy

this is not too hard:
- extract into /usr/local/firefox
- ensure the deps can be found in your paths
- start with the gtk1 version
if done correctly it should run without any further work.

foetz wrote: but be careful, most nekoware is gcc and some are not useable for building stuff with mipspro.

Only the old 'archived' Nekoware is gcc. The new stuff is built with MIPSpro.

Point 1 seems easy enough. I was doing 'inst name of tardist.tardist'. As a side note if you do it this way it takes a long, long time.

Point 2. "Setting up paths"
I know doing this depends on what shell you are using correct?
Is there a way to set this for all users regardless of the shell used?
Kind of a System path in ms-terms?
Also the libraries, if I install all of the Neko stuff, reside in a different place (/usr/nekoware/libxx). Is it an insanely stupid thing to do to create my own /lib_other dir and copy all the libs from /usr/freeware/libxx and /usr/nekoware/libxx into /lib_other/libxx/?
At this point can I just set a variable in my shell to point to my /lib_other/libxx path?
If this is possible, how does one do it?
Otherwise, can someone re-explain setting up these variables in a bash shell and/or a tcsh?


Point 3.
When you say dev stuff are you refering to the IRIX Dev Cd's?
Also, what is a header file and where do I put such files? (told ya I don't know diddly-poo, except ./configure,make,make install )

Last bit...
What is the difference between the gtk1 install and the gtk2 stuff? Besides the pretty colors and all.)

Thanks a bunch,
Your humble IRIX n00b
SoonerFan

nekonoko wrote:

foetz wrote: but be careful, most nekoware is gcc and some are not useable for building stuff with mipspro.

Only the old 'archived' Nekoware is gcc. The new stuff is built with MIPSpro.

really?
i recall a post that said gcc was made with gcc and glib2/gtk2 provide gcc typical errors when
used with mipspro...

Soonerfan wrote: Point 1 seems easy enough. I was doing 'inst name of tardist.tardist'. As a side note if you do it this way it takes a long, long time.

Point 2. "Setting up paths"
I know doing this depends on what shell you are using correct?
Is there a way to set this for all users regardless of the shell used?
Kind of a System path in ms-terms?
Also the libraries, if I install all of the Neko stuff, reside in a different place (/usr/nekoware/libxx). Is it an insanely stupid thing to do to create my own /lib_other dir and copy all the libs from /usr/freeware/libxx and /usr/nekoware/libxx into /lib_other/libxx/?
At this point can I just set a variable in my shell to point to my /lib_other/libxx path?

VERY bad idea

If this is possible, how does one do it?
Otherwise, can someone re-explain setting up these variables in a bash shell and/or a tcsh?

sure, ksh and compat. is: export PATH='/usr/foo:/temp'
csh is: setenv PATH '/usr/foo:/temp'

Point 3.
When you say dev stuff are you refering to the IRIX Dev Cd's?
Also, what is a header file and where do I put such files? (told ya I don't know diddly-poo, except ./configure,make,make install )

i would advise you to start with learning about apps and their deps.
later have a deep look at unix system environments.
after this build some custom stuff with gcc and then with mipspro.
proprietary unix with native compiler might not be the best starting point.

Last bit...
What is the difference between the gtk1 install and the gtk2 stuff? Besides the pretty colors and all.)

try gtk.org

foetz wrote: really?
i recall a post that said gcc was made with gcc and glib2/gtk2 provide gcc typical errors when
used with mipspro...

Yes really. I explained this once before ... it does not matter what compiler you use to bootstap gcc. Why? Because the end product is compiled with itself, i.e. gcc is always - (unless you're packaging up the raw stage1 which is a very broken way to go about things) - compiled with gcc in the end (ie. gcc 3.4 built with gcc-3.4). It makes zero difference how you get there, except maybe some sort of inflated ego (and maybe reduced compile time on stage1, but that doesn't change the end result).

Besides, gcc is not a library and your original complaint was regarding link compatibility between gcc and MIPSpro

As for glib2/gtk2 as far as I know they are 100% MIPSpro.

Thanks for all the information. It's just that this environment is quite a bit different that M$ and even linux to me. Maybe that's why it's so enjoyable to dink around in


thanks again,
SoonerFan

[quote="nekonoko"]
As for glib2/gtk2 as far as I know they are 100% MIPSpro.[/quote]

(Offtopic)

Didn't you get linking problems at the end of the compilation? What options did you used? Did you apply any patches on the source?

Orakel wrote:

nekonoko wrote: As for glib2/gtk2 as far as I know they are 100% MIPSpro.

(Offtopic)

Didn't you get linking problems at the end of the compilation? What options did you used? Did you apply any patches on the source?

squeen did those, but there should be notes/patches in the tardist as an optional install.

nekonoko wrote:

foetz wrote: really?
i recall a post that said gcc was made with gcc and glib2/gtk2 provide gcc typical errors when
used with mipspro...

Yes really. I explained this once before ... it does not matter what compiler you use to bootstap gcc. Why? Because the end product is compiled with itself, i.e. gcc is always - (unless you're packaging up the raw stage1 which is a very broken way to go about things) - compiled with gcc in the end (ie. gcc 3.4 built with gcc-3.4). It makes zero difference how you get there, except maybe some sort of inflated ego (and maybe reduced compile time on stage1, but that doesn't change the end result).

oh, maybe my post sounded a bit too rough. meant no harm with it!
i know about the gcc stuff mentioned here and that this is the official attitude but in some cases
i made other experiences.

Besides, gcc is not a library and your original complaint was regarding link compatibility between gcc and MIPSpro

it was NO complaint! just wanted to let him know that it's possible that sometimes some stuff
doesn't work and it's not his fault.

As for glib2/gtk2 as far as I know they are 100% MIPSpro.

sure if you say it i believe it. it just shows some well known issues happening with gcc builds so
this was the first that came to my mind.
i guess you know that i know very well how much work it is to provide a complete suite like nekoware.
be sure i esteem this!

nekonoko wrote:

Orakel wrote:

nekonoko wrote: As for glib2/gtk2 as far as I know they are 100% MIPSpro.

(Offtopic)

Didn't you get linking problems at the end of the compilation? What options did you used? Did you apply any patches on the source?

squeen did those, but there should be notes/patches in the tardist as an optional install.

Neat -- thanks squeen, and everyone else who documents their build process. I've succesfully compiled glib 2.4.0 and 2.4.2 now.

foetz wrote:

As for glib2/gtk2 as far as I know they are 100% MIPSpro.

sure if you say it i believe it. it just shows some well known issues happening with gcc builds so
this was the first that came to my mind.
i guess you know that i know very well how much work it is to provide a complete suite like nekoware.
be sure i esteem this!

foetz -- you willey old hacker -- I've been hoping to get some feedback from you regarding the new nekoware. It is my belief, unless configure out-foxed me, that the gtk 2.4 on nekoware/beta is 100% MIPSpro. If you have run into some errors please tell me what they are to I can go back and try and fix the port. Also, if your builds don't exhibit the same errors I'd like to know that as well. You know that I'm just stumbling my way through this and its a big help if the elder statesmen like yourself help keep things on course. The goal is to have a stable foundation that most folks feels comfortable building against and using.

squeen wrote: It is my belief, unless configure out-foxed me, that the gtk 2.4 on nekoware/beta is 100% MIPSpro. If you have run into some errors please tell me what they are to I can go back and try and fix the port.

most likely the biggest problem is that gtk-2 is awful I worked with a guy once who claimed that, "You can't make chicken pie out of chicken shit" and boy, looking at the direction gnu is headed, he had a point. A excellent point ....

squeen wrote:

foetz wrote:

As for glib2/gtk2 as far as I know they are 100% MIPSpro.

sure if you say it i believe it. it just shows some well known issues happening with gcc builds so
this was the first that came to my mind.
i guess you know that i know very well how much work it is to provide a complete suite like nekoware.
be sure i esteem this!

foetz -- you willey old hacker -- I've been hoping to get some feedback from you regarding the new nekoware. It is my belief, unless configure out-foxed me, that the gtk 2.4 on nekoware/beta is 100% MIPSpro. If you have run into some errors please tell me what they are to I can go back and try and fix the port. Also, if your builds don't exhibit the same errors I'd like to know that as well. You know that I'm just stumbling my way through this and its a big help if the elder statesmen like yourself help keep things on course. The goal is to have a stable foundation that most folks feels comfortable building against and using.

hehe, "elder statesman"
cool!!

well, no problem to provide some nekoware improvements. i haven't been under the impression
'foreign' influence is very welcome but i'm happy about this.

just compile an app with mipspro using the neko atk, pango, glib and gtk. you might see some
linker errors similar to those gcc builds provide.
then just replace the 4 packages with the ones from me and all runs fine...

feel free to contact me.