From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Subject: Re: linux compile fails on sys_error / stdio.h incompatible
Date: 09 May 2003 17:10:00 +0200 [thread overview]
Message-ID: <m3vfwk2m2f.fsf@cicero.benny.turtle-trading.net> (raw)
In-Reply-To: mailman.5777.1052414811.21513.help-gnu-emacs@gnu.org
Hi Maureen,
"Maureen Woodyard" <mew@azulsystems.com> writes:
> The problem appears to be the stdio.h in /usr/include defines
> strerror differently from movemail.c. If I compile without movemail,
> it just fails with a similar error on emacsclient.
My point is that neither movemail nor emacsclient should define
strerror() at all. It is part of the runtime library and there is no
reason to replace it. Which is probably why these definitions don't
fit with the runtime definitions, they were never intended to do that.
Both definitions of the function in movemail.c and in emacsclient.c
are surrounded by "#ifndef HAVE_STRERROR". This define should be set
by the configure script on Linux when it finds the function in the
compiler runtime.
You need to find out, why this doesn't work in your setup, e.g. by
looking at config.log. You may also be able just to set the define
yourself in some option to temporarily get around this, but that
wouldn't get at the root of the problem.
I wrote befiore:
> b) Investigate why configure doesn't find strerror() in the
> system headers. It does on my machine here, as it should and
> if it finds that, it shouldn't try to use it's own version. I
> admit my machine is linux-ppc, not i386.
Hope this helps, benny
next parent reply other threads:[~2003-05-09 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5777.1052414811.21513.help-gnu-emacs@gnu.org>
2003-05-09 15:10 ` Benjamin Riefenstahl [this message]
2003-05-08 17:21 linux compile fails on sys_error / stdio.h incompatible Maureen Woodyard
[not found] <mailman.5736.1052367227.21513.help-gnu-emacs@gnu.org>
2003-05-08 12:21 ` Benjamin Riefenstahl
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 4:09 Maureen
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=m3vfwk2m2f.fsf@cicero.benny.turtle-trading.net \
--to=benjamin.riefenstahl@epost.de \
/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.
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).