[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#86: HP-UX 11.X build/runtime issues for emacs 22.2

From: Chong Yidong
Subject: bug#86: HP-UX 11.X build/runtime issues for emacs 22.2
Date: Fri, 25 Jul 2008 14:20:07 -0400

Thanks for your bug reports.

> the configure script never tests for getrlimit() and hence config.h
> never has any HAVE_GETRLIMIT definition.

Thanks.  I've added a check for getrlimit to the configure script.

>  Sadly, similar code to the assignment above is present in src/alloc.c,
>  namely at line 278:
>  POINTER new = (*real_morecore)(0);
>  This again can cause an HP-UX core dump, but this time there is no
>  getrlimit() alternative code - maybe there should be to fix this
>  issue (I wonder if HP-UX isn't the only platform with this problem)?

I can't find this line in the sources.  Could you be more specific about
this problem?

> src/getloadavg.c declares an "nl" struct nlist array at line 493.
> Unfortunately, this clashes directly with ncurses 5.6's "nl" variable
> in ncurses.h [line 686: extern NCURSES_EXPORT(int) nl (void); ]

Okay, I've renamed it to name_list.  Hopefully that will solve the

> src/tparam.c declares a tparam() function at line 95 onwards. This is
> a function also declared by the termcap 1.3.1's termcap.h file (line
> 33), so I would suggest renaming all occurrences of tparam() in
> src/term.c, src/terminfo.c and src/tparam.c to emacs_tparam() instead.

Does this actually stop compilation?

> src/term.c has uninitialised static char * variables at lines 2179 to
> 2181.  If you look at the tty_default_color_capabilities() function
> directly below, you'll see statements that read those vars (lines
> 2192, 2196 and 2201), potentially without assigning to them first.

Fixed, thanks.

These changes will appear in Emacs 22.3, as well as the forthcoming
Emacs 23.1 release.

One additional request: since you have access to HP-UX, could you try
compiling the Emacs CVS trunk (which will become Emacs 23), and report
any problem you encounter?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]