Re: [dylan] FreeBSD support

Hannes Mehnert <[email protected]> Thu, 09 Jan 2014 11:34:16 +0000
Newsgroups gmane.comp.lang.dylan.gwydion.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi,

On 01/09/2014 08:53, Bruce Mitchener wrote:
> How good is our FreeBSD support really?

I use it. Works fine for me (on 64bit, FreeBSD-CURRENT).

> I'm on a 64 bit FreeBSD 9.2. I've noticed that our build machine is
> on 8.2 (32 bit), but I thought that hannes had said that he'd used
> the 32 bit compiler to get a working 64 bit compiler ...
> 
> I can't seem to get any of these to generate a working build of
> anything:
> 
> * Using the FreeBSD port to install 2013.2

This results for me in a shell script /usr/local/bin/dylan-compiler,
which does:
export LD_LIBRARY_PATH="/usr/local/lib/opendylan/lib"
exec /usr/local/lib/opendylan/bin/dylan-compiler "$@"

I also run make 3-stage-bootstrap (with some magic to configure to
find the path to boehm-gc; using a git checkout from 20th December,
698edf9810a437505d7ec85a7736691a3291c74a), resulting in a
/usr/local/opendylan-2013.2/bin/dylan-compiler:
/usr/local/opendylan-2013.2/bin/dylan-compiler: ELF 64-bit LSB
executable, x86-64, version 1 (FreeBSD), dynamically linked (uses
shared libs), for FreeBSD 11.0 (1100002), not stripped


> Using the FreeBSD port results in a build error as it can't find
> run-time.h and it has some other stuff going on that I'm not sure
> about. (A path from housel's machine for MPS, etc.)  Has anyone
> successfully used the FreeBSD port to install? Should the result
> work at all on 64 bit FreeBSD?

It does work for me fine on 64 bit.

> Using a compiler in /opt results in whatever I build getting an
> error in stream-position-setter when it does I/O and then it prints
> that "Error may not return". It is printing stack traces which
> seems to indicate that SIGTRAP got hit (and that walkstack() is
> happening). But it doesn't stop there and it keeps on erroring and
> printing stack traces.
> 
> I noticed that the SIGTRAP handler on FreeBSD doesn't try to chain
> the next sigaction like it does on Linux. Is that an issue?

I think this was the case for 2013.1, but is no longer in newer versions.

> I wanted to test some changes on FreeBSD and also need to generate
> a new HARP runtime object file ... but that's proving difficult.

Haven't actively used the HARP backend since a while on FreeBSD (and
not 32 bit at all)..


Cheers,

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJSzok3AAoJELyJZYjffCjuRGoP/jz2aV10Q3EtFmkwUWYfRI2i
en7s3AsneNnWIb0+hRWmucPRGIBsDS/qUUo8aRuN5Tz0YTUvSNc4zXoY4NnO4d8j
s8U5mQlQM4mrOWM/UR8VnjxZyL5qJQeYY+1FkfJakWGH96QpEi30Q73DxgjJdBH9
Skdt5dRbzu2zSv6t/N4V+35Qm3IO6WxS9Tcl78ueyEOPSkBqBdPBV071mNVlzbjM
7qbdswe8YFGjAIxVjZCngjP+kSN8wp+qdwhz0SeSSKj51JM4H+LEnt27H3Ljlh2d
ZcCZ/8rDXk8BUsoTSJduyMI9z4x/2Cn/5m5Dw9uPgFLIJQgg/imA1j7aonOt88Ak
RNYUSwMGi+yZMqxFbeB4nIIGMU97MqBaoa6aGJXiI5bxh/bZiEvCxFSIMGVOAtXa
BAwtGVM16bNlX1G+dGf/Fer9aYnIYABw1tjq1iEph6RxQ1xOiQjT41GegGDhPdYR
NebVpUK25l/VPIPnD3aAIbjZBfx7BeGxBeSf1xz3Xj/cWCBqHER4pl82o5EalJ4N
VPsKjV4poA6xexOIIr46c4uxHDRe8QgQFF8PfrDrdF1tspoz1Cb+0PIK/XpKpmu+
FxOK3Q1A2RDG1YZ5ct45FQk1AkW5PHX/yqJ2L8MrnE6+aUPUbc/eeBB1IuKSq5fm
XlTqAU74QshYOY9VHtP7
=Zynt
-----END PGP SIGNATURE-----
_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers