Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
InterWeb-60.9.8 is now available. Changed the about dialog a little, cleaned up help menu entries, and fixed a few gfx bugs.
Download: https://github.com/wicknix/InterWebSnow/releases
Change log: https://github.com/wicknix/InterWebSnow/compare/60.9.7...60.9.8

Cheers and happy holidays.

I do have one question about building 60.9.8, though:

I keep running into this error with the build which halts the compile, no matter what I try:

Code:
19:17.15 /opt/local/bin/clang++ -arch x86_64 -std=gnu++11 -o Unified_cpp_image0.o -c -fvisibility=hidden -fvisibility-inlines-hidden -DNDEBUG=1 -DTRIMMED=1 -DOS_POSIX=1 -DOS_MACOSX=1 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL -I/Users/Shared/InterWebSnow-60.9.8/image -I/Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/image -I/Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/ipc/ipdl/_ipdlheaders -I/Users/Shared/InterWebSnow-60.9.8/ipc/chromium/src -I/Users/Shared/InterWebSnow-60.9.8/ipc/glue -I/Users/Shared/InterWebSnow-60.9.8/dom/base -I/Users/Shared/InterWebSnow-60.9.8/dom/svg -I/Users/Shared/InterWebSnow-60.9.8/gfx/2d -I/Users/Shared/InterWebSnow-60.9.8/image/decoders -I/Users/Shared/InterWebSnow-60.9.8/layout/svg -I/Users/Shared/InterWebSnow-60.9.8/netwerk/base -I/Users/Shared/InterWebSnow-60.9.8/xpcom/threads -I/Users/Shared/InterWebSnow-60.9.8/gfx/skia -I/Users/Shared/InterWebSnow-60.9.8/gfx/skia/skia/include/config -I/Users/Shared/InterWebSnow-60.9.8/gfx/skia/skia/include/core -I/Users/Shared/InterWebSnow-60.9.8/gfx/skia/skia/include/gpu -I/Users/Shared/InterWebSnow-60.9.8/gfx/skia/skia/include/utils -I/Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/dist/include -I/Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/dist/include/nspr -I/Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/dist/include/nss -fPIC -DMOZILLA_CLIENT -include /Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/mozilla-config.h -MD -MP -MF .deps/Unified_cpp_image0.o.pp -Qunused-arguments -Qunused-arguments -Wall -Wc++11-compat -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wclass-varargs -Wloop-analysis -Wc++11-compat-pedantic -Wc++14-compat -Wc++14-compat-pedantic -Wc++1z-compat -Wimplicit-fallthrough -Wstring-conversion -Wthread-safety -Wno-inline-new-delete -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-unknown-warning-option -Wno-return-type-c-linkage -isysroot /Developer/SDKs/MacOSX10.7.sdk -fno-exceptions -fno-strict-aliasing -stdlib=libc++ -fno-rtti -fno-exceptions -fno-math-errno -pthread -pipe -g -O2 -fomit-frame-pointer -I/Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/dist/include/cairo -Wno-error=shadow /Users/Shared/InterWebSnow-60.9.8/obj-x86_64-apple-darwin10.8.0/image/Unified_cpp_image0.cpp

Ordinarily I’d be sleuthing it solo, but it’s worth mentioning since I’m building on the same Mac, on the same uptime session (58 days and counting), using the same build location (/Users/Shared/), and the same build parameters and toolchain as the 60.9.7 I built a couple of weeks ago. I haven’t updated anything or changed anything from two weeks ago on the macports side.

Just to be sure, I clobbered my old 60.9.7 build from then and began a new build of that. So far, that build is far further along and isn’t throwing up that error or anything unexpected.

Also, these are the .mozconfig settings I’m using (with 60.9.7, with 60.9.8, and so on):

Code:
export HOST_CC=/opt/local/bin/clang-mp-3.7
export HOST_CXX=/opt/local/bin/clang++-mp-3.7
#TARGET_CPU=i386
TARGET_CPU=x86_64
CC="clang -arch $TARGET_CPU"
CXX="clang++ -arch $TARGET_CPU"

# These must be set for cross builds, and don't hurt straight builds.
RANLIB="${TOOLCHAIN_PREFIX}ranlib"
AR="${TOOLCHAIN_PREFIX}ar"
AS=$CC
LD=ld
STRIP="${TOOLCHAIN_PREFIX}strip"
OTOOL="${TOOLCHAIN_PREFIX}otool"
export CC CXX HOST_CC HOST_CXX RANLIB AR AS LD STRIP OTOOL

CROSS_COMPILE=1
ac_add_options --target=x86_64-apple-darwin10.8.0
#ac_add_options --target=i386-apple-darwin10.8.0
ac_add_options --enable-macos-target=10.6
ac_add_options --enable-application=browser
ac_add_options --with-macos-sdk=/Developer/SDKs/MacOSX10.7.sdk
ac_add_options --disable-tests
ac_add_options --enable-optimize=-O2
ac_add_options --disable-debug
ac_add_options --disable-crashreporter
#ac_add_options --disable-updater
ac_add_options --disable-necko-wifi
ac_add_options --disable-safe-browsing
ac_add_options --disable-gamepad

export MOZ_TELEMETRY_REPORTING=0
export MOZ_ADDON_SIGNING=0
export MOZ_REQUIRE_SIGNING=0


And as sort of a P.S. general question: is there any reason why mozcfg-interweb lingers when .mozconfig contains the same build parameters?
 

wicknix

macrumors 68030
Original poster
Jun 4, 2017
2,621
5,304
Wisconsin, USA
Ack. Thanks for pointing that out. I found the cause. I forgot to merge a local file to github. Grab the fixed source here:

I left the extra mozcfg because i use this base for SpiderWeb as well, and that requires changes to .mozconfig and it made it easy to revert back to InterWebs when needed.

I also built a 64-bit build if you don't want to build your own. It is not linked to the snow leopard libs however as i meant it for Lion. Since you have macports installed, you more than likely already have them installed on your system, so not an issue. It's linked in the releases.

Cheers
 
Last edited:
  • Like
Reactions: B S Magnet
Ack. Thanks for pointing that out. I found the cause. I forgot to merge a local file to github. Grab the fixed source here:

I left the extra mozcfg because i use this base for SpiderWeb as well, and that requires changes to .mozconfig and it made it easy to revert back to InterWebs when needed.

I also built a 64-bit build if you don't want to build your own. It is not linked to the snow leopard libs however as i meant it for Lion. Since you have macports installed, you more than likely already have them installed on your system, so not an issue. It's linked in the releases.

Cheers

Thanks for verifying that. I’ll give this a second go. :)

So, just for future reference, the .mozconfig is for use with Spiderweb builds only, whereas the mozcfg-interweb is for Interweb only?

And last bit: I actually enjoy building Interweb locally! It lets me practice and troubleshoot for compiling a software application I use quite a lot (and also put onto Macs I donate for second lives). But it’s also reassuring to know there’s now a 64-bit build for folks who want to run it without the compile step.
 

wicknix

macrumors 68030
Original poster
Jun 4, 2017
2,621
5,304
Wisconsin, USA
The .mozconfig defaults to IW use, but i also use it for SW with some minor changes. Some times i'm lazy and just cp mozcfg-interweb back to .mozconfig when i'm done with SW builds. It's not really meant to confuse anyone. ;)

Edit: If it fails again, download from the link above once again. Sorry. Github can be a PITA at times. I just built from master w/out issue this time.
 
Last edited:
The .mozconfig defaults to IW use, but i also use it for SW with some minor changes. Some times i'm lazy and just cp mozcfg-interweb back to .mozconfig when i'm done with SW builds. It's not really meant to confuse anyone. ;)

So if I’m only building Interweb, I only need to modify .mozconfig to build Interweb to my desired configuration (i.e., 64-bit)… yes?

Edit: If it fails again, download from the link above once again. Sorry. Github can be a PITA at times. I just built from master w/out issue this time.

The InterWeb-master zip you just linked me to is much farther along with this compile, so even if it errors out, it’s already a big step beyond what I was dealing with a couple of hours ago.

Thanks again. :)

1639363368872.png
 
  • Like
Reactions: wicknix
Correct. By default it'll build for 32-bit. No other changes needed otherwise.

I feel like a squeaky wheel (with my own oil can I’m not using),

I’m running into this error late in the build regardless what I try (mainly of switching python39 to python27 and also commenting out the cross_compile flag. It occurs at the “native-overrides-test.xpi”.

To be sure, I re-ran 60.9.7 build from scratch and that did OK, so I’m guessing there’s something here it doesn’t like:

Code:
133:49.94 Exporting extension to unsafe-content-script.xpi.
133:52.56 native-addon-test.xpi
133:52.56 native-overrides-test.xpi
134:08.14 Traceback (most recent call last):
134:08.14   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 174, in _run_module_as_main
134:08.14     "__main__", fname, loader, pkg_name)
134:08.14   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
134:08.14     exec code in run_globals
134:08.14   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/action/jar_maker.py", line 17, in <module>
134:08.14     sys.exit(main(sys.argv[1:]))
134:08.14   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/action/jar_maker.py", line 13, in main
134:08.15     return mozbuild.jar.main(args)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/jar.py", line 597, in main
134:08.15     jm.makeJar(infile, options.d)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/jar.py", line 333, in makeJar
134:08.15     self.processJarSection(info, jardir)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/jar.py", line 388, in processJarSection
134:08.15     self._processEntryLine(e, outHelper, jf)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/jar.py", line 462, in _processEntryLine
134:08.15     pp.do_include(inf)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/preprocessor.py", line 776, in do_include
134:08.15     self.handleLine(l)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/preprocessor.py", line 550, in handleLine
134:08.15     cmd(args)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/preprocessor.py", line 776, in do_include
134:08.15     self.handleLine(l)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/preprocessor.py", line 550, in handleLine
134:08.15     cmd(args)
134:08.15   File "/Users/Shared/InterWebSnow-master/python/mozbuild/mozbuild/preprocessor.py", line 665, in do_endif
134:08.15     self.ifStates.pop()
134:08.15 IndexError: pop from empty list
134:08.16 make[5]: *** [libs] Error 1
134:08.16 make[4]: *** [browser/base/libs] Error 2
134:08.17 make[3]: *** [libs] Error 2
134:08.17 make[2]: *** [default] Error 2
134:08.20 make[1]: *** [realbuild] Error 2
134:08.23 make: *** [build] Error 2
134:08.29 360 compiler warnings present.
134:09.35 Notification center failed: Install terminal-notifier to get a notification when the build finishes.

Does this look familiar by chance?
 

wicknix

macrumors 68030
Original poster
Jun 4, 2017
2,621
5,304
Wisconsin, USA
I get the same error now on a fresh master download. *sigh* Did i mention i hate github at times? My local copy still builds fine, so i guess i have to hunt and peck to see what happened. I really didn't change anything drastic. I guess for now use my prebuilt release until i can figure this out.

Cheers
 
I get the same error now on a fresh master download. *sigh* Did i mention i hate github at times? My local copy still builds fine, so i guess i have to hunt and peck to see what happened. I really didn't change anything drastic. I guess for now use my prebuilt release until i can figure this out.

Cheers

I’ve been running it again, but this time I commented out those two xpis from /addon-sdk/source/test/fixtures/moz.build and I’m waiting to see how (or if) the build will kvetch.

EDIT update: whatever it is, the traceback dump is happening after the last item shown (which means it’s probably something after, if using the above example, native-overrides-test.xpi, which is causing the fatal error). I’m going to chalk this up to github being a pest and, for now, just download the binary you posted for 60.9.8. But if you do update/change the source for 60.9.8, I’ll be sure to give it a go.
 
Last edited:
  • Like
Reactions: wicknix

Snowlover

macrumors 6502
Nov 28, 2018
470
7,855
Alpine , CA
InterWeb-60.9.8 is now available. Changed the about dialog a little, cleaned up help menu entries, and fixed a few gfx bugs.
Download: https://github.com/wicknix/InterWebSnow/releases
Change log: https://github.com/wicknix/InterWebSnow/compare/60.9.7...60.9.8

Cheers and happy holidays.
Can you tell me the correct way to update interweb? I get the download etc, but what about the old version installed? just move it to the trash?
I want to make sure I keep all my bookmarks and extensions.
Thanks.
P.S. Same ? for Arctic Fox
 

wicknix

macrumors 68030
Original poster
Jun 4, 2017
2,621
5,304
Wisconsin, USA
You can just copy over the old version. Your settings are saved seperate of the app in ~/Library/Application Support/

Cheers
 

lerryjee

macrumors newbie
Jan 26, 2022
2
1
Thank you for this great list! Does anyone know of any browsers that can address this issue for me? I use 10.6.8 due to old CS software.

  • Browsers that do not support ECMAScript 6 (such as Internet Explorer 11) are no longer supported for the BLOX CMS admin. For the past several months we've been showing an error message on the BLOX login page for those attempting to log in with IE 11. After this release, their login will be prevented rather than showing an error message. (TNCMS-8096)

With this update yesterday, I can no longer access this website and have to use a separate newer computer in addition to the older 10.6.8 machine, which to say the least is a pain the rear.

Any help would be appreciated on a browser that works on 10.6.8 that supports ES6, or how I can trick this website into thinking one of my browsers does.

Thankyou!




Finding web browsers that are still usable on today’s web can be a chore for older versions of OS X.

The following is a list of known, up-to-date (or relatively up-to-date) and maintained web browsers, e-mail clients, and FTP clients, for Intel Macs with at least Snow Leopard support, then Lion and up.


BROWSERS

Arctic Fox
supports 10.6 through 10.9+

Chromium Legacy
supports 10.7 through 10.9

Firefox Legacy (aka, “Nightly”)
supports 10.6, 10.7, and 10.8

Firefox 78esr
supports 10.9 through 10.15+

iCab 5.9.2
5.9.2 supports 10.9 through 10.15; 5.8.6 supports 10.7 through 10.14

InterWeb
supports 10.6, 10.7, 10.8, and 10.9+

SeaMonkey 2.49.5
supports 10.7, 10.8 and 10.9+

SpiderWeb
supports 10.6, 10.7, 10.8, and 10.9+

TenFourFox Intel FPR32
supports 10.4.3 Intel through 10.14 (i.e., includes all SL-capable Macs)

TenSixFox
supports 10.6 and up

Waterfox Classic
supports 10.7, 10.8, and 10.9+

WhiteStar (forked from Pale Moon)
supports 10.7 through 10.15+


E-MAIL CLIENTS

GyazMail 1.5.21 (32-bit)
supports 10.4.3 through 10.14

GyazMail 1.6.3 (64-bit)
supports 10.6+ 10.9 to 10.15 (developer amended from 10.6+ to 10.12+, but 10.9, in an all-64-bit environment, might work here)

SpiderMail
supports 10.7, 10.8 and 10.9+

Thunderbird 45
supports 10.6, 10.7 and 10.8+

Thunderbird 52 (back-ported)
supports 10.7, 10.8 and 10.9+

Thunderbird 78 ESR
supports 10.9 through 10.15+



FTP CLIENTS

Cyberduck 7.8.5
supports 10.9+

Fetch 5.7.7
supports 10.6+

FileZilla 3.2.7.1
supports 10.5, 10.6+

Transmit 4.4.8
supports 10.5, 10.6+



NOTE: This is a Wiki post, so feel free to add any others to it. Just don't add anything which hasn't been updated in years.
 
Invitation to anyone who wants to double-check this for me:

When browsing to web.archive.org on Interweb, particularly if you’re doing so on an earlier OS like Snow Leopard or maybe Lion, are you finding you’re no longer able to see the input window for searching on an archived web page?

What I’m getting — even with uBlock/uMatrix disabled — is the following, in Snow Leopard:

1646135958758.png


I casually glanced at the same in High Sierra, with Firefox 78 ESR, and the page pulls up as expected. I also tried a few different user agents, but that didn’t seem to impact the outcome.

The change in function/behaviour appears to be fairly recent — possibly within the last couple of weeks.

Cheers.
 
Invitation to anyone who wants to double-check this for me:

When browsing to web.archive.org on Interweb, particularly if you’re doing so on an earlier OS like Snow Leopard or maybe Lion, are you finding you’re no longer able to see the input window for searching on an archived web page?

What I’m getting — even with uBlock/uMatrix disabled — is the following, in Snow Leopard:

View attachment 1966577

I casually glanced at the same in High Sierra, with Firefox 78 ESR, and the page pulls up as expected. I also tried a few different user agents, but that didn’t seem to impact the outcome.

The change in function/behaviour appears to be fairly recent — possibly within the last couple of weeks.

Cheers.

Update:

Checked the same with Nightly 52.9.1p1, ArcticFox 27.11.0, NewMoon 27.9.4 and also TFF FPR32 (the April 2021 build, the last one I’ve installed). Nightly, ArcticFox, and NewMoon echo the same as Interweb’s rendering. TFF FPR32 renders the page correctly.

I’m not sure why, but archive-dot-org definitely changed something in their site code recently.
 

MacBiter

macrumors regular
Jun 2, 2021
248
33
Heads up. I ONLY run Snow Leopard in a Parallels VM, not as a main OS . Few browsers work there - forget Safari, Opera, and Chrome. But even the browsers recommended here, such as Interweb, Snow Monkey, and all those that are based on the same architecture, don't work either; they launch but that's as far as it goes, you can't type in the search or address fields.

Up until now I've made do - successfully - with Arctic Fox (and its sibling TenFourFox works too; both must be built on different architecture than Interweb etc).

However, I've encountered what will seem like a minor irritation to you folks, but disrupts my workflow. I can login to MS OneDrive as ever, but the Upload button has stopped working - you can click it but nothing happens - and restarts/relogging make no difference. It means I can't upload my documents to OneDrive unless I write them to a memory stick and login to OneDrive on Mavericks and upload there, which is a big faff. The weird thing is that all the other buttons work fine, as ever.

Are there any alternatives I haven't considered, or am I stuffed? If only Chromium Legacy worked in 10.6.8....!.
 

wicknix

macrumors 68030
Original poster
Jun 4, 2017
2,621
5,304
Wisconsin, USA
I set up a Linux VM on 10.6 with virtual box. For anal websites i just use current Chromium/Firefox on the VM. I also set up a shared folder that linux can access, so copying files over is a breeze.

Cheers
 
  • Like
Reactions: Amethyst1

MacBiter

macrumors regular
Jun 2, 2021
248
33
I set up a Linux VM on 10.6 with virtual box. For anal websites i just use current Chromium/Firefox on the VM. I also set up a shared folder that linux can access, so copying files over is a breeze.

Cheers
I've never used Linux, but that sounds an interesting idea. You mean I could create a Linux VM via Parallels and it would use current browsers?

Can I a) get a free version of Linux to download, and b) create a VM within Parallels 11 running in Mavericks? If the answer to both is yes, would the Linux OS be in a form that Parallels can recognise, i.e. a kosher installer?.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.