The collected works of vishnu - Page 7

So you're saying that the PTB in the PRC keep track of who's downloaded what from sourceforge.net and take action on it? Scawy! :shock:
SAQ wrote:
vishnu wrote:
kubatyszko wrote:
<joke>
afair, two v12's mean the second one is upside-down, you may need some rotation tool or a because of that ;-)
</joke>
A Sit 'n Spin should suffice http://www.amazon.com/Spin-Around-Sit-and/dp/B000XQ51B4/ref=sr_1_1?s=toys-and-games&ie=UTF8&qid=1357365960&sr=1-1&keywords=sit+n+spin :mrgreen:


Do they make a hyperdimensional model for those tricky left/right things?

They do, but it involves the W plus, W minus and Z zero bosons of the weak nuclear interaction, so it's a little out of the price range of the average Nekochaner... :lol:

_________________
Project:
Movin' on up, toooo the east side
Plan:
World domination! Or something...
Presumably you're saying the STL that comes with MIPSPro can't compile it?

Here's the MIPSPro STL FAQ: http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=bks&fname=/SGI_Developer/books/STL_PG/sgi_html/FAQ.html&srch=STL

The STL is all header files, i.e. no STL functions exist in the MIPSPro C++ shared object, so it doesn't matter how nice an STL you install if the compiler(s) on your system can't compile it...
bitcpy wrote:
...it looks like message is stuck in "outbox"..
That's a phpbb "feature," PM's stay in your outbox until the recipient reads them. That way you can edit them or even delete them ("Unsend! Unsend!") should you so choose...
hamei wrote: I'm prob'ly teaching grandma to suck eggs here, but did you know that < man cc > has a ton of stuff about gcc-isms and how to get around them?
True but what I've compiled so far has not been a problem for MIPSPro in CC (not c99) mode. The show stopper in dialog.cc is just plain bad code, and I think it's a bug that gcc doesn't see that...

hamei wrote: This was a bit interesting ... at least we aren't the only people in the world with some unusual desires ...
http://stackoverflow.com/questions/1250 ... pplication
No replies, tho :(
No replies because, with regard to what he's asking about doing, well to put it quite simply "you can't get there from here..." ;)
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...
Pontus wrote: The main reason for getting raised floor for me is the uneven floor. Here are some pictures of my slow progress:

http://www.update.uu.se/~pontus/slask/garage/

:shock:

What the heck is that thing that looks like a giant chiller unit? :?: :?: :?:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...
So now I'm trying to compile it in c99 mode and I'm wondering if my compiler installation is borked, could someone kindly cd into dillo's dw directory and post the output from doing this:

Code: Select all

c99 -c -w findtext.cc -o findtext.o


I get seven errors all having to do with the variadic macros, which MIPSPro 7.4's c99 is supposed to understand. :cry:

So if any of you kind people can get it to compile I'll know it's a bad compiler installation on my end.
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...
So you set the display to 24 bits using xsetmon (a.k.a. "Graphics Back End Control") and you don't think it worked? What does `xdpyinfo | grep "depth of root window"` say?

_________________
Choosing stones, big enough to drag me down...
Um, well, maybe when you thought it was 8 bit it was really 24? Maybe try setting it to a lower bit depth and see if you notice any difference...

_________________
Choosing stones, big enough to drag me down...
And you're sure the LCD display you're using can display 24 bit color?

_________________
Choosing stones, big enough to drag me down...
hamei wrote: Notice the third warning down though ? Something odd going on ?
I think that's a bug in the header file, a couple of the others have it too: grep "ifndef __c99" /usr/include/*.h . . . How much does sgi charge for a MIPSPro license again? :roll:
canavan wrote: The MIPSpro C++ compiler isn't c99 compliant...
Yep, I think that's the "other difficulty" I was talking about above... :lol:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...
My thought was that the VFO file the OP is using to communicate with his LCD might be borked...

_________________
Choosing stones, big enough to drag me down...
Pontus wrote: Could you be more specific? You might be looking at the rear end of an 11/750
No, the thing with the copper pipes and the gauges... 8-)
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...
I though some of you might get a kick out of how obsessively well organized our customers at work insist that our wire runs be... 8-)

_________________
Choosing stones, big enough to drag me down...
Neeeever heard of 'im... ;) :lol:
Or Lance Rentzel? :lol:
hamei wrote:
A thousand eyes, a thousand hands ...
I'm pretty sure the Dillo team isn't that big... ;)
hamei wrote:
...and Larry, Moe and Curly in charge :P
Or that Stoogey... :lol:
Fuel wins in terms of disk transfer rates and CPU speed (900MHz[1] max compared to Octane2's 600MHz), it's a dead heat in terms of graphics since they both max out at V12, but other than that the Octane2 wins in every category, especially in terms of it's workstation-class construction, they're designed to keep working no matter what, the Fuel was SGI's attempt to see if it could compete with the high-end PC market, in terms of price. They couldn't... :lol:

[1]Finding a Fuel with a faster than 600MHz CPU is no simple task, basically because the people who own them aren't selling them; they're still too useful... :mrgreen:

_________________
Project:
Movin' on up, toooo the east side
Plan:
World domination! Or something...
hamei wrote:
"America's Team", yuck. But at least he was human. Yeah, Lance is still better than the plastic crap they serve up nowadays.
The dude could catch the football like none other but he had that nasty habit of flashing leetle girls... :shock:
Nah, this one wasn't for Apple it was for a much smaller organization - the US Navy... :lol:

And though I'd like to say we did it so nicely because of our dedication to the craft, the true reason is much less altruistic, cost plus... :shock:

_________________
Choosing stones, big enough to drag me down...
Using a Video Format Object file that's custom crafted for your LCD can make a significant impact in the quality of the display, see for example: http://forums.nekochan.net/viewtopic.php?f=3&t=16725909&p=7344752&

_________________
Choosing stones, big enough to drag me down...
Well I fixed the variadic macros enough to get it to try to compile findtext.cc, but now it's puking on dillo's use of namespaces. This might not be worth it... :x
jan-jaap wrote:
Thought I recognized the (smaller) MIL connectors -- D38999 series?
Yep, thirty eight triple nine, or as I like to refer to them, the bane of my existence... ;)

_________________
Choosing stones, big enough to drag me down...
So okay, the dillo guys are declaring three namespaces across two header files and one implementation file (findtext.cc, findtext.hh, and core.hh), MIPSPro seems to get through the header files okay but then pukes on the first namespace declaration in the implementation file. I've mimicked what I think they're doing in three much simpler test files, but MIPSPro turns those into an executable with no complaint. Perhaps the problem is with the dillo classes; my test harness just has functions not classes. Drear. I thought computers were supposed to free us from this kind of drudgery not enmesh us in it... :oops: :P
SAQ wrote:
bitcpy wrote:

If I can find a good example of each, I will buy both and just try them for myself to make a final decision on which to keep permanently.


Danger, Will Robinson.

You'll wind up keeping both.

Quote:

That's what I was going to say, if he ends up buying either the Fuel or the Octane or both, the one he'll end up purging will be the I2... :|

_________________
Project:
Movin' on up, toooo the east side
Plan:
World domination! Or something...
True dat, the US Navy's anything but real world... :lol:

No covers over the line fuses? I'm not sure OSHA would approve! :shock:

_________________
Choosing stones, big enough to drag me down...
smj wrote:
Framemaker and Interleaf were a big deal with the tech writers at various companies I worked for prior to ~1997.
Call us old fashioned but we're still using Interleaf 6 on virtually all of our technical publications to this day, running on Sun Blade 2500s... :mrgreen:

_________________
Project:
Movin' on up, toooo the east side
Plan:
World domination! Or something...
Ha ha, you guys are fawwwwny! :lol:

Looking at it some more tonight and I have to say I have no idea what the problem is. Maybe MIPSPro 7.4.4. can compile it? I'm using 7.4.3 so it seems a faint hope, but If anyone wants to give it a try, replace the msg.h that's in the lout subdirectory with this:
Code:
#ifndef __MSG_H__
#define __MSG_H__

#define prefs_show_msg    1

#if defined(__cplusplus) && defined (__sgi)
#include <iostream>

void _MSG      ()           {}
void _MSG      (char * str) {}
void _MSG_WARN ()           {}
void _MSG_ERR  ()           {}

void MSG(char * str)
{
using std::cout;
using std::endl;
if (prefs_show_msg) {
cout << str << endl;
}
}

#else

#define _MSG(...)
#define _MSG_WARN(...)
#define _MSG_ERR(...)

#include <stdio.h>

/*
* You can disable any MSG* macro by adding the '_' prefix.
*/

#define D_STMT_START      do
#define D_STMT_END        while (0)

#define MSG(...)                                   \
D_STMT_START {                                  \
if (prefs_show_msg){                         \
printf(__VA_ARGS__);                      \
fflush (stdout);                          \
}                                            \
} D_STMT_END

#define MSG_WARN(...)                              \
D_STMT_START {                                  \
if (prefs_show_msg)                          \
printf("** WARNING **: " __VA_ARGS__);    \
} D_STMT_END

#define MSG_ERR(...)                               \
D_STMT_START {                                  \
if (prefs_show_msg)                          \
printf("** ERROR **: " __VA_ARGS__);      \
} D_STMT_END

#endif /* defined(__cplusplus) && defined (__sgi) */

#endif /* __MSG_H__ */


...and then type `make' - DISCLAIMER: this version of msg.h has only been hacked enough to get past the compiler's attempt to objectify findtext.cc, additional overloaded C++ functions will have to be added to accommodate the rest of the program. One slogging source code file at a time, right? :P

EDIT: Diddled around with msg.h a bit more and got findtext.cc to compile! Also iterator.cc (fixed version of msg.h is above) So, forging ahead. Will update more status when there's more status to update...
My first experience with SGis was when the PTB at work decided to switch CAD systems from Anvil to Pro/ENGINEER. This would have been around 1992, when the only computers in the world capable of running Pro were SGIs. As the years went by we switched to less expensive Sun workstations for CAD, which was when I bought my personally owned Octane2, because I couldn't handle the 4Dwm withdrawl... :mrgreen:

_________________
Project:
Movin' on up, toooo the east side
Plan:
World domination! Or something...
hamei wrote:
I'm trying to put a date on it, but vishnu's phots are what control panels were like in the fifties...


The date on these is 1961 but have no fear, we still wire 'em all up like this... :mrgreen:

Dennis Nedry wrote:
What is it, and why is it built inside a box that appears to be 4-6mm thick metal?


It's a train and elevation test switch for a 5-inch Navy deck gun, built to the usual Navy "make it indestructible" standards... :shock:

_________________
Choosing stones, big enough to drag me down...
hamei wrote:
BSDero wrote:
Thanks, I think I'll try oleo!

https://lists.gnu.org/archive/html/bug- ... 00002.html

Wow, the development version of Oleo is almost 12 years old! There used to be some really good Motif hackers working on it, Danny Backx and Scott Tringali, couple of the guys behind NEdit and Lesstif. I guess once Gnome threw their weight behind Gnumeric they all just figured what the hell... :?
Yeah, you can't remove the variadic macro syntax (the three dots between ellipses) without replacing it with a series of overloaded C++ functions that can handle all the argument numbers and types that the source code is trying to pass in to them. Painful, I know, but that's what I'm trying to do with the Dillo code again right now. After nearly a year hiatus from when I first started working on it... :shock:
Yep I remember it:

"PROPHET is currently available on UNIX and ULTRIX workstations with Motif, OpenLook, and DECwindows windowing systems. These workstations include Sun-4, SPARCstation, and DECstation 5000. Additional ports and continuing enhancements are planned."

Link: http://www.ncbi.nlm.nih.gov/pmc/articles/PMC338184/
Tanqueray on the rocks with a Piquillo pepper stuffed Manzanilla olive please... 8-) :lol:

_________________
Choosing stones, big enough to drag me down...
If he does have a sense of humor then he, like me, is hoping that the open sourcing of Motif will bring it back from extinction... :lol: We need a dinosaur smiley... :mrgreen: :shock:
Pass -non_shared to the compiler?
mia wrote:
shopped!

Ha ha, nope, but I actually do have Photoshop 3 on my octane... :mrgreen:

_________________
Choosing stones, big enough to drag me down...
"First of all, JP Morgan is one of the best managed banks there is. Jamie Dimon, the head of it, is one of the smartest bankers we've got" --President of the United States Barack Obama, May 15, 2012 on "The View" :shock:

_________________
Choosing stones, big enough to drag me down...
So you're saying there's no way to do it by skipping rpath and just using autoconf's installation directory variables? For example: http://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Installation-Directory-Variables.html
It seems like the misdeeds have to be of nearly Enron-like proportions for anything to get done about it... :shock:

_________________
Choosing stones, big enough to drag me down...