Pale Moon 29.0.1
Moderator: dbsoft
Forum rules
Important note:
The old Mac OS versions of Pale Moon were provided by various people and not official or in any way organized. Please make sure you check the date of topic threads to know if the topic is current or relevant! We are using this board for both old discussions and new development of Pale Moon on Mac.
Any specific bugs you find that don't have their own topic yet: please make a new topic; one bug per topic please to keep things organized.
Important note:
The old Mac OS versions of Pale Moon were provided by various people and not official or in any way organized. Please make sure you check the date of topic threads to know if the topic is current or relevant! We are using this board for both old discussions and new development of Pale Moon on Mac.
Any specific bugs you find that don't have their own topic yet: please make a new topic; one bug per topic please to keep things organized.
Pale Moon 29.0.1
Download SHA256 1f0bde837852ecd844dcebc4da859c7a8fe5e5115df6067e31b87b91adfaa89f
Release Notes
Source
Enjoy
Brian
Release Notes
Source
Enjoy
Brian
-
- Astronaut
- Posts: 556
- Joined: 2018-04-20, 20:31
Re: Pale Moon 29.0.1
Works fine.
Even a little snappier, though that sometimes happens when I upgrade to any new version (guess it refreshes something).
Even a little snappier, though that sometimes happens when I upgrade to any new version (guess it refreshes something).
Re: Pale Moon 29.0.1
This version seems to work exceptionally well for my legacy xulrunner application on modern MacOS OSses! Could you perhaps share your mozconfig and used SDK versions and such?
Re: Pale Moon 29.0.1
The following web site has the build information:
http://developer.palemoon.org/build/mac/
For the specifics of my build environment, I am building on a MacPro1,1 running MacOS 10.11 El Capitan with XCode 8.2.1 and the 10.7 SDK recommended on the build page.
Re: Pale Moon 29.0.1
I actually followed this guide installing a fresh MacOS VM using MacOSX10.11 and the mentioned versions of the required tooling (including the 10.7 SDK and xcode 8.2.1) and the provided mozconf file. I dont get past this linker error:
0:05.08 configure: error: compiler is incompatible with sanitize options
0:05.08 DEBUG: <truncated - see config.log for full output>
0:05.08 DEBUG: ^
0:05.08 DEBUG: 1 error generated.
0:05.08 DEBUG: configure: failed program was:
0:05.08 DEBUG: #line 4432 "configure"
0:05.08 DEBUG: #include "confdefs.h"
0:05.08 DEBUG:
0:05.08 DEBUG: int main() {
0:05.08 DEBUG: return sizeof(__thumb2__);
0:05.08 DEBUG: ; return 0; }
0:05.08 DEBUG: configure:5112: /usr/bin/clang -std=gnu99 -o conftest -isysroot /Users/tom/MacOSX-SDKs-master/MacOSX10.7.sdk -Qunused-arguments conftest.c 1>&5
0:05.08 DEBUG: ld: library not found for -lcrt1.10.6.o
0:05.08 DEBUG: clang: error: linker command failed with exit code 1 (use -v to see invocation)
0:05.08 DEBUG: configure: failed program was:
0:05.08 DEBUG: #line 5105 "configure"
0:05.08 DEBUG: #include "confdefs.h"
0:05.08 DEBUG:
0:05.08 DEBUG: int main() {
0:05.08 DEBUG:
0:05.08 DEBUG: ; return 0; }
0:05.08 DEBUG: configure: error: compiler is incompatible with sanitize options
0:05.08 ERROR: old-configure failed
0:05.08 configure: error: compiler is incompatible with sanitize options
0:05.08 DEBUG: <truncated - see config.log for full output>
0:05.08 DEBUG: ^
0:05.08 DEBUG: 1 error generated.
0:05.08 DEBUG: configure: failed program was:
0:05.08 DEBUG: #line 4432 "configure"
0:05.08 DEBUG: #include "confdefs.h"
0:05.08 DEBUG:
0:05.08 DEBUG: int main() {
0:05.08 DEBUG: return sizeof(__thumb2__);
0:05.08 DEBUG: ; return 0; }
0:05.08 DEBUG: configure:5112: /usr/bin/clang -std=gnu99 -o conftest -isysroot /Users/tom/MacOSX-SDKs-master/MacOSX10.7.sdk -Qunused-arguments conftest.c 1>&5
0:05.08 DEBUG: ld: library not found for -lcrt1.10.6.o
0:05.08 DEBUG: clang: error: linker command failed with exit code 1 (use -v to see invocation)
0:05.08 DEBUG: configure: failed program was:
0:05.08 DEBUG: #line 5105 "configure"
0:05.08 DEBUG: #include "confdefs.h"
0:05.08 DEBUG:
0:05.08 DEBUG: int main() {
0:05.08 DEBUG:
0:05.08 DEBUG: ; return 0; }
0:05.08 DEBUG: configure: error: compiler is incompatible with sanitize options
0:05.08 ERROR: old-configure failed
Re: Pale Moon 29.0.1
Why aren't you just using the binary that is already built?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Pale Moon 29.0.1
Good question . Because I essentially need xulrunner, or (at least) as custom palemoon build that behaves more like xulrunner, by launching a custom app by-default, instead of the browser. Of course this can be achieved by using command line switches, but that is not really suitable for end users.
Re: Pale Moon 29.0.1
Oh actually... I think I remember this... search your SDKs for that crt1.10.6.o it should be in one of the SDK folders... put it in the 10.7 SDK. If you can't find it I'll send it to you.
Original-MacPro:Pale-Moon nuke$ locate crt1.10.6
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/crt1.10.6.o
Not sure why it is missing from the SDKs on github.
Re: Pale Moon 29.0.1
Would you please add the
"ui.use_standins_for_native_colors"
value to prefs.js to completely fix the "white text on white background problem" on newer macOS versions for the next build? (It fixes it completely in Firefox Developer edition)
Right now turning off "ui.use_native_colors" works but messes up different things as well (like autofill previews).
"ui.use_standins_for_native_colors"
value to prefs.js to completely fix the "white text on white background problem" on newer macOS versions for the next build? (It fixes it completely in Firefox Developer edition)
Right now turning off "ui.use_native_colors" works but messes up different things as well (like autofill previews).
Re: Pale Moon 29.0.1
Before you go off on a wild goose chase: "use_standins_for_native_colors" is a Tor browser consideration (to hide real theme colors from being requested as an identifier). We don't have it nor want it.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Pale Moon 29.0.1
I already had PM on my mac +/- 5 years ago, but then there were still some bugs, especially in the menu bar.
Rediscovered a few weeks ago and very satisfied.
This new version works well on High Sierra.
This will have been a lot of work, thank you !!!!!!
Rediscovered a few weeks ago and very satisfied.
This new version works well on High Sierra.
This will have been a lot of work, thank you !!!!!!
Re: Pale Moon 29.0.1
Hopefully we'll see a 29.1 binary show up soon.
I was building releases for Mac OS X a couple years ago.
If one were to build it from source,
after syncing the source code,
It was NOT the easiest code to get to compile.
- Are the any specific configuration/build requirements to get it to build?
I had a wide range of toolkits installed from macports, mixed w/ Apple's SDK
- gcc vs clang / llvm ??
- make vs gmake,??
- apple SDK version 10-9-10.15, 10.6-11.X.... etc??
If I remember correctly it took me quiet awhile to find the right combination to get it to build.
-- At the time I was building from Sierra or Yosemite,
I believe using 10.9 SDK in Yosemite.
-- -- (And trying for that compatibility from Sierra (This was 2-3 years ago)).
Well, if I get some free-time again,
-- a frame of reference to what's actually getting it built would help greatly....
I would try for a more modern optimized build.
I was building releases for Mac OS X a couple years ago.
If one were to build it from source,
after syncing the source code,
It was NOT the easiest code to get to compile.
- Are the any specific configuration/build requirements to get it to build?
I had a wide range of toolkits installed from macports, mixed w/ Apple's SDK
- gcc vs clang / llvm ??
- make vs gmake,??
- apple SDK version 10-9-10.15, 10.6-11.X.... etc??
If I remember correctly it took me quiet awhile to find the right combination to get it to build.
-- At the time I was building from Sierra or Yosemite,
I believe using 10.9 SDK in Yosemite.
-- -- (And trying for that compatibility from Sierra (This was 2-3 years ago)).
Well, if I get some free-time again,
-- a frame of reference to what's actually getting it built would help greatly....
I would try for a more modern optimized build.