The collected works of schleusel - Page 1


i've packaged some of of the things i built lately and thought i'd share them:

1. MLDonkey 2.5-4

MLDonkey ( ) is a popular client for several p2p networks. (eDonkey, Fasttrack, BitTorrent, Open Napster, Soulseek, Direct-Connect are activated in this build). Took me quite a while to get it running properly instead of just throwing bus errors all the time but it seems to be quite stable now. You should create some workdir for it inside your home directory and start it from within there to prevent it from dumping all its ini-files directly into your home dir.. (mips3)
needs: fw_gtk+, fw_glib, fw_gettext

2. ObjectiveCaml 3.07 + lablgtk

as MLDonkey is written in ObjectiveCaml ( ), I had to build that one too. Not sure if its of interest to many people but here we go: (mips3, built with gcc 3.3)

3. Sylpheed-Claws 0.9.6

Sylpheed-Claws is the "cutting edge" branch of sylpheed and adds quite a few features the original sylpheed doesn't have yet: (mips3, built with MipsPro 7.4.1m)

compiled with openssl and gnupg support. needs: fw_gettext, fw_glib, fw_gtk+, fw_openssl
I didn't include fw_gnupg as prereq as it still runs without that one (just with disabled gpg support)

4. Lame 3.93.1

Lame ( ) is a very powerfull mp3 encoder. I know that there already is a package of that version on nekochan but it still might be of interest to some as its built with MipsPro 7.4.1m and turned out to be a bit faster than the gcc 3.x compiled one:

the gcc build:

Encoding as 44.1 kHz 320 kbps stereo MPEG-1 Layer III (4.4x) qval=2
Frame | CPU time/estim | REAL time/estim | play/CPU | ETA
10062/10064 (100%)| 1:17/ 1:17| 1:27/ 1:27| 3.4065x| 0:00

this one:

Encoding as 44.1 kHz 320 kbps stereo MPEG-1 Layer III (4.4x) qval=2
Frame | CPU time/estim | REAL time/estim | play/CPU | ETA
10062/10064 (100%)| 1:07/ 1:07| 1:16/ 1:16| 3.9207x| 0:00

so it encodes 320kbit/s mp3 at about 4x realtime on r12k-300, not bad :-) (mips4, built with MipsPro 7.4.1m)

so long,
dexter1 wrote: Thanks for the nice tardists! I've put a blog entry on the main page

Thanks! Could you add a link to this forum thread for further information?

Hakimoto wrote: Cool... little question though: Did you get sylpheed claws to compile with iconv support? If so, what variables did you set for the build process?

hmm, it compiled right out of the box with iconv support. What problem are you seeing?

so long,

as squeen pointed out, the version reflected by lame tardist was wrong (dumb typo). The packaged version is of course 3.93.1 and not 3.91.1. I renamed the tardist and edited above announcement. Could someone please change the blog entry accordingly?

so long,
its been like this for several weeks now..

so long,


I uploaded a tardist of the new MPlayer 1.0pre3 release:

Key features of this build:

- built with MipsPro 7.4.1 and heavy optimizations (including IPA) - i can try to provide a recursive diff of the changes after I cleaned up the mess a bit. 99% of it was typical GCCisms, albeit a lot of them ;-)
- includes mips4 and mips3 selections
- ffmpeg libavcodec, libmpeg2, libvorbis codecs included
- x11, opengl and sdl video-out plugins included
- sgi, sdl and esd audio-out plugins included
- no prereqs as I linked all non-system libs statically

both mplayer and mencoder were tested with several files of different formats without major problems. The only problem I know of is Sorenson Video 3 (SVQ3) which is broken currently (probably endianness). It was already reported on the mailinglist so I hope it gets fixed soon.

a few hardware related notes:

The build was tested on MGRAS based Octanes (ESI, ESI+T, EXMI), Odyssey based Octanes (VPro8), O2 and Indigo² (MGRAS - HighImpact).
If you lack hardware Texturing you'll have to live with x11 or sdl video output and avoid scaling, as the software scaler is dead slow on Mips. If you still insist on the software scaler, use sdl instead of x11, its a bit faster..
For the x11 plugin make sure to have -depth 24 -class TrueColor in your /var/X11/xdm/Xservers

If you have Hardware Texturing you can choose one of the two OpenGL plugins to get hardware scaling. The gl2 plugin is the best choise in almost all cases - its faster than the gl plugin, it keeps the movie aspect when resizing and the OSD works well with it. If you experience broken colors with the GL plugins, force the output colorspace with -vf format=RGB24 on your command line or add vf=format=RGB24 to your config file. Note that on MGRAS gl2 doesn't work at all without that switch..
If you use the gl plugins make sure they can get a double buffered visual with enough colors. (findvis db tells you). On SI+T or ESI+T use one of the 1280x1024_XY_32db modes to achieve this.

Its always a good idea to have -framedrop enabled so mplayer starts skipping frames if needed (to keep a-v sync if the video is too much for the hardware).

I've included a default mplayer.conf with some IRIX related comments. Have a look at it and change it to your needs - or better: create your own ~/.mplayer/config to override those default settings.

so long,
squeen wrote: Requested video codec family [wmv9dmo] (vfm=dmo) not available.
Enable it at compilation.
Requested video codec family [wmvdmo] (vfm=dmo) not available.
Enable it at compilation.

Windows Media 9 will only play on x86 for now, as mplayer needs the win32 dlls to support it until libavcodec gets native support for it.

squeen wrote: Also, the audio which worked with your previous release is now garbled. I aplogize for needing so much hand-holding.

*sigh* indeed. I just dug out a similar file to test it. Looks like wma2 audio decoding is broken currently too.. I'll add the file to my growing collection of test fodder for future builds.

so for now your best way to get this to play on Irix is to use mencoder on some x86 machine and convert it to some more friendly format.. windows media should be boycotted anyway ;-)

so long,
0ctane wrote: okay, i got a little too excited. -vo gl2 -vf format=RGB24 is not working for me for the "classic evangelion comedy", although it works fine for an *.ogm file I have.

it works fine for 90% of the files I have here. There are a few that don't work - all of those are quite high res/high bitrate videos, so I suppose the problem is texture size limit on mgras (if so, this problem shouldn't exist on CRM or Odyssey) - I have yet to look deeper into this. For most files it should work fine on your SI+T (i tested it on ESI+T with many files) - just make sure it gets the double buffered high color visual it wants..

Octane wrote: Unfortunately, my system (195MHz Octane SI+T) is still too slow to play much of anything without -nosound. Oh, well.

yeah, smaller divx files and mpeg1 (and probably low bitrate mpeg2) works quite well on lower clocked r10k, anything larger can get painfull..

Octane wrote: Timo, can you post the configure options you used? I have an *.avi file here that I can play with my compiled player:

Code: Select all

Opening audio decoder: [liba52] AC3 decoding with liba52
No accelerated IMDCT transform found
AC3: 5.1 (3f+2r+lfe)  48000 Hz  384.0 kbit/s
No accelerated resampler found
AUDIO: 48000 Hz, 2 ch, 16 bit (0x20), ratio: 48000->192000 (384.0 kbit)
Selected audio codec: [a52] afm:liba52 (AC3-liba52)

but dies with yours:[code]Opening audio decoder: [liba52] AC3 decoding with liba52
No accelerated IMDCT transform found
AC3: 5.1 (3f+2r+lfe) 48000 Hz 384.0 kbit/s

MPlayer interrupted by signal 10 in module: init_audio_codec
- MPlayer crashed. This shouldn't happen.

Ok, thanks for the hint. I got this fixed now. MipsPro was the problem in this case.. I overlooked (yet another) __GNUC__ ifdef in liba52/bitstream.h. Do you have an urgent need for software AC3 decoding? Otherwise i'll try to get a few other things working too before I update the package..

thanks for the feedback,
0ctane wrote: BTW, when did Sorenson Video 3 break? I got it working during the pre2 and have that build sitting around.

It was still working in CVS around November iirc. It wasn't fixed yet.. so maybe i'll dig through the ffmpeg cvslog and try to find out which change broke it. Or I just send a proper bug report to the ffmpeg people instead.

Octane wrote: Also, on the mailinglist a while back someone was working with the Octane digital audio I/O. Any thoughts on getting that working? I don't ever use my Octane's digital I/O, but it might be an interesting feature. :)

hmm, shouldn't setting the default output to digital in apanel be all thats needed for this? If you are feeding it into an amp with integrated 5.1 (Dolby Digital, DTS) decoder it might be worth to try -ac hwac3 (AC3 through SPDIF) to make use of it (given an input file with ac3 of course). I have not the slightest idea if any of this works as I don't have the proper equipment to test it currently.. ;)

so long,
dexter1 wrote: Happy new year to all of you!

:hathat49: :silly: :smilecolros: :drinking:

exactly! *buuuuuuuurp*
while we're at it.. i'd also suggest posting hinv -mv instead of only -v as most people did so far..
-m gives quite a bit additional interesting output on most newer machines (part numbers and such)

so long,

I was wondering if anybody successfully got a non SGI gigE PCI card working in an SGI (o200, Octane..). Apparently the cards that SGI currently sells are based on the broadcom tigon3 chipset - the manpage of the driver (obviously) mentions only SGI cards as supported:

P/N 9210283 - PCI card with BCM5701 MAC, copper media
P/N 9210284 - PCI card with BCM5701 MAC, fiber media

Anyway, the tigon3 seems to be pretty wide spread these days so it shouldn't be too difficult to find a card based on it.. did anybody try this yet?


warerat wrote:
Are those boards approved for use in the Octane? I remember looking through the strings in if_tg.o and saw several error messages in there complaining if there is no PCI-X bus.

the option card SGI sells is a normal 64bit PCI board, no PCI-X. Accoding to the techpubs manual it is supported in Octane(2), o200, o2k, o3x0, o3k, fuel, tezro. The if_tg.o module is present in both the IP27 and IP30 kernel trees here.
In Tezro and o350 the integrated tg0 interface is on the IO9 card (together with U160 SCSI hosts and IDE for the DVD)

warerat wrote:
It may be possible, but the driver may need to be modified similarly like the Indigo2 Phobos E100 driver was for a 3Com EISA board.

thats the question.. I was hoping the driver would be as tolerant wrt. non SGI labeled cards as the qlogic driver is for example..

so long,

The Keeper wrote:
Unfortunately, no such luck. The IRIX QLogic Fibre Channel driver does appear to accept any and all revisions of the QLA2200, but I've been told by SGI employees that only SGI-specific revisions of Gigabit Ethernet cards will work under IRIX. Apparently SGI had to make some tweaks to the GigE cards to make them work properly.

Hmm, okay. When did you get that information? And was it a general statement or probably just connected to the cards they were selling at that time?

The Keeper wrote:
And I can understand why, too. When SGI added gigabit interfaces to IRIX, Fibre Channel was already somewhat mature, so the FC vendors already had an idea of what they were doing. But GigE came out a few years after FC (as was also the case with FDDI vs. 100Base-TX), and was fairly new to the game.

Yes. Although it's quite mature now and the tigon driver seems to be rather young. They seem to have sold Alteon based cards for quite some time before they switched to the tigons. Hence the above question.. if you got that information some time ago the situation might be different with the tigon cards/driver.

so long,

jwhat wrote:
Also would the 4958 patch still be required for IRIX version later then 6.5.19?
Thanks for info.

hmm, maybe I am interpreting things wrong. But to me the changelog of the patch reads like they disabled support for non SGI tigon3 cards at that point, not enabled it..

so long,

Hi Ian,

mapesdhs wrote: I notice there is a 1280x1024_72_32db in the directory above, but setmon complains
when I try to use that.

Note that the DivX file plays fine on my O2.

Yes, there is a problem with the gl plugins on MGRAS (mostly with high res/bitrate files) - see the fist comment from Octane above for example. I don't think its a double buffering thing (if it doesn't find a double buffered visual, the gl plugin bombs out earlier), I rather think its a texture size issue.. the problem doesn't exist on Odyssey and O2. I bet it displays smaller files without problems, right?

Btw. I'm planning to update the package when 1.0pre4 is out at some point in the next weeks. I'm currently playing with cvs and all looks good so far - at least all the codec problems reported in the above posts are fixed (SVQ3, WMA, AC3..). Unfortunately I don't have any MGRAS machine around anymore (switched to Odyssey), so I can't really experiment with the above issue currently. Hopefully I'll be able to pick up some r10k High Impact indigo2 in the near future to keep at least one MGRAS machine around..

mapesdhs wrote: Oh, the example file is on my site if anyone wants to replicate things: ... movie1.avi


so long,

i've updated the tardist with the new 1.0pre4 release:

testers welcome ;-)

Again built with MipsPro 7.4.1 and aggressive optimizations. I hope I got most problems resulting from my MipsPro related
changes sorted out by now, that is: the codec support should be on par with gcc builds from the unmodified source -
at least my growing collection of weird testfiles seems to imply this so far ;-) But please let me know if you find
any problems that might be related to my changes!

Some package specific information:

- again includes mips3 and mips4 selections

- again all external libs are linked statically, hence there are no prereqs.

- now installs to /opt/mplayer instead of /usr/local (as /usr/local is just wrong for packaged stuff)

- enabled codecs/plugins:
Input: ftp network edl tv matroska(internal)
Codecs: xvid libavcodec real faad2(internal) libmpeg2 liba52 mp3lib libvorbis libmad gif
Audio output: sgi sdl mpegpes(file)
Video output: sdl gif89a jpeg mpegpes(file) opengl x11 xover tga

- added an opt subsystem containing Release Notes, the original source and the lengthy patch used for this build

I guess that sums it up, check the Release Notes and the included default mplayer.conf for further information :-)

so long,
schleusel wrote: i've updated the tardist with the new 1.0pre4 release:

uploaded a new revision (128) of the package. Only difference is a small change to vo_gl2 (hopefully removing any remaining fullscreen flickering problems with large files on slower machines)

so long,
yup, known problem.. it was mentioned in the other mplayer thread as well. Some (mostly high res/high bitrate) files don't display on mgras with 4MB tram.. vo_gl2 only gives a still image, vo_gl only a blank window iirc. I didn't look deeper into this one but I supposed it was a texture size issue too.. given that it only appears with quite heavy files and odyssey and o2 don't show this behavior. Sorry to be not of much help here

barefoot wrote: BTW what does the -f switch do and what does the -ao switch do. Sorry but I don't seem to have any documentation and I don't know how to install the man pages(if it exists).

-f is non existant -ao selects the audio output plugin. The manpages are included but as I chose to install to /opt/mplayer they are not in your $MANPATH. So include /opt/mplayer/man in your $MANPATH or read it with man -M /opt/mplayer/man mplayer

so long,
barefoot wrote: Thanks, much reading ahead :-) , is the location of man pages defined at startup somewhere? (so I can just add /opt/mplayer/man to it)

you can set it in your ~/.login for example. Likely there is already a line defining the $MANPATH. Just add :/opt/mplayer/man at the end of it. If there is no such line just add one:
setenv MANPATH ${MANPATH}:/opt/mplayer/man

themacosxflies wrote: please, tell me that my Octane2 400 MHz 1 GB RAM V6 can use mplayer rightly

sure, no problem. Thats the config I was running until recently (dual 300 instead now).. mplayer was fun on it for almost anything I tried. Above problem doesn't exist on the V6..

so long,
unixmuseum wrote: 1- a shitload of new resolutions, that's cool! An interesting one is 1280_1024_safe, what's this for? safe as in secure or stable? I don't recall seeing that on SSE, but maybe I just didn't pay attention...

noticed that one too. The two seem to be exactly the same vfos though.. no idea if its just an accidentally packaged backup copy or if its there for a reason..
unixmuseum wrote: 2- a new, slightly puzzling "Valid Configurations" menu
This one got me puzzled because for a certain number of resolutions, it offer 2 options. For instance, 1280x1024_60_no_tiles.cmb and 1280x1024_60_4_tiles.cmb. What the heck is this?

Those are display combinations for using several odyssey pipes with an external compositor (InfinitePerformance(TM) ;-) )if i'm not totally mistaking.. see sgcombine(1) for example
unixmuseum wrote: 3- a new frame buffer depth control, I guess it's related to #2

this is used to switch between 8bytes/pixel and 16bytes/pixel framebuffer depth, see and friends :-)

so long,
87Porsche wrote: "This is the new Boeing 777. This is the box in came in." I've got this poster up in my office.

Damn, you bastard! I'd so love to own that one - or at least a high quality scan of it :-)
Here's a low quality shot for those that don't know it yet:

so long,
Intel-OUTSIDE wrote: after about 10 attempts the console outputed "diagnostic failure - press any key to continue" or something like that.

pressing any key of course did nothing.


I guess you tried the reseating game already? Also, what do the diagnostic leds behind the front door say? They aren't too helpful in most cases, but still..

Code: Select all

BaseIO  X
QA    X  X  PCI Expansion
QD    X  X  QB
QC    X  X  Heart

where QA-QD are the four XIO slots, Heart and BaseIO are IP30 and Frontplane - so those two should always be lit.

Mare wrote: It wouldnt happen to have the 747watt Cherokee power supply would it? mine makes the same sizzling noise when the system is off and so does both my O200 towers.

yeah, my o200 PSU does that too. I was quite irritated when I first switched the PSU on after I had received the machine ;-) Both my cherokee Octane PSUs are silent when the fan is not spinning though..

Altix 350 + Ultimate Vision.. as boring as expected :-) .. with cube logo :-(
Dubhthach wrote: As for the workstation, i find it interesting that they are going with twin AGP 8x, surely dual PCI-E 16x would have been better (well from a SLI point of view)

Prism still uses AGP 8x too. One can only guess why this is the case. Either it was already too long in development when the PCI Express hype started or they took the cheap route and simply built upon the AGP midplane of Onyx4 Ultimate Vision they already had.
Dorado is likely a repackaged Altix 350/Prism just like Tezro being a repackaged Origin 350/Onyx 350 IP. That would explain the rather high entry price point and the numalink option the article mentions. Now, with Origin 350 and Altix 350 sharing the same chassis too (and hence the nodeboards likely have the same form factor) and SGI tending to reuse every part they can I have this scary image of an Itanic workstation in a yellow Tezro case i my mind *shudder*.. ;-)
unixmuseum wrote:
Yes it is... Someone is actually paying attention... :lol: About that, happy now?


ok, the first two shots reveal that its indeed exactly the same chassis as the tezro tower, just with different plastics around it - as predicted :-) So instead of Origin 350 nodeboard there is an Altix 350 nodeboard installed and the I/O midplane was replace with a different one (with AGP instad of XIO, six instead of seven PCI-X slots - the spec sheet doesn't say on how many buses those PCI-X slots are though. That info would have been interesting to complete the tezro comparison..)
pub_bronx wrote: The reason why I'm upset is that I read somewhere that there is a frequency bug in the V6/V8, which means that they shoudn't be able to manage a range of frequencies, whose lower bound is about 103 MHz (don't remember about the higher bound). When I launch 'xsetmon', I can see that the Pixel Clock has a value of 107,76 MHz. So do I have to crawl eBay for a new V6?

109-193MHz was the "forbidden" pixel clock range. Modes in that range can't be selected at all on V6 and V8 so you didn't do anything wrong. Modes that are close to the lower end of that range (like 1280x1024_59/60) are only allowed at 8 bytes/pixel framebuffer size and even at that setting some people reported display problems (noise, flickering) in other threads.
I never really tried it myself (I was running my V6 at 1600x1200 most of the time) but I suppose that might be what you're seeing. In that case another V6 will be of no help of course..
pub_bronx wrote: I'm running a 1280x1024_59 mode at 16 bytes/pixel, which shouldn't be possible ?!?

Try switching to 8 bytes/pixel and see if it improves the situation
How did you manage to push your V6 to a 1600x1200 resolution ?

no magic involved. 1600x1200 is only possible at 8 bytes/pixel. At 16 bytes/pixel it would need ~30MB framebuffer but the largest possible framebuffer on the 32MB boards is 24MB.
So first switch to 8 bytes/pixel framebuffer size and then to 1600x1200
nekonoko wrote: Cool, I have one of those in my Indigo(1) R4400; makes a huge difference. I just bought a Set Engineering card to play with as I've heard they offer even more performance.

not really :-(
I have the Set Engineering in my r5k-180 Challenge S and it performs about as poor as the Phobos E100 (EISA) in an Indigo2 (~6.5 MB/s peak according to ttcp). And it does Half Duplex only.. :-(
It might keep up with the Phobos G100 but i'd trade it for a G130 in a second. The advantage of the Set Engineering is that you don't need extra drivers. Even the miniroot kernel already knows the board, so you can use it for network installs..
SAQ wrote: It might be a common ATX PSU- you could get a good one (e.g. Antec) and put it in. Make sure though, they aren't always the same.

The newer 460W Fuel PSU is an EPS12V (24+8 pin for "high end" PCs) model from Fortron Source (Sparkle) - that one to be precise: ... enumber=23

I see them listed starting at 85 EUR over here. Although i have no idea if they really use the stock model or even whether the pinout is the same..

I looked up the type of the older 430W one too back then but don't find my note right now..
MrWeedster wrote: But if IRIX is up, i wont be able to use one of both. They're doing nothing.

I used an USB keyboard (IBM Preferred USB) on my fuel without problems. You might have to edit /etc/ioconfig.conf to change the priorities of the ps/2 and usb input devices, see the usbinput manpage.
Another issue is that i can't configure the display resolutions higher then 1600x1024 (got a V10 in it). If i'd like to change the resolution to something >1600x1024, i get the question, if i'd like to make it the default for power on, which i answer with yes. Then there's an error-message, saying "illegal power-on configuration.

1600x1200 and higher is only supported at 8 bytes/pixel framebuffer size on the 32MB cards. You'll have to first change the framebuffer depth from 16 to 8 bytes in xetmon (or with -d8 if you're using command line setmon) before you can change the resolution in a second step.
Well, that should not be a problem, but i don't know with which tool i should make this?

with the hex editor of your choice :-)
MrWeedster wrote: Ok i tried that. First i tried setting the color-depth to 8 bytes and then did a reboot. After the reboot it was again 16 bytes. Tried to change that again in xsetmon and then the resolution without reboot - "Illegal power-on configuration". So, no success.

hmm, are you sure you really applied the setting? Notice the separate load button for the framebuffer depth field - its a little unintuitive.
And no need to restart anything in between. Choose the framebuffer depth, click the load button of that field, choose the resolution, click the load button of the resolution field..
whiter wrote: in beta:


cool, works great so far :-)
A file was packaged in subsystem neko_irssi.sw.perl while it actualy belonged in neko_irssi.sw.lib. In the new version of the tardist I moved this. What will inst do when upgrading the previously installed version of the package to this new one?

hm, the upgrade simply consists of removing the old content of the updated subsystems and installing the new content, no fancy merge procedure or the like.. so moving files between subsystems will simply work without side effects.
uploaded to beta:

neko_cyrus_imapd-2.2.12.tardist - new package of the same (still current) version because it had some hooks in the old perl tree
neko_cyrus_sasl-2.1.22.tardist new version
neko_db4-4.4.20.tardist new version

the cyrus_imapd build is linked against that new db4 version which apparently introduces some incompatibilities with the db files of existing cyrus imapd installations. Rebuilding them using db_recover (part of the neko_db4 package) fixed it for me. I placed a note about that in the relnotes. No other problems yet..

Anyway, even it its still the same release i'd like to watch it on my mail server for two days before moving it out of beta :-)
schleusel wrote:
uploaded to beta:
neko_db4-4.4.20.tardist new version

ok, this one broke neko_perl_db_file (and spamassassin with it..) :-|

I uploaded a rebuild of neko_perl_db_file-1.814.tardist against the new db4 to beta that fixes the problems..
new in beta:

neko_cdrtools-2.01.01a11.tardist Joerg Schilling's CD/DVD writing tools.

The DVD wrinting part of it was closed source until recently and was distributed binary only (cdrecord-ProDVD). This lead to GPL only forks like the dvdrtools already in nekoware or the cdrecord-ossdvd patches.
That part of the cdrtools is now free too and still appears to be more advanced than the forks (those still don't support DVD+R for example) - althogh some linux distributions still won't start packaging cdrtools again due to the weird GPL/CDDL license mix. Personally, i couldn't care less about that fact, but if somebody has a problem with it, please scream now ;-)

The package is marked icompatible with neko_dvdrtools (and actually makes that one obsolete)

Note that i couldn't test the DVD support yet because i'll have to buy new dvd recordables first, so hopefiully it actually works as promised :-)

neko_xcdroast-0.98alpha15.tardist GUI frontend for the cdrtools.

I've patched it with a patch kindly borrowed from gentoo (thanks, goolge) that disables the checks for cdrecord-ProDVD to make it work with the new cdrtools.

neko_cdrdao-1.2.1.tardist disk-at-once cd-copying/recording tool

neko_smake-1.2a36.tardist Schilling's own make variant.. because the world doesn't have enough of those already *sigh*
GeneratriX wrote:
Hello Schleusel, what is the package/release for neko_gdk_pixbuf.sw.lib which you're actually using as dependency on neko_xcdroast-0.98alpha15.tardist? ...It seems that I can't find the right tardist here.

oups, sorry, i fixed that prereq now.. I should finally learn not to keep package versions installed that never got uploaded :-)
GeneratriX wrote:
I'll download the new package to try again. What should be the first server having it uploaded?

it is on nekochan already. The first mirror to have it will likeley be dexter's ( All the other mirrors sync off that one i think. Not sure how often dexter syncs currently.. twice a day?
squeen wrote:
I was wondering why more folks weren't complaining about the GIMP being broken. I have 2 systems (an Octane and Tezro) runing 6.5.29 that had the same memory error problem. What version of OS are you using? Again, I'm wondering if a serious incompatability exists!?! Oh, also I'm compiling with 7.4.4m. Anyone else with and experience to share?

I had the same issue ages ago with an older glib/gimp combination. It appeared after i updated my ex-Octane from EMXI to V6 and hence updating parts of the os installation. Thinking the update simply wasn't perfectly complete i took the safe route and did an 'install same' of the complete os installation. That fixed it.. looking back i'm beginning to think this could be the rqs issue, chervarium covered again lately:

The current build works great for me so far, thanks :-)

@joerg: About prereqs: If an app as a prereq of GTK like the GIMP does, I do not feel it is a good idea to add all of GTK's prereq's to the GIMP. That's the way all the original nekoware wer packaged.

i'm seriously prefering the route of adding all linked shared libs as direct prereqs. The above way of indirect prereqs will always be less robust (and more error-prone) unless you make sure the package you inherit the prereqs from really has the currently installed package of the .so in question as prereq (and not some older package version)..

And isn't actually a lot more work to separate all indirect prereqs that way too?
new in beta triggered by the neko_openldap update:

neko_postfix-2.3.2.tardist - quite a version bump, works fine for me so far though
neko_sylpheed_claws-1.0.5.tardist still the same version (the gtk 1.x branch is dead :-( ) only rebuilt against the new openldap
neko_sylpheed_claws_gtk2-2.4.0.tardist newest member of the gtk2 branch
neko_libetpan-0.46.tardist multi purpose mail library (needed by claws gtk2)

the .opt subsystem of the previous claws gtk2 packages was accidentally marked as version 6 (instead of 1), hence i decided to mark the new package as version 7 to prevent the .opt subsystem from being declared as downgrade.

I keep being disturbed by the sheer slowness of gtk2 on irix, something is just wrong there. QT blows it away at the same level of questionable eye candy :-|
uploaded to beta:

neko_dvdauthor-0.6.11.tardist - command line DVD authoring tools
neko_libdvdread-0.9.6.tardist - library for reading DVD-video images
neko_mjpegtools-1.8.0.tardist - tools for MJPEG/MPEG capture/editing/compression
neko_mpgtx-1.3.tardist - command line MPEG audio/video toolbox
neko_dvdplusrw_tools-6.1.tardist DVD mastering tools (does not interfere with neko_cdrtools. It mereley adds some additional tools)

neko_dvdstyler-1.4.tardist wxwindows based GUI frontend for the dirty dozen ;-)

I couldn't test it much yet. Creating a very simple project and letting it create the DVD structures and image of it at least looked promising though..

DVDstyler is built against wxgtk. I was hoping to be able to build it against wxmotif but that didn't work out due to apparently missing drag and drop support in wxmotif :-(