[Bug 191899] [MAINTAINER] lang/sml-nj-devel: update to 110.76, unbreak, pkgngify, stagify, +amd64, -gmake

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191899

joemann at beefree.free.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Affects Only Me             |Affects Some People

--- Comment #2 from joemann at beefree.free.de ---
(In reply to Timothy Beyer from comment #1)
> I don't know if this helps, but I have gotten SML/NJ to run inside of
> a 32-bit jail on amd64:

Thanks for your report. But before I'll try to come up with a more
detailed response, could you consider the following questions:
- Did you take an smlnj-devel-110.71.t?z binary package created on an
  i386 machine and installed or unpacked that (in a (32-bit-)jail) on
  amd64?
- Which version(s) of FreeBSD run(s) on the amd64 machine(s) you're
  using?

> 1) I modified the PREFIX in multiexec-wrapper to something along the
> lines of /usr/jails/[name_of_jail]/usr/local

Sounds like this multiexec-wrapper is installed on the host system, and
not in the jail. But "jail" implies "chroot", and so in order to start
sml *within* the (32-bit-)jail the multiexec-wrapper itself should live
in /usr/jails/[name_of_jail]/usr/local and it's PREFIX setting inside
should be /usr/local. Then it would be able to do its job after you
jail(8) or chroot(8) to /usr/jails/[name_of_jail]. Or do I miss
something? (Maybe I don't fully understand your setup.)

> [...]
> Probably this won't help much, since the development version is
> probably different, but it works with version 110.71 at least.

It would be very helpful if you could test the patch in this PR
(apply it against the current state of ports/lang/sml-nj-devel).
That would be helpful for this PR and (more importantly:) for you,
as it should make your workaround on amd64 obsolete:-)

Using the patched version of the port I could build sml-nj-devel
directly from source on amd64, and run sml and also math/isabelle on
top of it. This requires the toolchain to understand the "-m 32"
options and the presence of /usr/lib32. Both should be fairly
standard I think ... here's the mileage from the jail on amd64 within
which I developed and tested the patch:

root at zzz:~ # uname -srm
FreeBSD 9.2-STABLE amd64
root at zzz:~ # sysctl security.jail.jailed
security.jail.jailed: 1
root at zzz:~ # pkg info -x sml
smlnj-devel-110.76
root at zzz:~ # ldd /usr/local/smlnj/bin/.run/run.x86-freebsd
/usr/local/smlnj/bin/.run/run.x86-freebsd:
    libm.so.5 => /usr/lib32/libm.so.5 (0x28081000)
    libc.so.7 => /usr/lib32/libc.so.7 (0x2809b000)

Thanx!
Johannes

ps The "-devel" in "sml-nj-devel" is mainly historic - 110.76 is
  the current "official" version from the SML/NJ project.)

-- 
You are receiving this mail because:
You are the assignee for the bug.