Disaster strikes - SeaMonkey removed from ports tree

...Or included a bunch of patches. But I wanted the port to include SeaMonkey "as is", and not something heavy modified; And if the code had to be fixed I first got in touch with the upstream instead of using patches (IMO a patch should only be necessary when the upstream can’t solve it for other reasons - or is unwilling to do so; and if I’m reading the porters handbook that’s how it should be: patches only if FreeBSD specific)...
This is 100% the way things should be. Patches should be hopefully temporary until upstream merges them. Unfortunately many upstreams are mostly dead, or aggressively anti-bsd, so sometimes patches are inevitable.
 
jmos Are you ceasing the maintenance of your unofficial SeaMonkey ports?
I've dropped all my public fun projects (were far too many). As of SeaMonkey: Doesn't compile on FreeBSD 14 [¹], and it's out of my capability to solve that. And unfortunately more and more websites simply saying "use another browser" - nothing more. And I myself am really missing two CSS properties: "gap" on gridded layouts and "aspect-ratio"; Those two makes it unusable for my daily work…

[¹] But the latest 2.53.18 compiles on FreeBSD 13.2, and that binary also works on FreeBSD 14.
 
I've dropped all my public fun projects (were far too many). As of SeaMonkey: Doesn't compile on FreeBSD 14 [¹], and it's out of my capability to solve that. And unfortunately more and more websites simply saying "use another browser" - nothing more. And I myself am really missing two CSS properties: "gap" on gridded layouts and "aspect-ratio"; Those two makes it unusable for my daily work…

[¹] But the latest 2.53.18 compiles on FreeBSD 13.2, and that binary also works on FreeBSD 14.
Unhappy to hear this. The main thing about Seamonkey for me is mail client. There is no much to choose from. But yes, I'm willing to use F13.x (without updating Seamonkey too) as long as possible, because no reason to break what's not broken. Thanks for your port anyway.
 
I can't believe we reached a point where the browser suite (aka Seamonkey) is now faster to start and use than Firefox. It was once the opposite. I recently fired it up on FreeBSD 14.1 (using the 13.2 binary) and was amazed at how fast it started.
 
Just for the record. The official build works in linux emulation.
Having python problems with that. I wonder what's the reason. Pulseaudio?

Code:
 0:07.15 gmake[5]: *** [/root/Downloads/t/seamonkey-2.53.18.2/config/makefiles/rust.mk:241: force-cargo-library-build] Error 101
 0:07.15 gmake[4]: *** [/root/Downloads/t/seamonkey-2.53.18.2/config/recurse.mk:74: toolkit/library/rust/target] Error 2
 0:07.15 gmake[4]: *** Waiting for unfinished jobs....
 0:09.64 1 warning generated.
 0:11.95 1 warning generated.
 0:19.67 gmake[3]: *** [/root/Downloads/t/seamonkey-2.53.18.2/config/recurse.mk:34: compile] Error 2
 0:19.67 gmake[2]: *** [/root/Downloads/t/seamonkey-2.53.18.2/config/rules.mk:361: default] Error 2
 0:19.67 gmake[1]: *** [client.mk:124: build] Error 2
 0:19.67 847 compiler warnings present.
gmake: *** [GNUmakefile:9: build] Error 2
 
I was really surprised of the interaction of SeaMonkey with the ports tree.

Looking at Xorg screen when exiting shows it trying to use stuff from my /usr/ports/www/SeaMonkey directory...

Upon further review I see Firefox looking/errors in the ports directory too. I don't build that.

Moral of the story don't use either program on a machine with a ports tree. They dig into your shizzle.
I am talking a user account mozilla doing this. Am I the only one seeing this on Xorg exit?
These messages don't seem to be logged either.
I have noticed that alot over the years. Maybe the default Xorg logging level does not catch it.
 
Building the latest Seamonkey version (2.53.19) on my 13.4-STABLE system did not go well because rust has dropped support for various features (not to mention for the macOS and Windows 7 and 8.1 platforms).

Code:
8:44.05 error[E0557]: feature has been removed
8:44.05    --> /tmp/seamonkey-2.53.19/third_party/rust/packed_simd/src/lib.rs:218:5
8:44.05     |
8:44.05 218 |     platform_intrinsics,
8:44.05     |     ^^^^^^^^^^^^^^^^^^^ feature has been removed
[...]
8:46.50 BUILDSTATUS BUILD_VERBOSE config/external/icu/common
8:47.21 error[E0703]: invalid ABI: found `platform-intrinsic`
8:47.21  --> /tmp/seamonkey-2.53.19/third_party/rust/packed_simd/src/codegen/llvm.rs:8:8
8:47.21   |
8:47.21 8 | extern "platform-intrinsic" {
8:47.21   |        ^^^^^^^^^^^^^^^^^^^^ invalid ABI
[...]
8:48.36 error[E0635]: unknown feature `stdsimd`
8:48.36    --> /tmp/seamonkey-2.53.19/third_party/rust/packed_simd/src/lib.rs:219:5
8:48.36     |
8:48.36 219 |     stdsimd,
8:48.36     |     ^^^^^^^
8:49.21 error[E0044]: foreign items may not have type parameters
8:49.21  --> /tmp/seamonkey-2.53.19/third_party/rust/packed_simd/src/codegen/llvm.rs:9:5
8:49.21   |
8:49.21 9 |     fn simd_shuffle<T, I, U>(x: T, y: T, idx: I) -> U;
8:49.21   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't have type parameters
8:49.21   |
8:49.21   = help: replace the type parameters with concrete types like `u32`
[Lots more of the same]

The solution was to track down an old version of rust, specifically 1.77.0 (1.81 is current in the ports tree). As it took me quite a while to track down the older version I thought I'd possibly save someone else the hassle - you can find it at in the git repo at https://cgit.freebsd.org/ports/ .

Note: You need to uninstall any later version of rust first - you cannot have two different versions installed at the same time. I built the older rust version in my temp directory and installed it from there.
 
It builds from the official Seamonkey source on FreeBSD 13-STABLE. I've seen reports that it does not build on FreeBSD 14 but noone specified what the problem there was (new version of Rust maybe?).
 
I volunteered years ago to take over this port. I am sorry I did not.

I find running SeaMonkey with Linuxulator quite amazing.

It also shows why I did not take over the SeaMonkey port. I have no idea what I am doing.

This method of installing baffles me. Simply extract archeive and run the execuatble.
Executable is in master directory unlike jmos port where the executable ends up in /usr/local/bin.
.
Those are things I just don't know about. I am sure /bin/ is proper Unix way. I am windows lizzard.
How does the Linux version work without installing any libraries... That is baffling.
I have fought those library conflicts for years everytime I upgrade Firefox it affects my unofficial Seamoney port.
I have SeaMonkey already installed on this machine so I need to test on clean install of Linux version.

Thanks for showing me another way. Very Interesting.

I hate instructional videos but I got to give the man credit. I learned something quite simple right there in front of me.
 
Pretty simple really.
Install and start Linuxator
Download x64 Linux Seamonkey
Unpack to location of your choice.
cd to directory created
run ./seamonkey

I chose /usr/local/etc/seamonkey for installation because I have an older version installed in /usr/local/bin.
Luckily the new version picked up all my settings and bookmarks.

Try and run seamonkey from terminal window command prompt and see what the errorr is.
I tried this method on clean install and it failed due to missing libxul.
So mileage may vary.
 
Pretty simple really.
Install and start Linuxator
Download x64 Linux Seamonkey
Unpack to location of your choice.
cd to directory created
run ./seamonkey

I chose /usr/local/etc/seamonkey for installation because I have an older version installed in /usr/local/bin.
Luckily the new version picked up all my settings and bookmarks.

Try and run seamonkey from terminal window command prompt and see what the errorr is.
I tried this method on clean install and it failed due to missing libxul.
So mileage may vary.
Thanks for your help.
I downloaded the whole rocky linux userspace and followed the rest of your instructions but it hangs when i try to launch with no error messages or any terminal output. I installed Chrome and Brave in a linux jail and those launch fine. I can't run seamonkey within/out a jail.
I am using 14.2 on a T450 Thinkpad.
 
Back
Top