The collected works of dexter1 - Page 4

squeen wrote: Are you saying the problem was supposed to be fixed in 7.4.x but was not? Or is it some sort of unintentional linking particular to the YafRay make?

The problem apparently wasn't fixed in 7.4.x because the static library libCio_pthreads.a is still being shipped with the devlib.
And linking this static with Yafray doesn't fall out of the sky, i had to learn scons for that :) But now i've sorta bluffed my way through it, i could even do -IPA builds and add -lfastm to the mix

Anyway neko_yafray-0.0.8.tardist is out, get it and test it :)
kinaed wrote: I installed it this evening. As soon as it starts to render under blender, blender dumps.

Any special instructins with this dist?

Not that i know of. Does the big.xml file render correctly? Which blender version are you using? What error message do you get? I haven't tested this Yafray build with Blender, since i never used Blender before.
Could be that the libyafrayplugin.so and blender doesn't like eachother.
kinaed wrote: I am using Blender 2.37a. If I run blender in debug mode, the only message I see at the console is :
Starting scene conversion.
Scene conversion done.
Loading plugins ...
Segmentation fault (core dumped)

Looks like the classic -D_PTHREADS ostreambuf bug. Those damn Yafray developers use -D_PTHREADS everywhere, even on places where it is definately not needed, which means i have to stub -lCio_pthreads all over the place. *Sigh*
I'll get on it and tomorrow (europe) i'll have that version ready.
Done: neko_yafray-0.0.8.tardist the 3rd

I have reverted back to the compile without the -D_PTHREADS -lCio_pthreads, since the blender binary needs those, because the libCio_pthreads.a can only be applied on executables and not DSO's, and i can't and won't be bothered to endeavour that :) Besides, it doesn't look like there's a big speed impact anyway so i went ahead and packaged it.

Oh and bad-assed blender only looks for yafray in /usr/local/lib :roll: so the tardist makes symbolic links. I know, UglyMutha, but it now works both standalone and as plugin.

Do

Code: Select all

setenv PYTHONHOME /usr/nekoware/lib
setenv PYTHONPATH /usr/nekoware/lib/python2.3

before starting blender, otherwise it can't find the plugin

And now i'd reeeeealy like a different project now 8) I've seen too many glassobjects with blue cubes....
You need a book, and later something you want to program :)

"The C handbook" By Kernigan&Ritchie is a good first time book on C-programming.

If you want to do GFX, you can ofcourse start with openGL. It's handbook is also famous for its numerous examples, though i don't know if it still can be had...
You mean the front end? Yeah that can be had on ebay. Be sure to mind the correct version of MIPSPro.
It's not so important that you get MIPSPro for C++ learning experience. GCC/G++ is also an excellent compiler to aid you in learning how to program C and C++.

The best C++ book out there is: "The C++ Programming Language, Third Edition" by Bjarne Stroustrup.
Steady there, Ian_finder...

I do not want this thread to go down by politics again. Please refrain from dragging US history into the Microsoft Corporate World Business Strategy Leveraging Crap Software Thingy.

Rebooted my NT server yesterday, because the print spooler partout refused to serve our spools after the move.
Needless to say, i'm secretly converting all spoolers to my O200 Cups server. Hope my esteemed colleague doesn't notice :twisted:
You could also try setting the environment variable LD to the gnu linker
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
...which will give you a unique Flock of Seagulls haircut if you place yourself in the draft area.

BTW, *bows* to you Ben. I am honored to see a legendary MegaMix DMC DJ entering our ranks! Must have been '83-'84 since i first heard of you via the Soul-Show i believe. I blame my older brother for all that music influence:)
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Between all the WoW activities, paintjobs in our house, driving lessons, and the odd SGI tinkering here and there i'm happy to announce to you all that Fem and I are going to be parents:

Image

Now clocking at 13 weeks, we still have a long way to go. Hopefully everything will go allright, but passing the 12 week milestone gives us confidence we might be looking at a new life soon.

Yay! :D
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Awesome new smilies :o

Let me try

:O2: :Indigo: :Indigo2IMP: :Indy: :Crimson: :O2000: :O200: :PI:

Good to see you all around after so many years, btw.

dexter1

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
You should be able to find some log stuff in /var/adm/crash. If there is nothing there, try enabling dumping with "chkconfig savecore on" and reboot and wait for the next crash.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
hi Joerg, Josehill and Squeen and everybody :) Yep i'm back, see my post in "Everything Else"

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
i just checked on your website, it looks awesome!
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O200: :O2000: :Onyx2:
You might also want to remove eoe.sw.gifts_perl since that is another non nekoware Perl it sees.

Looks like Inkscape needs some rld paths re-set.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Image
Our Fresh new baby boy (well, a month old already)! He goes by the name "Storm" and he is a big dude. We welcomed him the 18th of December last year. Doctors had to perform a Cesaerean, but Fem seems to recover fine. Click on the picture to check the album.

Ah well, covered in diapers leaves me not much to do anything regarding SGI's, though i have managed to revive my Indigo2 with another PSU. I have to get going with some builds again in the near future.

Unfortunately, personally my health is not 100%. I'm suffering from short Migraine attacks since early november and after substantial medication i am going to see a specialist soon, i hope :(

Thanks to Joerg who emailed me about the Primary mirror screw-up. It always helps to email me so i can put it on my todo list. Happy to tell you that a lot of email traffic is now diverted from mech001.citg.tudelft.nl, so this machine is returning to be a web-development box again. I have plans to upgrade hard and software so maybe we will be seeing some speed improvements the coming months.

yours always,

dex
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
I've briefly looked into this, since this codec is becoming increasingly popular among recent Blu-Ray formats and small handheld devices because of the higher quality and lower stream bandwidth requirements than conventional mpeg streams.

This codec is a real CPU hog. It looks to be an upgrade over the Sorensen codec which is used in early Quicktime designs in Mplayer from 2005. I did do some optimisations on this codec when i was busy with simple_idct.c for the mpeg codec, but the codec algorithm has much more branching and much finer idct blocking (4x4 instead of 8x8) so i only got a speedup of 5% or so.

To make a significant change in processing speed, i believe we have to resort to Assembly on the R10k/R12k and you probably need a second processor to handle the brunt of the remaining workload, like color conversion and loading/storing imaging, audio and openGL stuff.

Guess what i am reading at the moment? Yep: MIPS R10000 Microprocessor User Manual

This looks to be fairly complicated, because of the different design compared to X86 CPU's with mmx. If you browse ffmpeg source for H.264, you will see that this codec has extensive mmx/sse Assembly code for x86 architechture, so even there people had to resort to Assembly to speed things up.

Anyway, i will browse a bit and form some ideas.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
FYI, make sure you keep the old backups from techpubs, since SGI likes to refresh PDF documents for new systems, thereby increasing the minor document number and removing the old document :(

This happened to "OpenGL on Silicon Graphics Systems" : viewtopic.php?f=11&t=6345&p=47952

i have a june 2005 one, btw

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
jan-jaap wrote:
dexter1 wrote:
FYI, make sure you keep the old backups from techpubs, since SGI likes to refresh PDF documents for new systems, thereby increasing the minor document number and removing the old document :(

They add new revisions, but the old one is still there? Just look for "additional info" in the index listing all books.
For this book, there's still the -002 rev. from 1998 (The -001 rev probably relates to a pre-6.5 version of IRIX).


You are right, the book is still there, thanks for the pointer. Apparently my techpubs mirror does not have the "additional info" documents. The -001 i also have btw but that comes from the old source mentioned above.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
First try an 'resetenv' in the PROM. This will set the PROM environment to its default values, so you are certain there is no Linux cruft left there.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:
Neko, my advice is to keep the phpBB stuff. Don't waste time and money on something we don't have experience with. I'm very happy with phpBB as it runs smooth as silk.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
neko_python3-3.1.1.tardist is now in /beta
It does not supersede the current neko_python 2.5 since python3 is not compatible with older versions, hence the different name (python3) and version number (1). You can actually install both side by side.

I've created an account at python.org to issue bug reports so hopefully some IRIX stuff will trickle into the codebase soon.

All modules with dependencies are now separately listed and can be installed separately from the python3 core. Obviously Module zlib and bz2 are very valuable and needed, but only a few have sqlite3 or gdbm so they can opt-out for those modules.

I have sufficient ammo for python 2.6.3. but i rather return to firefox dev stuff. Been too long since i had a good look at that.

Go Blender 2.5, go!

dex
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
First of all can you tell us the exact pinout for the serial converter? Because you list the wrong section for the serial port on the Power Series. It should have been:
http://www.meadow.net/pinouts.html#sgiDB9F
I sometimes refer to it as a 4D-serial port, so for connecting a 4D-DB9 female to IBM-DB9 male serial port you need a 4D-DB9 male to IBM-DB9 female null modem cable. (for a stand alone terminal you need a 9-25 converter) I have such a cable for my Crimson and PI, and it took me a few tries to get it right.

This might explain why you do get output but no input response from the 4D-240. From "This old SGI" page:
Quote:
Buried deep within the GT graphics subsystem is a little-known interface which resides on the GM1 card. The GM1 appears to be built around a MC68020 CPU running at 16 Mhz. If you examine the card, you will notice a female DB9 connector. This connector provides an RS232C serial interface (9600,N,8,1) with more or less the same pinout as the standard SGI DB9 Serial connector. The only difference is that this serial interface doesn't support any of the hardware handshaking lines, so you can get away with simply connecting pins 2,3 and 7 via an appropriate adaptor cable (or you can use the same type of adaptor cable needed to connect an ASCII terminal to serial port 1 for debugging purposes. See the chapter on 4D Series Serial Port Pinouts for more details.)
So how about the GM> prompt? Can you enter stuff in there? Then chances are that your handshaking is correct for the GM serial port but incorrect for accessing the 240 serial port.

That output doesn't look good. I hope this improves by pulling out the GT boards and have a good look at it. Incidentally, can you make a photo of the GTX boardset? It can be anything ranging from 3 to 5 or even 6 boards. GM2 and GE4 should always be there, and they are bridged by a small board. You can have up to two RM1's and an RV1.5 or RV2.

Quote:
Also, is http://sgistuff.g-lenerz.de/ down or is it just me? (I just get a "500 Internal Server Error" message.)
http://www.g-lenerz.de/retro-collection.html might suggest that only his php link with apache is slightly shitty. standard html pages do load fine.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Thanks for the photos, i actually meant one photo of the system when powered on, but this looks neato as well :)
Quote:
030-0116-002 (some unlisted graphics option board with 2x RGBS BNC, 2x "composite" BNC, and DB-9 "trigger" ports)

I found something on:
http://groups.google.nl/group/comp.sys. ... c4a8deff72
and the VP1 is mentioned here:
http://groups.google.nl/group/comp.sys. ... 68f54c4c93
Could this be the VP1 digitizer? Can you check the board for a two-letter-one-number indication, usually next to the SGI part number. If you see a VP1 then you're the lucky owner of a rare video digitizer option for the GTX.

Where is the GM2 BTW?

Anyway, best way to isolate problems is to swap boards. The minimum gfx setup is an IO2, one IP7 and the MC2, followed by the GM2 bridged with GE4 and RV1.5. We only use the RV1.5 framebufer. If this already produces the pinstripe, then the RV1.5 board has bad memory somewhere. If reseating makes things worse, then also look at the backplane and check for bent pins or dirt.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Love the new site icon, Neko!

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
jan-jaap wrote:
My own 4D/440VGX has also started to act up. It looks like a glitch in the power resets the system after a couple of minutes. Looks like I'll have to get familiar with the PowerOne PSU's again this winter :(
Could it be a loose contact somewhere? Maybe the main switch? My Crimson suffered from a Main switch that didn't made fully contact and issued a reset every now and then. Replacing it with a new one solved the problem immediately

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Attachment:
GranParadiso.png
GranParadiso.png [ 431.6 KiB | Viewed 801 times ]


Check the Mozilla tag, it "proves" that it's running on my Quad R10K@225MHz Origin200.

I'm so bloody relieved, after more than half a year of pulling this project out of the mud in my spare time! 8)
More to come friday, i will post the patch file (+- 89 Hunks!) and the list of deps.

Stay tuned!

Dex

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
jan-jaap wrote:
I'll be damned. I changed both the breaker on the back and the on/off switch panel on the front, and at least for the time being it's working beautifully :D
Awesome, Jan-Jaap! This is exactly why i really love these old systems: Using soldering iron, steel file and pliers you can repair these machines very quickly.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Thanks Neko,

Though i limit my moderation to the actual SGI subforum, i haven't come accross nasty stuff in the last few months.

Maybe we should communicate who is checking out what, so that we can spread the moderation much more evenly. Ofcourse if one sees a violation you don't have to wait for another moderator or admin to remove it if you can do it yourself.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
hamei wrote:
Cairo is at 1.6.4 which compiles fine, newer versions do not :( Cairo is up to 1.8.8 or 1.9.2, depending on your bravery ...
You sure? I'm running 1.8.8 on my dev system. What's the problem with your compiles?

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
uh eh, libpixman is a requirement. Try building a new version of that first and let Cairo include it.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Hot off the presses:

http://www.blendernation.com/blender-fo ... rNation%29

No IRIX download yet, but atleast we have proper Python3 support and because it's fully python driven it should not be that difficult:

http://www.blender.org/download/get-25-alpha/

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Hi all,

Rich and i are still busy with Seamonkey 2.0 / Firefox 3.5 port. Hopefully i can get it done soon, so i can test the nspr pthread problems i discovered when running the 3.0.15 build.

We're helping eachother with compiler/C++ tips via email. He actually fixed a generic problem with header instantiation where templates and forward declarations are involved. i have to revisit my 3.0.15 patch and rework some of them.

Oh and '-Zf,_330 -ptused' in CXXFLAGS proves to be more robust than the generic options. The 3.3 Cfront frontend bypasses some dodgy g++-isms.

Hang in there guys! Holiday season is hitting us hard so there isn't much happening in terms of cool software projects and on top of that, my build machine rootdisk is giving errors so i have to duplicate that disk soon.

cheers,

Dex
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
I have a MC2 030-0117-039 Rev A but i have never occupied it with 8mb sticks since they are in my Crimson at the moment, and i do not have a IP7 anymore.

I'm sure JanJaap knows this.

from the 4dfaq it states that you cannot mix 2mb and 8mb on an MC2.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
To Xeno74:

I'm watching this thread closely. Please refrain from shouting, especially to forum members being so kind enough to actually test out patches and porting software.

People are waiting for firefox3 since march, and i don't hear anyone complaining...
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Firefox 3.5.6 patch file and first build is done. Running it gives me various runtime assertion failures:

Code: Select all

WARNING: NS_ENSURE_TRUE(compMgr) failed: file nsComponentManagerUtils.cpp, line 90
WARNING: NS_ENSURE_TRUE(compMgr) failed: file nsComponentManagerUtils.cpp, line 90
WARNING: NS_ENSURE_TRUE(compMgr) failed: file nsComponentManagerUtils.cpp, line 90
*** Registering components in: xpconnect
*** Registering components in: nsUCvMathModule
*** Registering components in: nsUConvModule
*** Registering components in: nsI18nModule
*** Registering components in: nsChardetModule
*** Registering components in: nsUniversalCharDetModule
*** Registering components in: necko
*** Registering components in: nsCookieModule
*** Registering components in: nsPermissionsModule
*** Registering components in: nsAuthModule
*** Registering components in: nsJarModule
*** Registering components in: ZipWriterModule
*** Registering components in: nsPrefModule
*** Registering components in: nsSecurityManagerModule
*** Registering components in: nsRDFModule
*** Registering components in: nsXPIntlModule
*** Registering components in: nsWindowDataSourceModule
*** Registering components in: nsParserModule
*** Registering components in: nsGfxModule
*** Registering components in: nsWidgetGtk2Module
*** Registering components in: nsImageLib2Module
*** Registering components in: nsPluginModule
*** Registering components in: nsLayoutModule
*** Registering components in: docshell_provider
*** Registering components in: embedcomponents
*** Registering components in: Browser_Embedding_Module
*** Registering components in: nsCJVMManagerModule
*** Registering components in: nsAccessibilityModule
*** Registering components in: appshell
*** Registering components in: nsTransactionManagerModule
*** Registering components in: nsComposerModule
*** Registering components in: nsChromeModule
*** Registering components in: application
*** Registering components in: nsFindComponent
*** Registering components in: Apprunner
*** Registering components in: CommandLineModule
*** Registering components in: nsFileViewModule
*** Registering components in: mozStorageModule
*** Registering components in: nsPlacesModule
*** Registering components in: tkAutoCompleteModule
*** Registering components in: satchel
*** Registering components in: PKI
*** Registering components in: nsToolkitCompsModule
*** Registering components in: RemoteServiceModule
*** Registering components in: nsSoftwareUpdate
*** Registering components in: JavaScript_Debugger
*** Registering components in: BOOT
*** Registering components in: NSS
*** Registering components in: nsSystemPrefModule
*** Registering components in: nsAutoConfigModule
*** Registering components in: mozSpellCheckerModule
*** Registering components in: nsUnixProxyModule
*** Registering components in: xpconnect
*** Registering components in: nsUCvMathModule
*** Registering components in: nsUConvModule
*** Registering components in: nsI18nModule
*** Registering components in: nsChardetModule
*** Registering components in: nsUniversalCharDetModule
*** Registering components in: necko
*** Registering components in: nsCookieModule
*** Registering components in: nsPermissionsModule
*** Registering components in: nsAuthModule
*** Registering components in: nsJarModule
*** Registering components in: ZipWriterModule
*** Registering components in: nsPrefModule
*** Registering components in: nsSecurityManagerModule
*** Registering components in: nsRDFModule
*** Registering components in: nsXPIntlModule
*** Registering components in: nsWindowDataSourceModule
*** Registering components in: nsParserModule
*** Registering components in: nsGfxModule
*** Registering components in: nsWidgetGtk2Module
*** Registering components in: nsImageLib2Module
*** Registering components in: nsPluginModule
*** Registering components in: nsLayoutModule
*** Registering components in: docshell_provider
*** Registering components in: embedcomponents
*** Registering components in: Browser_Embedding_Module
*** Registering components in: nsCJVMManagerModule
*** Registering components in: nsAccessibilityModule
*** Registering components in: appshell
*** Registering components in: nsTransactionManagerModule
*** Registering components in: nsComposerModule
*** Registering components in: nsChromeModule
*** Registering components in: application
*** Registering components in: nsFindComponent
*** Registering components in: Apprunner
*** Registering components in: CommandLineModule
*** Registering components in: nsFileViewModule
*** Registering components in: mozStorageModule
*** Registering components in: nsPlacesModule
*** Registering components in: tkAutoCompleteModule
*** Registering components in: satchel
*** Registering components in: PKI
*** Registering components in: nsToolkitCompsModule
*** Registering components in: RemoteServiceModule
*** Registering components in: nsSoftwareUpdate
*** Registering components in: JavaScript_Debugger
*** Registering components in: BOOT
*** Registering components in: NSS
*** Registering components in: nsSystemPrefModule
*** Registering components in: nsAutoConfigModule
*** Registering components in: mozSpellCheckerModule
*** Registering components in: nsUnixProxyModule
*** Registering components in: nsIconDecoderModule
*** Registering components in: BrowserDirProvider
*** Registering components in: nsBrowserCompsModule
*** Registering components in: xpconnect
*** Registering components in: nsUCvMathModule
*** Registering components in: nsUConvModule
*** Registering components in: nsI18nModule
*** Registering components in: nsChardetModule
*** Registering components in: nsUniversalCharDetModule
*** Registering components in: necko
*** Registering components in: nsCookieModule
*** Registering components in: nsPermissionsModule
*** Registering components in: nsAuthModule
*** Registering components in: nsJarModule
*** Registering components in: ZipWriterModule
*** Registering components in: nsPrefModule
*** Registering components in: nsSecurityManagerModule
*** Registering components in: nsRDFModule
*** Registering components in: nsXPIntlModule
*** Registering components in: nsWindowDataSourceModule
*** Registering components in: nsParserModule
*** Registering components in: nsGfxModule
*** Registering components in: nsWidgetGtk2Module
*** Registering components in: nsImageLib2Module
*** Registering components in: nsPluginModule
*** Registering components in: nsLayoutModule
*** Registering components in: docshell_provider
*** Registering components in: embedcomponents
*** Registering components in: Browser_Embedding_Module
*** Registering components in: nsCJVMManagerModule
*** Registering components in: nsAccessibilityModule
*** Registering components in: appshell
*** Registering components in: nsTransactionManagerModule
*** Registering components in: nsComposerModule
*** Registering components in: nsChromeModule
*** Registering components in: application
*** Registering components in: nsFindComponent
*** Registering components in: Apprunner
*** Registering components in: CommandLineModule
*** Registering components in: nsFileViewModule
*** Registering components in: mozStorageModule
*** Registering components in: nsPlacesModule
*** Registering components in: tkAutoCompleteModule
*** Registering components in: satchel
*** Registering components in: PKI
*** Registering components in: nsToolkitCompsModule
*** Registering components in: RemoteServiceModule
*** Registering components in: nsSoftwareUpdate
*** Registering components in: JavaScript_Debugger
*** Registering components in: BOOT
*** Registering components in: NSS
*** Registering components in: nsSystemPrefModule
*** Registering components in: nsAutoConfigModule
*** Registering components in: mozSpellCheckerModule
*** Registering components in: nsUnixProxyModule
###!!! ASSERTION: Failed to initialize nsScriptSecurityManager: 'NS_SUCCEEDED(rv)', file /usr/people/everdij/firefox35/mozilla-1.9.1/caps/src/nsScriptSecurityManager.cpp, line 3351
WARNING: Cannot create startup observer : service,@mozilla.org/scriptsecuritymanager;1: file /usr/people/everdij/firefox35/mozilla-1.9.1/embedding/components/appstartup/src/nsAppStartupNotifier.cpp, line 113
WARNING: NS_ENSURE_TRUE(mHiddenWindow) failed: file /usr/people/everdij/firefox35/mozilla-1.9.1/xpfe/appshell/src/nsAppShellService.cpp, line 396
###!!! ASSERTION: Failed to initialize nsScriptSecurityManager: 'NS_SUCCEEDED(rv)', file /usr/people/everdij/firefox35/mozilla-1.9.1/caps/src/nsScriptSecurityManager.cpp, line 3351
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8007000E: file /usr/people/everdij/firefox35/mozilla-1.9.1/content/base/src/nsContentUtils.cpp, line 288
###!!! ASSERTION: Could not initialize nsContentUtils: 'Error', file /usr/people/everdij/firefox35/mozilla-1.9.1/layout/build/nsLayoutStatics.cpp, line 156
WARNING: Not Initialized: file /usr/people/everdij/firefox35/mozilla-1.9.1/content/html/content/src/nsHTMLDNSPrefetch.cpp, line 109
++WEBSHELL 1020c4f0 == 1
###!!! ASSERTION: Failed to initialize nsScriptSecurityManager: 'NS_SUCCEEDED(rv)', file /usr/people/everdij/firefox35/mozilla-1.9.1/caps/src/nsScriptSecurityManager.cpp, line 3351
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8007000E: file /usr/people/everdij/firefox35/mozilla-1.9.1/docshell/base/nsDocShell.cpp, line 909
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8007000E: file /usr/people/everdij/firefox35/mozilla-1.9.1/xpfe/appshell/src/nsWebShellWindow.cpp, line 260
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8007000E: file /usr/people/everdij/firefox35/mozilla-1.9.1/xpfe/appshell/src/nsAppShellService.cpp, line 369
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8007000E: file /usr/people/everdij/firefox35/mozilla-1.9.1/xpfe/appshell/src/nsAppShellService.cpp, line 180
WARNING: NS_ENSURE_SUCCESS(rv, 1) failed with result 0x8007000E: file /usr/people/everdij/firefox35/mozilla-1.9.1/toolkit/xre/nsAppRunner.cpp, line 3206
--WEBSHELL 1020c4f0 == 0
nsStringStats
=> mAllocCount:           5159
=> mReallocCount:          129
=> mFreeCount:            5157  --  LEAKED 2 !!!
=> mShareCount:           4526
=> mAdoptCount:            344
=> mAdoptFreeCount:        344

Again i'm using lots of precompiled gtk+ glib stuff and gettext is giving me problems in circular dependencies, but atleast i have something to go on.

Let's attempt an optimized build first and also backport some stuff into Firefox 3.0.15, but i'm not going to spend much time there since the 3.0.x tree will be shelved pretty soon in favor of 3.5.x and the new 3.6.x trees
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
Vegac! So glad to see you here again.

What changed? Well, everybody has a Tezro nowadays and babies, 'cept for Neko, he has old Apple hardware ;)

Hamei is as always playing Culture Vulture in China and slagging his Fool , Hakim is living in Kabul and SGI went belly up and got assimilated by Rackable system, though you probably have guessed that already :)

Let's do some fun coding stuff together :) People want H.264 inside mplayer but they also want Firefox 3.x. Lots of things to do
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
C'mon, just treat the Atom as a brother of the late and great and dead R8000. Both are in-order instruction pipeline designs :)

I myself use an EeePC 901 with Atom N270 and it's been a sturdy friend with Ubuntu and helped reviving Indy's and Origins at work.

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
ShadeOfBlue wrote:
canavan wrote:
Quote:
find ~ -exec file {} \; | fgrep executable
I'd prefer find ~ -perm -1

This will also return directories and other files which happen to have the executable bit set (e.g. shared libraries, scripts, ...).


Code:
find . -type f -perm -1

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware
This can't be right. I've ported Python 3.1.1 upon specific request to enable the Blender port on IRIX. What has happened?

_________________
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP: :O2000: :Onyx2:
European nekoware mirror, updated twice a day: http://www.mechanics.citg.tudelft.nl/~everdij/nekoware
ftp://mech001.citg.tudelft.nl rsync mech001.citg.tudelft.nl::nekoware