SGI: Development

The firefox rebuild and the rebuild dependencies are in beta now. I only uploaded the gcc build glib since the mipspro based version causes a lot of crashes. Here is a list of packages:

If you want to see this packages in current please vote for it.

diegel wrote: Here is a list of packages:

Code: Select all

...
neko_zlib-1.2.8.tardist


Just out of curiosity ... did you build the libz un-optimized ? It builds both ways, but then I saw the note on the original version in nekoware that -03 breaks some png's. I didn't have any to test so chickened out and went no-0 but -03 might be nice if that is no longer a problem ?

thank you, btw ...

edit: okay le, extracted the release notes, got the info, cool, thanks.

On to the next hill to climb ....

While I'm here, is there a reason we are at libpng 1.2 when it's currently up to 1.6 ? Not complaining, just wondering ....

Mr Diegel Sir -

I assume that you stopped libpng at 1.2.52 because at 1.2.53 it fails the 'make check' step ?

I just discovered through process of elimination that libpng 1.4.16 makes (with your edit of libtool) and passes the gmake check step.

Installed it, so far no disasters. ymmv.


At 1.6.17 the effing thing kacks on AWK.

There is probably some place in the middle that still works. Research is ongoing.

Edit : okay, the break point is at 1.5.0 Here's what I find :



I'm looking at beta 33 especially becasue that seems related to the actual error I get ?

Also, do you think the beta 43 change affects us ?

btw, herr diegel - how come we are un-versioning the libraries ? What effect does that have ?

hamei wrote: btw, herr diegel - how come we are un-versioning the libraries ? What effect does that have ?

This was not my idea, it had been done in the current libpng package also. If this cause any problem, we have the problem already. I don't change much at the dependencies, I just rebuild them with better optimization. If I can't build a package with maximum optimization with MipsPro I used to gcc.

diegel wrote:

hamei wrote: btw, herr diegel - how come we are un-versioning the libraries ? What effect does that have ?

This was not my idea, it had been done in the current libpng package also.

Hmm. Thank you for the info .. more research required then

If this cause any problem, we have the problem already.

The major problem I've had with common dependencies is libjpeg. The original jpeg people seem to have gone off the deep end, while jpeg-turbo is supposed to be a drop-in. Maybe all the older versions hanging around have made trouble. Other than that, most of the basic depends have been okay.

Did you try png 1.4.16 ? Working well here. I rebuilt graphics magick to use it, works fine. Ran all the tests a-okay. A couple other apps, too. Hoping that stupid options.awk script is the only problem between us and 1.6.17 ...

A clean-out of the libs directory is in process ... this no-version thing seems attractive. Let's see what happens

If I can't build a package with maximum optimization with MipsPro I used to gcc.

I'm wondering what the actual problem is with libz ... That's a very foundational library.

A little late, but you have my endorsement for -current, with some very minor caveats:

First, this Firefox is an improvement over the previous releases as it does not exhibit the ~hourly crashes I would routinely experience with the previous build. As for speed, I haven't conducted any specific testing, although it certainly isn't a regression by any means.

Now -- (and if I sound overly critical, it's because I feel this is a top-tier package and this really needs to be in -current and in top shape).

The zlib is not versioned properly. Just my opinion, but zlib is not bleeding edge SW, so each new package that someone builds with zlib really doesn't need a *new* zlib, and it doesn't need to *require* the latest zlib. If this zlib goes into -current this way, it's going to muck up pretty much the whole distribution. I have a permanent workaround for this and libpng (which is another chronic offender) with RLD_LIST kung-fu, but this really needs to be fixed, and maybe there should be some guidance in the build Wiki about these issues. Every drop for a big program sends a new zlib that screws everything else up. Maybe if there's not a new security issues with zlib, we should lock this library in and just leave it alone unless it's necessary to upgrade.

The .ftr/.fti files were not installed into the "local" path under /usr/lib/filetype which seems to be the de-facto standard for basically anything else not originating from SGI (and the rest of Nekoware, AFAIK). This Firefox seems to also use a different #tag than the previous version. I had to troubleshoot blank FIrefox icons after installation.

Last nit-pick, the default installation choice for items such as dist files/patches/and release notes were not applied consistently between all the updated libraries for this Firefox.

All in all, good job on a *very* important package (hell, it's the best effort we currently have on IRIX for a web browser).

I agree it's the best web browser build for IRIX atm, but sadly it's so old now version-wise that I can't use my Fuel for a lot of the web stuff I do these days, which is rather sad. Find myself using my 5GHz 2700K more and more. :\

Ian.

mapesdhs wrote: it's so old now that I can't use my Fuel for a lot of the web stuff I do these days ...

Surfing Ashley Madison ?

:D

Online banking, tomshardware, eBay, etc.

Ian.

mapesdhs wrote: Online banking ...

So may the outward shows be least themselves - the world is still deceived with ornament.

In law, what plea so tainted and corrupt but, being seasoned with a gracious voice, obscures the show of evil?

In religion, what damned error but some sober brow will bless it and approve it with a text, hiding the grossness with fair ornament?

There is no vice so simple but assumes some mark of virtue on his outward parts.

How many cowards, whose hearts are all as false as stairs of sand, wear yet upon their chins the beards of Hercules and frowning Mars; who, inward search'd, have livers white as milk ?

And these assume but valour's excrement to render them redoubted!

Look on beauty and you shall see 'tis purchased by the weight which therein works a miracle in nature, making them lightest that wear most of it.

So are those crisped snaky golden locks which make such wanton gambols with the wind upon supposed fairness, often known
to be the dowry of a second head, the skull that bred them in the sepulchre.

Thus ornament is but the guiled shore to a most dangerous sea, the beauteous scarf veiling an Indian beauty -

In a word, the seeming truth which cunning times put on to entrap the wisest.

Unfortunately Firefox has become so bloated now, that a new version wouldn't run well on any of the more popular machines here like Indigo2, O2, Octane, Tezro and Fuel. Better to have an entirely new browser created/or find one that is lightweight.

Something like Origyn might work okay (it's been very successful on the Amiga), but I think NetSurf is a better basis, and is actually known to compile.

viewtopic.php?f=15&t=16728822&start=30

Krokodil wrote: Unfortunately Firefox has become so bloated now, that a new version wouldn't run well on any of the more popular machines here like Indigo2, O2, Octane, Tezro and Fuel. Better to have an entirely new browser created/or find one that is lightweight.

well that's the problem, that won't work. as discussed before, for whatever reason way too many websites seem to think they need to follow every trend no matter how much sense it makes for them or not. unfortunately right now that means using too large fonts, way too much js even if not needed at all and practically no gfx. the result is that they look very poor yet require tons of resources to achieve the same (at best) they had years ago already despite causing just a fraction of the load.
so a browser that can handle all that junk can't be light. the only hope is that at some point the trend will change again to something reasonable.

Right on! Thanks for the rebuild!

Axatax_ wrote: The zlib is not versioned properly.

Thanks for your feedback. Would you give some more details about this versioning issue.

mapesdhs wrote:

foetz wrote: so you're running a gtk2 firefox on an indigo
now that's brave

Ach it's not that bad given the CPU is only an R10K/195.

I wonder what would be the recommendation for even worser CPU.
Firefox 2 from Nekoware? I suppose it's GTK1 one? I'm stick to this now. Perhaps Seamonkey is better option...
Dillo? Not sure that version from -current is unicode capable. And version from -beta seems to have broken fonts rendering somewhere in the path.
Konqueror? Dunno...

Dillo is fine for simple sites, and renders Nekochan reasonably well. For other sites, I've personally found SeaMonkey to be more responsive than FF2 or FF3 on my Indigo2. Although even then, it's still slow of course!

dukzcry wrote: [ And dillo version from -beta seems to have broken fonts rendering somewhere in the path.

If this is a real problem, I can build dillo without xft.

diegel wrote: If this is a real problem, I can build dillo without xft.

Can you ? Did you know that, at least on Irix, X will serve up Type1 fonts ? And we have those ? And they are better than Truetype ?

All this stuff on top of X is, for us, just so many leeches sucking the blood from our cpu's

hamei wrote:

diegel wrote: If this is a real problem, I can build dillo without xft.

Can you ? Did you know that, at least on Irix, X will serve up Type1 fonts ? And we have those ? And they are better than Truetype ?

You can build fltk without xft support. In this case there is no support for any antialiased fonts.