The collected works of foetz - Page 28

you simply don't have a shared libstdc++
r-a-c.de
i have no idea which nekoware package has that specific file. maybe we should have an index for such cases and also we usually do add something like -gcc to the name of all contributions that are built with gcc
r-a-c.de
add a glibc and you have a linux vm :P
r-a-c.de
vishnu wrote: `man xsgi` doesn't mention it...

the 5.3 manpage doesn't mention it either :P
r-a-c.de
armanox wrote: I'm now using mbedTLS (used to be PolarSSL) with curl

and that causes problems?
r-a-c.de
diegel wrote: You find a lot of threads about beta testing a lack of response in this forum. I think we would have a lot more ported software if the participants of this forums would help or simply give any feedback.

that also depends on what's up for grabs. mame is something quite specific and surely not the typical sgi target.
as for some of the other threads, the 8th version of some minor lib might just not be so attractive especially if the previous ones worked fine.

either way if the package does conform to the nekoware guidelines and didn't show issues after some testing i see no reason not to declare it current. in doubt leave the previous version in place or move it somewhere else so no harm done. in fact imho nothing should be deleted. there's always the odd case where you need to go 2 versions back or something so for example an "archive" dir where all previous ones go would be a good idea i think
r-a-c.de
mapesdhs wrote: I was going to link to a post I made way back showing how this works with an O2 top lid

maybe this one viewtopic.php?p=7318821#p7318821
r-a-c.de
mapesdhs wrote: Odd, I have a different URL:

it doesn't matter. mine is a direct link to a specific post in which case the viewtopic script gets the rest by itself
r-a-c.de
well one step at a time. do certain programs only work right with openssl 1.x?
if so does openssl 1.x fail to build? and if yes is it something that is irix specific and cannot be fixed?
r-a-c.de
armanox wrote: OpenSSL 0.9.8 is too old to be useful for a lot of things

could you give a few examples?
r-a-c.de
vishnu wrote: One thing's for sure, the LibreSSL guys didn't think too highly of the state of the OpenSSL code when they forked it.

they should've kept the build system tho. libressl comes with a bunch of crap such as hardcoded, gcc specific cflags and such
r-a-c.de
PowerGraphics wrote: If I understand well, all I need to do to my system supports 24bit (dithered or not), it would be put in the Xserver file, only the command -depth 24, and nothing else, not even put -class TrueColor (or PseudoColor or DirectColor), is this?

just try it, it can't do much harm
r-a-c.de
vishnu wrote: 'Tis a thing 'o beauty! :mrgreen:

:D
r-a-c.de
uunix wrote: fitted new R12000 3000MHz.

:shock:

my son destroyed by knocking it off the table

:shock:
r-a-c.de

funny to read "- Do portability right. " in there. at that they not only completely failed so far but actully made it much worse.
"- Preserve API/ABI compatibility with OpenSSL - We want to be essentially a drop in replacement." which failed as well. e.g. they simply dropped egd stuff completely without leaving any kind of warning, replacement dummy or whatsoever in place.

that aside i'm curious about why the presentation looks like from a 5th grader :P

armanox wrote: Oh, and the fact that IRIX does not support mapping anonymous pages doesn't help either.

that's an easy fix. i did that for my last postgresql builds. i can dig out the details if you're interested
r-a-c.de
indeed impressive how you reconstructed the whole thing. i wonder what you would/could do to an 68k sgi :D
r-a-c.de
if that's gonna be a soho unit then, is something broken or some required functionality missing?
i mean do you actually need updates, patches and stuff?
r-a-c.de
Dennis Nedry wrote: I wanted to mess around with netbooting various clients around the house via iPXE (sanboot)

well then just do that. otherwise you won't know if you're actually missing something
r-a-c.de
you wanna put the boxes on the desk?
r-a-c.de
armanox wrote: Yes please, because if I should go back to it (which I may since I still have an interest) it would prove very useful.

no prob. just open /dev/zero and map that fd shared. it was based on this: http://man7.org/tlpi/code/online/dist/m ... map.c.html
in my case adopted to postgresql of course but you can use it for anything else
r-a-c.de
Physical Cpu Count: 4 x R1600
Cpu Speed: 10 GHz
Cpu Type: R1600

indeed a great deal for a quad r1600 at 10ghz :P
r-a-c.de
  • curl_7410.tardist
  • openssh_68p1.tardist
  • openssl_102.tardist

so that your box is safe :-)
r-a-c.de
i didn't have problems with 0.9.8 so far but the thread here made me curious so i built openssl 1.0.2 and ran a few tests. in particular what you mentioned:

Code: Select all

openssl s_client -connect google.com:443 -tls1_2
...
SSL-Session:
Protocol  : TLSv1.2
Cipher    : ECDHE-RSA-AES128-GCM-SHA256
Session-ID: 377D63936E31C49711BA2193BFE34113C136F9D25C7B753C36B47432D59D67EA
Session-ID-ctx:
Master-Key: E8D9D45EE9F7CF260481744A36E660E0F30CCDF3DCDAC649D95350023AC584DEA05E5D95887D55028ED60E58AE97E079

openssl dgst -sha1 curl_7410.tardist
SHA1(curl_7410.tardist)= ed4f05342ffab45dafc79419244e848416206c5b


also built a new curl and openssh based on 1.0.2 and they worked, too. maybe i missed something but the things i usually do worked all fine. in case you wanna grab them: viewtopic.php?f=7&t=16728266&p=7377731#p7377731
r-a-c.de
mattst88 wrote: It's 10 GHz since it's only an R1600. :)

ah yeah thanks, indeed that makes sense :D
r-a-c.de
lol seems i missed it by just a few minutes :P

EDIT:
  • openssl_102a.tardist

okay there it is
r-a-c.de
ajw99uk wrote:
foetz wrote:
mattst88 wrote: It's 10 GHz since it's only an R1600. :)

ah yeah thanks, indeed that makes sense :D

Maybe it's the one they developed from uunix's 3000MHz R12000? ;)

:P
r-a-c.de
turn on verbose make so that you can actually see the compilation line. then try the file in question with lower optimization or a different frontend as described there viewtopic.php?p=7373083#p7373083
r-a-c.de
Dennis Nedry wrote: what can I do (if anything)?

either get the patches and hope it helps or sell it or use it as it is or don't sell it but don't use it and put it in the closet :P
r-a-c.de
according to the homepage: "(Feb-2015) * The official DR4 release is cancelled"
which means?
r-a-c.de
Dennis Nedry wrote: That was the whole point of my original post. I would get the patches if I could, but apparently I can't, unless there's some other way to get them that I haven't thought of

that's how it is and i'm afraid discussing "alternative" ways of getting these patches or anything else that requires a valid support contract is against our forum rules.
r-a-c.de
Axatax_ wrote: This was a complete MIPSpro/SGI port that probably took a good portion of two weeks. Unfortunately I no longer have any of this, as I deleted it

what a pity. you just threw away a 2 week's work? :shock:
r-a-c.de
gijoe77 wrote: there was an error while linking xmame.obj (something about -lexpat)

then you either have no expat or the linker can't find it
r-a-c.de
gijoe77 wrote: I had to add

Code: Select all

INCLUDES = -I/usr/nekoware/include


to the makefile because the compilier was bombing on not finding expat.h at some point, which seemed to fix the issue up until the final linking. I did verify expat was installed when I first ran into the expat.h issue. so now the trick for me will be how to make the linker find it :)

since you seem to use the nekoware expat add -L/usr/nekoware/lib to the LDFLAGS.

btw that's general stuff not related to a specific compiler. you said you compiled it with gcc so the same would have applied there, too
r-a-c.de
gijoe77 wrote: I will not rest until Street Fighter 3 is running on my SGI...

:D
r-a-c.de
gijoe77 wrote: I'm surprised the gcc build runs a few frames faster then the MIPspro build! both were basically built with -O2

basically? that doesn't help :P
have a look at a full compile line of each and compare all options. also keep in mind that the vast majority of all freeware is made for gcc hence the makefiles as well as the source code often contain additional "tunings" if gcc is detected. only after finding such stuff and making the appropriate changes a fair comparison can be done.
either way the main goal here is to use -O3, no matter which compiler
r-a-c.de
gijoe77 wrote: so whats the main difference between -O3 and -Ofast ? is -Ofast > -O3?

How exactly does -OPT:Olimit=0 come into play? Can that be used with either -O3 and/or -Ofast?

Code: Select all

man cc

;)
r-a-c.de
vishnu wrote:
foetz wrote: according to the homepage: "(Feb-2015) * The official DR4 release is cancelled"
which means?

It says that on maxxdesktop.com? Because I'm not seeing it anywhere, or finding it using the search button.Link! Please... 8-)

oh you don't believe me :P
there: http://dev.maxxdesktop.com/trac/maxxdesktop
r-a-c.de
ha nice find :P
sadly from v10 upwards the gui sucked

vishnu wrote: But the Irix dl is only 225 kilobytes...

MEGAbytes :P
r-a-c.de
gijoe77 wrote: It still looks like PowerAnimator to me :)

no, the gui changed. it not only lacks contrast but first and foremost is way slower than the previous one that was in place before v10. starting with v10 they shifted their main focus to windows, how it ran on the other soon to be phased out machines didn't matter. they also dumped what was left of the animator branch step by step and started integrating studiopaint which however was only available with the windows versions.
the last good alias version for irix is 9.7.
r-a-c.de
  • re2c_0141.tardist

this is quite neat. it's a regex to c translator. for details have a look at http://re2c.sourceforge.net .
it's "modern" c++ tho so mipspro builds on pre-6.5 irix are not gonna happen without quite some rewrites.
r-a-c.de