unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Richard Lloyd <richard.lloyd@connectinternetsolutions.com>
Cc: 86@emacsbugs.donarmstrong.com
Subject: bug#86: HP-UX 11.X build/runtime issues for emacs 22.2
Date: Fri, 25 Jul 2008 14:20:07 -0400	[thread overview]
Message-ID: <8763qtzuzs.fsf@stupidchicken.com> (raw)

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
problem.

> 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?

Thanks.






             reply	other threads:[~2008-07-25 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 18:20 Chong Yidong [this message]
2011-03-10  6:52 ` bug#86: HP-UX 11.X build/runtime issues for emacs 22.2 Glenn Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8763qtzuzs.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=86@emacsbugs.donarmstrong.com \
    --cc=richard.lloyd@connectinternetsolutions.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).