all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: fqgouvea@colby.edu, bug-gnu-emacs@gnu.org
Subject: Re: compiling on Sun Blade 100 running Solaris 2.8
Date: Mon, 15 Jul 2002 07:46:27 +0300 (IDT)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020715074514.4715A-100000@is> (raw)
In-Reply-To: <200207141522.g6EFME720454@aztec.santafe.edu>


On Sun, 14 Jul 2002, Richard Stallman wrote:

>     gcc -c   -I/usr/openwin/include  -I/usr/dt/include   -g -O2  -DEMACS_BITMAP_FILES -DHAVE_CONFIG_H -Demacs  -I. -I../src -I/usr/local/src/gnu/emacs-21.2/lwlib -I /usr/local/src/gnu/emacs-21.2/lwlib/../src xlwmenu.c
>     In file included from /usr/openwin/include/X11/Xos.h:81,
> 		     from xlwmenu.c:32:
>     /usr/include/strings.h:25: conflicting types for `memmove'
>     /usr/include/iso/string_iso.h:62: previous declaration of `memmove'
>     /usr/include/strings.h:26: parse error before numeric constant
> 
> The only way to fix this is for someone to look at the specifics of
> the code and find the actual cause of the problem.  What are these
> conflicting declarations?  Why do they conflict?  Why are both
> eof them included?  Were any macro definitions involved in causing
> the conflict?

I think we already have that fixed in both CVS head and branch.  IIRC, I 
sent a patch in response to the original report, but got no replies.

  reply	other threads:[~2002-07-15  4:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 17:26 compiling on Sun Blade 100 running Solaris 2.8 "Root at morse"
2002-07-10  5:03 ` Eli Zaretskii
2002-07-14 15:22 ` Richard Stallman
2002-07-15  4:46   ` Eli Zaretskii [this message]
2002-07-15 18:47     ` T.L.Bowers
2002-07-16 12:39       ` T.L.Bowers
2002-07-16 12:39       ` T.L.Bowers
2002-07-16 12:39       ` T.L.Bowers

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

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

  git send-email \
    --in-reply-to=Pine.SUN.3.91.1020715074514.4715A-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=fqgouvea@colby.edu \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.