<?xml version="1.0" encoding="utf-8"?>
<!-- If you are running a bot please visit this policy page outlining rules you must respect. http://www.livejournal.com/bots/ -->
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:lj="http://www.livejournal.com">
  <id>urn:lj:livejournal.com:atom1:bezilla</id>
  <title>BeZilla blog</title>
  <subtitle>bezilla</subtitle>
  <author>
    <name>bezilla</name>
  </author>
  <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/"/>
  <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom"/>
  <updated>2008-07-25T19:22:39Z</updated>
  <lj:journal username="bezilla" type="community"/>
  <link rel="service.feed" type="application/x.atom+xml" href="http://community.livejournal.com/bezilla/data/atom" title="BeZilla blog"/>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:283737</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/283737.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=283737"/>
    <title>Is Cairo on BeOS ready for prime time?</title>
    <published>2008-07-25T19:22:39Z</published>
    <updated>2008-07-25T19:22:39Z</updated>
    <content type="html">A new bug has been filed to remove references to gfx for BeOS.  &lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=446675"&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=446675&lt;/a&gt;&lt;br /&gt;Has anyone proven the BeOS Cairo port stable enough to make this a safe thing to do?  Does it even matter since we can't build trunk for BeOS and by the time we can, we may be able to port Cairo more easily to Haiku?</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:283478</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/283478.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=283478"/>
    <title>Firefox 2.0.0.16 builds completed - on BeBits</title>
    <published>2008-07-22T05:32:11Z</published>
    <updated>2008-07-22T05:32:11Z</updated>
    <content type="html">The usual batch of builds:  R5, BONE and Zeta.  BONE builds have fyysik's Haiku patch applied (second version).  I had some spare CPU time sitting around, so I've also posted Thunderbird 2.0.0.16 and yes, updated builds of Sunbird 0.9.  BeBits has 'em all.  Enjoy!</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:283300</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/283300.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=283300"/>
    <title>Firefox 2.0.0.16 builds delayed</title>
    <published>2008-07-18T04:43:13Z</published>
    <updated>2008-07-22T05:33:55Z</updated>
    <content type="html">Seems either my HD is failing or maybe my (passively cooled) northbridge is overheating due to warm weather here.  Either way, I'd just started building 2.0.0.16 when they system decided to reboot, then not boot at all.  Posting this from the Xubuntu box in the garage.  Hopefully this will be quickly rectified.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt; so much for the "quickly" part.  Somehow it seems all of my BFS partitions are hosed, as is the grub/boot partition on my HD.  Very odd.  I booted the machine from the Zeta 1.21 live CD and could read (and backup) all data from my NTFS and EXT2 partions.  The BFS partitions are all there according to DriveSetup but the file system is unrecognized.  Diskprobe shows the files appear to be there also but I have no idea how to save them.  May be starting over on a few things...&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 2:&lt;/b&gt;  only the boot sector was trashed.  Zeta 1.21 livecd doesn't have a BFS driver, as pointed out in the comments.  My ignorance strikes again!  Machine is happier now.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:282898</id>
    <author>
      <name>Dub Stojerossoff</name>
    </author>
    <lj:poster user="fyysik"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/282898.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=282898"/>
    <title>Bots here</title>
    <published>2008-07-16T21:42:39Z</published>
    <updated>2008-07-16T21:42:39Z</updated>
    <content type="html">Hello, people. What do you think about switching CAPTCHA technology on here even for registered users?&lt;br /&gt;&lt;br /&gt;(There is new trend here in LJ in last 2-3 days, lot of spam-bots created and activated. They try to post on topic, more or less, using theme recognition, but actually are bots with advertasion in single posting or info page)</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:282797</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/282797.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=282797"/>
    <title>Haiku Firefox and Thunderbird available now</title>
    <published>2008-07-13T16:55:35Z</published>
    <updated>2008-07-16T22:02:22Z</updated>
    <content type="html">Sorry for the delay, fyysik.  I had to test a bit; Thunderbird caused KDL Crash with                                    r26384.  I had to make sure the build wasn't bad but works fine under r26375.&lt;br /&gt;&lt;a href="http://sheltonfamily.org/firefox_test/Firefox2.0.0.17pre_Haiku.zip"&gt;Firefox for Haiku&lt;/a&gt;&lt;br /&gt;&lt;a href="http://sheltonfamily.org/firefox_test/Thunderbird2.0.0.17pre_Haiku.zip"&gt;Thunderbird for Haiku&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;These are (manually) reordered packages, ready to unzip and run. If anyone wants Sunbird, please reply and I'll build that also.&lt;br /&gt;&lt;br /&gt;Edit:  forgot to mention, these also have a version of tqh's revised NSPR.  I don't know if it's the latest.  tqh doesn't love me any more and hasn't sent his latest.  ;-)</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:282378</id>
    <author>
      <name>Dub Stojerossoff</name>
    </author>
    <lj:poster user="fyysik"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/282378.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=282378"/>
    <title>Haiku-compatible FF with Haiku-specific "launch-kill" fix.</title>
    <published>2008-07-12T19:52:21Z</published>
    <updated>2008-07-13T09:46:24Z</updated>
    <content type="html">If someone needs Firefox which doesn't close other Mozilla apps and won't to be closed itself by others, there is &lt;a href="http://eudns9.esthost.com/~fyysik/firefox-2-bone-HaikuMemLayout2.zip"&gt;such build for download&lt;/a&gt; - until Tigerdogs publishes full set of  of Mozilla apps.&lt;br /&gt;&lt;br /&gt;Works also on R5-BONE. As it was built on my own development code, it fixes problem with mouse sticking (lost mouse-up events), features filtering in File Picker, proper file-type recognition and also adds Postscript printing.&lt;br /&gt;&lt;br /&gt;Also here is &lt;a href="http://eudns9.esthost.com/~fyysik/seamonkey-1.8-bone-HaikyAndBeOSMemLayoutFix2.zip"&gt;download for SeaMonkey&lt;/a&gt; users (Haiku, R5-BONE) with same critical fix and mentioned features.&lt;br /&gt;&lt;br /&gt;I think those fixed version will be safer for use also in R5 and Zeta - as that bug with ports may lead to unpredictable things in BeOS-based OS-es too.&lt;br /&gt;&lt;br /&gt;Look at older messages for solved problem explanation, e.g.&lt;br /&gt;&lt;a href="http://community.livejournal.com/bezilla/281777.html"&gt;http://community.livejournal.com/bezilla/281777.html&lt;/a&gt;&lt;br /&gt;&lt;a href="http://community.livejournal.com/bezilla/282356.html"&gt;http://community.livejournal.com/bezilla/282356.html&lt;/a&gt;</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:282356</id>
    <author>
      <name>Dub Stojerossoff</name>
    </author>
    <lj:poster user="fyysik"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/282356.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=282356"/>
    <title>Mozilla and Haiku-OS kernel kit - who's guilty?</title>
    <published>2008-07-10T11:15:49Z</published>
    <updated>2008-07-10T11:15:49Z</updated>
    <content type="html">That's again about misterious bug described in &lt;a href="http://dev.haiku-os.org/ticket/2049"&gt;ticket 2049&lt;/a&gt; - where launching some Gecko-based app instantly closes another running at the moment.&lt;br /&gt;&lt;br /&gt;I got fix for that, at Mozilla code level, but actually this is Haiku problem - or feature?&lt;br /&gt;&lt;br /&gt;We use for internal Mozilla communication BeOS ports,&lt;br /&gt;and to have access for those ports from different components and threads we assign to ports name, which must be unique.&lt;br /&gt;For that purpose we're using "current thread" identifier printed in octal form as port name - at stage of port creation. Then when we need somewhere to communicate, we are getting port by find_port - again, using portname created from current thread "number.&lt;br /&gt; - see&lt;br /&gt;&lt;a href="http://lxr.mozilla.org/mozilla1.8/source/xpcom/threads/plevent.c#382"&gt;http://lxr.mozilla.org/mozilla1.8/source/xpcom/threads/plevent.c#382&lt;/a&gt;&lt;br /&gt;&lt;a href="http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsAppShell.cpp#122"&gt;http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsAppShell.cpp#122&lt;/a&gt;&lt;br /&gt;&lt;a href="http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsToolkit.cpp#93"&gt;http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsToolkit.cpp#93&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;To get current port ID we use methods PR_GetCurrentThread() from NSPR (NS runtime kit):&lt;br /&gt;&lt;a href="http://lxr.mozilla.org/mozilla1.8/source/nsprpub/pr/src/bthreads/btthread.c#417"&gt;http://lxr.mozilla.org/mozilla1.8/source/nsprpub/pr/src/bthreads/btthread.c#417&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;and there is something wrong. I'm not so competent yet to analyze btthreads code, but once I replaced all calls for PR_GetCurrentThread() in 3 places mentioned above,&lt;br /&gt;plus this one (NB!!!, may be quite important, as it uses another PR method - mGuiThread = PR_CreateThread(PR_SYSTEM_THREAD,*)):&lt;br /&gt;&lt;a href="http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsToolkit.cpp#231"&gt;http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsToolkit.cpp#231&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;with simple native find_thread(0) - all started to work as "expected" in Haiku - mozilla apps can now run simultaneously.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:282007</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/282007.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=282007"/>
    <title>Firefox 2.x branch End of Maintenance is December 2008</title>
    <published>2008-07-08T19:40:07Z</published>
    <updated>2008-07-08T19:40:07Z</updated>
    <content type="html">I just read, Firefox 2 is going to be maintained only through the end of 2008.  Since the platform is already pretty stable and most holes appear to be patched, it'll have to work for us until Haiku is ready and we can resume development of trunk builds using gcc4.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:281777</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/281777.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=281777"/>
    <title>Fixing simultaneous execution under Haiku</title>
    <published>2008-07-06T15:36:33Z</published>
    <updated>2008-07-06T15:36:33Z</updated>
    <content type="html">As already discussed, starting one Mozilla app under Haiku closes others already running (see &lt;a href="http://dev.haiku-os.org/ticket/2049"&gt;ticket 2049&lt;/a&gt;.  Discussion in the ticket suggests separate ifdefs for each app &lt;a href="http://lxr.mozilla.org/mozilla1.8/source/toolkit/xre/nsNativeAppSupportBeOS.cpp#215"&gt;in this code&lt;/a&gt;.  If someone can provide a little more guidance, I'll try to add the ifdefs.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:281423</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/281423.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=281423"/>
    <title>Firefox 2.0.0.15 now on BeBits</title>
    <published>2008-06-17T16:50:05Z</published>
    <updated>2008-06-18T16:28:56Z</updated>
    <content type="html">Branch code has been frozen and spun off for Firefox 2.0.0.15.  I went ahead and pushed to BeBits, even though 2.0.0.15 does not appear to have been pushed to main platforms yet.  My calendar is getting full and I didn't want to miss it.  No major BeOS updates, just a couple of security and cross-platform fixes.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:281276</id>
    <author>
      <name>tqh</name>
    </author>
    <lj:poster user="tqh"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/281276.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=281276"/>
    <title>Rewriting NSPR for Haiku</title>
    <published>2008-06-05T08:49:10Z</published>
    <updated>2008-06-05T18:18:39Z</updated>
    <content type="html">Haiku has some nice locking primitives, I have an older rewritten NSPR. Both should improve speed quite a bit.&lt;br /&gt;&lt;br /&gt;Oh, and how about dropping support for BeOS and Zeta?&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt; &lt;br /&gt;NSPR is working fine and fast, only thing left is switch to Haiku locking primitives.&lt;br /&gt;&lt;br /&gt;After that it is probably time to figure out how to run the packaging script while crosscompiling, and that damn redraw problem.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:280922</id>
    <author>
      <name>tqh</name>
    </author>
    <lj:poster user="tqh"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/280922.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=280922"/>
    <title>I suspect that we may have a reader!</title>
    <published>2008-05-29T21:45:29Z</published>
    <updated>2008-05-30T07:03:15Z</updated>
    <content type="html">I think that Stippi is reading this blog from time to time, so I'm sending him a message :)&lt;br /&gt;&lt;br /&gt;As Axel increased BLooper's message queue to 200 today I was curious if that might not be what is the big problem behind our redrawing issue under Haiku. This because we may take a lot of time when dealing with messages which may allow it to fill up faster than we can manage. (Shame on us).&lt;br /&gt;&lt;br /&gt;Luroh who had a freshly built version of Haiku tested and he said he didn't experience any redrawing issues. &lt;b&gt;Update:&lt;/b&gt; Apparently it's still there.&lt;br /&gt;&lt;br /&gt;After that we went for punch and pie. Not really, but this is my story. Anyway I suspect that this might be the case and I will probably run some tests. Feel free to come with ideas, fix the issue or just not read this post :)</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:280615</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/280615.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=280615"/>
    <title>2.0.0.15pre for use with Haiku</title>
    <published>2008-05-26T01:20:01Z</published>
    <updated>2008-05-26T01:20:01Z</updated>
    <content type="html">I've created BONE builds from the latest branch for use with Haiku.&lt;br /&gt;&lt;a href="http://sheltonfamily.org/thunderbird_test/thunderbird-2.0.0.15pre.en-US.BeOS-bone.zip"&gt;Thunderbird&lt;/a&gt;&lt;br /&gt;&lt;a href="http://sheltonfamily.org/firefox_test/firefox-2.0.0.15pre.en-US.BeOS-bone.zip"&gt;Firefox&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Enjoy!</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:280343</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/280343.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=280343"/>
    <title>Branch Building Broken - or not</title>
    <published>2008-05-24T19:35:36Z</published>
    <updated>2008-05-25T21:50:17Z</updated>
    <content type="html">Hello all!&lt;br /&gt;I'm now settled into the new job and will hopefully be able to focus a bit more time on Firefox.  As I updated my 2.x branch code this morning, I noted a rather large number of commits coming down the line.  It seems &lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=419030"&gt;bug 419030&lt;/a&gt; now has the 2.x branch picking up changes in the security components that were being missed.  &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt; As usual, changes to the code have broken BeOS building.  Here's the latest problem.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 2:&lt;/b&gt; ...or not broken.  I restarted a clean build and everything was fine.  Very odd; may point to bfs weirdness on my HD, as fyysik diagnosed once before.  At any rate, updated code builds cleanly.  Looks like this was a system error.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:280249</id>
    <author>
      <name>tqh</name>
    </author>
    <lj:poster user="tqh"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/280249.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=280249"/>
    <title>Why firefox looks strange in Haiku</title>
    <published>2008-05-22T19:45:18Z</published>
    <updated>2008-05-22T19:45:18Z</updated>
    <content type="html">Michael Lotz gave this hint in #haiku today:&lt;br /&gt;&lt;quote&gt;&lt;br /&gt;the fonts in firefox are not broken, it just uses the wrong ones&lt;br /&gt;it uses the "extra light" versions of dejavu&lt;br /&gt;if you delete those firefox will look normal.&lt;br /&gt;&lt;/quote&gt;&lt;br /&gt;So how Firefox chooses fonts or the order returned by Haiku needs looking into.&lt;br /&gt;&lt;br /&gt;Fyysik?</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:279851</id>
    <author>
      <name>masahiro_yamada</name>
    </author>
    <lj:poster user="masahiro_yamada"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/279851.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=279851"/>
    <title>Is it needed to URL Encode ";" in file name on directory listing of file scheme ? (bug 412428)</title>
    <published>2008-05-20T06:38:44Z</published>
    <updated>2008-05-20T06:38:44Z</updated>
    <content type="html">I filed bug of directory listing that does not URL Encode ";" in file name on file scheme.&lt;br /&gt;It is bug 412428 (&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=412428"&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=412428&lt;/a&gt;).&lt;br /&gt;And I already wrote patch for the bug.&lt;br /&gt;But, I don't know how should we handle ";" in filename on BeOS.&lt;br /&gt;Current patch does not URL encode ";" in file name on BeOS.&lt;br /&gt;Is it needed to URL encode ";" on BeOS?</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:279804</id>
    <author>
      <name>franxico</name>
    </author>
    <lj:poster user="franxico"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/279804.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=279804"/>
    <title>Haiku 404</title>
    <published>2008-05-18T16:31:32Z</published>
    <updated>2008-05-18T16:48:01Z</updated>
    <content type="html">Hi guys,&lt;br /&gt;&lt;br /&gt;I'd like to change the usual error message, replacing it with a random haiku, like in NetPositive. What do you think? &lt;br /&gt;&lt;br /&gt;I tried some things, but I don't have knowledge enough to make it work properly. The page opens, but nothing is seen.&lt;br /&gt;&lt;br /&gt;&lt;a name="cutid1"&gt;&lt;/a&gt;&lt;div class="ljcut" text="Here's what I did"&gt;I found out how to modify that page &lt;a href="http://forums.techguy.org/tech-tips-tricks/443443-change-cannot-found-page-firefox.html"&gt;here.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Then I adapted a JavaScript that I &lt;a href="http://www.trap17.com/index.php/how-mank-random-quote-come-up-radomly_t9414.html"&gt;found&lt;/a&gt;. Here's the code (sorry, but I can't attach the files):&lt;br /&gt;&lt;br /&gt;//netError.xhtml file&lt;br /&gt;&lt;br /&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt; &lt;br /&gt;&amp;lt;html xmlns="http://www.w3.org/1999/xhtml"&amp;gt; &lt;br /&gt;&amp;lt;head&amp;gt; &amp;lt;title&amp;gt;Page cannot be reached&amp;lt;/title&amp;gt;&lt;br /&gt;&amp;lt;script src="haiku.js"&amp;gt;&amp;lt;/script&amp;gt;&lt;br /&gt;&amp;lt;link rel="stylesheet" href="chrome://global/content/customerror.css" type="text/css" media="all" /&amp;gt; &amp;lt;/head&amp;gt; &lt;br /&gt;&amp;nbsp;&lt;br /&gt;&amp;lt;body&amp;gt; &lt;br /&gt;&lt;br /&gt;&amp;lt;!-- All body content STARTS HERE! --&amp;gt; &lt;br /&gt;&amp;lt;script LANGUAGE = "JavaScript"&amp;gt;&lt;br /&gt;// this you put into you html doc where you want your quotes to appear&lt;br /&gt;document.write(haiku[rand(haiku.length)])&lt;br /&gt;&amp;lt;/script&amp;gt;&lt;br /&gt;&amp;lt;!-- All body content ENDS HERE --&amp;gt;&lt;br /&gt;&amp;nbsp;&lt;br /&gt;&amp;nbsp;&amp;lt;/body&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;lt;/html&amp;gt;&lt;br /&gt;&lt;br /&gt;---------------------------------------------&lt;br /&gt;&lt;br /&gt;// haiku.js file&lt;br /&gt;&lt;br /&gt;// JavaScript Document&lt;br /&gt;function makeArray(len) {&lt;br /&gt;for (var i = 0; i &amp;lt; len; i++) this[i] = null;&lt;br /&gt;this.length = len;&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;// you add as many quotes as you want here just make sure to change the makeArray(number)&lt;br /&gt;&lt;br /&gt;haiku = new makeArray(38);&lt;br /&gt;haiku[0] = "The web site you seek\u&lt;br /&gt;Lies beyond our perception\u&lt;br /&gt;But others await.",&lt;br /&gt;&lt;br /&gt;haiku[1] = "Sites you are seeking\n&lt;br /&gt;From your path they are fleeing\n&lt;br /&gt;Their winter has come.",&lt;br /&gt;&lt;br /&gt;haiku[2] = "A truth found, be told\n&lt;br /&gt;You are far from the fold, Go\n&lt;br /&gt;Come back yet again.",&lt;br /&gt;&lt;br /&gt;haiku[3] = "Wind catches lily\n&lt;br /&gt;Scatt'ring petals to the wind:\n&lt;br /&gt;Your site is not found.",&lt;br /&gt;&lt;br /&gt;haiku[4] = "These three are certain:\n&lt;br /&gt;Death, taxes, and site not found.\n&lt;br /&gt;You, victim of one.",&lt;br /&gt;&lt;br /&gt;haiku[5] = "Ephemeral site.\n&lt;br /&gt;I am the Blue Screen of Death.\n&lt;br /&gt;No one hears your screams.",&lt;br /&gt;&lt;br /&gt;haiku[6] = "Aborted effort:\n&lt;br /&gt;The site, passed this veil of tears.\n&lt;br /&gt;You ask way too much.",&lt;br /&gt;&lt;br /&gt;haiku[7] = "Morning and sorrow\n&lt;br /&gt;404 not with us now\n&lt;br /&gt;Lost to paradise.",&lt;br /&gt;&lt;br /&gt;haiku[8] = "Not a pretty sight\n&lt;br /&gt;When the web dies screaming loud\n&lt;br /&gt;The site is not found.",&lt;br /&gt;&lt;br /&gt;haiku[9] = "Site slips through fingers\n&lt;br /&gt;Pulse pounding hard and frantic\n&lt;br /&gt;Vanishing like mist.",&lt;br /&gt;&lt;br /&gt;haiku[10] = "The dream is shattered\n&lt;br /&gt;The web site cannot be found\n&lt;br /&gt;Inside the spring rain.",&lt;br /&gt;&lt;br /&gt;haiku[11] = "Bartender yells loud\n&lt;br /&gt;Your site cannot be found, boy\n&lt;br /&gt;Buy another drink.",&lt;br /&gt;&lt;br /&gt;haiku[12] = "Chrome megaphone barks\n&lt;br /&gt;It's not possible to talk\n&lt;br /&gt;Not yet anyway.",&lt;br /&gt;&lt;br /&gt;haiku[13] = "Emptyness of soul\n&lt;br /&gt;Forever aching blackness:\n&lt;br /&gt;"Blah.com not found."",&lt;br /&gt;&lt;br /&gt;haiku[14] = "Click exciting link\n&lt;br /&gt;Gossamer threads hold you back\n&lt;br /&gt;404 not found.",&lt;br /&gt;&lt;br /&gt;haiku[15] = "With searching comes loss\n&lt;br /&gt;And the presence of absence:\n&lt;br /&gt;The site is not found.",&lt;br /&gt;&lt;br /&gt;haiku[16] = "You step in the stream,\n&lt;br /&gt;But the water has moved on\n&lt;br /&gt;The site is not here.",&lt;br /&gt;&lt;br /&gt;haiku[17] = "Rather than a beep\n&lt;br /&gt;Or a rude error message,\n&lt;br /&gt;These words: 'Site not found.'",&lt;br /&gt;&lt;br /&gt;haiku[18] = "Something you entered\n&lt;br /&gt;Transcended parameters.\n&lt;br /&gt;The site is unknown.",&lt;br /&gt;&lt;br /&gt;haiku[19] = "Stay the patient course\n&lt;br /&gt;Of little worth is your ire\n&lt;br /&gt;The server is down",&lt;br /&gt;&lt;br /&gt;haiku[20] = "There is a chasm\n&lt;br /&gt;Of carbon and silicon\n&lt;br /&gt;The server can't bridge.",&lt;br /&gt;&lt;br /&gt;haiku[21] = "Chaos reigns within.\n&lt;br /&gt;Reflect, repent, and retry.\n&lt;br /&gt;Server shall return.",&lt;br /&gt;&lt;br /&gt;haiku[22] = "Won't you please observe\n&lt;br /&gt;A brief moment of silence\n&lt;br /&gt;For the dead server?",&lt;br /&gt;&lt;br /&gt;haiku[23] = "First snow, then silence.\n&lt;br /&gt;This expensive server dies\n&lt;br /&gt;So beautifully.",&lt;br /&gt;&lt;br /&gt;haiku[24] = "Seeing my great fault\n&lt;br /&gt;Through darkening dead servers\n&lt;br /&gt;I begin again.",&lt;br /&gt;&lt;br /&gt;haiku[25] = "Visit the home page\n&lt;br /&gt;It can't be done easily\n&lt;br /&gt;When the site is down.",&lt;br /&gt;&lt;br /&gt;haiku[26] = "Cables have been cut\n&lt;br /&gt;Southwest of Northeast somewhere\n&lt;br /&gt;We are not amused.",&lt;br /&gt;&lt;br /&gt;haiku[27] = "Site is silent, yes\n&lt;br /&gt;No voices can be heard now\n&lt;br /&gt;The cows roll their eyes.",&lt;br /&gt;&lt;br /&gt;haiku[28] = "Silicon shudders\n&lt;br /&gt;The site is down for the count\n&lt;br /&gt;One big knockout punch.",&lt;br /&gt;&lt;br /&gt;haiku[29] = "Yesterday it worked\n&lt;br /&gt;Today it is not working\n&lt;br /&gt;The web is like that.",&lt;br /&gt;&lt;br /&gt;haiku[30] = "Errors have occurred.\n&lt;br /&gt;We won't tell you where or why.\n&lt;br /&gt;Lazy programmers.",&lt;br /&gt;&lt;br /&gt;haiku[31] = "The code was willing\n&lt;br /&gt;It considered your request,\n&lt;br /&gt;But the chips were weak.",&lt;br /&gt;&lt;br /&gt;haiku[32] = "Error reduces\n&lt;br /&gt;Your expensive computer\n&lt;br /&gt;To a simple stone.",&lt;br /&gt;&lt;br /&gt;haiku[33] = "The ten thousand things\n&lt;br /&gt;How long do any persist?\n&lt;br /&gt;The file, not there.",&lt;br /&gt;&lt;br /&gt;haiku[34] = "A file that big?\n&lt;br /&gt;It might be very useful\n&lt;br /&gt;But now it is gone.",&lt;br /&gt;&lt;br /&gt;haiku[35] = "Server's poor response\n&lt;br /&gt;Not quick enough for browser.\n&lt;br /&gt;Timed out, plum blossom.",&lt;br /&gt;&lt;br /&gt;haiku[36] = "To have no errors\n&lt;br /&gt;Would be life without meaning\n&lt;br /&gt;No struggle, no joy",&lt;br /&gt;&lt;br /&gt;haiku[37] = "Login incorrect.\n&lt;br /&gt;Only perfect spellers may\n&lt;br /&gt;Enter this system."&lt;br /&gt;&lt;br /&gt;// The random number generator.&lt;br /&gt;function rand(n) {&lt;br /&gt;seed = (0x015a4e35 * seed) % 0x7fffffff;&lt;br /&gt;return (seed &amp;gt;&amp;gt; 16) % n;&lt;br /&gt;}&lt;br /&gt;var now = new Date()&lt;br /&gt;var seed = now.getTime() % 0xffffffff&lt;br /&gt;&lt;br /&gt;-----------------&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:279314</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/279314.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=279314"/>
    <title>2.0.0.14 Coming, now here</title>
    <published>2008-05-01T05:01:20Z</published>
    <updated>2008-05-03T03:57:53Z</updated>
    <content type="html">I've completed builds of the next Firefox 2 point release, version 2.0.0.14.  I am not able to post to BeBits.  It seems the password for the Bezilla account is different than before.  Anyway, for those who read this blog and want the latest in security updates, here are links to the usual three versions:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://sheltonfamily.org/firefoxbuilds/firefox-2.0.0.14.en-US.beosR5-i586.zip"&gt;BeOS R5&lt;/a&gt;&lt;br /&gt;&lt;a href="http://sheltonfamily.org/firefoxbuilds/firefox-2.0.0.14.en-US.beosBONE-i586.zip"&gt;BONE, Dano and derivatives&lt;/a&gt;&lt;br /&gt;&lt;a href="http://sheltonfamily.org/firefoxbuilds/firefox-2.0.0.14.en-US.Zeta-i686.zip"&gt;Zeta (requires i686 or later CPU)&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt;  now posted to BeBits</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:279099</id>
    <author>
      <name>tigerdog</name>
    </author>
    <lj:poster user="tigerdog"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/279099.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=279099"/>
    <title>absent for a while now...</title>
    <published>2008-04-14T03:42:18Z</published>
    <updated>2008-04-14T03:42:18Z</updated>
    <content type="html">sorry I've been absent for a few weeks.  I've been monitoring the blog and am very happy to see the great progress mmadia is making with reordering.  I'm about to begin a new job, so I may be scarce again for a while.  Everything is great, just very busy at the moment.  I'll start building again as quickly as time allows and will definitely try to keep up with the .point releases if nothing else.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:279013</id>
    <author>
      <name>mmadia</name>
    </author>
    <lj:poster user="mmadia"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/279013.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=279013"/>
    <title>Experimental Re-Order *.so , *.so.stub Builds</title>
    <published>2008-04-13T16:31:12Z</published>
    <updated>2008-04-13T18:55:42Z</updated>
    <content type="html">Some hosting has been provided by Master199 at &lt;a href="http://bezilla.beuser.de"&gt;http://bezilla.beuser.de&lt;/a&gt;&lt;br /&gt;Right now, It's just a file repository.&lt;br /&gt;A new BeZilla BeBits entry page has been created: &lt;a href="http://bebits.com/app/4552"&gt;Experimentally Built BeZilla Builds&lt;/a&gt;&lt;br /&gt;&lt;a name="cutid1"&gt;&lt;/a&gt;&lt;br /&gt;As there are builds for FF, SM, TB, SB, and XULRunner, &lt;br /&gt;I didn't want to litter all of the individual application pages.&lt;br /&gt;Also, any problems that occur in one build, should occur in the others.&lt;br /&gt;eg, reaching the 32mb add-on limit in R5 or incorrect *.so, *.so.stub placement&lt;br /&gt;&lt;br /&gt;Once we feel reasonably confident that these builds do not introduce new issues, &lt;br /&gt;that bebits app page can be deleted and links moved to their individual pages.&lt;br /&gt;&lt;br /&gt;All comments are enabled for now.&lt;br /&gt;&lt;br /&gt;&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=425962"&gt;425962 - re-order *.so&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Testing and feedback on R5Bone is needed!</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:278775</id>
    <author>
      <name>mmadia</name>
    </author>
    <lj:poster user="mmadia"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/278775.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=278775"/>
    <title>another note about embedding</title>
    <published>2008-04-12T10:15:00Z</published>
    <updated>2008-04-12T10:31:48Z</updated>
    <content type="html">It seems XULRunner is the current method of embedding gecko.&lt;br /&gt;&lt;br /&gt;quote:&lt;br /&gt;Roll your own browser - An embedding HowTo&lt;br /&gt;From MDC&lt;br /&gt;&lt;br /&gt;Note: this document is out of date. According to Benjamin Smedberg: "build XULRunner and use that for all new embedding. You do not need/should not use embedding/config".&lt;br /&gt;:etouq&lt;br /&gt;&lt;a href="http://developer.mozilla.org/en/docs/Roll_your_own_browser_-_An_embedding_HowTo"&gt;linky&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://developer.mozilla.org/en/docs/XULRunner"&gt;Main XULRunner dev page&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;here's a random email about embedding with xulrunner 1.8 &lt;br /&gt;&lt;a href="http://groups.google.com/group/mozilla.dev.embedding/browse_thread/thread/23257b1e3315a11f/c136034a7e04aeef"&gt;link&lt;/a&gt;</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:278393</id>
    <author>
      <name>mmadia</name>
    </author>
    <lj:poster user="mmadia"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/278393.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=278393"/>
    <title>Updates on bugs</title>
    <published>2008-04-04T00:33:12Z</published>
    <updated>2008-04-06T09:29:05Z</updated>
    <content type="html">&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=425962"&gt;425962 - re-order *.so&lt;/a&gt; -- review request not set.&lt;br /&gt;Should these builds be posted publicly before requesting review?  &lt;br /&gt;Not many people have been using these builds on net_server, bone, or zeta.&lt;br /&gt;&lt;a name="cutid1"&gt;&lt;/a&gt;&lt;br /&gt;&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=423182"&gt;423182 - default MOZ_ZIP_FORMAT&lt;/a&gt; : patch landed on trunk and branch.&lt;br /&gt;&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=423183"&gt;423183 - replace TARGET_OS/TARGET_CPU&lt;/a&gt; : patch landed on trunk and branch.&lt;br /&gt;&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=426083"&gt;426083 - fix XULRunner build&lt;/a&gt; : approved for 1.9 and 1.8 branch. waiting for checkin on both.</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:278148</id>
    <author>
      <name>mmadia</name>
    </author>
    <lj:poster user="mmadia"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/278148.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=278148"/>
    <title>default HOST_OPTIMIZE_FLAGS </title>
    <published>2008-04-02T00:32:27Z</published>
    <updated>2008-04-02T00:32:27Z</updated>
    <content type="html">In &lt;a href="http://mxr.mozilla.org/mozilla1.8/source/configure.in#1344"&gt;http://mxr.mozilla.org/mozilla1.8/source/configure.in#1344&lt;/a&gt; &lt;br /&gt;the default optimization level is set to '-O3'&lt;br /&gt;isn't '-O3' highly unreliable for R5?&lt;br /&gt;Should this get changed to -02 or even -Os?</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:277918</id>
    <author>
      <name>mmadia</name>
    </author>
    <lj:poster user="mmadia"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/277918.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=277918"/>
    <title>Haiku support ...</title>
    <published>2008-04-01T23:59:25Z</published>
    <updated>2008-04-02T00:00:37Z</updated>
    <content type="html">Even though Haiku is for the most part source and binary compatible with R5, &lt;br /&gt;there are some issues.&lt;br /&gt;Most notably, configure scripts break due to different values for `uname`&lt;br /&gt;In particular,  `uname -s` reports "Haiku" and "BeOS" respectively.  &lt;br /&gt;&lt;a name="cutid1"&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Currently mozilla's build system performs conditional testing on $(OS_ARCH), which is equal to `uname -s`&lt;br /&gt;&lt;br /&gt;It's possible to pass --host=i586-beos or a similar line to configure to use the BeOS definitions, but this isn't an ideal solution.&lt;br /&gt;Numerous beos-workarounds will no longer be needed.&lt;br /&gt;For example, Haiku has better posix support.&lt;br /&gt;&lt;br /&gt;For reference, the other beos-specific build system variables are:&lt;br /&gt;BEOS_PROGRAM_RESOURCE :: for applying the .rsrc file, &lt;br /&gt;    defined in (application)/app/Makefile.in&lt;br /&gt;    used in &lt;a href="http://mxr.mozilla.org/mozilla1.8/source/config/rules.mk#831"&gt;http://mxr.mozilla.org/mozilla1.8/source/config/rules.mk#831&lt;/a&gt;&lt;br /&gt;BEOS_ADDON_WORKAROUND :: for creating *.so.stub, &lt;br /&gt;    defined in &lt;a href="http://mxr.mozilla.org/mozilla1.8/source/config/config.mk#114"&gt;http://mxr.mozilla.org/mozilla1.8/source/config/config.mk#114&lt;/a&gt;&lt;br /&gt;    used in &lt;a href="http://mxr.mozilla.org/mozilla1.8/source/config/rules.mk#671"&gt;http://mxr.mozilla.org/mozilla1.8/source/config/rules.mk#671&lt;/a&gt; and #681&lt;br /&gt;&lt;br /&gt;So how are we going to implement Haiku support?</content>
  </entry>
  <entry>
    <id>urn:lj:livejournal.com:atom1:bezilla:277703</id>
    <author>
      <name>mmadia</name>
    </author>
    <lj:poster user="mmadia"/>
    <link rel="alternate" type="text/html" href="http://community.livejournal.com/bezilla/277703.html"/>
    <link rel="self" type="text/xml" href="http://community.livejournal.com/bezilla/data/atom/?itemid=277703"/>
    <title>Composer is dead.  Long live KompoZer,  *crash*  KompoZer has crashed.</title>
    <published>2008-03-30T12:52:57Z</published>
    <updated>2008-03-30T14:53:09Z</updated>
    <content type="html">Just a small note, Composer on 1.8 is horribly busted on all OS's.&lt;br /&gt;Compiling KompoZer, &lt;a href="http://www.kompozer.net/"&gt;http://www.kompozer.net/&lt;/a&gt; went easy enough...&lt;br /&gt;It loads but it crashes as soon as something is typed.&lt;br /&gt;It also crashes on exit.&lt;br /&gt;&lt;br /&gt;Note: it &lt;a href="http://sourceforge.net/project/stats/detail.php?group_id=170132&amp;amp;ugn=kompozer&amp;amp;type=svn&amp;amp;mode=12months"&gt;appears&lt;/a&gt; the project is dead or very idle&lt;br /&gt;&lt;a name="cutid1"&gt;&lt;/a&gt;&lt;br /&gt;In mozilla/composer/app/Makefile.in, this was added:&lt;br /&gt;( i didn't bother checking if it actually needed -lgame though )&lt;br /&gt;ifeq ($(OS_ARCH),BeOS)&lt;br /&gt;BEOS_PROGRAM_RESOURCE = $(srcdir)/apprunner-beos.rsrc&lt;br /&gt;ifdef BUILD_STATIC_LIBS&lt;br /&gt;OS_LIBS += -ltracker -lgame&lt;br /&gt;endif&lt;br /&gt;endif&lt;br /&gt;&lt;br /&gt;For the mozconfig, i edited  mozconfig.linux , ripped out some parts and dropped in a block of common options for BeOS:&lt;br /&gt;&lt;br /&gt;# sh&lt;br /&gt;# Build configuration script for LINUX&lt;br /&gt;#&lt;br /&gt;# See &lt;a href="http://www.mozilla.org/build/unix.html"&gt;http://www.mozilla.org/build/unix.html&lt;/a&gt; for build instructions.&lt;br /&gt;#&lt;br /&gt;export MOZILLA_OFFICIAL=1&lt;br /&gt;export BUILD_OFFICIAL=1&lt;br /&gt;&lt;br /&gt;export MOZ_STANDALONE_COMPOSER=1&lt;br /&gt;mk_add_options MOZ_STANDALONE_COMPOSER=1&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# Uncomment the two following lines if you want the Site Manager&lt;br /&gt;# to use KDE mimetypes icons. Warning, experimental feature...&lt;br /&gt;# You may have to edit the following files&lt;br /&gt;#   mozilla/composer/app/Makefile.in&lt;br /&gt;#   mozilla/editor/libeditor/html/Makefile.in&lt;br /&gt;#   mozilla/composer/src/ *&lt;br /&gt;#export SITE_MANAGER_KDE_ICON_STYLE=1&lt;br /&gt;#mk_add_options SITE_MANAGER_KDE_ICON_STYLE=1&lt;br /&gt;&lt;br /&gt;# Uncomment and edit this line if you want to build&lt;br /&gt;# outside of the source tree&lt;br /&gt;mk_add_options MOZ_OBJDIR=/preR1/KompoZer-bone&lt;br /&gt;&lt;br /&gt;# Comment out the following lines for a debug build&lt;br /&gt;#ac_add_options --enable-optimize&lt;br /&gt;ac_add_options --disable-debug&lt;br /&gt;&lt;br /&gt;# You may need to uncomment and edit that line. On Linspire,&lt;br /&gt;# just uncomment it&lt;br /&gt;#ac_add_options --with-default-mozilla-five-home=/usr/lib/mozilla&lt;br /&gt;&lt;br /&gt;# You probably have nothing to change below that line&lt;br /&gt;ac_add_options  --disable-svg&lt;br /&gt;ac_add_options  --without-system-mng&lt;br /&gt;ac_add_options  --without-system-png&lt;br /&gt;ac_add_options  --disable-ldap&lt;br /&gt;ac_add_options  --disable-mailnews&lt;br /&gt;ac_add_options  --disable-installer&lt;br /&gt;ac_add_options  --disable-activex&lt;br /&gt;ac_add_options  --disable-activex-scripting&lt;br /&gt;ac_add_options  --disable-tests&lt;br /&gt;ac_add_options  --disable-oji&lt;br /&gt;ac_add_options  --disable-necko-disk-cache&lt;br /&gt;ac_add_options  --enable-single-profile&lt;br /&gt;ac_add_options  --disable-profilesharing&lt;br /&gt;ac_add_options  --enable-extensions=wallet,xml-rpc,xmlextras,pref,universalchardet,spellcheck&lt;br /&gt;ac_add_options  --enable-necko-protocols=http,ftp,file,jar,viewsource,res,data&lt;br /&gt;ac_add_options  --disable-pedantic&lt;br /&gt;ac_add_options  --disable-short-wchar&lt;br /&gt;# // I don't want to do strip yet&lt;br /&gt;#ac_add_options  --enable-strip-libs&lt;br /&gt;ac_add_options  --enable-crypto&lt;br /&gt;ac_add_options  --disable-mathml&lt;br /&gt;ac_add_options  --with-system-zlib&lt;br /&gt;ac_add_options  --enable-toolkit=beos&lt;br /&gt;ac_add_options  --enable-default-toolkit=beos&lt;br /&gt;ac_add_options  --disable-freetype2&lt;br /&gt;&lt;br /&gt;# Note: Only include icon for mac, windows and os2&lt;br /&gt;ac_add_options --enable-image-decoders=default,-xbm&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;### // COMMON BeOS mozconfig stuff not found above.&lt;br /&gt;&lt;br /&gt;### //EDIT THESE VALUES TO REFLECT YOUR LOCAL BUILD ###&lt;br /&gt;export GLIB_CONFIG=/boot/home/glib-libIDL-beos/glib/bin/glib-config&lt;br /&gt;mk_add_options GLIB_CONFIG=/boot/home/glib-libIDL-beos/glib/bin/glib-config&lt;br /&gt;&lt;br /&gt;export LIBIDL_CONFIG=/boot/home/glib-libIDL-beos/libIDL/bin/libIDL-config&lt;br /&gt;mk_add_options LIBIDL_CONFIG=/boot/home/glib-libIDL-beos/libIDL/bin/libIDL-config&lt;br /&gt;&lt;br /&gt;### //Automatic updates not currently supported on BeOS.  Delete this when we add this feature.&lt;br /&gt;ac_add_options --disable-updater&lt;br /&gt;&lt;br /&gt;### //Explicitly enable native BeOS threading&lt;br /&gt;ac_add_options --with-bthreads&lt;br /&gt;&lt;br /&gt;### //Build without Cairo&lt;br /&gt;ac_add_options --disable-svg&lt;br /&gt;ac_add_options --disable-canvas&lt;br /&gt;&lt;br /&gt;### //Reduce build size and time by omitting test suite and IPv6 support (not needed on BeOS)&lt;br /&gt;ac_add_options --disable-tests&lt;br /&gt;ac_add_options --disable-ipv6&lt;br /&gt;&lt;br /&gt;### //Required configure options&lt;br /&gt;ac_add_options --enable-cpp-rtti &lt;br /&gt;ac_add_options --enable-static  ## STATIC BUILD&lt;br /&gt;ac_add_options --disable-shared&lt;br /&gt;&lt;br /&gt;### //Eliminate lots of relatively useless warnings during build&lt;br /&gt;ac_add_options --disable-cpp-exceptions&lt;br /&gt;&lt;br /&gt;### Optional optimizations&lt;br /&gt;ac_add_options --enable-optimize='-Os'</content>
  </entry>
</feed>
