SGI: Development

Well as far as Nekoware goes, new packages would need to be created but it's definitely possible. I run my own custom php5/mysql5 packages for Nekochan.net and it works just fine.

neko-pgsql-8.2.3 - fast relational SQL server

regards
Joerg

Guys,

I just uploaded neko_Squeak-3.9.8.tardist to incoming. Squeak is an implementation of the powerful Smalltalk programming language and environment.
Enjoy.



Benchmarks on 500MHz Fuel:


Compared to the results reported on Squeak site, this rather sucks; and this is already built with -OPT:Olimit_opt=on, which tripled the performance. I suspect this is due to quick'n'dirty way I "fixed" their use of inlining, viz. #define inline to empty string. In near future, I may look into this issue, and find the proper way to do inlining in mipspro.

Who have made the neko_binutils package?

This package only contains one image wich also not use the term sw.eoe. There is no dist, src, relnotes files. It would be fine if every package contains all the standard informations.

Btw. is there any risk when installing the binutils and use mips cc as default compilier. The usr/nekoware/bin is the first in $PATH when i compile software for nekoware and i expect some kind of trobule. Or is mips cc smart enough and use its own linker, assember?

regards
Joerg

That package came from regan_russell; he sent me a PM when he uploaded it but didn't post to the forum afterward. I don't keep gcc installed on my IRIX systems (to remove temptation) so I've no easy way to test it.

F**K

All the stuff goes into /usr instead /usr/nekoware. After the deinstallation all went away and mips cc works anymore because ar,ld and more are now missing. I nuked my installation.

Please remove the package from /beta.

regards
Joerg

Uploaded version with fixed up dependencies, namely removed dependency on expect. This is such a small change that I didn't even bump a package version.

I just uploaded neko_mpfr-2.2.1.tardist to incoming. The MPFR library is a C library for multiple-precision floating-point computations with correct rounding. MPFR is based on the GMP multiple-precision library (which already is packaged for nekoware).



Testsuite passes, but I had to degrade the optimization to -O2. No patches were necessary.

Enjoy.

LOL, i build the same software for nekoware a few hours ago because a friend of mine need it for building gcc 4.x.

I now move my build into the dumpster and use yours. Package looks good.

There is a odd thing about "/usr/nekoware-build/share/info/dir" which contains only a description of npfr. But the filename isnt very specific and i think "gmake install" makes something wrong. So its good that your package doesnt contain this file.

Btw.
I prefer to assing files from nekoware/share to the sw.eoe subimage because most time it contains stuff which is need for running the binary. Thats not true for npfr but i think "man.manpages" isnt the right place for it.

regards
Joerg

Heh, same here, but the person building gcc was me :) Last time I built mpfr locally just for gcc, but I did whole-tree rebuild now, and thought heck, why not do a proper package :)



This file is a common byproduct of installing info pages. "dir" is a directory with references to all the info pages installed on a system. When it doesn't exist, installation procedure creates a new one.

On my installation, info files are in /usr/nekoware/info; in /usr/nekoware/share/info there is currently only mpfr page. Possibly the installation process is hosed in how it handles info pages.



Well, it's a documentation that serves the purpose very similar to man page. It's in no way necessary for mpfr runtime. I think "man.manpages" suits them well.

Thinking about it, packaging the info file without post-install command "install-info" is wrong, too, because then the info page isn't in "dir". I will fix that, but will first have to experiment with pre/post-install commands a bit, e.g. how it handles package upgrades.

I was the guilty party who uploaded binutils, which was a sereously bad tardist. I have since attempted to fix all the problems. I stated in a pm that it was my first tardist and I said it was

I would like to publically apologise to Jeorg and thank him for his guidence in fixing the mess I created.

I am as of right now, uploading a corrected version: neko_binutils.tardist
It puts things in /usr/nekoware, and I think it is a valid tardist, built with MIPSpro 7.4.4

Edit: While I am thinking about it... It is not that hard to test. Use a compiler either MIPSpro or gcc and compile with the -s flag to generate assembler from any C or C++ code.. Assemble the .s code with /usr/nekoware/bin/as object dump or octal dump (od -c) or nm or strings or whatever you like with result and try linking it with /usr/nekoware/bin/ld against something say glibc.


Regan

Or you can use "man.infopages". I always used it while I packed tardists.

From last week
neko_mysql4-4.1.22 - Fast relational RDBMS

Today
neko_rrdtool-1.2.19 - Logging & Graphing

Also working on neko_net-snmp-5.4 . This time i also want to add init script to our package. But iam clueless about the snmp stuff and its config files which dont exits :). The naming of the libs are different now and i expect some problems with apps which links agains the previous version of neko_net_snmp. Needs some checking first.

regards
Joerg

Moin

I've managed to do my first tardist:

neko_fvwm2-2.4.20 An extremely powerful ICCCM-compliant multiple virtual desktop window manager

thanks for all the help go to joerg

cheers

Can someome check audacity?
The package name on http://www.nekochan.net/wiki/nekoware/index.php?path=beta/ looks ugly.

/tmp/dist/audacity 1 9630d5f1a8ba658414d163f2b4ed1258

regards
Joerg

Moin

Added neko_pkgconfig-0.21 ...

( I meant 0.21 )

Its me again

I just added neko_windowmaker-0.92.0

Ooh... gotta check that! WM is my favourite!

i take a look for windowmaker in the download section, but nothing
where to get it ?

laurent