[REBOL] REBOL does not work on Debian Linux 2 2 Re:
From: jhagman:infa:abo:fi at: 14-Sep-2000 3:19
Quoting [Terrence_Brannon--Instinet--com] ([Terrence_Brannon--Instinet--com]):
>
> And given that there 25+ Linux distributions out there (and Red Hat
> is not the best, just the most popular --- see linuxcare.com), my
> guess is there are a few more on which it will also dump core.
Actually if your Debian is OK, Rebol does not dump the core. I know I
am running Debian (and my Debian was not OK earlier)
> This "hidden source" model is proving to be frustrating... your
> major competitors (Perl, Python, and Tcl/Tk) dont hide their code
> and yet have managed to be popular products.
Core dump and "hidden source" model don't have anything to do with
eachother.
> I have some serious testing to get done and I cant get it done
> because the REBOL interpreter is dying on the only machine I have
> available for testing.
What does
$ldd ./rebol
produce?
On my system (Debian Woody) the output is following:
libm.so.6 => /lib/libm.so.6 (0x4001f000)
libtermcap.so.2 => /lib/libtermcap.so.2 (0x4003c000)
libc.so.6 => /lib/libc.so.6 (0x4007a000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
If you can see both libc.so.5 and libc.so.6 on output rebol (well
actually libc) crashes. This is just because your system is mixing
different versions of libc and because you probably have old
libtermcap compiled for libc5.
On my system there is no libtermcap installed. I just have made a link
from it to libncurses which is compatible.
To cure your problem you should get rid of the obsolete libtermcap
package (unless you are using some software that depends on it) and
use ncurses instead.
Hopefully this helps, feel free to contact me on or off the list
regarding this matter.
Yours,
Jussi
--
Jussi Hagman CS in Åbo Akademi University
Studentbyn 4 D 33 [juhagman--abo--fi]
20540 Åbo [jhagman--infa--abo--fi]
Finland
