XPost: alt.comp.software.seamonkey

frg <frgrahl@gmx.net> wrote:

Louis Epstein wrote:

I just recently upgraded my FreeBSD from
no-longer-supported 11.x to supported-until-year-after-next
12.x but Seamonkey is refusing to launch with a
"Couldn't load XPCOM" message...I am using an
ad hoc port of 2.53.7 because they stopped maintaining
an official port after 2.49.4 (that port went through
many iterations but they abandoned it out of impatience
for 2.49.5 JUST before 2.49.5 finally came out).
Since I use AdBlockPlus I'm not sure if a later Seamonkey
is compatible on that end (I see 2.53.13 won't use it)
but is there a specific breakage with newer FreeBSDs?

What software is needed to supply XPCOM to Seamonkey
and how can I load it in my FreeBSD 12.3 system?

Usually points to a missing dll. I know that there are later ports available.

FRG

I've been updating my whole tree and nothing has
made Seamonkey stop failing on "Couldn't load XPCOM".

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.software.seamonkey

JKB <JKB@hilbert.invalid> wrote:

Le 04-09-2022, Louis Epstein <le@top.put.com> a ?crit?:

I just recently upgraded my FreeBSD from
no-longer-supported 11.x to supported-until-year-after-next
12.x but Seamonkey is refusing to launch with a
"Couldn't load XPCOM" message...I am using an
ad hoc port of 2.53.7 because they stopped maintaining
an official port after 2.49.4 (that port went through
many iterations but they abandoned it out of impatience
for 2.49.5 JUST before 2.49.5 finally came out).
Since I use AdBlockPlus I'm not sure if a later Seamonkey
is compatible on that end (I see 2.53.13 won't use it)
but is there a specific breakage with newer FreeBSDs?

What software is needed to supply XPCOM to Seamonkey
and how can I load it in my FreeBSD 12.3 system?

I build SM 2.53.* from sources on:

pythagore:[~] > uname -a
FreeBSD pythagore 13.1-RELEASE FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC amd64

Now, I successfully run seamonkey-2.53.13 from
seamonkey-2.53.13.source.tar.xz.

I have built rust from ports (1.61.0) and my .mozconfig contains :

export CC=clang13
export CXX=clang++13
ac_add_options --enable-application=comm/suite
ac_add_options --enable-calendar
ac_add_options --enable-irc
ac_add_options --enable-dominspector
ac_add_options --enable-optimize
ac_add_options --disable-debug

Firefox from pkg runs fine also.

Of course, I only have a 13.1-RELEASE, but I have built without
trouble (and run without issue) Seamonkey on a FreeBSD 12.*.

Best regards,

JKB

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

We've tried various versions of rust.(I note ports/packages now
have 1.63 but "rustup" has 1.64 as its default).

In the meantime both Firefox and Firefox-usr have become broken
because of XPCOM issues as a result of the attempts to get Seamonkey going...XPCOM doesn't load with them either and attempts to deinstall/ reinstall from ports or delete/install with pkg don't produce working
versions.

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.software.seamonkey

Gunther Nikl <gnikl.invalid@justmail.invalid.de> wrote:

Louis Epstein wrote:

Gunther Nikl <gnikl.invalid@justmail.invalid.de> wrote:

Please show the output of "pkg info -d seamonkey" and maybe "pkg info -B >>>>> seamonkey" as well.

In both cases I get
pkg: No package(s) matching seamonkey

This could mean seamonkey was not installed through the port/package
system before and thus survived the upgrade process of the system.

Yes...

Someone found a port elsewhere and installed it for me,
he says he has also rebuilt since we upgraded to 12.x

Ok, then your problem is now solved? Which seamonkey version are you using?

...I was referring to how it was installed back when I got 2.53.7
installed for FreeBSD 11.x (despite it having been dropped from the
Ports Collection just before 2.49.5 was released) and the problem has
NOT been solved for FreeBSD 12.x for me.

Please show the result of:

a) ls -l /usr/local/bin/seamonkey

-rwxr-xr-x 1 root wheel 190888 Sep 2 14:52 /usr/local/bin/seamonkey

I suppose this is the old seamonkey from the 11.x time?

Yes.

On my system the
entry in /usr/local/bin is a symlink to ../lib/seamonkey/seamonkey. The difference might be the result of how the package is built.

Right now he's symlinking that to his home directory's not-working
attempts.

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.software.seamonkey

Louis Epstein wrote:

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

It must support m4, it's part of the autotools and needed to build most anything that uses configure.
SM does need (unless it has changed, haven't built any recent versions) autoconf213 and if he is trying with a recent autoconf, I'd guess weird
errors.
You might need export AUTOCONF=/path/to/autoconf213 or such in your
environment

We've tried various versions of rust.(I note ports/packages now
have 1.63 but "rustup" has 1.64 as its default).

In the meantime both Firefox and Firefox-usr have become broken
because of XPCOM issues as a result of the attempts to get Seamonkey going...XPCOM doesn't load with them either and attempts to deinstall/ reinstall from ports or delete/install with pkg don't produce working versions.

The unable to load XPCOM error is a generic error caused by a missing or
the wrong version of a library.
Are there tools to see what the dependencies of a binary are?
Dave

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 14 Oct 2022 21:39:45 -0700, Dave Yeo wrote:

Louis Epstein wrote:

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

It must support m4, it's part of the autotools and needed to build most anything that uses configure.
SM does need (unless it has changed, haven't built any recent versions) autoconf213 and if he is trying with a recent autoconf, I'd guess weird errors.
You might need export AUTOCONF=/path/to/autoconf213 or such in your environment

m4 is part of the base system. Years ago I used it for sendmail.
Simply try ``man m4´´.

Detlef
--
https://www.12schrittefrei.de/
https://www.noart.de/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.software.seamonkey

In alt.comp.software.seamonkey Dave Yeo <dave.r.yeo@gmail.com> wrote:

Louis Epstein wrote:

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

It must support m4, it's part of the autotools and needed to build most anything that uses configure.
SM does need (unless it has changed, haven't built any recent versions) autoconf213 and if he is trying with a recent autoconf, I'd guess weird errors.
You might need export AUTOCONF=/path/to/autoconf213 or such in your environment

It appears that it is simply not finding /usr/local/share/autoconf2.13/autoconf.m4
which does exist.
Does a more recent autoconf also being in /usr/local/share
confuse things?

We've tried various versions of rust.(I note ports/packages now
have 1.63 but "rustup" has 1.64 as its default).

In the meantime both Firefox and Firefox-usr have become broken
because of XPCOM issues as a result of the attempts to get Seamonkey
going...XPCOM doesn't load with them either and attempts to deinstall/
reinstall from ports or delete/install with pkg don't produce working
versions.

The unable to load XPCOM error is a generic error caused by a missing or
the wrong version of a library.
Are there tools to see what the dependencies of a binary are?
Dave

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

[AIOE didn't allow me to crosspost this to alt.comp.software.seamonkey.]

Louis Epstein wrote:

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

to which Dave Yeo <dave.r.yeo@gmail.com> replied:

It must support m4, it's part of the autotools and needed to build most
anything that uses configure.
SM does need (unless it has changed, haven't built any recent versions)
autoconf213 and if he is trying with a recent autoconf, I'd guess weird
errors.
You might need export AUTOCONF=/path/to/autoconf213 or such in your
environment

Louis Epstein <le@top.put.com> responded:

It appears that it is simply not finding /usr/local/share/autoconf2.13/autoconf.m4
which does exist.

FWIW, on a FreeBSD 13.1 system, I find:

/usr/local/share/autoconf2.71/autoconf/autoconf.m4

so there's an extra "autoconf/" to get to autoconf.m4 compared to
what you have above, but since you say the file exists, maybe
things changed between 2.13 and 2.71.

/usr/local/bin/autoconf is the short POSIX shell script:
----------
#! /bin/sh
${DEFAULT_AUTOCONF:+exec "$0${DEFAULT_AUTOCONF}" "$@"}
c=$(ls -d "$0"[0-9]* 2>/dev/null | sort -Vr | head -n1)
exec "${c:?$0: not installed}" "$@"
----------

That script appears to list the /usr/local/share/autoconf[0-9]*
directories and take the one that sorts the highest. If 2.13
does that, too, then the answer to:

Does a more recent autoconf also being in /usr/local/share
confuse things?

is likely yes. It looks like it would be simple enough to create your
own version of the shell script that avoids the sort and just uses /usr/local/share/autoconf2.13/ .

HTH,
-WBE

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.software.seamonkey

Louis Epstein wrote:

In alt.comp.software.seamonkey Dave Yeo <dave.r.yeo@gmail.com> wrote:

Louis Epstein wrote:

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

It must support m4, it's part of the autotools and needed to build most
anything that uses configure.
SM does need (unless it has changed, haven't built any recent versions)
autoconf213 and if he is trying with a recent autoconf, I'd guess weird
errors.
You might need export AUTOCONF=/path/to/autoconf213 or such in your
environment

It appears that it is simply not finding /usr/local/share/autoconf2.13/autoconf.m4
which does exist.
Does a more recent autoconf also being in /usr/local/share
confuse things?

It appears so. I'm on OS/2, our libc was ported from freebsd to build
Mozilla and autoconf213 likewise. I installed with yum/rpm.
I have /usr/share/autoconf213 which contains all the *.m4 files plus the
other ac* scripts with /usr/bin/autoconf213 having this line about line 38,
: ${AC_MACRODIR="${AC_PREFIX-/@unixroot/usr}/share/autoconf213"}
: ${M4=m4.exe}

note that @unixroot expands to a drive letter here as we're multi-root
Perhaps something similar would support both autoconf's being installed
in /usr/local
Dave

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.software.seamonkey

In comp.unix.bsd.freebsd.misc Dave Yeo <dave.r.yeo@gmail.com> wrote:

Louis Epstein wrote:

In alt.comp.software.seamonkey Dave Yeo <dave.r.yeo@gmail.com> wrote:

Louis Epstein wrote:

I still don't have a working Seamonkey on my FreeBSD 12.3!
The guy who's been trying to build it for me says his most recent
"attempt didn't work because the version of SM uses and[sic]
autoconfig.m4 file, where FreeBSD doesn't support m4."

It must support m4, it's part of the autotools and needed to build most
anything that uses configure.
SM does need (unless it has changed, haven't built any recent versions)
autoconf213 and if he is trying with a recent autoconf, I'd guess weird
errors.
You might need export AUTOCONF=/path/to/autoconf213 or such in your
environment

It appears that it is simply not finding
/usr/local/share/autoconf2.13/autoconf.m4
which does exist.
Does a more recent autoconf also being in /usr/local/share
confuse things?

It appears so. I'm on OS/2, our libc was ported from freebsd to build
Mozilla and autoconf213 likewise. I installed with yum/rpm.
I have /usr/share/autoconf213 which contains all the *.m4 files plus the other ac* scripts with /usr/bin/autoconf213 having this line about line 38,
: ${AC_MACRODIR="${AC_PREFIX-/@unixroot/usr}/share/autoconf213"}
: ${M4=m4.exe}

note that @unixroot expands to a drive letter here as we're multi-root Perhaps something similar would support both autoconf's being installed
in /usr/local

Apparently autoconf.m4f was in a misnamed directory...
I NOW HAVE A WORKING SEAMONKEY 2.53.14 running with my FreeBSD 12.3

BUT...

Firefox won't build properly,won't launch
(there are some sites that work with it and not Seamonkey).

Is anyone else having THAT FreeBSD problem at this time?
(Before it was complaining about rust,now there's a
message about MAKE_JOBS_UNSAFE,but either way it comes
up missing libldap60.so and won't load XPCOM.

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)