[haiku-development] Re: weird segfault in malloc internals when trying to call fdopen()

> >> FWIW I got emacs to compile and run (in terminal mode).  I
> > > disabled
> >> dumping because I didn't know enough about haiku to make it work.

Btw, this weekend I got XEmacs to build :
http://revolf.free.fr/beos/shots/shot_xemacs_haiku.001.png

some issues to fix though, but it still works fine in ZETA, so those
must be Haiku bugs ;)

> > I'm actually having issues getting it to run in terminal mode. I'm
> > getting an infinite select loop on keyboard input when I run temacs
> > (the
> > undumped emacs). Otherwise it kind of vaguely works. I was actually
> > going
> > to cheat and start working on the GUI mode, though I know nothing
> > about how
> > to do that or really BeAPI.. :) I like shooting blind I guess.

Either it's some bug in select() or there is something missing that
makes select() be called with a file that is always writeable or
readable, thus returning always.
Also, some OSes do update the timeout args, others don't, maybe there
is a define for this around ?

>
> Have to turn off 'INTERRUPT_INPUT' in the system file.  The GUI code
> for each platform looks to be tacked on - a different c layer of
> system related functions for each platform, that are then called from
> platform specific lisp code, which is spread all over the place.  It
> will take quite a lot of learning about the internals to get it to
> work (and explains why e.g. the gtk port took years ...).

Yes if it's like XEmacs the division is not always obvious.

> Ok, diff against 23.1 @ http://users.on.net/notzed/haiku/emacs-23.1-haiku.diff
> >
> Includes src/s/haiku.h and configure.in change, oh, and elf.h from
> glibc since haiku doesn't have one.  Might be incomplete - i didn't
> want to include the new configure autoconf generated.  Once it's
> compiled it'll fail doing a hardlink, i just changed the makefile

It's odd, usually the configure script detects hardlinks and replaces
the command in the Makefile by a cp, you shouldn't have to do this.

> manually to use 'cp' instead of 'ln' at that point.  Because it
> doesn't dump it takes a really long time to compile all the lisp too.
> After make install, It runs but a bunch of stuff doesn't work
> properly, e.g. shell mode resets the environment, and so on.

It's actually intended I think.

> FWIW remote xterms have been broken since xfree86 and then xorg.conf
> keep changing what 'xterm' as a termtype means, so if you're logging
> into a linux box blame that/use a different termtype.

try xterm-color maybe ?

Seems they removed beterm altogether :-(

François.

Other related posts: